Using WebSphere MQ Automation Classes for ActiveX

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 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, also know:

• The code page used by the remote system

• The encoding used by the remote system

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.