Checking optional software

 

Check through this topic to identify which additional software is supported for use with WebSphere MQ.

 

Compilers

The following compilers are supported for WebSphere MQ for AIX applications:

C/C++

COBOL

Java™

These Java SDKs are supplied with WebSphere MQ, and can be installed during the installation process described in this document.

 

Transaction monitors

The following transaction processing monitors (coordination through X/Open XA interface) are supported for use with the Extended Transactional Client:

WebSphere MQ for AIX, V6.0 supports WebSphere Application Server as an XA coordinator. For more information about the WebSphere MQ application adaptor, see the WebSphere Application Server Enterprise Edition WebSphere MQ Application Adaptor Development Guide, SC09-4444.

 

Java Messaging and SOAP transport

If you want to use Java Messaging and SOAP (Simple Object Access Protocol) Support, we need a Java Runtime Environment V1.4.2 or later. An appropriate runtime environment is provided in the JDKs provided on the WebSphere MQ Server CD- ROM. These JDK packages can be selected for install during the installation procedure described in this book, see WebSphere MQ Components for package information.

The JDKs available on the server CD-ROM are:

These JDKs provide support for SOAP and are FIPS 140-2 compliant.

Note that to use the JDK shipped with WebSphere MQ for AIX, V6.0, the fileset Java14.ext.java3d 1.4.2.0 requires the following fileset updates:

An error message will be displayed when you install the JDK if you do not have these updates.

Note also that, by default, the IBM Software Developer's Kit (SDK) for AIX, Java 2 Technology Edition for AIX, V1.4.2, 64-bit uses the IPv6 extensions to the TCP/IP protocol.

On AIX Version 5.2, if your applications uses multicast sockets, or explicitly uses IPv6 format addresses, configure the network interfaces on your system to work with IPv6 addresses. The network interfaces can be configured to work with IPv6 using the System Management Interface Tool (smitty), or by using the autoconf6, or ifconfig commands.

Alternatively, if you do not want to use IPv6 protocols, we can force the use of IPv4 protocols by setting the java.net.preferIPv4Stack property of your class file to true using the following command: 

java -Djava.net.preferIPv4Stack=true <classname>
Where <classname> is the name of your .class file.

For a list of alternative JDKs, see

www.ibm.com/software/integration/websphere/mqplatforms/supported.html

For WebSphere MQ V6.0 Java scripts to function properly a number of environment variables must be set. For information on setting these environment variables and general information about using Java with WebSphere MQ see, Using Java.

For further information about SOAP see, WebSphere MQ Transport For SOAP book.

If you use a JDK other than the one supplied by WebSphere MQ V6.0 you should be aware that:

 

Secure Sockets Level (SSL)

If you want to use the SSL support, we need IBM Global Security Kit V7. This is supplied with WebSphere MQ as one of the components available for installation. If you are migrating from WebSphere MQ V5.3 and have no other requirement for the IBM Global Security Kit V6, we can uninstall it using the process described in Uninstalling WebSphere MQ, the package name is gskak.rte.

You must also have installed version 6.0.0.2 (or later) of the C++ runtime to use the SSL support.

 

Parent topic:

Checking hardware and software requirements


aq10550_