For Web service requester and provider applications to participate
in Web service transactions, you must configure CICS® accordingly by installing a number
of CICS resources.
Before you can install these resources you must know the location
of the pipeline configuration files that CICS supplies in support of Web service
transactions. By default, the configuration files are supplied in the /usr/lpp/cicsts/cicsts31/pipeline/configs directory,
but the default file path might have been changed during CICS installation.
CICS support
for Web service transactions uses a CICS-supplied registration services service
provider and service requester, and you must install resources for both of
these. Even if your applications are all service providers, or all service
requesters, you must install both.
You must also install a program definition
for the header handler program that is invoked when you run your service provider
and requester applications.
The resources you require to configure CICS for
Web service transactions are all supplied in the DFWSAT group, except for
DFHPIDIR which is supplied in one of the following groups: DFHPIVS, DFHPIVR,
or DFHPICF. The DFHWSAT group is not included in the DFHLIST list, and therefore
is not installed automatically. You cannot change the resources supplied by CICS in
the DFHWSAT group.
To configure CICS for Web service transactions:
Add the DFHPIDIR data set to your startup
JCL. DFHPIDIR stores a mapping between contexts and tasks.- Add a new DD statement for the DFHPIDIR data set to your CICS
startup JCL
- Create the DFHPIDIR data set using information in DFHDEFDS.JCL. The default RECORDSIZE of DFHPIDIR is 1 KB, which is adequate
for most uses. You can create DFHPIDIR with a larger RECORDSIZE if you need
to.
- Install the appropriate group for the data set on your CICS system:
DFHPIVS, DFHPIVR, or DFHPICF.
If you want to share the DFHPIDIR file across CICS regions, the regions
must be logically connected over MRO.
- Copy the contents of the DFHWSAT group to another group. You cannot change the resources supplied by CICS in the DFHWSAT group. However, you
must change the CONFIGFILE attribute in the PIPELINE resources.
- Modify the CICS-supplied registration services provider PIPELINE
resource. The PIPELINE is named DFHWSATP, and specifies pipeline
configuration file /usr/lpp/cicsts/cicsts31/pipeline/configs/registrationservicePROV.xml in the CONFIGFILE attribute.
- Change the CONFIGFILE attribute to reflect the location of the
file in your system.
- Leave the other attributes unchanged.
Use the pipeline configuration file exactly as provided; do not change
its contents.
- Install the PIPELINE resource. The registration services
provider PIPELINE resource need not be in the same CICS region as your service requester or
provider applications, but must be connected to that region with a suitable
MRO or APPC connection.
- Without changing it, install the URIMAP that is used by the registration
services provider in the same region as the PIPELINE. The URIMAP
is named DFHRSURI.
- Modify the CICS-supplied registration services requester PIPELINE
resource. The PIPELINE is named DFHWSATR, and specifies pipeline
configuration file /usr/lpp/cicsts/cicsts31/pipeline/configs/registrationserviceREQ.xml in the CONFIGFILE attribute.
- Change the CONFIGFILE attribute to reflect the location of the
file in your system.
- Leave the other attributes unchanged.
Use the pipeline configuration file exactly as provided; do not change
its contents.
- Install the PIPELINE resource. The registration services
requester PIPELINE resource must be in the same CICS region as the service requester and
provider applications.
- Install the programs used by the registration service provider
pipeline in the same region as your PIPELINE resources. The programs
are DFHWSATX, DFHWSATR, and DFHPIRS. If both your PIPELINE resources are in
different regions, you must install these programs in both regions.
- Install the PROGRAM resource definition for the header handler
program. The program is named DFHWSATH. Install the PROGRAM in
the regions where your service provider and requester applications run.
CICS is
now configured so that your service provider and requester applications can
participate in distributed transactions using WS-AtomicTransaction and WS-Coordination
protocols.
You must now configure each participating application individually.