Siebel Application Integration for Oracle Fusion Middleware Guide > Overview of SAI for Oracle Fusion Middleware >

How Does SAI for Oracle Fusion Middleware Work?

SAI for Oracle Fusion Middleware provides a mechanism for making Siebel Web services available through Oracle WebLogic Server. It contains the components shown in Figure 1.

Figure 1. SAI for Oracle Fusion Middleware Workflow

Figure 1 illustrates the functional components involved in processing an inbound Web service called using SAI for Oracle Fusion Middleware.

1. A client application (5) sends a request that is processed by the Web service (4) deployed on Oracle WebLogic Server (2).
2. This Web service deployment communicates through the Resource Adapter (3) to the Siebel Server (1) where the message is passed to the EAI Object Manager.
3. Within the EAI Object Manager, the inbound message is examined and any XML Schema Definition (XSD) referenced in the message is presented to the XSD to the integration object transformation section (6).
4. Next, a cache is consulted to see if an existing integration object is available, and if not, then a dynamic integration object (7) is created and loaded into the cache.
5. This dynamic integration object is then used to pass the data through the target business service and workflow process (8) and interacts with the Siebel business object layer (9).

SAI for Oracle Fusion Middleware Workflow

Figure 1 additionally illustrates the following workflow:

1. The Siebel Server executes one or more instances of the Siebel EAI Object Manager.
2. Oracle WebLogic Server executes one or more instances of the Resource Adapter and instances of the deployed Web services and other client applications.
3. The Resource Adapter provides the communications channel between the Siebel Server and Oracle WebLogic Server.
4. Siebel integration services are implemented as deployments within Oracle WebLogic Server architecture; these deployments include both specific SOAP-based services or generic Siebel RESTful Services.
5. Client applications can be either internal or external to Oracle WebLogic Server instance.
6. At runtime, the XSD referenced in any inbound message is examined, checked against a cache, and if required, converted to a dynamic IO.
7. At this stage, the underlying cache for dynamic integration objects is queried and, depending on the result, a new cache entry is created. The new cache is based on the message format.
8. Business services and workflow processes are the functional service components that provide access to Siebel CRM data through the Siebel Object Model.
9. Business object and business components are representative of the Siebel Object Model through which Siebel data is transferred to and from Oracle WebLogic Server.