Checking optional software - PA-RISC platform

 

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 HP-UX applications:

C/C++

• HP C/ANSI C Developer's Bundle for HP-UX 11.0 and 11i Version 1

• HP aC++ VA.03.52 for HP-UX 11.0 and 11i V1 (A.03.52 available as patch PHSS_29483)

COBOL

• Micro Focus Server Express V4.0

Java™

• HP-UX Software Development Kit for the Java 2 Platform, V1.4.2

This product is supplied with WebSphere MQ, and can be installed during the installation process described in this document.

 

Databases

The following databases are supported:

• DB2 Universal Database™ V8.2

• Informix Dynamic Server (IDS) V9.40 plus Client SDK V2.90

• Informix Dynamic Server (IDS) V10

• Oracle 9i Release 2 with Patch Set 4 (9.2.0.5) plus patch 3501955

• Oracle 10g

• Sybase Adaptive Server Enterprise (ASE) 12.5.3 ESD#1 plus Sybase SDK 12.5.1 ESD#7

 

Transaction monitors

The following transaction processing monitors (coordination through X/Open XA interface) are supported:

• BEA Tuxedo V8.1

• IBM WebSphere Application Server (WAS) V5.1

• IBM WebSphere Application Server (WAS) V6.0.2 plus IBM WebSphere MQ V6.0 Fix Pack 1 (CSD01).

• IBM TXSeries for HP-UX V5.1

• BEA WebLogic V8.1 plus SP4

WebSphere MQ for HP-UX, V6.0 supports WebSphere Application Server as an XA coordinator. For more information about the WebSphere MQ application adaptor, see the WebSphere Application Server documentation.

 

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 JDK provided on the WebSphere MQ Server CD-ROM. This JDK package can be selected for install during the installation procedure described in this book, see WebSphere MQ Components for package information.

The JDK available on the server CD-ROM is:

• HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.2

This JDK provides support for SOAP and are FIPS 140-2 compliant.

For a list of alternative JDKs, see:

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

For further information about using Java with WebSphere MQ see, WebSphere MQ Using Java.

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

If your JDK has not been supplied by IBM you should be aware that:

• The JDK may not be FIPS level 140-2 compliant and by using it with WebSphere MQ, will not comply the FIPS 140-2 standards.

• SOAP is not supported.

On HP-UX, the 32-bit and 64-bit JDKs are typically installed to the same directory /opt/mqm/java/sdk/bin. To run a 64-bit or 32-bit JVM use the -d64 or -d32 parameters on the command line when running a Java application to ensure the correct JVM is used.

 

Secure Sockets Level (SSL)

If you want to use the SSL support with WebSphere MQ for HP-UX, we need to install the IBM Global Security Kit (GSKit) V7 package: gsk7bas64. 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 gsk6bas.

To use SSL, WebSphere MQ clients on HP-UX 11i v1 and HP-UX 11i v2 must be built:

• Using the C++ compiler (not the C compiler)

• Using POSIX threads

• With the compiler options: -W1,+b/opt/ibm/gsk7/lib:/opt/mqm/lib

Note that if you are using SSL with 32-bit WebSphere MQ clients on HP-UX 11i v1, the cryptography included in the 32-bit GSKit is not FIPS 140-2 certified. The 32-bit GSKit provides the SSL support for 32-bit WebSphere MQ clients on HP-UX 11i v1, and as such, if you attempt to start an SSL channel, or an MQCONNX call, that requires FIPS-certified cryptography you will receive an error message. To start an SSL channel that does not require FIPS-certified cryptography, set the MQSSLFIPS environment variable to NO. To start an MQCONNX call that does not require FIPS-certified cryptography, set the FipsRequired value in the MQSCO SSL configuration options to MQSSL_FIPS_NO.

 

Parent topic:

Checking prerequisite hardware and software

hq10240_