Questions on Policy Configuration in Context of Services Migration From 11g to 12c (Doc ID 2734851.1)

Last updated on AUGUST 18, 2022

Applies to:

Goal

In the context of migration of services from 11g to 12c(12.2.1) of Application Integration Architecture (AIA), environment configuration was done as following:

1. install Fusion Middleware (FMW) 12.2.1.4 and out-of-the-box(OOTB) AIA 12.2.1 on new hosts

2. deploy OOTB AIA PIPs(Process Integration Pack) 12.2.1 in the new environment

3. open OOTB AIA 12.2.1 composite in JDeveloper, change and add customizations there

4. deploy them by JDeveloper in 12c environment

It was observed that policy configuration is not configured as it was present in 11g even if it is mentioned in it wsm-assembly file or in configurationproperties file.

See the difference found in policy configuration while testing for QueryCustomerPartyListSiebelProvABCSImplV2.

In 11g, the below policy is enabled under Directly attached policy :

oracle/no_authentication_client_policy

In 12c PIP, below policy is enabled under Globally attached policy and no policies added under Directly attached policy:

oracle/aia_wss10_saml_token_client_policy_OPT_ON

Is this expected behavior?

We need to understand how policies are being attached globally after deployment and what is the significance of the same?

Should Globally attached policy oracle/aia_wss10_saml_token_client_policy_OPT_ON be removed for all services in 12c?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.