Configure Customer to Meter to Support Embedded Applications and Data Synchronization

To support ongoing data synchronization between Oracle Utilities Customer to Meter and the Oracle Fusion applications required for these solutions, you must configure the substitution variable for the CX Industry Fabric (CXIF) URL to support Message Sender configuration.

If your implementation includes CX for Utilities Agent Service, configure the CORS filter and Content Security Policy as described below. For instructions on the substitution variables technique, refer to the "Installation and Planning Worksheets" section of the Customer to Meter Installation Guide, available in the Oracle Utilities Customer to Meter library.

Set System Properties

Set the following properties in Oracle Utilities Application Framework:

• com.oracle.ouaf.web.csp.enable=true

• com.oracle.ouaf.web.allowCORS=true

• com.oracle.ouaf.web.csp.allowedFrameAnsMaxNumber=MAX-NUMBER

  The default value is 2. If you created more than 2 host variables, update this value to reflect the number of host variables.

• com.oracle.ouaf.uriSubstitutionVariables.file=FILE-PATH-VALUE

  This is the file path where substitutionVariableList.xml is located.

Verify that com.oracle.ouaf.web.disableSecureCookie is not present, or is set to false.

Create Substitution Variables for Data Synchronization

Create the following substitution variable:

• C1FABRIC with value <fabric APIGW host>

This variable is then used in when configuring the Ongoing Data Synchronization.

Create Substitution Variables for Embedded Application Support

For the CORS filter, create the following substitution variables:

• FA_DOMAIN: Populate this value with the Fusion Applications URL

• ALM_DOMAIN: Populate this value with the https://alm.oraclecorp.com

• CSP_FRAME_ANS_HOST1: Populate this value with the Fusion Applications URL

• CSP_FRAME_ANS_HOST2: Populate this value with the Fusion Applications identity domain (or IDCS) URL

If additional host variables are needed, create them by incrementing the number. For example, create CSP_FRAME_ANS_HOST3 if your system is configured for Single Sign On with an External Identity Provider.

Configure the Content Security Policy

If CORS is enabled, the Oracle Utilities Application Framework responds with a Content Security Policy (CSP) header that controls frame-ancestors, script source, image source, and other attributes.

By default, Oracle Utilities Application Framework populates CSP header options as follows.

default-src 'self'; img-src 'self' data: ; script-src 'self' 'unsafe-inline'
                'unsafe-eval'; style-src 'self' 'unsafe-inline'; base-uri 'self'; form-action
                'self';

Customize the web.xml.template and list all of the allowed origins for the CSP Filter under the cspOption parameter value, as described below.

1. Run this command: cd $SPLEBASE/templates

2. Run this command: cp web.xml.template cm.web.xml.template

3. Run this command: vi cm.web.xml.template

4. Locate this line:

   <param-value>default-src 'self'; img-src
                           'self' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src
                           'self' 'unsafe-inline'; base-uri 'self'; form-action
                           'self';</param-value>

5. Set the new value to:

   <param-value>default-src 'self'; img-src
                           'self' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval'
                           https://static.oracle.com; style-src 'self' 'unsafe-inline'; base-uri
                           'self'; form-action 'self';</param-value>

6. Execute: initialSetup.sh

7. Re-deploy and re-start the application.