The WebSphere MQ Automation Classes provide full access to all the functions of the WebSphere MQ API, so you can benefit from all the advantages that using WebSphere MQ can bring to your Windows application. The overall design of your application will be the same as for any WebSphere MQ application, so you should first consider all of the design aspects described in the WebSphere MQ Application Programming Guide.
To use the WebSphere MQ Automation Classes, you code the Windows programs in your application using a language that supports the creation and use of COM objects; for example, Visual Basic, Java, and other ActiveX scripting clients. The classes can then be easily integrated into your application because the WebSphere MQ objects you need can be coded using the native syntax of the implementation language.
When designing an ActiveX application that uses WebSphere MQ Automation Classes for ActiveX, the most important item of information is the message that is sent or received from the remote WebSphere MQ system. Therefore you must know the format of the items that are inserted into the message. For an MQAX script to a work, both it and the WebSphere MQ application that picks up or sends the message must know the message structure.
If you are sending a message with an MQAX application and you want to perform data conversion at the MQAX end, you must also know:
To help you keep your code portable it is always good practice to set the code page and encoding, even if these are currently the same in both the sending and receiving systems.
When considering how to structure the implementation of the system you design, remember that your MQAX scripts run on the same machine as the one on which you have either the WebSphere MQ queue manager or the WebSphere MQ client installed.