1. Integrating with Oracle Commerce
  2. Integrate with Oracle Unity
  3. Configure Commerce for Oracle Unity

Configure Commerce for Oracle Unity

Once you have set up your Oracle Unity configuration, you need to configure Oracle Commerce to work with Unity.

To complete the configuration, you must configure the integration settings in the Oracle Integrations page. You must also configure the property mapping for profile and account enrichment. To use Commerce with Unity:
  • Enable Unity Integration from the Oracle Integrations Page.
  • Define profile and account enrichment.
  • Optionally define new custom properties on Account and Profile types to be populated with Unity data.
  • Define property mappings using the /enrichmentMaps endpoint.
  • Define audiences using enriched profile properties.

Enable Unity Integration from the Oracle Integrations Page

Perform the following steps to set up a Unity integration in Commerce

  1. Use the administration interface to select Settings and then Oracle Integrations.
  2. Use the drop down menu to select Unity Configuration.
  3. Click the checkbox to enable the Unity integration.

Define profile and account enrichment

Once you have enabled the Unity integration, you are presented with the Unity Configuration page, which requires you to:
  • Enter the Server URL
  • Enter the Channel ID
  • Enter the Channel Token
  • Add Unity Users.
You must set the Unity Profile Attributes by selecting the attributes of the data objects available for the Profile, such as Account, Address and Customer. The following attributes are for Account:
  • Account Name - The name of the account.
  • DUNS# - The Dunn & Bradstreet 9 digit business identifier.
  • Employee Total - The number of employees within the company.
  • NAICS Code - The North American Industry Classification System 6 digit code for the business type.
  • SIC Code - The Standard Industrial Classification 4 digit code for the company industry.
  • Year Established - The year the company was established.
  • Account Type - The type of the account.
  • Account Status - The status of the account.
  • Annual Revenue - The annual revenue of the company.
  • Line of Business - The line of business.
The following attributes are for Address:
  • Account ID
  • Address Line 1
  • Address Line 2
  • City
  • State
  • AV is Valid - A flag that indicates if the address is valid or invalid
  • Commerce Address Type - The type of address, for example, Shipping or Billing.
  • Latitude
  • Longitude
Set the Unity Behavioral Attributes, which include:
  • Customer ID
  • Severity - The severity level of the incident, including Critical, Major and Minor
  • Sentiment
  • Coupon Code
Set the Unity Transactional Attributes, which include:
  • Customer ID
  • Order Date
  • Quantity
  • Discount
  • Subtotal
  • Tax Total
Set the Unity Product Attributes:
  • Product ID
  • Product Name

Set any other attributes necessary for your environment.

Once you have selected the attributes, save the page. Commerce creates the profile extension table with the selected attributes.

Obtain the Unity client credentials

Use the Identity Cloud Service administration console for the Unity instance. Then navigate to your Oracle Unity Data Platform application instance by accessing Oracle Cloud Services and selecting CXUNITYSI-commerceoudp). You can obtain a client ID/Secret using the Configuration tab. Test your configuration using the Provisioning tab. Refer to How to Access Oracle Identity Cloud Service for detailed information on working with Identity Cloud Services.

Before you can configure an integration, you need to collect the Oracle Unity API configuration settings. You will need the following information:

Property Description
Token URL This is the URL to the Identity Cloud Service Oauth2 Token API. Use the following format: https://idcs-xxxxxxx.identity.oraclecloud.com/oauth2/v1/token
Username The name of the Unity API user with access to the Unity API. You must have the Instance Admin role access.
Password The Unity API user's password.
Client ID The client ID of the Unity application.
Client Secret The client secret for the Unity application.
Tenant URL The URL of your Unity instance.
IDCS App Scope The IDCS scope for the Unity application in the form https://unityTenantUrl/cxunity.
Tenant Key The MCPS tenant access key. If you do not know this key, contact your Unity administrator.

You must also configure the Oracle Object Store (OOS), which contains the Object Store Pre-Authenticated Request (PAR) URL, which is the URL used by Commerce to upload incremental export files. For information on creating this URL, refer to Using pre-authenticated requests.

Map your properties

To synchronize Profile and Account properties from Unity into Commerce, you need to define the mappings that specify which Unity Account or Customer attributes map to which Commerce Organization or Profile properties. To do this, you must use the Commerce API.

Unity attributes must be mapped onto existing Profile and Organization properties. You may want to create custom properties to receive these mappings. Before defining the property mappings, the Organization and Profile types should be extended using the itemTypes and shopperTypes endpoints.

The following is an example of an itemTypes endpoint:
PUT  /ccadmin/1/itemTypes/organization

{
  "specifications": [
    {
     "label": "Account Notes",
     "id": "internal_notes",
     "default": null,
     "required": false,
     "localizable": false,
     "internalOnly": false,
     "textSearchable": false,
     "searchable": false,
     "multiSelect": false,
     "type": "richText",
     "uiEditorType": "richText"
    }
  ]
}
The following is an example of a shopperTypes endpoint:
PUT   /ccadmin/v1/shopperTypes/users

{
    "properties": {
        "social_media_rating": {
            "label": "Social Media Rating",
            "type": "shortText",
            "uiEditorType": "shortText",
            "internalOnly": false,
            "default": null,
            "required": false,
            "audienceVisibility": "all"
        },
        "top_brand": {
            "label": "Favorite Brand",
            "type": "shortText",
            "uiEditorType": "shortText",
            "internalOnly": false,
            "default": null,
            "required": false,
            "audienceVisibility": "all"
        }
    }
}

Define properties using the /enrichmentMaps endpoint

Once you have extended the properties, you must define property mappings using the /enrichmentMaps endpoint. For example: 
PUT  /ccadmin/v1/enrichmentMaps

{
    "IDGraphRuleName": "occ1",
    "subRuleName": "OCC_Profile_Subrule",
    "configMap": [
        {
            "sourceName": "Social_Score",
            "sourceType": "string",
            "targetName": "social_media_rating"
        },
        {
            "sourceName": "top_brand",
            "sourceType": "string",
            "targetName": "top_brand"
        }
    ],
    "source": "customer",
    "target": "profile"
}