Native Integration with Oracle CPQ for Configuration

Experience seamless integration and optimal performance with the new native integration between Oracle Commerce and Oracle CPQ for complex product configuration.

Highlights :

  • Native integration between Oracle Commerce and Oracle CPQ.
  • Introduced new Commerce REST APIs for CPQ interactions.
  • Takes advantage of the high availability and scale of Storefront servers.
  • Streamlined experience that takes advantage of the latest version of APIs from Oracle CPQ.
  • Integrates with the new “Get Configuration Layout Attribute Data” CPQ API  that provides metadata specific to the layout and it is more performant compared to the corresponding layout API in the SSE implementation.
  • Leverages Coherence cache for caching layouts and also provides cache invalidation post layout changes on the Oracle CPQ ensuring optimal performance for configuration flows.
  • Brand New User experience on OSF with redesigned navigation flows aligned with new reference store.
  • With out-of-the-box UI and APIs implementation costs are reduced.
  • Periodical updates to the integration to take advantage of new CPQ features.

Steps to Enable

1. Register Oracle Commerce as Client application on Oracle CPQ. Please invoke below API using basic authentication.

URI: POST <CPQ Host>/rest/v1/clients

Sample Payload:

{

"name": "OCCS Client Application",

"description": "OCCS Client Application",

"expires": 600,

"refreshExpires": 3600,

"clientKey": "occs_client_cred",

"grantType": "ClientCredentials"

}

2. Make a note of clientId and clientSecret from the response in Step 1 to complete the configuration in Oracle Commerce.

3. A new user with login as 'system_user_occs_client_cred' is created with type set to FullAccess.

Steps to set-up Oracle Commerce

  1. Login to the Administration Console.
  2. Navigate to Settings -> Oracle Integrations.
  3. Select CPQ Native Integration from the drop-down.
  4. Select “Enable Integration”.
  5. Enter values for CPQ Environment “Host URL”, “Client Id” and “Client Secret”.
  6. Save the changes.
  7. Publish the changes.

Tips And Considerations

  1. Please refer 24A REST API documentation for detailed information on the new Oracle Commerce REST APIs.
  2. Please refer to REST API documentation for Get Configuration Layout Attribute Data API for more information
  3. This feature works for Anonymous shoppers also.
  4. Customers using StoreFront Classic are required to build their own UI widgets.
  5. Open Storefront Reference widgets will be made available in an upcoming release.