Deploying a web service requester to CICS

You can generate and deploy a logic part that runs on z/OS® CICS® and accesses a web service.

Prerequisites

To deploy a web service requester to CICS:

  1. Add web service binding information. For more information, see “Adding a SOAP service binding to a deployment descriptor.”
  2. Create a Program part that uses the web service.
  3. In the build descriptor of the project, set the following build descriptor options:
    deploymentDescriptor
    The name of the EGL deployment descriptor to which you added the binding information
    destDirectory
    The root HFS directory containing folders that receive the generated web services binding file and WSDL file. An example destDirectory value is /u/myname/requesters. CICS must have permission to read and write to this directory.

    The web services binding file is necessary to convert SOAP messages to COBOL at run time.

    destHost
    Specify the name or numeric TCP/IP address of the target system where the build server resides.
    destPassword
    Specifies the password that EGL uses to log on to the remote build server where your output will be prepared for deployment.
    destPort
    Specify the port on which a remote build server is listening for build requests.
    destUserID
    Specifies the user ID that EGL uses to log on to the remote build server where preparation occurs.
    genDirectory
    Specifies the fully qualified path of the directory into which EGL places generated output, control files, and results files.
    prep
    Set prep to YES.
    serverType
    Set serverType to CICS3.1.
    system
    Set system to ZOSCICS.
  4. Generate the program and the deployment descriptor.
  5. Define a web service PIPELINE:
    1. If you need to create a PIPELINE for requesters, type the following command:
      CEDA DEF PIPELINE(name) GROUP(group)
      For name, use the name of the new PIPELINE; for group, use the name of the group.
    2. For CONFIGFILE, specify /u/cicsts31/pipelines/basicsoap11requester.xml. If the code uses HTTP basic authentication, ensure that CONFIGFILE references the re-linked transport handler ELAWSHBA, as noted earlier in this topic.
    3. For SHELF, specify destDirectory/requester/shelf, where destDirectory is the value that you used for the destDirectory build descriptor option.
    4. For WSDIR, specify destDirectory/requester, where destDirectory is the value that you used for the destDirectory build descriptor option.
  6. Create a PROGRAM for the requester by typing the following command:
    CEDA DEFINE PROGRAM(name) GROUP(group) LANGUAGE(COBOL)
    For name, use the program name; for group, use the group name.
  7. Create a TRANSACTION for the requester by typing the following command:
    CEDA DEFINE TRANSACTION(name) GROUP(group) PROGRAM(programName) TWASIZE(1024)
    Use the transaction name for name, the group name for group, and the program name for programName.
  8. Install the group by typing the following command:
    CEDA INSTALL GROUP(group)
    Use the name of the group for group.
  9. Run the transaction.

Feedback