IMS Mobile Feature Pack for z/OS Connect is no longer enhanced. Instead, use the IMS service provider that is included in IBM z/OS Connect Enterprise Edition V2.0.5 (APAR PI70432) or later, which not only supports later releases of the Liberty server but additionally provides support for REST API creation and deployment. For the latest IMS mobile solution information, see Using the IMS service provider in z/OS Connect EE documentation.

Verifying server communication with IMS

Use the IMSPingService to verify that the IMS™ gateway server can communicate with IMS Connect by specifying the hostname, port number, and IMS data store name.

About this task

The IMSPingService service is installed as part of the IMS Mobile Feature Pack that you can use to check if the IMS gateway server is up and running. This service can also be used to verify that the IMS gateway server can communicate with IMS Connect.

Procedure

In your REST client or Java™ application, use the HTTP PUT method to invoke the provided IMSPingService service, and specify host name, the port number, and the IMS data store name.

https://hostname:port/zosConnect/services/IMSPingService?action=invoke&HOSTNAME=my.ims.host.com&PORT=9999&DATASTORE=IMS1

The HOSTNAME, PORT, and DATASTORE parameters must be in all uppercase letters, and all three parameters must be specified. If one of the required parameters is missing or the parameter names are misspelled, the parameters are ignored, and the request is treated as a ping request to the IMS gateway server. This service issues a /DISPLAY OTMA command to verify that the a mobile service on the IMS gateway server can access the IMS host system.

Results

You would receive the following response:

{
   message: "The ping request for the IMS gateway server was successful."
   pingTestResults: "Ping request for HOSTNAME: my.ims.host.com, PORT: 9999, DATASTORE: IMS1 was successful"
}