Prerequisites

 

For the latest information about the prerequisites for WebSphere MQ Java, see the WebSphere MQ README file.

To develop WebSphere MQ Java applications, we need a Java™ 2 Software Development Kit (SDK).

To run WebSphere MQ Java applications, we need the following software components:

• A WebSphere MQ queue manager, for applications that connect to a queue manager

• One of the following publish/subscribe brokers, for publish/subscribe applications:

  • WebSphere MQ Publish/Subscribe

  • WebSphere MQ Integrator, V2

  • WebSphere MQ Event Broker, V2.1

  • WebSphere Business Integration Event Broker, V5.0

  • WebSphere Business Integration Message Broker, V5.0

• A Java Runtime Environment (JRE), for each system on which you run applications

• For i5/OS, QShell, which is option 30 of the operating system

• For z/OS, UNIX System Services (USS)

To determine the supported Java 2 SDKs for your platform, see www.ibm.com/software/integration/websphere/mqplatforms/supported.html . The supported JREs are those JREs that are embedded in the supported Java 2 SDKs.

To support Secure Sockets Layer (SSL) authentication fully, we need a JRE at V1.4.2 for your platform. A WebSphere MQ Java application can use SSL to obtain a secure connection to a queue manager, with authentication, message integrity, and data encryption.

If you require SSL connections to use cryptographic modules that have been FIPS 140-2 certified, we need the IBM Java JSSE FIPS provider (IBMJSSEFIPS). Every IBM Java 2 SDK and JRE at V1.4.2 contains IBMJSSEFIPS.

We can use Internet Protocol V6 (IPv6) addresses in your WebSphere MQ Java applications provided IPv6 addresses are supported by your Java virtual machine (JVM) and the TCP/IP implementation on your operating system. The WebSphere MQ JMS administration tool (see Using the WebSphere MQ JMS administration tool) also accepts IPv6 addresses.

To use the WebSphere MQ JMS administration tool, we need one of the following service provider packages, supplied with WebSphere MQ:

• Lightweight Directory Access Protocol (LDAP) - ldap.jar, providerutil.jar.

• File system - fscontext.jar, providerutil.jar.

These packages provide the Java Naming and Directory Service (JNDI) service. This is the resource that stores physical representations of the administered objects. Users of WebSphere MQ JMS probably use an LDAP server for this purpose, but the tool also supports the use of the file system context service provider. If you use an LDAP server, configure it to store JMS objects. For information to assist with this configuration, see the documentation for your LDAP server.

To use the XOpen/XA facilities of WebSphere MQ JMS on i5/OS you need a specific PTF. See the WebSphere MQ README file for further information.

uj10290_