If you encounter problems testing the service flow see Step 5.6: Troubleshooting.
To invoke the new service flow as the application program component of a Web service running on Web Services for CICS®, you must have a TCPIPService defined on your z/OS® system. The TCPIPService must be defined for the same port that you specified in the End Point URI input field in CatalogOrderGP.sfgen.
In this tutorial the value specified in the End Point URI input field was http://system.company.com:6182/user25/sampcapn (see Edit the generation properties file for CatalogOrder.seqflow). Therefore, the new service flow assumes that a TCPIPService is defined on port 6182 of the remote z/OS system.
To invoke the new service flow as the application program component of a Web service running on Web Services for CICS, you must also have a CICS PIPELINE defined on the remote z/OS system.
The pipeline must have as its working directory the UNIX System Services directory onto which you copied your Web service BIND file. This information is specified in the WSBind file input field on the second page of the Generate Runtime Code wizard.
In this tutorial the value specified for the WSBind file is /u/cicsts32/webservices/wsbind/cicssfrp (see Run the Generate Runtime Code wizard for CatalogOrderGP.sfgen).
This tutorial uses the pipeline CICSSFRP in the CICS group PIPELINE. The working directory is /u/cicsts32/webservices/wsbind/cicssfrp.
See your CICS administrator for information on how to set up a PIPELINE (see Required environment, materials, and assistance). One PIPELINE can be used by multiple programs, so you may be able to use an existing PIPELINE.
Once the PIPELINE is defined you must install your programs into the group to which they belong. "Installing" means that the PIPELINE searches for programs belonging to a specified group and adds such programs to its list of files that belong to the group.
If you do not select the check box Install the Program, Transaction, and ProcessType resources, then the group definition is specified in the resource definition JCL file #SAMPCAR.JCL (see JCL files). When the JCL is submitted, CICS generates the resources and specifies that they belong in group PIPELINE. Then when you install the programs into the CICS group PIPELINE, CICS searches for programs belonging to the group and adds them to the group.
ceda install group(your_group_name)For example
ceda install group(pipeline)
Even though you have copied your Web services BIND file (in this tutorial sampcapn.wsbind) to the PIPELINE's working directory (in this tutorial /u/cicsts32/webservices/wsbind/cicssfrp) nevertheless the PIPELINE has not been told that the new Web service BIND file exists.
If you do not select this check box, then to make the PIPELINE aware of the new WSBind file you must have the PIPELINE do a scan of its working directory to detect any new WSBind files.
cemt perform pipeline(your_pipeline_name) scanFor example
cemt perform pipeline (cicssfrp) scan
In this section you will run the Web service in the Web Services Explorer. To run the Web service you will use the information contained in the local copy of the WSDL file (sampcapn.wsdl) that was created when you generated the runtime code for the CatalogOrder flow.
To run the Web service:
In the Remote Systems view, verify that your connection with the remote z/OS system is active (see Set up a connection to z/OS in the Remote Systems view).
In the EST Project Explorer, right-click sampcapn.wsdl.
Click . The Web Services Explorer opens.
In the Navigator view of the Web Services Explorer:
file:/D:/Tutorial/CatalogSample/deployment/CICS SFR L2.0/CatalogOrder/sampcapn.wsdl
Under the file entry, expand the tree and click the node for the operation.
The names of the node for the WSDL service details, the node for the WSDL binding details, and the node for the WSDL operation can be different, depending on the value that you set for the check box Expose All CICS SFR Headers in Interface (ADVANCED) in the generation properties editor (see Attention):
If you cleared the check box (default setting) then click .
If you selected the check box then click .
The Actions view should now display the page Invoke a WSDL Operation.
Specifying values for the request message header:
The names and the number of these input fields can be different, depending on the value that you set for the check box Expose All CICS SFR Headers in Interface (ADVANCED) in the generation properties editor (see Attention):
Expand .
If you selected the check box:
Expand .
| Field name: | Input value: |
|---|---|
| dfhma_strucid | MAH1 |
| dfhma_version | 2 |
| dfhma_struclength | 384 |
| dfhma_returncode | 0 |
| dfhma_compcode | 0 |
| dfhma_mode | 0 |
| dfhma_suspstatus | 0 |
| dfhma_abendcode | 0 |
| dfhma_uowcontrol | 0 |
| dfhma_processtype | SAMPCARN1 |
| dfhma_requestname | SAMPCARN1 |
| dfhma_datalength | 7 |
| dfhma_linktype | 1 |
| dfhma_more_data_ind | 0 |
| dfhma_bridge_rc | 0 |
| 1You must type this input using uppercase! | |
Most of the values shown in this table are the same for any Web service that you have created.
Specifying values for the input data container:
In the Actions view, expand the input data container. The path of the input data container can be different, depending on the value that you set for the check box Expose All CICS SFR Headers in Interface (ADVANCED) in the generation properties editor (see Attention):
If you cleared the check box (default setting) then expand .
If you selected the check box then expand .
In the itemnumber field type the item number that you want to test (for example 0010).
In the itemquantity field type the number of items that you want to order (for example 25).
To run the service flow, scroll to the end of the Actions view and click Go.
Check the return information:
In the Web Services Explorer, expand the Status view. The fields in this view can be different, depending on the value that you set for the check box Expose All CICS SFR Headers in Interface (ADVANCED) in the generation properties editor (see Attention):
If you cleared the check box (default setting) then expand .
If you selected the check box then expand .
| Scenario: | returncode | returnmessage |
|---|---|---|
| If the item number was found and number of items requested are in stock: | 0 | ORDER SUCCESSFULLY PLACED |
| If the number of items requested were not in stock: | 97 | INSUFFICIENT STOCK TO COMPLETE ORDER |
| If the specified item was not in the catalog. | 99 | ITEM WAS NOT AVAILABLE IN CATALOG |
The meanings of the return codes are documented in the CICS Service Flow Runtime User's Guide.