OPA Integration Doesn't Work On Siebel Remote With IO Mapping (Doc ID 1593561.1)

Last updated on MARCH 02, 2017

Applies to:

Oracle Policy Automation Connector for Siebel - Version 10.2.1.1006 and later
Information in this document applies to any platform.

Symptoms

On : 10.4 version, Oracle Policy Automation

ACTUAL BEHAVIOR
---------------
The customer are implementing a solution to integrate Siebel Remote with OPA to help our engineers work in a disconnected mode. As part of our implementation, we found out that the Siebel - OPA connector relies on the Integration Object (IO) definition to define the input parameters (Policy Automation Get IO). The Remote database is usually initialized without repository tables and hence the process is not able to extract the IO definition, hence the overall end to end system fails to operate.
Note: The same configuration works on server.

Per updates received from other SR the AdminSmokeTestIO was not operational on Siebel Remote and Product Manager's recommendation was to import the IO definition manually into the Remote database. This is not a viable option for a large scale remote client deployment.

We want to understand if there are any inbuilt processes which transfers the IO definition into Siebel Remote? I have attached a Remote Client database which somehow got the IO definition used by our implementation, however we have no idea how it ended up in the Remote DB. FYI, neither the IO definition was available when the DB was initialized nor it was imported manually.

If we don't have an answer to the above question, can we do the following:
1. Dock Object "DOX_OPA_ENT_VIS" is available based on table "S_PA_RULE_DEF" to exchange IO Mappings between Server and Remote clients.
2. Add the following "Dock Object Tables" under this dock object to transfer IO definitions to Siebel Remote?
Table Name Source Column Name Target Table Name Target Column Name
S_INT_OBJ NAME S_PA_RULE_DEF INT_OBJ_NAME
S_INT_OBJ_UPROP INT_OBJ_ID S_INT_OBJ ROW_ID
S_INT_COMP INT_OBJ_ID S_INT_OBJ ROW_ID
S_INT_FIELD INT_COMP_ID S_INT_COMP ROW_ID
S_INTFLD_UPROP INT_FIELD_ID S_INT_FIELD ROW_ID
S_INT_CKEY INT_COMP_ID S_INT_COMP ROW_ID
S_INT_CKEY_FLD INT_KEY_ID S_INT_CKEY ROW_ID
S_INTCOMP_UPROP INT_COMP_ID S_INT_COMP ROW

EXPECTED BEHAVIOR
-----------------------
Implementation work expected work  in Siebel  remote client too.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
The customer has an issue in Siebel remote client due to integration table not supported OPA Siebel connector in the standard siebel table.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms