EXTENDING IBM WEBSPHERE USING E2OPEN SOFTWARE ON DEMAND FOR MULTI-COMPANY PROCESS MANAGEMENT

Transcription

1 EXTENDING IBM WEBSPHERE USING E2OPEN SOFTWARE ON DEMAND FOR MULTI-COMPANY PROCESS MANAGEMENT E2open, Inc. E2OPEN WHITE PAPER

2 CONTENTS 2 Introduction 3 Extending IBM WebSphere Business Integration (WBI) 4 Scenario 1: WebSphere Business Integration Server Scenario 2: WebSphere Business Integration Server Integrating with WebSphere MQ 8 Scenario 3: WebSphere MQ Scenario 4: WebSphere MQ 5.2 and Earlier 12 Scenario 5: WebSphere Business Integration Connect Scenario 6: WebSphere Application Server Conclusion INTRODUCTION Establishing and managing server-to-server relationships across trading partners spanning a company s multi-tier value chain can be very challenging and cost prohibitive. Trading partners have to manage many different exchange protocols, various transaction formats and multiple process choreographies as required by the business needs and the capabilities of their back-end systems. Extending IBM s WebSphere with E2open software on demand for Multi- Company Process Management (MCPM), organizations can quickly and cost effectively establish and manage synchronized, server-to-server integration between their back-end systems and their partners internal systems. E2OPEN SOFTWARE ON DEMAND FOR MULTI-COMPANY PROCESS MANAGEMENT E2open software on demand for Multi-Company Process Management (MCPM) is a fully-integrated solution for dynamically managing inter-company processes across multiple partner tiers. E2open s solution for MCPM combines multi-company process management workflows, decision support tools, exception management capabilities and an open, service-oriented integration platform delivered on demand (software as a service) to significantly reduce total cost of ownership and enable companies to minimize operational complexity. E2open s solution for Multi-Company Process Management address three core areas: E2open s Supply Chain Coordination Solution provides capabilities to enable companies to manage next-generation inter-company processes including multi-tier visibility, vendor managed inventory, automated procurement, and demand/supply planning. E2open s B2B Integration Solution significantly reduces the cost and complexity of implementing B2B, server-to-server integration with trading partners. E2open s Partner Enablement Solution changes the economics of large scale trading partner enablement by lowering the cost and complexity of onboarding trading partners both large and small, enabling a company to manage inter-company processes across 100% of its supply chain. INTEGRATING WITH E2OPEN E2open integration capabilities are enabled by the E2open Integration Platform software, which provides a comprehensive set of partner integration capabilities and support for an array of communication protocols. Built on a standards-based, service oriented architecture, the E2open Integration Platform is designed around key E2open technologies including: A UDDI-based Network Directory, which enables dynamic use and re-use of stored partner profile and process capabilities An engine for advanced translation, transformation and process choreography A standards-based security and management software and practices Using E2open, an organization can rapidly synchronize their business processes and systems of record with all partners in their value chain. 2

3 E2OPEN AND IBM E2open and IBM have established a strategic alliance to jointly provide customer solutions for managing inter-company processes across the extended value chain. E2open solutions make use of IBM s WebSphere Application Server software, IBM s DB2 database software, IBM Tivoli Software s Secureway platform for security and authentication and IBM Rational software development tools. Additionally, IBM and E2open are planning offerings to integrate and optimize IBM Lotus Software technologies with E2open technologies. E2open solutions are optimized for Intel-based IBM eserver xseries hardware running the Linux operating system. IBM Global Services provides hosting and network management services as a component of E2open s on demand delivery model. To support customers with global deployment capabilities, the companies have created the IBM/E2open Center of Excellence deployment practice to assist customers implement solutions for Multi-Company Process Management. EXTENDING IBM WEBSPHERE BUSINESS INTEGRATION (WBI) IBM s WebSphere Business Integration (WBI) is the IBM business integration solution for process integration, workforce management and enterprise application connectivity. Built on open industry standards with components that work together seamlessly, WebSphere Business Integration can accelerate a variety of integration requirements, including: Creating and deploying new enterprise business processes Synchronizing business events in multiple back-end systems Integrating applications on diverse platforms Transforming information formats en-route between applications Companies that have already deployed IBM WebSphere software products such as IBM WebSphere MQ, IBM WebSphere Business Integration Server, IBM Websphere Business Integration Connect or IBM WebSphere Application Server, have numerous options for extending their existing investment by leveraging E2open. This document examines six reference architectures for how IBM WebSphere software customers can rapidly integrate and leverage E2open by extending the following WebSphere technologies: WebSphere Business Integration Server 4.2 WebSphere Business Integration Server 4.1 WebSphere MQ 5.3 WebSphere MQ 5.2 WebSphere Business Integration Connect 4.2 WebSphere Application Server 5.0 3

4 SCENARIO 1: WEBSPHERE BUSINESS INTEGRATION SERVER 4.2 WebSphere Business Integration Server 4.2 is a complete integration solution available on Microsoft Windows TM 2000, IBM-AIX, HP-UX and Sun Solaris TM for managing internal systems integration. WebSphere Business Integration Server 4.2 consists of: IBM WebSphere InterChange Server IBM WebSphere MQ Workflow IBM WebSphere MQ Integrator Broker for Multiplatforms IBM WebSphere Business Integration Toolset IBM WebSphere Business Integration Adapters UDB DB2 Enterprise Edition WebSphere MQ One of the key advances in WebSphere Business Integration Server 4.2 is the addition of the IBM Web Services Adapter, which greatly simplifies integration with the E2open Integration Platform using standard IBM WebSphere Business Integration Server components (see figure 1). Using Web services for B2B integration is an ideal choice for encapsulating and abstracting private processes within an enterprise and selectively making those processes publicly accessible. Web services can also be used to wrapper other legacy B2B exchange protocols to facilitate transport and exchange. Figure 1. Integration between the WebSphere Interchange Server component of WebSphere Business Integration Server 4.2 and the E2open Integration Platform Software Requirements Integration with the E2open Integration Platform requires WebSphere Business Integration Server 4.2 and WebSphere Business Integration Adapter Framework 2.3 or higher. The WebSphere Interchange Server component of WebSphere Business Integration Server 4.2 enables the deployment of the Web Services Adapter 3.0 or higher. Message Format The message format exchanged between the WebSphere Busniess Integration Server and the E2open Integration Platform in this scenario is constructed of a Simple Object Access Protocol (SOAP) envelope and corresponding XML payload. WebSphere tooling can be used to assist with content creation. The Web Services Description Language Object Discovery Agent (WSDL ODA) shipped with Web Services Adapter automates the creation of business objects. The Web Services Adapter is shipped with a SOAP Data Handler that envelopes and de-envelopes the data in the SOAP envelope. Transport Protocol WebSphere Business Integration Server communicates with the Web Services Adapter using a range of options, including IIOP, JMS or MQ, enabled by the WebSphere InterChange Server component of WebSphere Business Integration Server 4.2. Web services invocation between the WebSphere Business Integration Server and the E2open Integration Platform is handled via SOAP over HTTP(S). 4

5 How the Integration Works Web services simplify document exchange between WebSphere Business Integration Server and the E2open Integration Platform. When the E2open Integration Platform sends documents to WebSphere Business Integration Server, the Web Services Adapter exposes collaborations in the WebSphere InterChange Server component of WebSphere Business Integration Server as Web services that the E2open Integration Platform can call. When the WebSphere InterChange Server component of WebSphere Business Integration Server sends documents to the E2open Integration Platform, the document exchange is handled in much the same way. The Web Services Adapter invokes the Web Service exposed to E2open, again supporting both synchronous and asynchronous invocation. Summary Companies that have deployed WebSphere Business Integration Server 4.2 already have the infrastructure necessary to integrate with the E2open Integration Platform by leveraging the Web Services Adapter and E2open s support for SOAP-based services. 5

6 SCENARIO 2: WEBSPHERE BUSINESS INTEGRATION SERVER 4.1 WebSphere Business Integration Server 4.1 does not support the Web Services Adapter so the integration between WebSphere Business Integration Server 4.1 and the E2open Integration Platform requires a different approach that uses a Server Access Interface (SAI) Servlet and the WebSphere Business Integration Adapter for XML (see figure 2). Figure 2. Integration between the WebSphere InterChange Server component of WebSphere Business Integration Server 4.2 and the E2open Integration Platform Inbound, the Server Access Interface (SAI) allows external processes to request execution of collaborations inside the WebSphere Business Integration Server. The SAI supports call-triggered flows, which support synchronous, non-persistent request/response interchanges. The SAI handles the external requests. Outbound from the Business Integration Server, the XML Adapter Object provides a means for WebSphere Business Integration Server to call services from E2open. Software Requirements In order to integrate with the E2open Integration Platform in this scenario companies must be running WebSphere Business Integration Server 4.1 and WebSphere Business Integration Adapter Framework 2.1 or higher. This enables the deployment of the XML Adapter 3.0 or higher, which can run on AIX, Sun Solaris and Microsoft Windows NT or 2000 Server and which requires an integration broker (in this scenario, WebSphere Business Integration Server and its underlying technologies). A custom servlet also needs to be developed using the SAI. This servlet can be deployed on only those platforms that support WebSphere Business Integration Server 4.1. Message Format The message format in this scenario is XML 1.0. The XML Adapter supports conversions of business objects to and from XML 1.0. The adapter is packaged with WebSphere Business Integration Data Handler for XML, which helps manage the XML over HTTP transactions. To use custom formats other than XML (for example, name value pairs or delimited files), use the data handlers in WebSphere Business Integration Server. Transport Protocol WebSphere Business Integration Server communicates with the XML Adapter via IIOP, the WebSphere MQ transport or JMS. XML service invocation between the WebSphere Business Integration Server and the E2open Integration Platform is handled via XML over HTTP; standard protocols are supported on both sides of the transaction. How the Integration Works This scenario requires a custom servlet developed using the SAI. The servlet is required only for the invocation of WebSphere Business Integration Server by the E2open Integration Platform. The SAI is used to create and deliver a Web servlet that runs on a customer proxy server to manage the exchange of XML documents. When the E2open Integration Platform sends transaction level documents to WebSphere Business Integration Server, the servlet, developed using the SAI, executes WebSphere Business Integration Server collaborations. Only synchronous invocations are supported by the server access framework. 6

7 When WebSphere Business Integration Server sends a document to the E2open Integration Platform, it does so by making a service call to the XML Adapter. This invokes the URL on which the E2open Integration Platform is expecting the document. If the document is being sent over HTTP, a custom XML adapter may have to be developed to manage the invocation of the E2open Integration Platform. Typically though, protocol handlers plug in to the XML Adapter to manage document transfer between WebSphere Business Integration Server and the E2open Integration Platform. Summary This scenario demonstrates that those customers that have deployed WebSphere Business Integration Server 4.1 can leverage industry standard protocols and standards, including XML and HTTP, to exchange transactions and integrate with partners by invoking the E2open Integration Platform. 7

8 INTEGRATION WITH WEBSPHERE MQ WebSphere MQ messaging products enable application integration by helping business applications to exchange information across different platforms, sending and receiving data as messages. WebSphere MQ 5.3 is available on over 35 different platforms including Linux for Intel, zseries, iseries and Microsoft Windows XP. WebSphere MQ messaging products address network interfaces, assure reliable delivery of messages, deal with communications protocols, dynamically distribute workload across available resources, handle recovery after system problems and help make programs portable. Using WebSphere MQ, programmers can use their skills to handle key business requirements, instead of wrestling with underlying network complexities. The most current version of WebSphere MQ is 5.3 but WebSphere MQ has enjoyed a long release cycle and many customers have version 5.2 deployed in their organizations. This section examines the scenarios for using both versions of WebSphere MQ with the E2open Integration Platform. SCENARIO 3: WEBSPHERE MQ 5.3 WebSphere MQ enables application integration by helping business applications to exchange information across different platforms, sending and receiving data as distinct messages. Although WebSphere Business Integration Server includes WebSphere MQ as an integral part of the platform, many customers have deployed standalone versions of WebSphere MQ as well as WebSphere Business Integration Message Broker, which is based on the WebSphere MQ messaging platform. To support such customers, IBM and E2open enable a straightforward approach for establishing and managing message queues between WebSphere MQ and the E2open Integration Platform (see figure 3). This would also enable integration of the E2open Integration Platform and WebSphere Business Integration Message Broker so transformed and enriched data can be used in the E2open environment. Figure 3. Integration Between WebSphere Business Integration Server 4.2 and the E2open Integration Platform Software Requirements To integrate WebSphere MQ and the E2open Integration Platform in this scenario, companies must be running WebSphere MQ 5.3, bundled with WebSphere Business Integration Message Broker. This version provides support for Secure Sockets Layer (SSL), the Internet standard for secure communications, as well as enhancements to the platform s JMS support. Message Format The message format in this scenario is MQ Messages transported by WebSphere MQ and WebSphere Business Integration Message Broker. In most implementations, the E2open Integration Platform performs dynamic transformation of the MQ Message to a specific data format required by a trading partner. This transformation is executed for both inbound and outbound messages. Transport Protocol Inbound and outbound message queues are exchanged between WebSphere MQ and the E2open Integration Platform by WebSphere MQ or JMS transport. WebSphere MQ 5.3 s built-in SSL support secures the transport channel. 8

9 How the Integration Works The integration requires that each WebSphere MQ queue for each appropriate WebSphere MQ Server be mapped to a corresponding queue on the E2open Integration Platform. In this scenario, inbound and outbound MQ messages are queued and managed using the standard MQ messaging techniques between WebSphere MQ and an MQ Channel on the E2open Integration Platform. Monitoring of the implementation is performed by API exits. Monitoring, in conjunction with error handling ensures that messages reach their appropriate destination. Summary The E2open Integration Platform enables the straightforward creation and management of inbound and outbound message queues between WebSphere MQ and the WebSphere Business Integration Message Broker offering that it underpins and E2open. 9

10 SCENARIO 4: WEBSPHERE MQ 5.2 (FORMERLY MQSERIES) WebSphere MQ messaging products enable application integration by helping business applications to exchange information across different platforms by sending and receiving data as messages. WebSphere MQ provides a consistent multi-platform, application-programming interface. A key factor is time-independent processing. This means that messages are dealt with promptly, even if one recipient is temporarily unavailable. MQSeries 5.2 focused on usability enhancements such as MSI Install, Active Directory and built-in authentication, and has achieved Microsoft certification for Windows 2000 Server. MQSeries is an additional release. MQSeries 5.2 improved performance levels with some operations being five times faster than before. It extended the list of over 35 IBM and non-ibm supported platforms to include Linux and Windows It also included enhancements to AS/400 scalability and security, more support for SNA, and synergy with IBM WebSphere. Integration with the E2open Integration Platform through WebSphere MQ 5.2 and earlier is much the same as with v5.3; however, because these versions lack built-in SSL support, customers must construct and manage their own virtual private network (VPN) channel in order to exchange messages in a secure fashion (see figure 4). Alternatively, there is firewall plug-in available that will provide an SSL session with the E2open Integration Platform. Figure 4. Integration Between WebSphere Business Integration Server 4.2 and the E2open Integration Platform Software Requirements Integration with the E2open Integration Platform requires WebSphere MQ 5.2. This version does not provide support for Secure Sockets Layer (SSL) unless the firewall plug-in is employed. Instead, it is recommended that this implementation employ a VPN for secure communications. Message Format The message format in this scenario is MQ Messages, which are transported by WebSphere MQ. In most implementations, the E2open Integration Platform is performing dynamic transformation of the MQ Message to a specific data format required by a trading partner. This transformation is executed for both inbound and outbound messages. Transport Protocol Inbound and outbound message queues are exchanged between WebSphere MQ and the E2open Integration Platform by MQ. JMS transport is not a feature of MQSeries 5.2. A VPN secures the channel. How the Integration Works In this scenario, inbound and outbound WebSphere MQ messages are queued and managed in basic messaging protocol between WebSphere MQ and an MQ Channel on the E2open Integration Platform. Error handling ensures that messages reach their appropriate destination. 10

11 Summary The E2open Integration Platform enables the straightforward creation and management of inbound and outbound message queues between WebSphere MQ and the E2open Integration Platform. Conclusion Customers that have deployed WebSphere Business Integration Server and/or WebSphere MQ - be it standalone or within WebSphere Business Integration Message Broker - already have the technology in-house to integrate with partners through the E2open Integration Platform. Leveraging industry standards like HTTP, XML, SOAP, JMS and more, companies can reliably and affordably create the partner integrations required to enable multi-company, multi-tier process management, a requirement for building more responsive and competitive supply chain capabilities. 11

12 SCENARIO 5: WEBSPHERE BUSINESS INTEGRATION CONNECT 4.2 WebSphere Business Integration Connect 4.2 enables the secure, cost-effective and reliable exchange of information across company boundaries. WebSphere Business Integration Connect is designed to address any size of business with three editions that accommodate the specific operational B2B requirements of the organization. WebSphere Business Integration Connect provides support for a wide range of industry standard protocols and multiple security standards. WebSphere Business Integration Connect 4.2 is a complete integration solution available on Microsoft Windows 2000, AIX Sun Solaris and Linux. WebSphere Business Integration Connect - Express supports AS2 and HTTP. WebSphere Business Integration Connect Advanced and Enterprise editions support RNIF, AS2 and AS1, SOAP / HTTP, and cxml. It also supports the HTTP, HTTPS, SMTP and FTP transports. One of the key advances in WebSphere Business Integration Connect 4.2 is the flexibility of the solution in regards to transport protocols and payload definition. This provides multiple options for integrating with the E2open Integration Platform using standard WebSphere Business Integration Connect components (see figure 5). WebSphere Business Integration Connect is an ideal choice for encapsulating and abstracting private processes within an enterprise and selectively making these processes publicly accessible. Figure 5. Integration Between WebSphere Business Integration Connect 4.2 Enterprise and Advanced editions and the E2open Integration Platform Software Requirements Integration with the E2open Integration Platform requires WebSphere Business Integration Connect Server 4.2. Message Format WebSphere Business Integration Connect stores and transmits any document type including XML (RosettaNet, proprietary, and so on), EDI, text files, binary and that used by the E2open Integration Platform. This flexibility allows the customer to choose the format that best fits their specific implementation requirements. Transport Protocol WebSphere Business Integration Connect can communicate with the E2open Integration Platform over several protocols including RNIF (RosettaNet) AS1 or AS2, depending on the version of WBIC implemented. These protocols can be used over transports such as HTTP, HTTP(S), FTP or SMTP with the respective industry standard packaging. How the Integration Works The flexibility of WebSphere Business Integration Connect, in connecting with the E2open Integration Platform, allows for two primary implementation options depending on the document format. EDI documents can be exchanged using either AS1 or AS2, over SMTP or HTTP(S), respectively. When the E2open Integration Platform sends documents to WebSphere Business Integration Connect, the specific type of channel is invoked according to how WebSphere Business Integration Connect is configured. Summary WebSphere Business Integration Connect is a lightweight, easy to use, cost-effective B2B connectivity tool leveraging a range of B2B protocols and transports with all of the necessary features for transmitting documents securely over the Internet to the E2open Integration Platform. 12

13 SCENARIO 6: WEBSPHERE APPLICATION SERVER 5.0 WebSphere Application Server 5.0 is a comprehensive Java 2 Platform Enterprise Edition (J2EE) 1.3 and Web services technology-based application server that integrates enterprise data and transactions with today s e-business world. The platform provides a rich application environment for developing and deploying dynamic e-business applications that extend back-end business data and applications to the E2open Integration Platform. WebSphere Application Server network deployment offers advanced Web services that can operate across disparate application frameworks and business-to-business applications, providing direct integration to the E2open Integration Platform. Using Web services for B2B exchange is an ideal choice for encapsulating and abstracting private processes within an enterprise and selectively making these processes publicly accessible. Web services can also be used to wrapper other legacy B2B exchange protocols to facilitate transport and exchange. Figure 6. Integration Between WebSphere Application Server 5.0 and the E2open Integration Platform Software Requirements As the foundation of the WebSphere platform and the core J2EE and Web services configuration, WebSphere Application Server 5.0 has been optimized for organizations that need to build and deploy Web services. WebSphere Application Server extends the J2EE 1.3 programming model by providing a comprehensive infrastructure to support the production-ready deployment of Web services-based applications. The platform allows you to build, publish and manage integration-ready Web services that are used by the E2open Integration Platform. Messaging The message format exchanged between the WebSphere Integration Server and the E2open Integration Platform in this scenario is constructed of a SOAP envelope and corresponding XML payload. WebSphere Application Server supports key Web services open standards, including SOAP, Universal Description, Discovery and Integration (UDDI) and Web Services Description Language (WSDL). Transport Protocol Web services can be deployed with a variety of communication mechanisms, including SOAP and HTTP, JMS or Remote Method Invocation Internet Inter-ORB Protocol (RMI /IIOP). Web Service invocation between WebSphere Application Server and the E2open Integration Platform is typically handled on SOAP over HTTP(S). 13

14 How the Integration Works Use of Web services simplifies transaction exchange between the IBM WebSphere Application Server and the E2open Integration Platform. When the E2open Integration Platform wants to send documents to the WebSphere Integration Server, a Web services method is invoked on the WebSphere Application Server. In most applications, several methods are made available on the WebSphere Application Server. The E2open Integration Platform supports both synchronous and asynchronous invocation. Both request-only and requestresponse Web service invocations are supported. When the WebSphere Application Server sends documents to the E2open Integration Platform, the document exchange is handled in the same way. E2open exposes a method as a Web service. WebSphere Application Server invokes the service, again supporting both synchronous and asynchronous invocation. Summary Companies that have deployed WebSphere Application Server 5.0 already have a built-in Web services infrastructure to integrate with the E2open Integration Platform simply by leveraging Web services functionality delivered with the server. 14

15 CONCLUSION As organizations expand their business processes across their extended supply chain, they need to share information and work collaboratively with their customers, suppliers and partners in complex processes that span many organizations. The most critical element to enabling this process is providing robust integration capabilities for each member of the ecosystem. Customers that have deployed WebSphere Business Integration Server, WebSphere MQ, WebSphere Business Integration Connect or WebSphere Application Server already have the technology in-house to integrate with their trading partners via the E2open Integration Platform. Leveraging industry standards like HTTP, XML, SOAP, JMS and more, companies can reliably and affordably create the partner integrations required to enable inter-company, multi-tier process management, a requirement for building more responsive and competitive supply chains. IBM and E2open have partnered to provide solutions that enable you to meet the demands of today s increasingly complex business environment. With WebSphere software from IBM and a proven integration platform from E2open built on IBM s middleware you get affordable, scalable and secure access that helps you collaborate with trading partners securely and dynamically both within your organization and across the value chain. ABOUT IBM WEBSPHERE IBM is the world s largest information technology company, with 80 years of leadership in helping all types of computing platforms, allowing customers to take full advantage of the new era of e-business. IBM WebSphere is the market-leading Internet infrastructure software, or middleware, for creating, running and integrating e-business applications across a variety of computing platforms. Built on open standards such as J2EE, XML and the new Web services standards, and endowed with IBM s core strengths of reliability, scalability and security, WebSphere server software and development tools are used by tens of thousands of customers and have shown 14 consecutive quarters of doubledigit sales growth. FIND OUT MORE To learn more about E2open and integration with your WebSphere infrastructure, visit OFFICE E2open USA California 1600 Seaport Blvd., 5th Floor Redwood City, CA Phone: Fax: Texas 2 Lincoln Center, Suite LBJ Freeway Dallas, TX Phone: Fax: E2open Japan , Mita Minato-ku Tokyo , Japan Phone: Fax: E2open Korea 23-5 Hanwha B/D 22F Yoido-Dong Yeongdeungpo-Ku Seoul, Korea Phone: Fax: E2open Malaysia Suite Menara Citibank 165 Jalan Ampang 50450, Kuala Lumpur, Malaysia E2open Singapore Pte Ltd 152 Beach Road #18-07/08 Gateway East Singapore Phone: Fax: E2open Taiwan 13F/C # 109 Sec. 3 Ming Sheng East Rd. Taipei, Taiwan ROC Phone: Fax: E2open, Inc. E2open and the E2open logo are registered trademarks of E2open, Inc. IBM, the IBM logo, WebSphere, pseries, xseries, DB2, Tivoli, Rational, and Lotus are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both. Microsoft and Windows are trademarks of Microsoft Corporation. Sun and Solaris are registered trademarks or trademarks of Sun Microsystems. Intel is a registered trademark of Intel Corporation. All other marks are trademarks, service marks or registered trademarks of their respective owners. All rights reserved. #WPWSS