To create the CICS® infrastructure
for a JavaScript Object Notation (JSON) service provider, you must
create a pipeline configuration file and create a number of CICS resources.
Procedure
- Define the transport infrastructure.
- Define the message handlers that you want to include in
the pipeline configuration file to process inbound web service requests,
and their responses.
If you want to perform your own
processing in the pipeline, you must create a message handler. See Message handlers for details. If you decide to
create custom message handler programs, to optimize performance you
must make them threadsafe.
- Create an XML pipeline configuration file containing your
message handlers, header processing programs, and application handler. CICS provides a basic
provider mode pipeline configuration file sample, jsonjavaprovider.xml.
You can edit this sample to add additional message handlers as appropriate.
This sample is provided in the directory /usr/lpp/cicsts/mobilefp/samples/pipelines,
where /usr/lpp/cicsts/mobilefp installation directory
for the CICS TS Feature Pack for Mobile Extensions.
For more information about options available in the pipeline configuration
file, see Configuration elements used in service provider pipelines.
- Copy the pipeline configuration file to a suitable directory
in z/OS® UNIX.
- Change the pipeline configuration file permissions to allow
the CICS region to read the
file.
- Create a PIPELINE resource. The PIPELINE resource defines the location of the pipeline configuration
file. It also specifies a pickup directory, which is
the z/OS UNIX directory that contains the web service
binding files. Repeat this step for each different pipeline configuration. When you install a PIPELINE resource or perform a PIPELINE
SCAN, CICS reads the .wsbind files
in the specified pickup directory, and creates appropriate WEBSERVICE and URIMAP resources dynamically.
- Unless you use autoinstalled PROGRAM definitions, create
a PROGRAM resource
for each program that runs in the pipeline. These include the target
application program, which normally runs under transaction CPIH. The
transaction is defined with the attribute TASKDATALOC(ANY).
Therefore, when you link-edit the program, you must specify the AMODE(31) option.
Results
You have created the infrastructure needed for each service
provider and you can now install these resources on your CICS system.
What to do next
Install the resources. You can extend the configuration when
you need to do so, either to define additional transport infrastructure,
or to create additional pipelines.