Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Exploring messaging options -- Chapter 1. Introduction -- 1.1 Introducing the products we will use -- 1.2 Integration scenarios -- Chapter 2. WebSphere product family positioning -- 2.1 Messaging systems -- 2.1.1 WebSphere MQ -- 2.1.2 Embedded Messaging -- 2.1.3 Network Deployment -- 2.1.4 Messaging systems summary -- 2.2 Publish/subscribe brokers -- 2.2.1 Embedded Messaging publish/subscribe broker -- 2.2.2 WebSphere MQ Version 5.3 MA0C - Publish/Subscribe broker -- 2.2.3 WebSphere MQ Event Broker Version 2.1 -- 2.2.4 WebSphere MQ Integrator Broker Version 2.1 -- 2.2.5 WebSphere positioning examples -- 2.2.6 Publish/subscribe broker summary -- Chapter 3. Installation and configuration -- 3.1 Overview of software and installation locations -- 3.1.1 Software used in our environment -- 3.1.2 Hardware used in our environment -- 3.2 Overview of WebSphere Application Server installation options -- 3.2.1 WebSphere Application Server Express -- 3.2.2 WebSphere Application Server Base -- 3.2.3 WebSphere Application Server Network Deployment -- 3.2.4 WebSphere Application Server Enterprise -- 3.3 Overview of JMS messaging options -- 3.3.1 WebSphere JMS provider -- 3.3.2 WebSphere MQ JMS providers -- 3.3.3 Generic JMS Providers -- 3.4 Overview of possible JMS solutions -- 3.4.1 Integral JMS - single-base server -- 3.4.2 Integral JMS - multiple-based servers -- 3.4.3 Integral JMS - Network Deployment within a cell -- 3.4.4 Integral JMS - Network Deployment with high availability -- 3.4.5 Integral JMS - Network Deployment between cells -- 3.4.6 WebSphere MQ JMS - no clustered queues -- 3.4.7 WebSphere MQ JMS - clustered queues -- 3.4.8 WebSphere MQ JMS - Network Deployment between cells.

Chapter 4. Migration -- 4.1 Considering different scenarios -- 4.2 Comparison of publish/subscribe functionality -- 4.2.1 Basic WebSphere MQ publish/subscribe function -- 4.2.2 WebSphere MQ Event Broker publish/subscribe function -- 4.2.3 Publish/subscribe function in the other Integrator brokers -- 4.2.4 Migration from "basic" pub/sub to a WebSphere MQ broker -- 4.3 Case 1 -- 4.4 Case 2 -- 4.5 Case 3 -- 4.6 Case 4 -- 4.7 Case 5 -- 4.7.1 Case 5a -- 4.7.2 Case 5b -- 4.7.3 Case 5c -- 4.8 Summary -- Chapter 5. Other considerations -- 5.1 Introduction -- 5.2 Architecture of WebSphere Application Server messaging -- 5.2.1 WebSphere JMS Provider -- 5.2.2 WebSphere MQ JMS Provider -- 5.2.3 WebSphere Application Server Generic JMS Providers -- 5.2.4 WebSphere Application Server Network Deployment -- 5.2.5 Code independence -- 5.3 Design patterns with message-driven beans -- 5.4 Message providers and transactions -- 5.5 Security -- 5.5.1 Basic issues -- 5.5.2 Messaging through a firewall -- 5.5.3 Security issues with message-driven beans (MDBs) -- 5.6 Working with multiple providers -- Part 2 Example scenarios -- Chapter 6. Introduction to scenarios -- 6.1 Brief history of the example company -- 6.2 Impending changes for TZFORU -- 6.3 Net effect on TZFORU -- 6.4 Typical scenarios in infrastructure -- 6.4.1 Web enabling of applications -- 6.4.2 Decoupling applications from each other and the database -- 6.4.3 Sending data to multiple destinations -- 6.4.4 Publish/subscribe model of sharing data -- 6.4.5 Assuring consistency between distributed resources -- 6.4.6 Communication with legacy applications -- 6.4.7 Summary -- Chapter 7. Base setup -- 7.1 Installing DB2 -- 7.1.1 Install DB2 Fix Pack -- 7.2 Configuring DB2 -- 7.2.1 Enable JDBC 2.0 support -- 7.3 Installing WebSphere Application Server -- 7.4 Common tasks in WebSphere.

7.4.1 Starting WebSphere Application Server -- 7.4.2 Stopping WebSphere Application Server -- 7.4.3 Starting the WebSphere Administrative Console -- 7.4.4 Creating JDBC resources -- 7.4.5 Installing an enterprise application -- 7.5 Configuring Embedded Messaging in WebSphere -- 7.5.1 WebSphere JMS Provider -- 7.5.2 Internal JMS Server -- 7.5.3 Listener ports -- 7.6 The messaging samples in WebSphere -- 7.7 Installing WebSphere Studio Application Developer -- 7.8 Overview of WebSphere Studio -- 7.8.1 Common WebSphere Studio tasks -- Chapter 8. Embedded Messaging scenarios -- 8.1 Structure of application -- 8.1.1 Database schema -- 8.1.2 Sub-group 1 -- 8.1.3 Sub-group 2 -- 8.1.4 Sub-group 3 -- 8.1.5 Sub-group 4 -- 8.2 Application verification -- 8.3 Deployment of order entry application -- 8.3.1 Instructions to download application -- 8.3.2 Setting up the database tables -- 8.3.3 Connecting WebSphere Application Server to the database -- 8.3.4 Creation of JMS entities -- 8.3.5 Installation of order entry application -- 8.4 Using the order entry application -- 8.4.1 Creating orders -- 8.4.2 Verifying the behavior of the order entry application -- 8.5 Code snippets -- 8.5.1 Scenario 1: Decoupling applications and database -- 8.5.2 Scenario 2: Sending messages to multiple destinations -- 8.5.3 Scenario 3: Publish/subscribe model of shared data -- Chapter 9. Embedded Messaging scenarios in WebSphere Studio -- 9.1 Embedded Messaging in WebSphere Studio -- 9.1.1 How to set up the project in WebSphere Studio -- 9.1.2 Define the project resources -- 9.1.3 How to define WebSphere JMS Provider resources for server1 -- 9.1.4 How to configure the message listeners -- Chapter 10. Network Deployment scenario -- 10.1 Network Deployment overview -- 10.1.1 Deployment Manager -- 10.1.2 Node Agent -- 10.1.3 Cells -- 10.1.4 Clusters -- 10.1.5 Scope.

10.1.6 Remote file services -- 10.2 Network Deployment scenario -- 10.2.1 Running on a single node -- 10.2.2 Running within a cell -- 10.2.3 Tooling support -- 10.2.4 Our environment -- 10.3 Application setup using WebSphere Studio Application Developer -- 10.3.1 Basic approach -- 10.3.2 Import the application -- 10.3.3 Create a server -- 10.3.4 Configure server resources to use Embedded Messaging -- 10.3.5 Testing the server configuration -- 10.3.6 Server configuration checklist -- 10.3.7 Troubleshooting -- 10.3.8 Moving to WebSphere Application Server -- 10.4 Setting up the environment -- 10.4.1 Installing Network Deployment -- 10.4.2 Reviewing the Deployment Manager configuration files -- 10.4.3 Starting the Deployment Manager -- 10.4.4 Add a node to a cell using a command -- 10.4.5 Add node using the Administrative Console -- 10.4.6 Remove node from a cell using a command -- 10.4.7 Remove a node from a cell using the Administrative Console -- 10.4.8 Start the Node Agent using a command -- 10.4.9 Stop the Node Agent using a command -- 10.4.10 Start the Deployment Manager using a command -- 10.4.11 Stop the Deployment Manager using a command -- 10.4.12 Other Network Deployment commands -- 10.4.13 Exploring the changes -- 10.4.14 Creating a new application server -- 10.4.15 JMS Server -- 10.5 Application setup -- 10.5.1 Installing the enterprise archive file -- 10.5.2 JMS administration -- 10.5.3 Configuring the WebSphere JMS Provider -- 10.5.4 Updating the configuration repository -- 10.5.5 Running the EmployeeDetails application -- 10.5.6 Troubleshooting -- 10.6 Working with clusters -- 10.6.1 Cluster management -- 10.6.2 Creating clusters -- 10.6.3 Adding a new cluster member -- 10.6.4 Creating cluster members -- 10.6.5 Modification of clusters -- 10.6.6 Deploying and managing applications in a cluster -- 10.6.7 Starting clusters.

10.6.8 Stopping clusters -- 10.6.9 Remove cluster -- 10.7 Terms -- Chapter 11. XA coordination with WebSphere Application Server -- 11.1 Introduction to transactions -- 11.1.1 Local transactions -- 11.1.2 Distributed transactions -- 11.1.3 Distributed Transaction Processing Model -- 11.2 Support for transactions in JMS -- 11.3 Support for JMS messaging -- 11.3.1 Asynchronous message handling in message-driven beans -- 11.4 Support for transactions -- 11.4.1 Container-managed transactions -- 11.4.2 Bean-managed transactions -- 11.4.3 MDBs with container-managed transactions -- 11.4.4 MDBs with bean-managed transactions -- 11.4.5 Creation of a new JMS session in a transaction -- 11.4.6 Use of XA resources in a transaction -- 11.5 Architecture of two-phase commit application -- 11.5.1 Steps performed by the application client -- 11.5.2 Steps performed by the OrderConfirm MDB -- 11.5.3 Steps performed by the UpdateCustomer MDB -- 11.6 Deployment of two-phase commit application -- 11.6.1 Instructions to download application -- 11.6.2 Database setup -- 11.6.3 Creation of JMS entities -- 11.6.4 Installation of two-phase commit application -- 11.7 Using the two-phase commit application -- 11.8 Verification of server-side components -- 11.8.1 Effect on database -- 11.8.2 Contents of WebSphere Application Server logs -- 11.9 Code in two-phase commit application -- 11.9.1 Application client code -- 11.9.2 OrderConfirm MDB - container-managed transactions -- 11.9.3 OrderConfirm MDB - bean-managed transactions -- 11.10 Summary -- Chapter 12. Setting up the WebSphere MQ environment -- 12.1 Deciding what must be in the environment -- 12.2 Defining the basic MQ environment -- 12.2.1 Installing the WebSphere MQ V5.3.0.1 product -- 12.2.2 Creating the queue managers -- 12.3 Defining the WebSphere MQ Integrator Broker on ITSOM1.

12.4 Defining the WebSphere MQ Event Broker.