As an alternative to using the pipeline scanning mechanism
to install URIMAP resources, you can create and install them using
resource definition online (RDO).
Before you begin
Important: If you use RDO to define the WEBSERVICE
and URIMAP resources, you must ensure that their web service binding
files are
not
in the pickup directory of the PIPELINE. This
ensures that the WEBSERVICE and URIMAP resources are not dynamically
installed during a pipeline scan of the pickup directory.
Alternatively,
you can ensure that no value is specified for WSDIR in the PIPELINE.
However, if you do not specify a value for WSDIR, no pipeline scans
of the pickup directory occur. Therefore, all WEBSERVICE and URIMAP
resources have to be created and installed using RDO.
Procedure
- Use the
CICS Explorer®
to create a URIMAP definition for the inquire catalog
function of the example application.
- Create a URIMAP definition in the
CICS Explorer
by selecting
.
- Right-click in the
URI Map Definitions
view
and select
New
to create a new URIMAP definition.
- Type
INQCURI
in the
Name
text
box, and type
*
in the
Host
text
box. You must enter the
Path
attribute before
you can create the URIMAP definition. In the
Path
text
box type
/exampleApp/inquireCatalog.
Usage
must
be set to
Pipeline
; the PIPELINE resource is
EXPIPE01
or
EXPIPE03
for
Java-based pipelines.
- Click
Finish
to finish the URIMAP
definition.
- Double-click the new URIMAP resource to open the
Editor.
In the
Attributes
tab in the
Editor
,
set the
Web Service
attribute to
EXINQCWS
and
TCP/IP
Service
to
SOAPPORT.
- Repeat the preceding step for each of the remaining functions
of the example application. Use the following names for
your URIMAPs:
| Function |
URIMAP name |
| INQUIRE SINGLE ITEM |
INQSURI |
| PLACE ORDER |
ORDRURI |
| DISPATCH STOCK |
Not required |
| DISPATCH STOCK endpoint (optional) |
ODEPURI |
- Specify the following distinct attributes for each URIMAP:
| Function |
URIMAP name |
PATH |
WEBSERVICE |
| INQUIRE SINGLE ITEM |
INQSURI |
/exampleApp/inquireSingle |
EXINQSWS |
| PLACE ORDER |
ORDRURI |
/exampleApp/placeOrder |
EXORDRWS |
| DISPATCH STOCK endpoint (optional) |
ODEPURI |
/exampleApp/dispatchOrder |
EXODEPWS |