WebSphere Adapter for Siebel Business Applications

Scenario

An integrated solution is made up of applications written in a variety of languages and running on a variety of operating systems. The applications might exist on the same physical computer or they might reside on other systems, such as an enterprise information system (EIS). The solution might involve custom-written applications interacting with off-the-shelf programs. A vital component of the integrated solution is the WebSphere® Adapter. A typical scenario involves a WebSphere Adapter making an EIS application available as a service that can be called by other components in the solution. WebSphere Adapters expose these services without disrupting the programming and data associated with them. Businesses large and small can make adapters part of their integration strategy.

Consider the example of a stock-purchase program (StockPurchase). The program needs to check the credit of customers before buying stock for the customers. An application that provides the credit ratings resides on a CICS® server.

Similarly, the StockPurchase program needs to be notified when a stock price changes. An application that provides this notification resides on an SAP server.

StockPurchase could interact with these two applications, but it would need to know the underlying API and data structures of the two applications. Instead, it makes use of WebSphere Adapter for SAP and the Adapter for CICS (ECIResourceAdapter) to create an integrated solution.

The enterprise service discovery wizard of each adapter discovers the applications on the servers and creates components to represent the applications.
  • The enterprise service discovery wizard creates an import component (Customercredit) to represent the application on the CICS server because the StockPurchase initiates the interaction.
  • The enterprise service discovery wizard creates an export component (Stockprice) to represent the application on the SAP server because the interaction (the notification of the stock price) originates at the SAP server.

StockPurchase can now invoke the CustomerCredit import to get the credit rating. The interaction is a two-way or request-response interaction. StockPurchase makes the request (which is performed by the application on the CICS server), and CustomerCredit responds with the ratings.

The StockPurchase program also receives notification when a stock price changes. The application resides on an SAP server. Adapter for SAP enables the interaction between the application on the SAP server and the StockPurchase component.

This image is described in the surrounding text.

How a stock purchase component uses external services as part of its solution


Terms of use |

Last updated: Thu 12 Oct 2006 03:37:05

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)