Software requirements

IMS Enterprise Suite Version 3.2 SOAP Gateway supports IMS 14, 13, or 12, and requires a minimum of IBM® Java™ software development kit (SDK), Java Technology Edition, V7.0.9.10

Supported IMS versions

IMS Enterprise Suite Version 3.2 works with IMS 14, 13, and 12.

Java requirement

SOAP Gateway runs on both IBM 64-bit and IBM 31-bit Java software development kit (SDK), Java Technology Edition, Version 7, with the minimum required version of V7.0.9.10 You can order Java for z/OS® through Shopz by using PID 5655-W44 for Java for z/OS 64-bit, or PID 5655-W43 for 31-bit. The non-SMP/E installable package can be downloaded from the download site at http://www.ibm.com/systems/z/os/zos/tools/java/.

Requirements for send-only with acknowledge support for synchronous callout

For IMS 13, you must apply the fix for IMS 13 APAR PM91344 or V12 APAR PM91443 for this feature.

Requirements for transaction tracking IDs and logging

For IMS 12, IMS APAR PM69983 and APAR PM76333 are required to use horizontal IDs.
IBM Tivoli® Composite Application Manager for Transactions Application Program Interface V7.3 or later

Required versions of Rational Developer for System z

If you are using IBM Rational® Developer for System z® to generate web service artifacts, Rational Developer for System z Version 9.0 or later is required.

Rational Developer for System z has a Eclipse-based development environment (or client) for SOAP Gateway web service artifact generation, and a server or host portion that must be configured. The host portion consists of permanently active tasks and ad-hoc started tasks to allow the client to work with the various components of your z/OS host, such as MVS™ data sets, TSO commands, z/OS UNIX files and commands, job submit, and job output.

To use the IMS Connect XML converter function for SOAP Gateway, the Rational Developer for System z SFEKLMOD module must be concatenated to the STEPLIB of the IMS Connect startup JCL to use the XML converter function. The SFEKSAMP library and the SFEKLMOD module are required at the XML converter compilation time, and the SFEKLMOD module is also required at run time.

Important:

The correlator schema has changed in IMS Enterprise Suite Version 3.1 SOAP Gateway to schema version 3.0.
- When you upgrade to IMS Enterprise Suite Version 3.2, migration of the correlator files is handled as part of web service migration process when you use the SOAP Gateway management utility iogmgmt -migrate path_to_source_installation command.
- To generate correlator files in schema version 3.0, use Rational Developer for System z Version 9.0.1 or later. Correlator files that are generated by older versions of Rational Developer for System z are in correlator schema version 2.0 and must be migrated. You must run the iogmgmt -migrate correlator command to migrate the correlator files in the SOAP Gateway server XML directory to the new schema before deploying the web services.
- Rational Developer for System z Version 9.0.1 or later generates correlator files in version 3.0 schema only. If you still need to generate correlator files in version 2.0 schema for existing production environment while testing the IMS Enterprise Suite Version 3.2 SOAP Gateway, stay with Rational Developer for System z Version 9.0. When version 3.0 schema is needed, use the SOAP Gateway migration utility iogmgmt -migrate correlator command to migrate the correlator files to version 3.0 schema.
If you plan to use the top-down provider scenario that generates a PL/I application from a web service WSDL file, the generated application is based on a set of segmentation APIs. The IRZPWSIO segmentation APIs are included in Rational Developer for System z V9.0 and older versions. In Rational Developer for System z V9.0.1 or later, the APIs are removed, and are now included in IMS V12 (APAR PM97469) and IMS V13 (APAR PI17898). The IRZPWSIO segmentation APIs are renamed to DFSPWSIO in IMS. The IRZPWSH include file is renamed to DFSPWSH in IMS.