Sample SOAP WebSphere MQ Communications Binding for TPF

Copyright International Business Machines Corporation, 2006. All Rights Reserved.

Note to US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

NOTE: Before using this information and the product it supports, read the general information under "NOTICES" in this document.

CONTENTS

This file includes the following information:

1.0 ABOUT THIS README
2.0 SYSTEM REQUIREMENTS
3.0 DOWNLOADING
4.0 COMPILING, LINKING, AND LOADING
5.0 RUNNING
6.0 NOTICES
6.1 Trademarks

1.0 ABOUT THIS README

This readme file will guide you through the process of downloading, installing, and using a sample SOAP WebSphere MQ communications binding on your TPF 4.1 system to transport SOAP messages.

Go to the IBM TPF Product Information Center for more details about SOAP support and WebSphere MQ support.


Note: The TPF development lab does not maintain this application and will not accept APARs on this code.

2.0 SYSTEM REQUIREMENTS

To install and use this sample SOAP WebSphere MQ communications binding code on your TPF 4.1 system, you must have the following:

  • TPF SOAP support (APAR PJ29396)
  • WebSphere MQ support (minimum APAR level PJ28136)

Go to the IBM TPF Product Information Center for more information about these APARs, including specific migration information.

3.0 DOWNLOADING

To download this module, do the following:

  1. Click the Download Now button to download the compressed sample SOAP WebSphere MQ communications binding package (the “tarball”) to your workstation. The name of this package is MQSOAPbindingSample.tar.Z.

  2. FTP the tarball to your OS/390 UNIX System Services (OS/390 UNIX) machine using binary mode:

    1. Open an MS-DOS window and activate FTP by entering the following command:
      ftp your.os390.unix.machine.com
    2. Sign in entering your user name and password.
    3. Set the mode to binary by entering the following command:
      binary
    4. Send the file to OS/390 UNIX by entering the following command:
      send c:\your_path\MQSOAPbindingSample.tar.Z MQSOAPbindingSample.tar.Z
    5. Exit FTP by entering the following command: bye

  3. On OS/390 UNIX, extract the program files from the sample SOAP WebSphere MQ communications binding package by entering the following command:
    pax -rqvzkf MQSOAPbindingSample.tar.Z -o from=ISO8859-1,to=IBM-1047 "*/*.c"

    You should then have the following file:

    • Sample SOAP WebSphere MQ communications binding code (cso8.c).

4.0 COMPILING, LINKING, AND LOADING

Before you can run the sample SOAP WebSphere MQ communications binding code, do the following:

  1. Compile cso8.c

  2. Create a DLM for cso8.c that includes a stub for SOAP support (csoa) and a definition side-deck (DSD) for WebSphere MQ support (cmqs).

  3. Link the binding code (cso8.c) and its associated .o file with CSTRTD(40).

  4. Create a loadset and load the program to your TPF system.

5.0 RUNNING

To run the sample SOAP WebSphere MQ communications binding code, you must complete the appropriate MQ communications setup. Refer to the instructions located in the prolog at the top of the source file cso8.c and the IBM TPF Product Information Center.

The prolog also contains information about how you might need to update either or both of the sample SOAP communications binding and your tpf_soap_appl_handler user exit (cso4) to route requests to the appropriate application.

6.0 NOTICES

IBM may not offer the products, services, or features discussed in this information in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
Department 830A
Mail Drop P131
2455 South Road
Poughkeepsie, NY 12601-5400
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

6.1 Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
IBM
OS/390
WebSphere

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.