Installing WebSphere MQ Web transport for SOAP

Use these instructions to install the WebSphere® MQ Web transport for SOAP. The installation creates tools to run Web service clients or services using WebSphere MQ as the SOAP transport. The tools are used in the .NET Framework 1, .NET 2, Axis 1.4, or Axis2 SOAP environments.

Before you begin

Check the prerequisite products at System Requirements for IBM® WebSphere MQ. The installation process does not check for the presence and availability of the prerequisite software. You must verify that the prerequisites are installed.

WebSphere MQ provides a copy of the Axis 1.4 run time. Use this version with WebSphere MQ rather than any other you might have installed. IBM does not provide technical support for Apache Axis. Contact the Apache Software Foundation if you have technical problems with it.

To run Web services in the .NET Framework 3 SOAP environment, WebSphere MQ uses Windows Communication Foundation. The WebSphere MQ custom channel for Windows Communication Foundation runs Web service clients and services using WebSphere MQ as a transport for SOAP messages.

About this task

You can install the WebSphere MQ Web transport for SOAP as either a WebSphere MQ MQI client or Server application. If you have already installed WebSphere MQ as a client or a server on your computer, check that you have installed the components listed.

MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

Carry out the following installation steps.

Procedure

  1. Select the Java and .Net Messaging and Web services component for installation.
  2. On Solaris and HP-UX, select the Java Runtime environment component for installation.
  3. Select the Development toolkit for installation.
  4. Install and verify WebSphere MQ as described in the Quick Beginning for your platform.
  5. Copy the Apache Axis 1.4 run time, axis.jar from the prereqs/axis directory on the WebSphere MQ installation media. Copy it to the installation directory described in Table 1, Table 2 , or Table 3.
    Windows
    Copy D:\PreReqs\axis\axis.jar MQ_INSTALLATION_PATH\java\lib\soap
    AIX®
    cp -f PreReqs/axis/axis.jar MQ_INSTALLATION_PATH/java/lib/soap/axis.jar
chown mqm:mqm MQ_INSTALLATION_PATH/java/lib/soap/axis.jar
chmod 444 MQ_INSTALLATION_PATH/java/lib/soap/axis.jar
    HP-UX, Solaris, and Linux® (all platforms) installation directories
    cp -f PreReqs/axis/axis.jar MQ_INSTALLATION_PATH/java/lib/soap/axis.jar
chown mqm:mqm MQ_INSTALLATION_PATH/java/lib/soap/axis.jar
chmod 444 MQ_INSTALLATION_PATH/java/lib/soap/axis.jar
  6. On Windows 2003, run Aspnet_regiis.exe to update the script maps to point to the version of the Common Language Run time your are using.
    Look for the Aspnet_regiis.exe utility in %SystemRoot%Microsoft.NET/Framework/version-number .
  7. Set the environment variable, WMQSOAP_HOME , to point to the WebSphere MQ installation directory.

Results

Table 1. Windows installation directories
Location Contents
MQ_INSTALLATION_PATH\programs\bin Binary, command, DLL, and executable files
MQ_INSTALLATION_PATH\programs\java\lib .jar files
MQ_INSTALLATION_PATH\programs\java\lib\soap SOAP .jar files
MQ_INSTALLATION_PATH\programs\soap\samples Samples and IVT
Table 2. AIX installation directories
Location Contents
MQ_INSTALLATION_PATH/bin Shell scripts
MQ_INSTALLATION_PATH/java/lib .jar files
MQ_INSTALLATION_PATH/java/lib/soap axis.jar and other JAX-RPC .jar files
MQ_INSTALLATION_PATH/samp/soap Samples and IVT
Table 3. HP-UX, Solaris, and Linux (all platforms) installation directories
Location Contents
MQ_INSTALLATION_PATH/bin Shell scripts
MQ_INSTALLATION_PATH/java/lib .jar files
MQ_INSTALLATION_PATH/java/lib/soap axis.jar and other JAX-RPC .jar files
MQ_INSTALLATION_PATH/samp/soap Samples and IVT

What to do next

  1. For .NET only, you must register the WebSphere MQ transport for SOAP files with the Global Assembly Cache. If .NET is already installed when you install WebSphere MQ, registration is performed automatically at installation. If you install .NET after WebSphere MQ, the registration is performed automatically when the IVT is first run.

    You can run amqiregisterdotnet.cmd to perform registration of the .NET assemblies. You can also run amqiregisterdotnet.cmd to force reregistration at any stage. Once made, this registration survives system restarts and subsequent reregistration is not normally necessary.

  2. Run the Installation Verification Test, as described in Verifying the IBM WebSphere MQ transport for SOAP.

  3. If you intend to develop Axis2 client, you must download Axis2 1.4.1 from Apache; see Developing a JAX-WS client for WebSphere transport for SOAP using Eclipse.