Overview
The specific business functionality supported by applications that integrate WebSphere and SAP varies from one industry to another, and for each individual implementation of this type of solution. The designs that follow illustrate solutions that address Self-Service, Extended Enterprise, and Electronic Commerce functionality.
Select the Runtime pattern that best meets the needs of your e-business solution.
Self-Service designs for small or mid-sized manufacturing companies
As shown in the figure below, small or mid-sized businesses can make use of SAP products in combination with the Self-Service business pattern and the Application Integration pattern.
A small or medium manufacturing company
- has finished successful implementation of SAP R/3
- is clearly challenged to run even this standard SAP R/3
- no transition to mySAP. com is foreseen yet, because of complexity and additional license costs
- the company wants to open up for the internet and e- business
Companies in small and medium business
- often use the SAP standard R/3 with SAP GUI interface
- often have no mySAP. com components like CRM, SCM, or SAP market set etc.
- often precustomize solutions (ready to run)
- future trend to hosted solutions (ASP) with mySAP.com functionality (CRM, SCM) and web enabled (e.g. SAP connect & go)
Application Integration and Extended Enterprises designs for large manufacturing enterprises
This WebSphere/SAP Integration custom design represents multiple different combinations of the following patterns for use by large manufacturing enterprises that are similar to the example criteria for use below.
A holding company wants to have an SAP rollout over all subsidaries and plans to do this over 5 years. They have a mix of 390, Unisys and NT applications, but the main legacy systems run on 390. To reduce risk, the company plans to roll out SAP in three waves : First SAP Finance, then SAP Logistics, and third, go for mySAP.com SCM. In addition they plan to implement the automotive industry solution.
In advance, the company made a detailed analysis of which functions can be migrated to SAP R/3 and found that in total 60% of their business could be handled with SAP R/3. 40% of their business, which consists mainly of the HR payroll system, PPS, CAD, a 390 procurement system and some PC Apps, remain outside of the functionality range of SAP.
Additional requirements are to have a common middleware / integration technology to support internal and internet access needs.
The company today has neither ABAP nor Java skills but wish to develop both. They recognize that most of their younger employees are more interested in learning java.
Electronic Commerce large distributor/retailer enterprises
This WebSphere/SAP Integration custom design represents multiple different combinations of the following patterns for use by large distributors and retailers.
After successful implementation of SAP R/3 the company wants to implement an internet front-end which shows the latest product information and some CRM functions with the following tasks:
- share shipping and product availibility information with customers
- share product prices where special customer arrangements apply
- leverage field sales and service access using pervasive services
- provide realtime order tracking for customers
Also they would like to build up a Web shop for customers. This should include
- a personalized catalog
- order entry to SAP R/3
- price, shipping and availibilty information (same as for CRM)
- order tracking (same as for CRM)
- Payment via credit card and automatic update of SAP Finance accounts
As this is essential for the company it must be available 24hrs a day and orders must be accepted independent of whether the SAP system is available. Orders must not get lost under either circumstances!