Using Publish and Subscribe for Customized Integration Topologies

Customers can utilize the hybrid mode for configuring a customized integration topology based on their integration requirements. Following are some sample use case scenarios:

Scenario #1: An existing customer connects their systems (applications) with UCM through a middleware using SOAP protocol, since all their systems are using SOAP messaging. A new requirement is to integrate a newer system that uses REST API. Customer has a choice to either connect the new system directly (stand-alone) to UCM using REST protocol or to configure a new middleware using REST protocol and connect the new system to UCM through this new REST middleware.

Scenario #2: A new customer has multiple systems (applications) supporting REST API, and several legacy systems supporting only SOAP message. To integrate all their systems with UCM, customer can configure two middleware systems, one for supporting REST API and the another for supporting SOAP. UCM can be configured to work with these two middleware systems; the external systems can integrate with UCM through the middleware based on the system's supported protocol.

Diagram of a Hybrid Mode Scenario - UCM connects to multiple middleware systems, and multiple stand-alone external systems.