Configure the Data Synchronization Process

To configure this part of the synchronization, log in to CX Industry Framework identity domain. Under Oracle Cloud Services locate an application created for the ongoing data synchronization in the CX Industry Framework identity domain. This was likely created during the initial registration process, and is named something similar to CX4UINT. You will be using the OAuth client credentials configured in this application to complete the remaining steps. Contact your delivery team if you need assistance gathering the required information.

Refer to the Data Synchronization section in the Oracle Utilities Framework User Guide for more information on batch processing and error handling.

  1. Configure the Key Ring C1-CXIF to store:

    • OAuth Client ID: The client ID for the OAuth Client mentioned above.

    • OAuth Client Secret: The client secret for the OAuth Client mentioned above.

  2. Configure the outbound data synchronization with a Message Sender of C1CxPersonSy for the delivered application Outbound Message Type of C1PERSYNC on the External System of CX4U for Real-time HTTP / JSON messages. The context is delivered for sending the synchronization records with the following values:

    • HTTP Method: PUT

    • HTTP URL 1: URL for CX Industry Framework API with path variables

    • OAuth Grant Type: client_credentials

    • Sender Security Type: OAUTH

  3. Additional values need to be configured for the CX Industry Framework pairing:

    • Oauth Access Token URL: The OAuth server URL from which to obtain the access token. Use the CX Industry Framework identity domain.

    • OAuth REST API Scope: Scope for CX Industry Framework REST API.

  4. Schedule the F1-SYNRQ (sync request monitor) batch process to send the sync request messages from Customer Cloud Service. This is a generic batch process that is used for multiple integration sync processes and should be scheduled based on frequency for all external system synchronizations.

  5. The person synchronization is controlled by an F1-DataSyncControl extendable lookup business object of C1-CX4U-PERSON. The status of this lookup record must be ACTIVE to enable the synchronization and the external system.

  6. The Installation Options - Person should be configured to allow synchronization from the Fusion application without government issued identifiers prior to linking the person to a utility billing account or prior to starting new utility service. The Person ID Usage setting cannot be configured as required, as this will cause the data synchronization to fail when no person identifiers are passed from Fusion. Depending on your business requirements, use one of these settings for the Person ID Usage:

    • Optional

    • Required When Financially Responsible

    • Required When Linked to Account

    • Required When Main Person

  7. Complete the steps to flush the caches for the Server Cache, Batch Cache, and Client Cache as described in the Caching Overview section of the Customer Cloud Service Administrative User Guide, available in the Oracle Utilities Customer Cloud Service library.

    For additional information on batch processing and error handling, see Data Synchronization in the Oracle Utilities Framework User Guide, available in the Oracle Utilities Customer Cloud Service library.

Contact your delivery team and confirm that the Cloud Customer Support team prepared the environments for registration, including variables that are referenced such as @C1FABRIC@ for the HTTP URL in the application cloud parameters.

Parent topic: Utilities Data Synchronization