Create Basic Routing Integrations
You create an integration that provides a template with empty trigger and invoke connections in which to add your own adapters. You can also create a single routing expression and request and response enrichments, as needed. You cannot create multiple routing expressions. If your integration requires this feature, create an orchestrated integration.
Topics:
-
Create a Basic Routing Integration
Note:
The basic routing integration style has been deprecated. Oracle recommends that you use the app driven orchestration integration style, which provides more flexibility. You can migrate basic routing integrations to app driven orchestration integrations. See Convert a Basic Routing Integration to an App Driven Orchestration Integration. -
Create Routing Paths for Two Different Invoke Endpoints in Integrations
-
Create Routing Expression Logic in Both Expression Mode and Condition Mode
- Map Faults in Basic Routing Integrations
- Add Customized Mappings to Prebuilt Basic Routing Integrations
- Remove Customized Mappings from Prebuilt Basic Routing Integrations
Create a Basic Routing Integration
This section describes how to create a basic routing integration.
- Follow the steps in Create Integrations to create a basic routing integration.
An integration canvas with empty trigger and invoke connections is displayed.
Add a Trigger (Source) Connection
The trigger (source) connection sends requests to Oracle Integration. The information required to connect to the application is already defined in the connection. However, you still must specify certain information, such as the business object and operation to use for the request and how to process the incoming data.
Add an Invoke (Target) Connection
Oracle Integration sends requests or information to the invoke (target) connection. The information required to connect to the application is already defined in the connection. However, you still must specify certain information, such as the business object and operation to use for the request and how to process the data.
Add Request and Response Enrichments
When you create an integration, you also have the option of adding both request and response message enrichment points to the overall integration flow. Enrichments participate in the overall integration flow and can be used in the request and/or response payloads between the trigger and invoke.
Delete Request and Response Enrichments
You can delete the request and response message enrichment point mappings added to an integration. After deleting the enrichment point mappings, the integration is returned to its original pre-enrichment state.
Create Routing Paths for Two Different Invoke Endpoints in Integrations
You can create an integration in which you define routing paths for two different invoke endpoints. During runtime, the expression filtering logic for the routing paths is evaluated and, based on the results, the path to one of the invoke endpoints is taken. If the filtering logic for neither routing path is satisfied, then neither invoke endpoint is contacted.
-
You define an expression filter on the first (upper) invoke endpoint.
-
You define either an ELSE condition or an expression filter on the second (lower) invoke endpoint.
During runtime, if the expression filtering logic for the first (upper) invoke endpoint evaluates to true, then the path to that invoke endpoint is taken. If the expression evaluates to false, then that invoke endpoint is skipped, and the path to the second (lower) invoke endpoint is taken through either an ELSE condition or an expression filter.
In addition to creating routing paths, you also define request and response (and optionally, enrichment) mappings on both invoke endpoints.
To create routing paths for two different invoke endpoints in integrations:
Create Routing Expression Logic in Both Expression Mode and Condition Mode
You can create XPath expressions for routing conditions in two different user interface modes:
-
Expression mode: This mode provides an interface for creating and viewing the entire XPath expression.
-
Condition mode: This mode provides an easier-to-read interface to create and view XPath condition expressions. This mode is useful for business analysts who may be less experienced with XPath expressions.
-
Three levels of elements are loaded by default in the tree in the Source area. When you reach the third level, a Load more link is displayed. Click this link to display all the direct children of that element. Only base types are loaded automatically. To load the extended types of the base type, click the base type, which is identified by a unique icon. This invokes a menu of extended types that you can select to load one by one into the tree.
Description of the illustration ics_logic_express_base.png -
Elements in the tree in the Source area that you have already dragged to an expression are identified by green checkboxes. These elements are displayed even if they are deeper than three levels in the tree.
-
You can search for an element that is not yet loaded in the tree by entering the name in the Find field and clicking the Search icon. This action loads that specific element into the tree.
This section provides an example of building an expression using both modes.
To create routing expressions in both expression mode and condition mode:
Delete Routing Paths
You can delete routing paths that have been created on different target endpoints in an integration.
-
Delete the routing path and expression filter.
-
Delete the endpoint and routing path, but retain the expression filter.
Deleting the Routing Path and Expression Filter
To delete the routing path and expression filter:
-
In the Integrations page, select the integration in which to delete a routing path.
-
Expand the Routing Drawer icon to display the diagram of routing paths.
-
Above the integration, select the routing path to delete.
Description of the illustration routing_select_delete.png -
Click the Filter icon.
-
Select Delete Route from the menu that is displayed.
Description of the illustration routing_delete.png -
Click Yes when prompted to confirm.
This action deletes the routing path, including the expression filter and the request mapping for the selected path. The diagram above the integration shows that the routing path is deleted.
Description of the illustration routing_delete_complete.png
Deleting the Endpoint and Routing Path
To delete the endpoint and routing path:
-
In the integration, click the target endpoint to delete.
-
Click Delete in the menu that is displayed.
-
Click Yes when prompted to confirm.
This action deletes the target endpoint and routing path. The diagram above the integration shows that the routing path is deleted. Within the integration, only the expression remains defined in the integration because it is not using anything from the deleted target endpoint.
Description of the illustration routing_delete_endpt.png
Map Faults in Basic Routing Integrations
You can map portions of a message into the fault message to compose a description that helps you understand the fault.
Add Customized Mappings to Prebuilt Basic Routing Integrations
It is a common practice to customize the application endpoints of the prebuilt integrations that you import into Oracle Integration from the Oracle Marketplace (for example, adding custom fields). As a result, you must customize the integration mappings to take advantage of these custom fields. Oracle Integration enables you to customize the mappings in the prebuilt integrations that you import from the Oracle Marketplace. This action creates a customized mapping layer on top of the base mapping file, which is not modified. You can only add customized mappings to prebuilt integrations imported from the Oracle Marketplace, and not to integrations you or another user created.
See Mapping Data of Using the Oracle Mapper with Oracle Integration Generation 2.
Remove Customized Mappings from Prebuilt Basic Routing Integrations
You can remove the customized mappings that you added to prebuilt integrations that you imported from the Oracle Marketplace. You can remove all customized mappings or specific subsets of mappings (for example, request, response, faults, enrichment source, or enrichment response mappings).