Verifying server communication with IMS
Use the IMSPingService to verify that the IMS service provider can communicate with IMS Connect by specifying the hostname, port number, and IMS data store name.
About this task
zosConnect-2.0 Applies to zosConnect-2.0.
The IMSPingService service is included as part of the IMS service provider that you can use to check if the IMS service provider is configured correctly. This service can also be used to verify that the IMS service provider can communicate with IMS Connect.
Procedure
Use an API testing tool, for example, POSTMAN to send 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=1234&DATASTORE=IMS1The 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 z/OS® Connect Server. When these parameters are provided
correctly, this service issues a /DISPLAY OTMA command to verify that the
IMS service provider on the z/OS Connect Server can access the IMS host system.
Results
{
...
"message": "The ping request for the IMS system \"HOSTNAME: 192.0.2.0, PORT: 1234, DATASTORE: IMS1, RACF ID: admuser\" through z/OS Connect and the IMS service provider was successful."
...
} What to do next
Before you start creating an IMS service and
an API, see the following information:
- See IMS connection profiles and IMS interaction profiles for configuration information.
- See Security configuration for the z/OS Connect Server for security-related configuration, such as setting up secure connections from z/OS Connect to IMS.
- To start creating a service and an API, see the following IMS scenarios. Each scenario includes a tutorial with detailed steps.