IBM Websphere Partner Gateway (WPG)


Published on

Websphere Partner Gateway es una solución para proyectos Business-to-Business (B2B) donde manejamos documentos EDI, XML o Binary sobre canales seguros y soportando protocolos como AS1, AS2, AS3, RNIF, SOAP, cXML,ebMS, CIDX, EDI y text files.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IBM Websphere Partner Gateway (WPG)

  1. 1. Business-to-business white paper December 2008 B2B innovation with IBM WebSphere Partner Gateway leveraging SOA and BPM By Jai Singh Arun Mohan Annamalai Shaji Balakrishnan Sreedhar Janaswamy Steven Koehler (IBM WebSphere Software Group)
  2. 2. Business-to-business white paper Page 2 Table of Contents Introduction.............................................................................................................................................................. 3 How IBM’s B2B solutions approach enables innovation and business value ............ 4 IBM WebSphere Partner Gateway is an integrated B2B environment ........................... 6 Partner community management is the core of partner integration................................ 7 Secure communication beyond the enterprise................................................................................ 8 Integration and transformation across heterogeneous IT environment......................... 10 B2B Integration empowered by SOA and BPM is the future of multienterprise integration ................................................................................................................................................................. 13 An innovative approach for B2B integration enabling flexibility and reducing cost: A scenario example .............................................................................................................................. 16 Summary .................................................................................................................................................................... 19 For more information......................................................................................................................................... 20
  3. 3. Page 3 Business-to-business white paper Introduction “Eighty-five percent of CEOs plan to partner to capitalize on global integration opportunities— more than half plan to do so extensively. We also found that outperformers are 20 percent more likely to partner extensively than underperformers. This reinforces what was discovered in the last CEO Study: extensive collaborators outperform their competitive peers.”—IBM Global CEO Study 2008. As companies are forced by market drivers to become globally integrated enterprises, they increasingly need to expand their ecosystems with more and more partners. This expansion increases the need for channel integration. Business-to-business (B2B) projects play a critical role in channel and partner integration with a fundamental challenge of seamless, secure and reliable integration across a multienterprise value chain. Multienterprise data, process and application integration needs are rapidly growing, and so B2B projects are proliferating. The IT user’s challenge is to consistently manage a B2B abstract layer in a multienterprise integration environment to quickly support new, emerging and proliferating transport and communication protocols, standards, and integration technologies as required to support dynamic business needs. Primarily, customers are looking for the following value from a B2B integration provider: ● A single, cost-effective, easy-to-use package based on a powerful management-by-exception paradigm that reduces ongoing operational costs ● A B2B gateway that allows modular configuration and reusable building-block approaches, delivering large-scale, rapid onboarding of trading partners, low maintenance and strong return on investment (ROI) ● An architecture that delivers scalability for both small- and large-scale implementations, supporting mission-critical business processes with automated enablement and comprehensive event support, delivering extreme scalability for even the most demanding workloads, full extensibility and broad interoperability—validated in many small and large innovative deployments across the globe
  4. 4. Page 4 Business-to-business white paper These critical needs arise from recent business and market dynamics such as supply chain integrations, mergers and acquisitions, or spin-offs. As departments increasingly consolidate trading partners into their processes, information exchange is exploding. Data transfer size and frequency are growing at a rapid pace. The need for B2B Integration is crucial for a multienterprise business process platform (ME-BPP). A B2B solution is a critical component of any IT portfolio that addresses a multienterprise integration strategy. How the IBM B2B solution approach enables innovation and business value IBM’s approach to B2B solutions is influenced by our customers’ needs and feedback, market trends, the evolution of standards and technology, customer buying patterns and the input of leading analysts. IBM also aims to align its B2B solutions with the IBM business process management (BPM) and application integration (AI) components of our service oriented architecture (SOA) offerings. This approach ultimately influences how we define our strategy for our B2B solution. IBM’s focused strategy and investment for B2B solutions is based on these key factors: ● B2B needs are increasingly driven by a need for flexibility and agility to support continuous business model innovation. As part of the need for companies to embrace this “flat world” model, companies are expanding the partner ecosystem to support their core processes. ● B2B Integration is an integral part of SOA-based integration platforms, where the distinction between application-to-application or A2A (intraenterprise) and B2B (interenterprise) communication blurs over time. An increasing number of common infrastructure services (for example, transformation, process execution, registries, directories and Internet standards) are being shared and reused by developers. — This is in contrast to a historical paradigm where organizations have implemented B2B capability as an entirely stand-alone, edge-of-the-enterprise function. — This is consistent with SOA to enable consistent description and connectivity among dissimilar existing applications using a common metadata framework. (SOA is also backward-compatible, evolutionary, intelligent, sustainable middleware that can allow enterprises to better track and leverage existing assets.)
  5. 5. Page 5 Business-to-business white paper — Existing B2B standards will evolve to make even stronger use of XML, Web services and other Internet standards. Business process solutions supporting B2B interactions will increasingly be described and exposed through Web service interfaces to support noninvasive interoperability with trading partners. This is very similar to how A2A interactions are described. — IBM expects more B2B standards in various industry verticals that have been historically message-based. These standards will evolve to embed business process and rules intelligence. We see this happening with Web Services Interoperability Organization (WS-I) profiles, Electronic Business using eXtensible Markup Language (ebXML) message handling (with action headers) and chemical industry data exchange (CIDX) messages and continuing to mature within RosettaNet Partner Interface Processes (PIPs). ● B2B Integration is very process-conscious, where customers connect internal processes with B2B flows as part of the enterprise BPM platform and standardize on common standards such as Web Services Business Process Execution Language (WS-BPEL) and Web services. These connections can include the modeling of existing electronic data interchange (EDI) and XML messages, where process logic and business rule relationships can be created between purchase orders and invoices, and where rules associated with timeliness, cardinality (one-to-many relationships between messages), as well as roles and responsibilities of trading partners, can be defined and enforced. This trend builds upon and extends process-conscious B2B exchanges such as PIPs pioneered by RosettaNet from UML models. ● B2B Integration includes several components: — Connectivity services — Industry standards (AS1, AS2 and AS3) — Nonrepudiation of data — Transformation services (EDI, for instance) — Process execution capabilities (B2B protocols) — Integration (with internal processes, systems and people) — Monitoring capabilities at the business level and the IT level — Trading partner management and governance over trading partner relationships ● B2B Integration extends BPM beyond the enterprise to a company’s network of partners. The IBM WebSphere® Partner Gateway solution provides the structured partner management and governance for this interaction as B2B and BPM dependencies become stronger.
  6. 6. Page 6 Business-to-business white paper IBM’s leadership, through our knowledge and long history of expertise in the B2B sector, allows us to deliver a comprehensive and differentiated B2B solution called WebSphere Partner Gateway. IBM WebSphere Partner Gateway is an integrated B2B environment WebSphere Partner Gateway is a complete set of integrated B2B capabilities, in a single, cost-effective, easy-to-use package. The solution is based on a powerful management-by-exception paradigm that reduces ongoing operational costs. WebSphere Partner Gateway provides these benefits: Its community management paradigm uses an SOA-based, modular approach based on reusable building blocks with partner self-service capabilities. This approach delivers large-scale, rapid onboarding of trading partners, low trading-partner maintenance costs and strong ROI. 1. Its SOA-based extensibility framework delivers the flexibility required for applications that can range from large-scale, innovative, global B2B implementations to “niche” gateway applications. 2. Its SOA architecture delivers comprehensive, event-based BPM integration, extreme scalability even under the most demanding workloads and broad interoperability—as validated in large, innovative deployments across the globe. Figure 1: WebSphere Partner Gateway: a highly scalable, components-based integrated B2B environment
  7. 7. Page 7 Business-to-business white paper The current customer adoption of IBM B2B solutions has expanded well beyond our earlier focus on RosettaNet and supply chain management processes (order management, purchase and planning management and inventory management) to varied business areas across every major industry. These include banking, telecommunications, airlines, cargo, insurance, education, health care, logistics and high- tech manufacturing. Partner community management is the core of partner integration Today’s B2B trading partners expect easy onboarding, self management, granular security settings, operational reporting, simulation and alerting capabilities from the community. WebSphere Partner Gateway scores high in each of these areas. WebSphere Partner Gateway is configured using an object- oriented, modular building-block approach, implemented in an intuitive, Web-based graphical user interface. The XML-based import/export facility enables rapid onboarding of trading partners in large volume with minimal effort. The WebSphere Partner Gateway console is reserved for authenticated users only. Trading partner users securely log in to the console through a Web browser using their user name and password. Each trading partner has administrator group users who manage the permission of the other user groups. Trading partners can manage the certificates that can be configured at the partner, protocol and connection level. The WebSphere Partner Gateway console ensures confidentiality by allowing trading partners to view only the documents that were sent or received by them. Reporting tools in WebSphere Partner Gateway display document information, including payload details, volume and status, such as overdue EDI functional acknowledgements. WebSphere Partner Gateway provides a generic document viewer and process-specific viewers for Autonomous System (AS), RosettaNet and ebMS. This support offers users a wide range of search options so that they can easily locate the intended business document. Process-related viewers provide specific information for AS, RosettaNet Implementation Framework (RNIF) and ebXML documents. The document viewer also helps users find the events associated with any related documents. WebSphere Partner Gateway offers a simple resending option through the user interface (UI) for the failed documents, which can also stop processing if needed.
  8. 8. Page 8 Business-to-business white paper Extensive alert and event management capabilities provide standard and trading partner-specific alerts, based on any of over 300 standard WebSphere Partner Gateway events—or an unlimited number of user- defined events. Alerts can be based on items such as technical events, business events, volume deviation, field ranges and more. An alert can also trigger an internal or external Web service, allowing for the direct invocation of diagnostic or remedial bilateral Business Process Execution Language (BPEL) flows, collaborative Web services at a trading partner and similar responses. Because WebSphere Partner Gateway events are generated for both positive and negative events, you can define powerful and innovative process- collaboration patterns specific to your trading partners. WebSphere Partner Gateway has strong simulation features that are useful for enterprises before deploying into production. The RosettaNet Simulator works through the UI to help simulate real-life RosettaNet document traffic. One trading partner can ping the other ebXML trading partner to get the response and also test the HTTP destinations of other trading partners. Secure communication beyond the enterprise Every enterprise interacts with its customers, trading partners and suppliers, often exchanging sensitive business data. They use different communication infrastructures, such as private value-added networks (private VANs) or public domain Internet. On top of this infrastructure, every business uses different basic communication transports to transfer their business documents between trading partners, customers and suppliers and to their own back-end applications. In this way, they can provide a real-time view of their business transactions to this ecosystem of enterprise, customers and partners. As the B2B integration enables the information that is available to your partners in real time, it should also ensure that the information exchanged is protected from all kinds of security exposures. Here are examples of security requirements for business data exchanged between partners: ● Confidentiality: Data should be read only by the intended partner and should not be read by any other party. ● Identification and authentication: Data should be received only from a known sender.
  9. 9. Page 9 Business-to-business white paper ● Authorization: The sender or the user should be able to perform only the functions that the user authorized. ● Nonrepudiation: There must be a way to verify that the data is sent only by the sender and not by anyone else. Also, the sender should not be able to deny sending the data. A business protocol defines the process, structure and rules of how business documents are exchanged between trading partners. The business document can be in any format, such as EDI, XML or binary. The business documents are exchanged between the trading partners over the available communication channels, adhering to the specifications defined by the business protocol. WebSphere Partner Gateway supports AS1, AS2, AS3, RNIF, Web Services (SOAP), cXML, ebMS, CIDX and PIDX with a wide range of data formats, including EDI, text files, binary and XML. However, the majority of general businesses exchange their business documents using common communication protocols such as HTTP over SSL (HTTPS), FTP over SSL, Simple Mail Transport Protocol (SMTP), Post Office Protocol Version 3 (POP3) and Java™ Message Service (JMS). The exchange of B2B documents over the Internet requires strong security. WebSphere Partner Gateway provides robust security features at two levels: ● Transport level WebSphere Partner Gateway supports SSL communication using server-based and client-based authentication. This support is available for HTTPS and FTP over SSL. In addition, basic authentication over HTTP is also supported. ● Document level Along with the secure transport, you can also protect the actual document by encrypting and signing it. WebSphere Partner Gateway supports S/MIME-based encryption, as well as signing using several encryption and signing algorithms. The user can vary the encryption and signing certificates based on the partner, package, protocol or document type. WebSphere Partner Gateway also provides an interface to manage the certificates.
  10. 10. Page 10 Business-to-business white paper Users can also configure WebSphere Partner Gateway to operate in a mode with Federal Information Processing Standard (FIPS) 140-2 security, often required for interaction with systems owned by the U.S. government and other regulated industries (such as financial and health care institutions). Integration and transformation across heterogeneous IT environments Regardless of the B2B gateway vendor, many B2B implementations require some ability to augment the function provided. Reasons range from a deliberate strategy to innovate or differentiate at the edge of the enterprise, to the need to support narrowly used B2B standards. WebSphere Partner Gateway provides an innovative, SOA-based extensibility framework that enables customers to build, encapsulate, govern and deploy implementation-specific services as part of their B2B implementation. The service encapsulation mechanism in WebSphere Partner Gateway allows specialized communication protocol handlers, content recognition routines, compression or encryption algorithms and other programs to be easily registered, integrated, deployed and protected through the Web-based console for WebSphere Partner Gateway. By extending the WebSphere Partner Gateway architecture through plug-ins, users can add custom functions called exits or handlers at different stages of document processing. Besides adding custom transports, packages, protocols or document types, users can customize existing transports, packages, protocols and document types. Figure 1 shows the stages of document processing that can be customized. Figure 2: Customizing document processing in WebSphere Partner Gateway
  11. 11. Page 11 Business-to-business white paper For example, exits can be used for document encryption, decryption validation and transformation. As WebSphere Partner Gateway receives and processes a document, it can call another program as part of the possessing. Services deployed using the WebSphere Partner Gateway extensibility framework need only be defined and registered once. That’s because the encapsulation mechanism in WebSphere Partner Gateway protects the customer’s investment in these services from release to release. Configuration and management parameters for these services are managed by the same WebSphere Partner Gateway services that manage the functions of WebSphere Partner Gateway itself. So, for example, if a customer uses the WebSphere Partner Gateway extensibility framework to create support for a narrowly used communication protocol, the configuration, administration and management UIs will be the same as those used by the natively supported WebSphere Partner Gateway protocols. This support provides seamless integration and management of user-developed capabilities, with no impact on the learning curve of B2B administrative and operational staff. WebSphere Partner Gateway services can also be stored in and managed by IBM WebSphere Service Registry and Repository, IBM Rational® Asset Manager and other third-party service registries in order to deliver the same level of SOA governance for the ”edge of the enterprise” as for internally deployed services. Interoperability of WebSphere Partner Gateway with competitive B2B gateways and gateway components has been validated through third-party interoperability testing (for example, Drummond certification), as well as large customer deployments with thousands of trading partners across the globe. WebSphere Partner Gateway provides stand-alone B2B gateway capabilities for standard B2B integration needs. The solution also provides extended capabilities in conjunction with other connectivity solutions (such as an enterprise service bus, or ESB) to integrate across various enterprise applications. The documents that are received by WebSphere Partner Gateway usually need to be processed by one or more internal applications. WebSphere Partner Gateway can interact directly with those internal applications using JMS, HTTP or the file system.
  12. 12. Page 12 Business-to-business white paper For more complex integration scenarios, it is common for WebSphere Partner Gateway to interact with an enterprise application integration (EAI) layer, an ESB such as IBM WebSphere Message Broker or IBM WebSphere Process Server. The ESB can then handle the distribution of incoming documents to one or more internal applications using either WebSphere adapters or mediation handlers. If an incoming document needs to be delivered to only one application, WebSphere Partner Gateway can interact with that application directly. Figure 3: IBM WebSphere Partner Gateway extending the reach of integration However, if a document needs to be delivered to more than one internal application based on the content or the document type, using an ESB greatly simplifies the overall infrastructure. Several connection options can be used to integrate WebSphere Partner Gateway and ESB servers. When the documents are sent to a back-end application, detailed metadata can be exchanged over transport headers, which helps in building flexible solutions.
  13. 13. Page 13 Business-to-business white paper Another type of integration is available through the transformation engine, especially with EDI translators such as IBM WebSphere Data Interchange and IBM WebSphere Transformation Extender. Documents can be transformed within WebSphere Partner Gateway or at the ESB level. WebSphere Partner Gateway can validate and generate functional acknowledgments and use a transformation engine to transform XML and other document formats. These transformed documents are then delivered to internal applications. B2B Integration empowered by SOA and BPM is the future of multienterprise integration B2B Integration with BPM and SOA is a primary consideration for many multienterprise integration implementations today, and it will continue to evolve. IBM sees business, IT alignment and business model innovation as the most important aspects of an enterprise strategy. A need for B2B transaction visibility, processing and ability to monitor in real time and take rapid actions are requirements now and will continue to be critical for multienterprise integration environments. This enables B2B Integration to become a core part of any enterprise’s platform for BPM, business activity monitoring (BAM), application integration (AI) and SOA. WebSphere Partner Gateway is based on a highly scalable SOA infrastructure for BPM, leveraging IBM WebSphere Application Server and integrating with complementary functions in WebSphere and other platforms. WebSphere Partner Gateway uses WebSphere Application Server Network Deployment to support consolidated application management—with existing investments, for Web services, and throughout the BPM and SOA infrastructure. For an overview of the functions provided by SOA, see Figure 4. The SOA architecture below depicts how partner services are critical to an SOA platform and how and where it can be integrated into the overall infrastructure.
  14. 14. Page 14 Business-to-business white paper Figure 4: B2B as Partner Services is a Critical Component in SOA Architecture WebSphere Partner Gateway is based on physical component architecture with multiple deployment options—providing high throughput, near linear scalability and many high-availability options. Multiple instances of specific B2B gateway components (such as receivers, gateways, document managers, community consoles and so on) can be dynamically installed and configured on multiple servers (and dynamically decommissioned) to support rapidly changing or unpredictable scalability and throughput requirements.
  15. 15. Page 15 Business-to-business white paper WebSphere Partner Gateway integrates with the WebSphere SOA infrastructure for business process management, extending the reach of BPM solutions to secure B2B transactions with trading partners. WebSphere Partner Gateway supports related middleware services in the IBM Software Group portfolio, including IBM WebSphere Transformation Extender, IBM WebSphere Data Interchange, IBM WebSphere DataPower® SOA Appliances, IBM WebSphere MQ, IBM WebSphere Process Server, IBM WebSphere Business Monitor, IBM Lotus® Forms and IBM WebSphere Application Server. WebSphere Partner Gateway supports BAM by using the Common Base Event specification to format events about B2B transactions and then delivering these events to WebSphere Business Monitor, IBM Tivoli® Monitoring and other third-party monitoring environments. WebSphere Partner Gateway comes with over 300 ready-to-use Common Base Event definitions for technical and business B2B events, and it allows users to create their own custom events. These events can be used today with Tivoli Monitoring for IT-level problem resolution as well as with WebSphere Business Monitor for business activity monitoring—through business-level dashboards used by line-of-business (LOB) executives and other LOB professionals. IBM WebSphere Partner Gateway provides a complete B2B environment that is created by the intersection of B2B, SOA and BPM capabilities, as shown in Figure 3. Figure 5: WebSphere Partner Gateway at the intersection of B2B, SOA and BPM capabilities
  16. 16. Page 16 Business-to-business white paper Example of an innovative approach for B2B integration that enables flexibility and reduces cost: TradeMerit leveraging WebSphere Partner Gateway for Supply Chain Management – Software as Services Solution TradeMerit is a global international trade and logistics services company providing visibility solutions for enterprises and their partners into their supply chains. TradeMerit’s solutions provide proactive supply- chain event management, trade planning and supply chain analytics, and performance analysis. The company delivers on-demand, business-focused solutions that allow users to effectively manage, thoroughly plan and accurately measure performance in their supply chains. TradeMerit’s customers faced many business problems, including: ● Uncertain trade-lane delivery ● Excessive buffer inventory ● Expedited deliveries and premium transportation costs ● Compliance penalties ● Costly manual interventions ● Risky change and optimization These pain points are felt in a business environment that is highly competitive, with demanding customers, government regulations, resource constraints, diminishing time to action and lower margins. TradeMerit’s challenge was to find a highly functional and proven solution to offer supply chain management to its customers. The solution needed to be highly adaptable and to provide BAM, process management and B2B functions—all built upon an SOA foundation for the greatest flexibility and lowest cost deployment. A proven solution with the ability to be operative quickly was very important to TradeMerit, because this technology would be an asset for a company that makes software services the core of its business. Because change and evolution is expected for the company’s future growth, TradeMerit needed its SOA foundation to be highly adaptable and scalable while providing a foundation for the deployment of new business solutions.
  17. 17. Page 17 Business-to-business white paper TradeMerit, an IBM business partner, took less than one year to move from solution investigation and selection to solution deployment. This speed was necessary for TradeMerit, a start-up company, to get a solution to market quickly. The speed in which the solution was deployed was also a testimony to the strength, ease of use and functional richness of IBM technology. IBM was chosen over Microsoft® and other competitive best-of-breed solutions—such as BEA, Tibco, Oracle and SAP—because the IBM WebSphere portfolio was the most complete, well integrated and easiest to deploy. TradeMerit needed software that met its requirements with no need for customization. TradeMerit offers supply chain management (SCM) capability as a software service to its customers alon with browser-based dashboards and analytic capability. g Figure 6: Sample B2B solution implemented by TradeMerit As shown in Figure 4, TradeMerit monitors events in the supply chain through IBM WebSphere Partner Gateway. These events can be in various media and formats including FAX, EDI and messages. TradeMerit noted that the IBM solution was much more sophisticated than a traditional EDI messaging infrastructure. This meant TradeMerit’s solution development was simpler and less prone to error. As a result, TradeMerit could offer its customers a solution that was functionally richer at less cost. Events are passed to
  18. 18. Page 18 Business-to-business white paper IBM WebSphere ESB for mediation and routing and on to IBM WebSphere Process Server. IBM WebSphere Process Server then manages the flow of information and, with IBM WebSphere Business Monitor, the software performs event correlation and analysis, implements rules, generates alerts and measures various key performance indicators (KPIs). TradeMerit’s customers can then view various KPIs and alerts in a browser, using a dashboard that TradeMerit offers as a service to its customers. IBM WebSphere Business Modeler and IBM WebSphere Integration Developer are the tools used to construct the various process flows, KPIs and executable programs. TradeMerit’s customers can then modify alerts and rules and analyze alternate scenarios using the data provided and the dashboard. During each phase of the supply chain, customers can complete various tasks using the dashboard provided by TradeMerit: ● Plan — Establish trade agreements and shipping plans — Set up KPIs — Set up operational targets ● Identify operational rules ● Collaborate — Identify key supply-chain members — Identify compliance and other certification — Identify communication channels (EDI, XML, paper and others) ● Measure — Detect exceptions and trigger resolution process — Provide real-time performance measurements — Monitor dashboards and scorecards ● Optimize — Create alternative scenarios — Analyze the cost and impact of implementing each scenario — Optimize the current supply-chain model to reflect new findings
  19. 19. Page 19 Business-to-business white paper The IBM solution is the core technology of TradeMerit as a business and delivers the following benefits: ● WebSphere software helped TradeMerit maintain a very aggressive development schedule. ● WebSphere software provides an SOA foundation upon which to build new services and evolve offerings without discarding what has already been built. ● Functional richness meant that valuable development effort could be spent on solution delivery versus building infrastructure or middleware services. This richness also reduced complexity, because the complexity of the middleware was contained in the IBM software. ● WebSphere software delivered a highly scalable solution, which is critical for a growing company. ● WebSphere BPM proved to be consumable and rich in function for a small company. Summary B2B integration is evolving and becoming an integral part of the business strategy for most of the enterprises as they grow their ecosystem with partners and customers. The increasing demand for business and IT alignment is driving a critical requirement for end-to-end value chain management and visibility. This requirement fuels multienterprise integration needs beyond the applications and data used by the processes. As a result, B2B technology must leverage SOA and BPM. Multienterprise integration capabilities that leverage BPM, BAM and SOA provide the most advanced capabilities to enable IT users and business users to overcome the challenges of B2B integration. IBM WebSphere Partner Gateway, an industry-leading B2B gateway software offering, enables greater flexibility, faster time to value, lower maintenance cost and strong ROI by providing: ● Centralized and secure B2B trading-partner and transaction management ● Extensive support for data formats, protocols and industry standards ● Extensibility framework to support the integration of third-party applications
  20. 20. ● Component architecture for high scalability, throughput and availability ● The ability to leverage WebSphere Application Server Network Deployment and its capabilities ● Business activity or process monitoring through events formatted using the Common Base Event standard ● Integration with SOA and BPM capabilities For more information For more information or to learn more about business-to-business integration, please contact your IBM marketing representative or IBM Business Partner, or visit the following Web site: © Copyright IBM Corporation 2008 IBM Corporation Software Group Route 100 Somers, NY 10589 U.S.A. Produced in the United States of America December 2008 All Rights Reserved IBM, the IBM logo,, DataPower, Lotus, Rational, Tivoli and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries or both. Microsoft is a trademark of Microsoft Corporation in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates. WSW14042-USEN-00