Mapper Connectivity Properties Support

The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.

Note:

This support is only available for non-OUAF Applications.

• Set the Oracle Utilities Adapter Connectivity Properties in the Mapper
• Support for Dynamic REST Endpoints

Set the Oracle Utilities Adapter Connectivity Properties in the Mapper

You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.

• Connectivity properties (invoke request)

  You can set the following property for invoke requests in the mapper.

  Property	Description
  ConnectionId	The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.

  
  
  
  
  

Support for Dynamic REST Endpoints

The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration. This feature is useful in the following scenarios:

• A REST endpoint must be invoked dynamically at runtime.
• An endpoint is not known at design time.

To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.

For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime:

1. Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.
2. Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.
3. Create an integration adding any connection of the non-OUAF application on the invoke.
4. In the target pane of the mapper, expand Plugin under ConnectivityProperties. These elements are made available automatically through a static schema that is added to the user-provided schema.
5. Using the source schema in the source pane, create a mapping to ConnectionId in the target pane. Alternatively, you can also provide a static mapping. The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier. The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.
6. Activate and invoke the integration. The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.