Configuring Oracle Utilities Customer Cloud Service
This chapter describes the Oracle Utilities Customer Cloud Service configuration required to synchronize Person and Case data with Oracle Fusion CX Service through Oracle Integration Cloud (OIC). It includes the following sections
How Customer Cloud Service Data Maps to Fusion CX Service Data
The following table shows how Person and Case data in Oracle Utilities Customer Cloud Service maps to Contact or Account and Service Request data in Oracle Fusion CX Service.
| Data | Oracle Utilities Customer Cloud Service | Oracle Fusion CX Service |
|---|---|---|
| Person | Person (C1-CXperson) | Contact or Account |
| Case | Case (C1-Case) | Service Request |
Configuring Admin Data
Configure the message senders, outbound message types, and external system used to send synchronization messages to OIC.
-
Login to Oracle Utilities Customer Cloud Service
-
Create message senders. Refer to the Message Senders section for details.
-
Create outbound message types. Refer to the Outbound Message Types section for details.
-
Associate the message senders and outbound message types with the integration external system. Refer to the External System section for details.
-
Complete the Person Synchronization and Case master configuration described in the following sections.
-
Generate certificates. Refer to the Adding Oracle Integration Cloud Certificates section for more details.
Note: To create the external system and outbound message types follow the naming conventions specified to ensure compatibility with the refresh endpoint and related customizations.
Message Senders
This section provides the message sender configuration details in Oracle Utilities Customer Cloud Service.
To create a message sender:
-
Navigate to the Message Sender page, either from the Admin menu or from the Search menu.
-
Enter a unique message sender and its description.
-
Populate the following values:
- Invocation Type: Real-time
- Message Class: RTJSONSNDR
- Active: Select the checkbox.
-
Select the Context tab and set values for the following context types:
-
HTTP Method: POST
-
HTTP Timeout: 60
-
HTTP Transport Method: SendReceive
-
HTTP URL 1: Set the Activated Integration end point URL by removing the ?wsdl from the URL.
If the URL value does not fit, use the additional HTTP URL types to set the complete URL.
In addition to the values listed above, from the following security types, add the corresponding security policy specific context types.
-
- For Basic Auth Security type:
- HTTP Login User: User ID to access the Oracle Integration Cloud flow.
- HTTP Password: Password to access the flow.
- Sender Security Type: BASIC
- If the security policy used is OAuth Client Credentials, additional configuration for the context types should be as follows:
- OAuth Access Token URL: Identity service token url to retrieve the OAuth token for Oracle Integration Cloud Instance.
- The Token URL is of format:
https://<idcs-tenant>/oauth2/v1/token - OAuth Client ID: OAuth Client ID for Client Credentials grant type of Oracle Integration Cloud Instance.
- OAuth Client Secret: OAuth Client Secret for Client Credentials grant type of Oracle Integration Cloud Instance.
- OAuth Grant Type: client_credentials
- OAuth REST API Scope: OAuth Scope for Client Credentials grant type of Oracle Integration Cloud Instance.
- Sender Security Type: OAUTH
Message Sender Configuration for Integration Services
| Message Sender | Description | HTTP Transport Method | HTTP Method | HTTP URL |
|---|---|---|---|---|
| C1OICPerSync | CX Person Synchronization | SendRecieve | POST | https://OIC_HOST/ic/api/integration/v2/flows/oracleutilities/project/OUTL-BA-CCS_CX/OUTL-BA-CCS_CX_PERSON_SYNC/1.0/personSync |
| C1CxCaseSy | Case synchronization to oracle fusion service | SendReceive | POST | https://OIC_HOST/ic/api/integration/v2/flows/oracleutilities/project/OUTL-BA-CCS_CX/OUTL-BA-CCS_CX_CASE_SYNC/1.0/caseSync |
Outbound Message Types
To create a new outbound message type for each integration process:
-
Navigate to the Outbound Message Type page from the Admin menu or from the Search menu.
-
Enter an outbound message type, description, and detailed description.
-
Select the outbound message business object created for a specific service.
Outbound Message Types for Integration Services
| Integration Service | Outbound Message Type | Description | Business Object |
|---|---|---|---|
| Person Sync | C1PERSYNC | Person Data Synchronization | C1-CxPerSyncMessage |
| Case Sync | C1CASESYNC | Case Data Synchronization | C1-CaseDataSyncMessage |
External System
To create a new external system to support the integration:
-
Navigate to the External System page from the Admin menu or from the Search menu.
-
Enter a unique external system and description.
For example: Name = INT_CX_ES, Description = CX Fusion External System
-
Set the Our Name in Their System field to CCS.
-
Associate the outbound message types and message senders created to the external system.
For each outbound message type, set the following:
- Outbound Message Type: Outbound message type created for the respective integration service.
- Processing Method: Real-time
- Message Sender: Set the message sender created for the integration service
- Date/Time Format: XSD
- JSON Conversion Method: Base JSON Conversion.
For more information about message senders and outbound message type for each integration service, refer to the Message Senders and Outbound Message Types sections respectively.
External System Configuration for Integration Services
Example External System - INT_CX_ES
| Integration Service | Outbound Message Type | Message Sender |
|---|---|---|
| Person Sync | C1PERSYNC | C1OICPerSync |
| Case Sync | C1CASESYNC | C1CxCaseSy |
Configuring Person Synchronization
Person synchronization requires audit algorithms to detect changes and a data synchronization control record to route synchronization requests to the integration external system.
Person Maintenance Object Algorithms
-
Open Maintenance Object from the Admin menu or search and select PERSON.
-
Verify that the following audit algorithms are associated with the maintenance object. Add any required association that is missing, then save.
| Audit algorithm | Sequence | Purpose |
|---|---|---|
| C1-PERECDCSA | 15 | Person synchronization audit processing. |
| F1ONGDATASYN | 20 | Ongoing data synchronization processing. |
Data Synchronization Control
-
Open Extendable Lookup from the Admin menu or search.
-
Select the F1-DataSyncControl business object and open C1-CX4U-PERSON.
-
Set the record status to Active.
-
Configure the record to reference the external system used by this integration, for example INT_CX_ES.
-
Review the Person synchronization request and outbound message associations, then save the record.
Configuring Case Synchronization
Configure the Case data synchronization control record to reference the external system used by this integration.
Case Maintenance Object Algorithms
-
Open Maintenance Object from the Admin menu or search and select CASE.
-
On the Algorithms tab, verify the following association. Add it if missing, then save.
Audit algorithm Sequence Purpose F1ONGDATASYN 10 Ongoing data synchronization processing.
Data Synchronization Control
-
Open Extendable Lookup from the Admin menu or search.
-
Select the F1-DataSyncControl business object.
-
Clone the existing OIC Case synchronization entry.
-
Associate the new entry with the integration external system, for example, INT_CX_ES, and save.
Master Configuration
The master configuration has the necessary information to support this integration.
-
Navigate to the Master Configuration page from the Admin menu or from the Search menu.
-
Select the Case Synchronization master configuration.
-
Click + next to the Case Synchronization master configuration.
-
In the Master Configuration Details zone, configure the following values.
a. Configure the Service Request URL value with the following CX service request API
Example:
https://<CX_HOST>/fscmUI/redwood/service/ec/container/sr/details?srNumber=b. In the Case Types section:
- To display a case type in the dropdown, the C1-SRNO characteristic must be configured for that case type.
- Once configured, select the case type which you needed to create case and synchronize it to CX
Adding Oracle Integration Cloud Certificates
Add the Oracle Integration for Cloud (OIC) certificate to the Oracle Utilities Customer Cloud Service stores where ever applicable to send transactions to the OIC layer.
Managing Catalog Services
The REST web service catalog exposes the external system and inbound services used by the Oracle Utilities Adapter. Configure its URL in the OU REST CCS for CCS-CX connection in OIC
To configure the catalog service in Oracle Utilities Customer Cloud Service:
-
Login to Oracle Utilities Customer Cloud Service.
-
Navigate to the Web Service Catalog page either from the Admin menu or the Search menu.
Select REST and add the following services to the catalog:
Service Type Service Name Description Inbound Web Service (REST) C1-CXperson Person Information Synchronization. Inbound Web Service (REST) C1-Person Person -
To get the catalog URL to be configured in OIC connection OU REST CCS for CCS-CX, append “/ouaf/rest/ouaf/openapi/iws/catalog” to the on- premises application.
Example:
http(s)://<CCS_HOST>:<CCS_PORT>/<ContextRoot>/ouaf/rest/ouaf/openapi/iws/catalogIf using Oracle Utilities Customer Cloud Service, the format should be:
https://{host}:{port}/{tenant}/{domain}/{appName}/rest/ouaf/openapi/iws/catalog
For more information about configuration, refer to the Oracle Utilities Customer Cloud Service documentation. The documentation is available on Oracle Help Center.
Batch Jobs
Run the following batch process to process Person synchronization requests and send messages to Oracle Integration Cloud.
| Batch Code | Description |
|---|---|
| F1-SYNRQ | Sync Request Monitor |
To submit the batch:
-
Open Batch Job Submission and select F1-SYNRQ.
-
Enter the batch parameter values listed below.
Parameter Value Description maintenanceObject F1-SYNC REQ Maintenance object for synchronization requests. isRestrictedByBatchCode true Restricts processing to requests whose current state is associated with this batch code. restrictToBusinessObject C1-PersonSynRequest Restricts processing to Person synchronization requests. restrictToBOStatus PENDING Restricts processing to requests in Pending status. -
Submit the batch.