Integration Design Considerations & Approach

There are several business today who would want to use Oracle Commerce Cloud (OCC) for their eCommerce needs. Specially since it allows b2b sites alongwith b2c functions in the same site. In addition, they might use Oracle Integration Cloud (OIC) for their integration needs. So, Integration Design will be a critical factor for such businesses. Therefore, I present solution experience from recent project. And, hopefully, this is useful to businesses implementing eCommerce and integrations around it.

Integration Design
Integration Design

This is part 1 of several articles on OCC and ERP Integration using OIC.

Read here on Part 2: Integration Components in OCC, OIC & ERP

Links to rest of the articles will appear here, when done.

Business Integration Design Considerations

Foremost, we need to identify the single Source-Of-Truth System for entities involved in integration, so that we centralize the data and streamline our processes. So, a specific action should occur exactly once. Next, we sync up the data in rest of the systems.

Consequently, we identify the systems where creation of entities need to take place. Furthermore, we allow or restrict modification of data after syncing, in systems.

Business Processes

Below are some of the major business areas for eCommerce.

  • Customer Management including credit score, payments, statements etc.
  • Product SKU & attributes corresponding to functions of procurement, manufacturing, engineering or assembly
  • Product tracking, cycle counts, damaged goods, return goods inspection etc.
  • Order fulfillment including inventory movements, serial number & lot tracking
  • Advanced order fulfillment solutions i.e. back to back orders, consignments

Integration Design Artifacts

Foremost, we need to design Business Messages (i.e. JSONs) for Webhooks and REST APIs in OCC. In addition, JSON Schemas need to be formalized for EBS REST APIs.

Next, system End points (Trigger and Invoke) to be identified as per business process. Finally, mapping needs to be defined between OCC and ICS & between EBS & ICS.

Further, we should plan for audit needs i.e. for intra system message flows and tracking transactions.

Integration Design Technical Aspects

The technical components are listed below.

  • REST APIs in OCC & Authentication
  • REST API creation in EBS for stored procedures (using Integrated SOA Gateway aka ISG)
  • Inbound & Outbound Data Stage for Error Handling & Reporting
  • Logging of API execution messages by module
  • Tracking ids of other system for Customer & Orders


After designing the systems, entities, business process, we can move on to design integration artifacts, endpoints and technical aspects. With these the integration project should move in a planned manner, reducing risk and leading into a successful implementation.


2 Responses

  1. […] Read here on Part 1: Integration Design Considerations & Approach […]

  2. Roy says:

    It’s very easy to find out any topic on web as compared to textbooks,
    as I found this piece of writing at this site.

Leave a Reply