Siebel Order Management Infrastructure Guide > Service-Oriented Architecture >
How Siebel C/OM Can Be Integrated with Other SOA Applications
Web Services is the most common enabler of SOA. Siebel applications support both inbound and outbound Web Services. The Siebel application can:
- Generate and read WSDL
- Process and transform XML
- Receive and process Web Service requests over HTTP
- Invoke an external Web Service from any Siebel event, script, or Workflow
Outbound Integration of C/OM Services
You can call an external service from C/OM. Predefined integration interfaces can be implemented or hosted by an external application or by UAN. Service can be provided by an external application, an integration server, a Siebel business service, or a Siebel business process (workflow).
Figure 2 illustrates services integration for outbound integration.
Figure 2. Services Interfaces for Outbound Integration
Calling an External Service from C/OM
The workflow process shown in Figure 3 provides an example of calling an external service from Siebel order management. The figure shows a workflow process that includes a subprocess called Check Inventory Levels. The subprocess includes a step called Perform Inventory Check, which involves a Web service invocation.
Figure 3. Example: Check Inventory Level During Product Recommendations Algorithm
Web Service Performance
C/OM services such as Pricer or Eligibility are designed to work on batches of data to improve end-user response times. Any external service called by Pricer or Eligibility must support a batched interface that processes an entire set of data (such as all line items in an order) in a single invocation. Thus the overhead associated with Web Service invocation and with context establishment within the Web Service is only incurred once instead of, potentially, hundreds of times.