Verifying the operations of the CICS TS Feature Pack for Mobile Extensions

The sample program, DFH0MOBI (COBOL), helps you to test that the CICS® TS Feature Pack for Mobile Extensions is working. The sample program uses a JSON aware WEBSERVICE to receive your request and construct a simple response.

Before you begin

Make the load module DFH0MOBI available to the CICS region, by adding hlq.SDFHMOBL to the DFHRPL concatenation or define a LIBRARY resource containing hlq.SDFHMOBL.
Use hlq.SDFHMOBS(DFH0MOBC) as input to a DFHCSDUP job to add the definitions to the CICS region. DFH0MOBC contains the resource definition for the DFH0MOBI group.

About this task

You can access DFH0MOBI by using the supplied sample URIMAP resource DFH0MOBI. The URIMAP resource points to the supplied sample WEBSERVICE DFH0MOBI and supplied sample pipeline DFH0MOBI.

The sample programs construct JSON responses in this way:

{
   "DFH0MOBI_structure": {
      "DFH0MOBI_data": "DFH0MOBI on system applid successfully invoked through CICS Transaction Server for z/OS Feature Pack for Mobile Extensions V1.0"
   }
}

where applid is the application ID of the CICS system in which the CICS TS Feature Pack for Mobile Extensions is running.

To run the sample programs:

Procedure

Modify and install the sample TCPIPSERVICE definition HTTPNSSL, which is provided in group DFH$SOT. You must change the following options:
1. PORTNUMBER: HTTPNSSL uses port 80, the port number for HTTP. If port 80 is not reserved for the use by CICS, specify another port that belongs to z/OS® Communications Server that you have reserved for the use of CICS.
2. HOST or IPADDRESS: HTTPNSSL does not specify an IP address, so this option defaults to the IP address corresponding to the default z/OS Communications Server TCP/IP stack. This situation is the most typical. If you have multiple TCP/IP stacks in your z/OS image, and you want to use a nondefault stack, specify the IP address corresponding to that stack.
Install the sample JVMSERVER DFH$AXIS from group DFH$AXIS.
Install the sample application:
1. Edit the sample PIPELINE DFH0MOBI in group DFH0MOBI. Ensure that the path to the configuration file, /pathprefix/usr/lpp/cicsts/mobilefp/samples/pipelines/jsonjavaprovider.xml, is correct for your installation.
2. Edit the sample WEBSERVICE DFH0MOBI in group DFH0MOBI. Ensure that the path to the wsbind file, /pathprefix/usr/lpp/cicsts/mobilefp/samples/wsbind/dfh0mobi.wsbind, is correct for your installation.
3. Install group DFH0MOBI (PROGRAM, PIPELINE, WEBSERVICE, and URIMAP).
In a web browser, enter a URL that connects to the CICS TS Feature Pack for Mobile Extensions, by using the following URL components:
Scheme

HTTP

Host

The host name that is assigned to the z/OS image. If you do not know the host name, you can use the dotted decimal IP address from the HTTPNSSL TCPIPSERVICE definition. If you do not specify the IP address explicitly, it is completed by CICS, and you can view it in the installed TCPIPSERVICE definition.

Port number

The port number that is specified in the TCPIPSERVICE definition. If the number is 80, you do not have to specify it explicitly.

Path

To access DFH0MOBI, use the path /DFH0MOBI.

For example:
```
http://my.zos.image:1234/DFH0MOBI
```
The components of a URL has more information about how the components of a URL are delimited. For more information, see The components of a URL.
Optional: When you are satisfied that the CICS TS Feature Pack for Mobile Extensions is working, you can discard the sample TCPIPSERVICE definition HTTPNSSL and disable the URIMAP definition DFH0MOBI, the PIPELINE DFH0MOBI, the WEBSERVICE DFH0MOBI, and the PROGRAM DFH0MOBI.

verifying_operation_of_featurepack.html | Timestamp icon

Last updated: Thursday, 27 June 2019