As an alternative to using the PIPELINE scanning mechanism to install
URIMAP resources, you can create and install them using Resource Definition
Online (RDO).
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 PIPELINE's pickup directory.
- Use the CEDA transaction to create a URIMAP definition for the
inquire catalog function of the example application.
- Enter the following: CEDA DEF URIMAP(INQCURI) G(EXAMPLE).
- Enter the following additional attributes:
USAGE(PIPELINE)
HOST(*)
PATH(/exampleApp/inquireCatalog)
TCPIPSERVICE(SOAPPORT)
PIPELINE(EXPIPE01)
WEBSERVICE(EXINQCWS)
- 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 |
- Enter the following additional attributes, which are the same
for all the URIMAPs:
- USAGE(PIPELINE)
- HOST(*)
- TCPIPSERVICE(SOAPPORT)
- PIPELINE(EXPIPE01)