This blog is the second entry in a series of step-by-step screenshot guides to set up an integration between Oracle Engagement Cloud and Oracle Commerce Cloud using Oracle Integration Cloud which is detailed in guide here https://docs.oracle.com/cd/E97801_03/Cloud.19A/UsingCCCloudComm/html/index.html. For a full introduction and guidance on how to use this guide please see Section 0 of this series.
*The numbering in this blog links to the numbering in the official integration guide.
1/2. In the guide these steps refer to downloading the integration package so no screenshots are needed.
3. Importing OCC-OECComms_Integration_1.0.par: Once logged into the Oracle Integration Cloud console, click the Integrations options on the menu and then the Packages link on the menu from the left hand side of the window. This will take you to the installed package page. Click the import button on the top right of the screen. Select the .par file.
4. Following the import there are three connections which need configuration.
While in the integrations page, select the menu on the left hand side and select Connections.
Click “configure connectivity”. Add your url settings to the connection.
Then test, save and close.
Click save and you should see a green notification bar with “Connection Oracle Engagement Cloud Comms was saved successfully.”
Enter your Connection base URL to point to your Oracle Commerce Cloud ccadmin url: https://hostname/ccadmin/v1.
Add you Security Token which you can get from your OCC system like this:
Test and save.
5. When enabling the integrations navigate to the integration page from the menu. Use the slider to activate.
Make sure you click “activate” and not “activate and publish”. Do this for all 6 integrations.
When completed you should see this:
By hovering over the cog/wheel you can see how to run the service. If you click this
If you click the link in the endpoint url for accounts for example:
https://host.com/ic/api/integration/v1/flows/rest/OCC_OEC_ACOUNT_CREATE_SSE/1.0/metadata
You will get re-directed to this endpoint description:
Previous Post
Next Post