Introduction by Pat Flanders

Are you integrating to SAP applications using SAP Business Connector? SAP has announced they will no longer produce new versions of SAP Business Connector. As a result, users of SAP Business Connector software will need to resolve an immediate business problem by (1) migrating to SAP NetWeaver XI/PI; (2) remaining on back level versions of SAP Business Connector; or (3) using an industry-proven SOA platform solution. Replacing proprietary integration technology can be cost-prohibitive-- especially for organizations with limited resources, or those undertaking an expansive SAP consolidation effort. That's why IBM is partnering with Miracle Software to offer SAP Business Connector users a fast, easy, and cost-effective migration option based on IBM's market-leading integration software from the IBM WebSphere integration suite. Today’s MarketWatch segment will focus on migration from SAP Business Connector to IBM WebSphere, touching a little bit on how customers can strategize, plan and execute this migration solution. Intended Audience: The intended audiences for this document are customers who have SAP Business Connector and are looking for alternative solutions.

1. What is SAP Business Connector Architecture:

SAP Business Connector allows you to extend your business processes over the Internet and integrate non-SAP applications using common interface standards. It allows for bi-directional, real-time, as well as asynchronous communication to and from the SAP Server.

You can think of SAP Business Connector architecture as having either one or two functional components, a server component and an optional client component. The server component is responsible for handling incoming XML messages and executing the appropriate SAP transactions via standard SAP BAPI, IDOC, or RFC interfaces. The client component is often installed on the same hardware system as the external application and is responsible for interfacing to that system and converting integration data to or from an XML format if necessary.

The BC Migration Tool is designed to be able to replace both the server and client components, or just the server component, if a phased approach is preferable.

2. Why Migrate From SAP Business Connector:

The growing demand to integrate SAP to external applications through the internet drove the urgent need for a temporary solution to address this requirement. SAP Business Connector was introduced to integrate with SAP applications and function as a translator/gateway to the internet. Its primary role was to translate SAP messages into XML format, and vice-versa. Over time, the functionality of Business Connector was enhanced to also solve common integration challenges within the firewall. With the announcement of SAP NetWeaver, the SAP XI module within NetWeaver became SAP’s recommended interface mechanism to all SAP Applications. As a result, this new strategy also spelled the inevitable end for the Business Connector technology. In addition, many customers have communicated that they are experiencing issues related to the stability of their installed SAP BC technology. This can also be a driver to consider prioritizing an effort to migrate to a reliable integration platform, especially if there are accelerator tools available to make it cost effective.

3. Can you describe the architecture of the replacement solution? The architecture of the replacement solution is based on IBM WebSphere Message Broker and WebSphere Adapters. WebSphere Message Broker provides the foundation for a flexible, reliable, scalable Enterprise Service Bus, or ESB. An Enterprise Service Bus is the fundamental component for organizations moving towards a Service Oriented Architecture strategy. WebSphere Message Broker also provides key integration capabilities such as content-based message routing, distribution, data transformation, transactional integrity when invoking multiple service calls, asynchronous and synchronous communication management, and enforcement of various integration qualities-of-service such as encryption, auditing, archiving, and once-only delivery. The WebSphere Adapters provide the bridge to the native connectivity with SAP and other packaged, custom, or legacy applications. The Adapters are built upon a common adapter framework and exist as reliable, scalable components in themselves. WebSphere Adapters are rich, multi-threaded engines responsible for managing the connection pool to the source or target application, and ensuring that data can not be lost between the application and the message broker in failure situations.

4. What is the recommended Migration Strategy?

There are two migration strategies for customers to consider.

1. Migrate SAP Business Connector Server Only:

WebSphere Message Broker can replace SAP BC on the server side alone and leave SAP BC, or other XML interface, on the end points as-is. WebSphere Message Broker can then be configured to interface directly to messages or documents sent by the SAP BC client, or directly to the web applications. Customers may choose this option to limit the amount of change impact to their existing infrastructure, while gaining the reliability and support of replacing the most critical risk point in front of their SAP system. In addition, if the client component is connecting to an application that will be retired in the near future, customers may choose this strategy to minimize any additional cost to any such applications.

2. Migrate Client and Server:

Another alternative is to replace the SAP BC technology for both the client component and the server component. This would require replacing the BC server with WebSphere Message Broker, and in most cases, a WebSphere Adapter would only be needed to replace the equivalent functionality of the client SAP BC component. The replacement architecture is optimized to be able to handle end-point documents in various data formats over MQ, JMS, HTTP, HTTPS, FTP/FTPS, batch file, or Web Services. This migration strategy is best for customers who require a supportable architecture that also maximizes reliability, hardware utilization, and one that exercises principles of a true SOA methodology.

5. What is the role of Miracle Software Systems in this Migration strategy?

Miracle Software Systems developed the migration methodology and accelerator tooling to efficiently migrate artifacts from an SAP Business Connector environment to an IBM WebSphere environment. They have developed these to incorporate best practices for migration, based on extensive experience they have in both SAP and the IBM WebSphere domain.

The migration effort is offered as a service. Miracle Software has evolved a three step process to arrive at a fixed cost approach to the migration solution based on a factory delivery model.

Step 1 involves a pre-assessment questionnaire that the customer can use to collect basic information about the setup, infrastructure environment and existing as-is SAP BC solution.

Step 2 is a brief on-site study. Based on the answers provided by the customer in the pre-assessment questionnaire, a Miracle Software technical team will be engaged to confirm, further understand, and augment the details of the current SAP BC environment. During this study, existing interfaces will be inventoried and classified into categories by complexity (Low, Medium, and High).

Step 3 results in an executable Statement of Work, or SOW. Based on the information gathered in Step 2, a formal executable SOW with details of hardware, software and services costs involved in the migration effort will be provided to the customer.

6. So what should customers do to find out more information?

That’s a good question. There is a white paper covering the migration methodology in more detail. That paper is available for download on the main podcast web page.