You are here: Integrating With CPQ Cloud > Integration Guides > Integration Cloud Service (ICS)



By integrating with Oracle Integration Cloud Service (ICS) middleware, CPQ Cloud can provide an all-encompassing, standard Oracle solution to all integration needs. By using the power of ICS, system integrators can manage all CPQ Cloud integrations from a single location with a consistent toolset. ICS integration enables CPQ Cloud to connect to back office systems, on premise environments, and other Oracle products in a consistent, enhanced manner.

ICS is the recommended go-forward Oracle solution for customers who have previously relied on third-party middleware solutions, including webMethods and Cast Iron, to integrate Oracle CPQ Cloud with a variety of other systems.

For more information on ICS in general, see the Oracle Cloud Integration site.

Existing CPQ Cloud point-to-point integrations with Oracle products (that could be accomplished through ICS middleware) can still be implemented and will function as expected.

Oracle Sales Cloud Integration through ICS

Pre-built integration flows are available for CPQ Cloud-Oracle Sales Cloud (OSC) integrations through ICS to further simplify implementation.

For more information on CPQ Cloud-OSC integration through ICS, and for a step-by-step implementation guide, see the ICS Integration Guides for CPQ Cloud page on My Oracle Support.


ClosedOverview of ICS

To easily integrate applications with each other, use ICS as the middleware.  Any application with an integration to ICS can integrate with any other application with an integration to ICS. 

The ICS interface contains both pre-defined and customized data mappings between applications.  It discovers all SOAP and REST services available from CPQ Cloud.

By leveraging these existing ICS integrations, it is easy to connect two applications through ICS.

ClosedOracle Cloud Adapters

Cloud Adapters simplify and accelerate integration with your SaaS applications. These adapters provide lower costs of implementation and maintenance, ease of use, improved developer productivity and faster time-to-market for SaaS application integrations.

The Adapters enable the ability to create ICS flows, or mappings, and pre-defined Packages, or collections of ICS flows. ICS flows establish the relationship between an application and ICS. With these flows, you do not have to write the SOAP messages that are at the heart of an integration. The messaging has been written, and tested, for you.

For example, an application might map what they call the Customer field to what ICS calls the Name field.  Another application might map what they call the Contact field to what ICS calls the Name field. 

When both applications exchange data, through ICS, referring to ICS’ Name field, they can exchange data even though the individual applications refer to the fields differently.  And, the applications can exchange data without one application knowing how the other defines its fields.

You can create your own ICS flows.  See the Oracle Cloud Integration page for more information.

ClosedOracle Cloud Adapters: An Example Using Oracle Sales Cloud

Leverage pre-defined ICS flows in CPQ Cloud, built by Oracle product development, for the following integrations:

Other required Sales Cloud to CPQ Cloud integrations (such as revenue items, Parts, and Accounts) are part of the CPQ Cloud reference application.  Because these integrations can already occur through existing means, they have not been defined in an ICS flow.

For more information, see My Oracle Support.

Steps to Enable

Before you can leverage the pre-built ICS flows, you must establish a connection between ICS and CPQ Cloud.  For this example, you must also establish a connection between ICS and OSC.  In both cases, this is done in ICS, and the steps are not covered in this document.

For information on how to set up these connections, see the Oracle Cloud Integration page.

ClosedEstablish a Connection From CPQ Cloud to ICS

In CPQ Cloud, you must establish a connection from CPQ Cloud to ICS that complements the existing one from ICS to CPQ Cloud.

  1. In CPQ Cloud, go the Admin Home Page.
  2. Click Integration Center under Integration Platform.

    The Integration Center page appears.

  3. Click Create Integration.

    If you click Create Integration when there are no more available integrations to create, the following message appears:

  4. Select Integration Cloud Service from the Type drop-down.

    Only one entry can be created for each integration type.  Any previously created integration types are disabled, and only uncreated integration types can be selected. 

    The first valid selection is selected by default.

    Only two integrations are available in this release: eSignature and Integration Cloud Service (if enabled).

    Changing the Integration Type will immediately change which fields are present.

  5. Enter a Name and Variable Name.

    Use a name that will make it easy for you to find your integration.

  6. Enter the Discovery URL.

    For Middleware integrations, the Discovery URL is pre-populated with 'https://'.  For example, it might look like this:

    https://<ICS URL>:7002/icsapis/v1/integrations

  7. Enter your ICS Username and Password.
  8. Optionally, click Test to verify your connection to ICS.
  9. Enable your integration by checking Enable Integration.

    Enable Integration is disabled until the Discovery URL, Username, and Password have been entered.

    An enabled integration shows the Discover URL, Username, and Password fields as read-only once it has been saved.

  10. Click Save.

ClosedDisable an Connection From CPQ Cloud to ICS

If a user disables a previously enabled integration—by removing the checkmark next to Enable Integration—a warning appears that this will disable all existing integrations based on that integration type.

When the user clicks Save, this alert disappears, the integrations are disabled, and the Discover URL, Username, and Password fields return to being editable.

Working with Integrations

To use the integration you just created in the Integration Center, you must create an Integration on an existing Process.

ClosedCreating an Integration Process

  1. Click Admin to go to the Admin Home Page.
  2. Click Process Definition under Commerce and Documents.

    The Processes page appears.

  3. For the Commerce Process, choose Integrations in the Navigation drop-down and click List.

    This selection was called Integration XSLs in previous releases.

    The Integrations page appears.  This page lists any XSL Integrations, as well as any Middleware Integrations.

  4. Click Add.

    The Select Integration Types dialog box appears.

  5. Select Integration Cloud Service and click Next.

    The Edit Integration dialog box appears.

  6. The Services drop-down shows a dynamic list of the services available in the CPQ Cloud–ICS Adapter.  Select a Service

  7. Enter a Name and Variable Name.
  8. Select an Action.  This is just a label for the integration to describe how it will be used, and does not have any effect on how it works. 
  9. Click Add.

    The process now appears on the Integrations page.

ClosedEditing or Previewing an Integration Process

  1. Click Admin to go to the Admin Home Page.
  2. Click Process Definition under Commerce and Documents.

    The Processes page appears.

  3. For the Commerce Process, choose Integrations in the Navigation drop-down and click List.

    The Integrations page appears.

  4. Click the name of the integration you want to edit.

    The Edit Integration page appears.

  5. Make any desired changes.
  6. To preview the integration, enter a Transaction ID and click a Preview link.

    This will execute the integration, and may modify the remote site.

  7. Click Update.

Next Steps

ClosedOverview of Next Steps

Now that you have a Integration Cloud Service Integration and a Process that uses it, tie the Integration to a new or existing Action and put the Action on a Layout.  The integration is performed when a user clicks the button. 

Or, if you add the Integration to an existing Action, it will run implicitly with other Actions that a user would normally click. 

For example, a Quote Update Integration process would be run on an existing Quote.  It makes sense to add this Integration to the Action that the user already uses to save the Quote.  You could, for instance, rename the button from “Save” to “Save and Sync” to convey everything that happens when the button is clicked.  Or, leave the button name as it was; functionality is not affected.

After tying the Integration to an Action or Process, and, if necessary, updating a layout to include the Action or Process, remember to deploy the Commerce Process.

ClosedTie an Integration to a Process

ClosedAdd the Integration Action to a Layout

ClosedDeploy Commerce


Actions that don’t have the Integrations tab are not supported for any integration type. The following actions are supported:


Related Topics Link IconSee Also