1. REST API Guide
  2. About Siebel Open Integration

About Siebel Open Integration

Siebel Open Integration enables organizations to expose Siebel CRM processes as REST APIs. It supports both standard and customized applets, views, business services, and workflows, enabling headless operation. You can use Open Integration to build custom user interfaces, integrate with external systems, and support Internet of Things (IoT)-driven event flows.

Open Integration reuses existing Siebel CRM configurations and customizations when creating APIs. This eliminates the need to reimplement user interface logic as business services or workflows, helping reduce development effort and technical debt. It also provides metadata access for alternative user interface frameworks and delivers performance and scalability comparable to existing Siebel CRM REST APIs.

In addition to API exposure, Open Integration includes capabilities for payload transformation, process orchestration, and event-driven integration. These capabilities help external applications interact with Siebel CRM processes through consistent, maintainable, and standards-based integration patterns. The framework also supports modern integration use cases, including AI-driven automation and industry-specific solutions.

The key benefits offered by Open Integration are:

  • Transformation mappings: Define mappings to transform request and response payloads so integrations align with external API contracts and industry models, without adding transformation logic to custom code.
  • Declarative orchestration: Configure multi-step execution flows by using a domain-specific language (DSL). The DSL supports step sequencing, conditional routing, success and failure transitions, and looping where required.
  • Event publish and subscribe: Support asynchronous publish and subscribe patterns for event-driven integration scenarios. This helps reduce tight coupling between systems and improves responsiveness for event-triggered business processes.
  • Framework for industry solutions: Provide a reusable foundation for industry teams to deliver standards-aligned assets, such as transformations and DSL patterns aligned with industry APIs.
  • Git-based extensibility: Manage extensions in a source-controlled model so customer changes remain separate from Oracle-delivered updates. This helps reduce upgrade risk and simplifies ongoing maintenance.
Note:
  • Minimum Siebel Version for Integrations:

    Siebel Open Integration requires Siebel version 26.5 or higher for Siebel Enterprise Server.

  • MinimumSiebel Version for Open Integration:

    Siebel Open Integration requires Siebel version 25.6 or higher for Siebel EnterpriseServer.

  • MinimumSiebel Version for using Open Integration's Cache Configuration:

    To use the Cache configuration feature in Siebel Open Integration, you must have Siebel version 25.10 or later. For versions earlier than 25.10, ensure that the cache enabled flag is set to false.