The Outbound Web Service Request node type causes the specified application to be invoked as a Web service.
(Recall that an outbound Web service is any Web service that you invoke from within a flow -- see Outbound Web services subproject and Importing an outbound Web service definition.)
For more information about these generation properties see the CICS® Service Flow Runtime User's Guide (see Supported runtime environments for each project type).
| NAME | DESCRIPTION | VALUE RANGE | DEFAULT VALUE |
|---|---|---|---|
| Invoke Type | Type of Invoke node. | Outbound Web Service Request. | Outbound Web Service Request |
| Activity Name | Name of the activity performed by
the node. Note: When the runtime code is generated for
the CICS Service
Flow Runtime environment, the runtime code generator uses the information
in this node to create a CICS Business Transaction Services (BTS) activity. The
name that you specify here is used as the name of the new BTS activity.
|
String value: 1-23 characters. Note: The
limitation to a maximum of 23 characters is necessary because the Generate
Runtime Code wizard in some places in the generated COBOL source code appends
a 7-character string to this Activity Name.
|
The name of the outbound Web service Invoke node in the flow editor. |
| Comment | Optional text associated with the individual node | String value | Blank |
| WEBSERVICE resource | The CICS resource name of the Web service to be invoked. (In CICS, a web service must be defined and registered as a CICS resource.) | String value. | The name (without the extension) of the original WSDL file containing the outbound Web service definition. This is also the name that is generated automatically by CICS when a PIPLELINE SCAN command is performed. |
| Web Service Request URI | The URI of the Web service to be invoked. Used by CICS to locate the Web service. | String value. | The value specified in the original WSDL file containing the outbound Web service definition. |
| Operation name | The name of the function in the Web service that is to be invoked. | String value. | The name of the operation in the operations file for the outbound Web services request. |
| Adapter Transaction ID | The CICS TransID for the COBOL program that implements the invocation of the Web service. | String value: 1-4 characters | CMAO You can accept the default transaction ID, or you can override the default transaction ID by typing another transaction ID into this field. An error message is displayed if the input field is blank or if the transaction ID begins with C and is something other than CMAO. (Transaction IDs beginning with C are reserved by CICS). |
| Remote WSBind file location | (Optional) The name of the directory in z/OS® UNIX System Services on the remote z/OS system (for example, /u/cicsts31/websrv/wsbind/) to which you want the Generate Runtime Code wizard to copy the WSBind file associated with the outbound Web service request (see Files created when an outbound Web service definition is imported). You can either:
|
String value. | Blank |
| Remote WSDL file location | (Optional) The name of the directory in z/OS UNIX System Services on the remote z/OS system (for example, /u/user25/cicsts32/sfp01) to which you want the Generate Runtime Code wizard to copy the WSDL file associated with the outbound Web service request (see Files created when an outbound Web service definition is imported). You can either:
|
String value. | Blank |
This option is available only if you have created and started a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server).
If a connection to a CICS Resource Definition server is available then each of these two fields expands to a list of the WSBind pickup directories that are defined for PIPELINEs in the connected CICS regions.
Select a remote directory from the list or type an entry.
This option is available only if you have created a connection to the remote z/OS system using the Remote Systems view (see Step B3. (Optional) Create a connection to the remote z/OS system using the Remote Systems view).
The generation properties editor displays the path of the selected subdirectory in the input field beside the Browse button.