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.

WebSphere MQ File Transfer Edition provides an enterprise-ready managed file transfer capability that is both robust and easy-to-use. WebSphere MQ File Transfer Edition exploits the proven reliability and connectivity of WebSphere MQ to transfer files across a wide range of platforms and networks. In this IBM® Redbooks® publication, we provide a complete guide for getting started with WebSphere MQ File Transfer Edition. In Part one of the book, we provide a technical overview of the product and provide installation, configuration, and administration guidance for distributed and z/OS® platforms. In Part two, we provide a series of scenarios to show how you can use WebSphere MQ File Transfer Edition to create managed file transfer solutions. These scenarios range from simple point-to-point transfers through to resource monitoring and complex scripted transfers that include the use of Apache Ant. We describe each scenario step-by-step, which allows you to follow along in your own environment. In Part three of this book, we discuss topics, such as security, user exits, and the integration of WebSphere MQ File Transfer Edition with other products and solutions. <u>Related publications:</u> <a href="http://www.redbooks.ibm.com/abstracts/redp4533.html">IBM Redguide: Managed File Transfer for SOA using IBM WebSphere MQ File Transfer Edition</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4532.html">IBM Redpaper: IBM WebSphere MQ File Transfer Edition Solution Overview</a>

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.

In this IBM Redbooks publication, we discuss the concepts, planning, and migration paths that you must understand before attempting to migrate source artifacts, which are created by using IBM WebSphere Studio Application Developer Integration Edition 5.1, to IBM WebSphere Integration Developer 6.2. We also discuss how to migrate models that are developed in WebSphere Business Integration Modeler 5.1 to WebSphere Business Modeler 6.2. In this book, we discuss the new features and differences between WebSphere Business Integration Server Foundation and WebSphere Process Server 6.2. We cover discussions around the considerations for target topologies to be migrated to, and we also cover the deprecated features of WebSphere Process Server 6.1. We also give you information that is critical to any upgrade path and help you realize the benefits of the IBM new breed of integration products.

The IBM® System z® platform is the strategic core of business world wide. By using a realistic customer scenario, two IBM teams ventured to demonstrate how to deploy the IBM service-oriented architecture (SOA) portfolio on IBM z/OS® and on z/OS in partnership with additional platforms such as AIX® and Linux® for System z. The teams created the experience that is documented in this IBM Redbooks® publication to explain the work that is required to create, deploy, and test the SOA solution on both z/OS and z/OS with additional platforms. The teams also performed extensive testing to verify the correct behavior of the platforms, products, and applications involved. This Redbooks publication covers the product configuration that is necessary to build the SOA solution described in the project scenario. This book provides useful hints and tips that were discovered during the course of testing to ensure successful solution deployment. It also provides an extensive set of references to other documents that proved useful for building the solution. This book is designed for IT professionals who are interested in creating an SOA solution either entirely on z/OS or on z/OS in conjunction with other platforms. Prior to reading this book, you must have basic knowledge of SOA solutions, z/OS or other platforms, and the SOA products running on those platforms.

This IBM® Red paper books® publication is divided into three parts: Part 1, "Introduction" on page1, provides an introduction to message-oriented middleware and the WebSphere® MQ product. We discuss the concept of messaging, explaining what is new in WebSphere MQ V7.0 and how it is implemented. An overview is provided on how it fits within the service-oriented architecture (SOA) framework. Part 2, "WebSphere MQ V7.0 enhancements and changes" on page 41, explains the new WebSphere MQ V7.0 features and enhancements in detail and includes compatibility and the migration considerations from the previous supported versions. Part 3, "Scenario" on page253, contains a scenario that demonstrates how the new features and enhancements work and how to use them. The sample programs and scripts used for this scenario are available for download by following the instructions in Appendix B, "Additional material" on page379.

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.

Service Oriented Architecture (SOA) promises a great leap forward in the re-use of applications by simplifying application composition. The technology that simplifies application composition is Service Component Architecture (SCA). SCA is an open component architecture for wiring services together to build composite applications. WebSphere Enterprise Service Bus provides the on-ramp and off-ramp to incorporate many different applications and services into an SOA solution. In this IBM Redbooks publication we introduce SCA and how it has evolved from earlier application integration architectures. We explain how WebSphere ESB connects applications and components to the service bus by using adapters and other types of SCA imports and exports. Our main focus is helping you sort through the many choices that need to be made when deciding how to connect applications together to meet the requirements of a business scenario. We propose six different solution patterns, each with alternative implementations to choose from, to take on most integration scenarios. We also provide seven worked examples of some of the alternatives, which are fully described in the text, and are also available as working samples from the ITSO Redbooks Web site.

Service-oriented architecture (SOA) is one of the most important topics on the agenda of any IT person. SOA involves a new vision of how to design, develop, and manage applications. It also has new requirements when building an architecture for the underlying infrastructure. This IBM Redbooks publication is the result of a project managed in the IBM European Design Center, based in Montpellier, France. The scope of the project involved helping a major worldwide customer in the automotive industry to validate and justify an SOA implementation. In particular, the customer wanted to add new business values to work with its partners, by adding new data models. It also wanted to modernize an infrastructure, by adding new Internet interfaces. The customer faced the need to eradicate an obsolete programming language. Furthermore, it wanted to build a smooth migration path, with as few risks and costs as possible. The thought, planning, and architecture of the new system, which included integration of the SOA concepts, was built by the customer with the participation of Atos Origin, a leading international IT services provider. The existing customer IT infrastructure was already built around UNIX systems, IBM System z, non-IBM clusters, SAP solutions, 3270 screens, IMS-DL/I databases, and specific code. SOA was the right solution to connect this existing environment to new components using Java, Web services, and DB2 in particular. This book explores the business needs and the architectural choices that were faced by t