To enable XML Gateway services through Oracle E-Business Suite Integrated SOA Gateway, some setup tasks are required for both strongly-typed services and generic XML Gateway services. For detailed setup and configuration tasks, see Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2, My Oracle Support Knowledge Document 1311068.1 for details.
Additionally, to enable Web service transactions, the following setup tasks are required to provide and consume Web services:
Perform the following setup tasks to provide services through XML Gateway inbound transactions:
Enabling Agents and Starting Agent Listeners
For providing services through XML Gateway inbound transactions, agent listeners running on ECX_INBOUND queue for strongly-typed XML Gateway services need to be up and running.
The following agents must be enabled and the seeded agent listener service components must be running:
| Agent Name | Listener Name |
|---|---|
| WF_WS_JMS_IN | Web Services IN Agent for generic XML Gateway services |
Use the Workflow Administrator: Agents window to enable the agents if necessary (the agents are enabled by default). The same window can be used to disable an agent.
Use Oracle Applications Manager to schedule and manage agent listener service components. For more information, refer to the Oracle Applications Manager online help.
The agent listener components are seeded with a manual startup mode and therefore must be manually started.
Setting profile option ECX_IN_JAVA_PROCESSING to Yes
This enables message processing in Java. For more information about this profile option, see Setting Profile Options.
Perform the following setup tasks to consume services through XML Gateway outbound transactions:
Enabling Agents and Starting Agent Listeners
The following agents must be enabled and the seeded agent listener service components must be running for XML Gateway outbound services
| Agent Name | Listener Name |
|---|---|
| WF_WS_JMS_OUT | Web Services OUT Agent |
Use the Workflow Administrator: Agents window to enable the agents if necessary (the agents are enabled by default). The same window can be used to disable an agent.
Use Oracle Applications Manager to schedule and manage agent listener service components. For more information, refer to the Oracle Applications Manager online help.
The agent listener components are seeded with a manual startup mode and therefore must be manually started.
Defining Lookup Values
You need to set up the correlation identifier in Oracle E-Business Suite. The correlation identifier enables you to label messages meant for a specific agent, in case there are multiple agents listening on the outbound queue. The agent listening for a particular correlation picks up the messages that match the correlation identifier for the agent.
In the Lookup form, search for COMM_METHOD in the Type field to see if it exists in the system. Add a new record to the COMM_METHOD type by entering BPEL for the Code field and the Meaning field. Enter description information and save the record.
Oracle XML Gateway puts the correlation of BPEL when enqueueing the message on the ECX_OUTBOUND queue. In addition to having the correlation identifier set up correctly, you need to ensure the trading partner that you want to use has the Protocol Type field set to BPEL.
To support XML Gateway Web services, the following profile options described in the table need to be set properly.
| Profile Option | Description | Required | Default Value |
|---|---|---|---|
| FND: XML Gateway Map Generic Service | Use this profile option to display or hide the generic XML Gateway service information for the selected XML Gateway map.
| Yes | Yes
Attention: If you do not start from this release and you have been using generic XML Gateway Web service, set the profile option to 'Yes'. This allows the Generic XML Gateway Services subregion to be displayed within the Web Service region. Otherwise, subregion will not be shown and any invocations of generic XML Gateway Web services will return a fault message. |
| ISG: Generic Service WSDL URL for XMLG | Once a generic XML Gateway Web service has been deployed, the deployed service WSDL URL should be populated as the profile value. The URL is also displayed in the 'Generic XML Gateway Service' subregion. If the profile value is not shown which means that the generic service has not yet been deployed, no WSDL URL is displayed in the subregion for the selected XML Gateway interface. | Yes | N/A |
| ECX_IN_JAVA_PROCESSING | This profile option determines if inbound messages will be processed in Java or PL/SQL.
| Yes | Yes |
Use the FND: XML Gateway Map Generic Service profile option to display or hide generic XML Gateway service information in the Generic XML Gateway Service subregion only if your system is upgraded from a previous release and you have been using generic XML Gateway Web services.
For information on setting profile options, see User Profiles and Profile Options in Oracle Application Object Library, Oracle E-Business Suite Setup Guide.