This IBM Redbook provides a step-by-step migration guide from previous releases of WebSphere InterChange Server to Version 4.3 for AIX and Windows. A comprehensive outline of the new features of WebSphere InterChange Server after Release 4.1.1 is provided. Planning requirements and pre-migration tasks are discussed in addition to the detailed technical steps required for a successful migration. WebSphere InterChange Server, a key component of WebSphere Business Integration Server, provides the capability to enable heterogeneous business applications to exchange data. It addresses the need for efficiency and flexibility in automating and synchronizing business activities. WebSphere InterChange Server 4.3 provides an important base level for delivering support to new operating systems, as well as reliability, availability, scalability, performance, and security enhancements, including use of open standards. This book is intended for an audience that is familiar with the WebSphere InterChange Server product and wishes to migrate an existing solution on a previous version of WebSphere InterChange Server to Version 4.3. Information is also included for those less familiar with the product or who are interested in an overview of the key new features of WebSphere InterChange Server 4.3.

IBM® WebSphere® Process Server is the next generation business process integration server that has evolved from proven business integration concepts, application server technologies, and the latest open standards. In this IBM Redbooks® publication, we provide guidance for WebSphere InterChange Server users about how to migrate IBM WebSphere InterChange Server and WebSphere Business Integration Adapters to WebSphere Process Server. We discuss the critical concepts that are related to integration solution architecture, migration project planning, and the technical implementation approach. We provide a detailed discussion about the capabilities of the migration tools. In addition, we include various migration examples that show how to upgrade IBM WebSphere InterChange Server and WebSphere Business Integration Adapters to WebSphere Process Server and WebSphere Adapters. The four parts are: - Part 1 introduces the high-level concepts required to comprehend the migration roadmap. - Part 2 discusses relevant migration implementation concepts. - Part 3 covers the standard migration tools to upgrade from WebSphere InterChange Server to WebSphere Process Server. - Part 4 provides comprehensive examples to migrate end-to-end integration solutions.

This IBM® Redbooks® publication provides guidance on how to transition from a WebSphere® MQ Workflow 3.6 environment to WebSphere Process Server V 6.1. It provides a conceptual overview of WebSphere MQ Workflow and WebSphere Process Server, describes new features provided by the WebSphere Process Server, and discusses benefits of a transition to the new environment. The book discusses the transition concepts available for converting a business process from WebSphere MQ Workflow to WebSphere Process Server. It compares human interaction in business processes in WebSphere MQ Workflow to people assignment in WebSphere Process Server and how to map from one to the other. Integration of back-end applications is described for both environments, together with information about how to transition from one to the other. This book compares how clients were implemented in WebSphere MQ Workflow and how the corresponding implementation is performed in WebSphere Process Server. It helps assess the topology in place in WebSphere MQ Workflow and define a corresponding one in WebSphere Process Server, as well as best practices for target topology high availability, scalability, deployment of applications, and administration. This book has two sections: Part 1 provides planning information required to assess the current environment, define the target environment, and plan for a transition from WebSphere MQ Workflow 3.6 to WebSphere Process Server V6.1. Part 2 provides detailed information about transition techniques, ar

In this IBM® Redbooks publication, we discuss the concepts, differences, and migration paths that you must understand before you attempt to migrate the artifacts that you created using the IBM WebSphere® Studio Application Developer Integration Edition 5.1 product to the IBM WebSphere Integration Developer 6.0.2. We also include a discussion on how to migrate models that are developed in WebSphere Business Integration Modeler 5.1 to WebSphere Business Modeler 6.0.2. In this book, we provide guidance on how to migrate the processes that are installed and running in WebSphere Business Integration Server Foundation to the new integration platform. We also tell you how to bring your components and artifacts to this new generation of integration paradigm. Part 1, "Products overview and migration planning" on page 1 of this book provides a product overview and helps you to assess your environment and plan WebSphere Business Integration Server Foundation migration to WebSphere Process Server 6.0.2 Part 2, "Migration procedure" on page 51 provides detailed steps that are required for migration and includes the tools that are available, the artifacts that are involved, and best practices. In this section, we also demonstrate the migration process using practical migration scenarios that cover most of WebSphere Business Integration Server Foundation capabilities, which includes process choreography, human activities and staff assignment, and exception and error handling.

This IBM Redbook describes three major phases in a WebSphere Business Integration (BI) project. We discuss the planning and system design for a WebSphere BI infrastructure designed to support several business integration projects. - We extend the real-life scenario written for another IBM Redbook. Following planning and design, we discuss the implementation of the run-time engines available in IBM WebSphere Business Integration Server V4.3. - The next phase is developing and testing a business integration solution within our infrastructure. The integration solution combines three run-time engines of WebSphere Business Integration Server V4.3. These engines provide for human interaction, straight-through processing, and message brokering and aggregation. - The final phase of our WebSphere BI project involves deploying the solution into the production environment, and how to manage this solution. We address issues such as how to coordinate stopping and starting components, and troubleshooting run-time problems. We end by discussing performance tuning in WebSphere Business Integration Server V4.3.

This IBM Redbook describes the big phases in a business integration project. First, we discuss the planning and system design phase for a business integration infrastructure that should be able to support several business integration projects. When the planning and design is complete, we discuss the implementation of several run-time engines of a WebSphere Business Integration Server V4.2.2 implementation. We also cover the implementation steps for a development environment and an administration environment. The next phase is the development and testing of a business integration solution that can be deployed within the infrastructure. The integration solution combines the powers of the three run-time engines of WebSphere Business Integration Server V4.2.2, providing for human interaction, straight-through processing, and message brokering and aggregation. The last phase of a business integration project is the process of moving the solution to production and determining how to manage this solution, addressing such issues as how to stop and start components in a coordinated way, and where to find answers for run-time problems. The book ends with a discussion about performance tuning that is focused on WebSphere InterChange Server V4.2.2.

Your company has customers on five continents and in every time zone in this on-demand world. Applications throughout the Enterprise run non-stop to support your business. 7x24x365. Or, maybe it is 5x12. If you're going to satisfy your uptime requirement, high availability is an important part of your system design. This IBM Redbook examines valuable design and implementation considerations involved in deploying your highly available WebSphere Business Integration solution, and details the design, implementation, and execution of a sample HA WebSphere Business Integration solution.

Web services are being considered an excellent technology to solve distributed computing challenges in the Internet area. At the same time, investments in business integration are increasing as well. In this IBM Redbook we discuss how Web service technologies can be used in combination with various components and products of the WebSphere Business Integration family. After a review of Web services technology, the book describes a sample Web services based application. This application is then used in integration scenarios based on message flow technology in WebSphere BI Message Broker and collaborations in WebSphere InterChange Server. Besides demonstrating how these products can call Web services, we also investigate how integration solutions of the Message Broker and the InterChange Server can be exposed as Web services as well. A third component of the WebSphere Business Integration family is WebSphere Business Integration Adapters. This publication investigates the use of these adapters based on Web service technologies. Finally, this publication shows the value of exposed message flows and collaborations by invoking them from within Process Choreographer, which is a flow engine running in WebSphere Application Server Enterprise.

This IBM Redbook introduces the reader to the world of EDI. In addition to general terms about EDI, it also introduces a number of products in this area. WebSphere Data Interchange is discussed as the translation engine to map EDI documents to and from documents in other formats. This redbook also introduces two communication products that use Internet technologies: iSoft's P2PAgent and Trading Partner Interchange. In addition to product introductions, the redbook describes several implementation scenarios in a multi-partner and multi-product environment. Besides a network where trading partners only use iSoft's P2PAgent, we also look at a setup where trading partners use a combination of the two products. For each communication product, we investigate several integration options with internal applications and other middleware. We discuss the integration options with the translation product WebSphere Data Interchange and with the process integration product WebSphere BI Interchange Server. The integration technique can be file-based or messaging-based. Finally, we take a look at options to combine the flexibility of the Internet with the reliability of value-added networks. When Internet connectivity is temporarily not available, a trading partner has the ability to use Expedite to dial into IBM's network and send or receive EDI documents. By exploiting the recycle mechanics in iSoft's P2PAgent, we can implement a solution that provides a highly available connection between trading partners. For more up-to-da