WebSphere software- Copyright IBM Corporation 2005. All rights reserved. IBM WebSphere Application Server Version 6: Proof of Technology Lab 05 - Service Integration Technologies NOTE: This lAB is optional What You should be able to do In this lab exercise, you will become familiar with WebSphere Application Server Version 6 administration support for Service Integration, JMS and Message Driven Beans(MDB). You will investigate the Message Driven Beans application that is part of the WebSphere Samples Gallery and use the Administrative Console to explore the resources that have been configured for support of application processing. Several resources are required for support of the sample MDB application including Service Integration Resources and JMS Resources. You will see how the Service Integration Resources map to JMS resources, and also also see how these esources are bound in the Web Sphere Application namespace, using the dumpName Space utility. The intent of this exercise is to provide you with basic administration skills for support of messaging applications Exercise Instructions This lab is divided into four parts, with an optional exercise Part One: Install MDB Sample Part Two: Explore the Service Integration and JMS Resources Part Three: Configure and Run the MDB Sample Part Four: Using dumpNamespace Proof of Technology ab 08- Service Integration and JMS Product Introduction Exploration(PI+E) Page 1 of 18
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 08 – Service Integration and JMS Product Introduction + Exploration (PI+E) Page 1 of 18 IBM WebSphere Application Server Version 6: Proof of Technology Lab 05 - Service Integration Technologies NOTE: This LAB is optional What You Should Be Able to Do In this lab exercise, you will become familiar with WebSphere Application Server Version 6 administration support for Service Integration, JMS and Message Driven Beans (MDB). You will investigate the Message Driven Beans application that is part of the WebSphere Samples Gallery and use the Administrative Console to explore the resources that have been configured for support of application processing. Several resources are required for support of the sample MDB application including Service Integration Resources and JMS Resources. You will see how the Service Integration Resources map to JMS resources, and also also see how these resources are bound in the WebSphere Application namespace, using the dumpNameSpace utility. The intent of this exercise is to provide you with basic administration skills for support of messaging applications. Exercise Instructions This lab is divided into four parts, with an optional exercise: Part One: Install MDB Sample Part Two: Explore the Service Integration and JMS Resources. Part Three: Configure and Run the MDB Sample Part Four: Using dumpNamespace
Copyright IBM Corporation 2004. All rights reserved. Part 1: Install the MDB Sample NOTE: If you have not completed the Systems Administration and Management lab you will need to install ND, start the Deployment Manager and federate the node using the addNode command, prior to proceeding with this lab 1. Stop the Deployment Manager. Check the status of the Deployment Manager(dmgr) process. If the Deployment Manger has a status of Stopped, then skip to the next step a. Open a command prompt and navigate to C: WebSphere\AppServerlprofilesldmgrlbin b Issue the stopManager command to stop the Deployment Manager stopManager. bat C. Wait for the Deployment Manager to stop. A successful stop will result in the message being display ADMU4000 Server dmgr stop completed 2. Stop the Node Agent Check the status of the Node Agent (nodeagent) process. If the Node Agent has a status of Stopped, then skip to the next step a. Open a command prompt and navigate to C: WebSpherelAppServerlprofileslprofile 1\bin b Issue the stopNode command to stop the Node Agent and application servers stopNode. bat- stopservers C. Wait for the Node Agent to stop. A successful stop will result in the following ge being displaye ADMU4000: Server nodeagent stop completed. 3. Install the MDB Sample a. Open a command window and navigate to C: WebSpherelAppServerlprofilesldmgrbin b. Issue the command setupCmdLine. bat C. Navigate to C: IWebSpherelAppServerISamples\bin d. Issue the command install-cell dmgrCell -node node1-server server1 samples Message Driven Beans
© Copyright IBM Corporation 2004. All rights reserved. Lab 08 – Service Integration and JMS Page 2 of 18 Part 1: Install the MDB Sample NOTE: If you have not completed the Systems Administration and Management lab you will need to install ND, start the Deployment Manager and federate the node using the addNode command, prior to proceeding with this lab. ___ 1. Stop the Deployment Manager. Check the status of the Deployment Manager (dmgr) process. If the Deployment Manger has a status of Stopped, then skip to the next step. ___ a. Open a command prompt and navigate to C:\WebSphere\AppServer\profiles\dmgr\bin. ___ b. Issue the stopManager command to stop the Deployment Manager. stopManager.bat ___ c. Wait for the Deployment Manager to stop. A successful stop will result in the following message being displayed: ADMU4000I: Server dmgr stop completed. ___ 2. Stop the Node Agent. Check the status of the Node Agent (nodeagent) process. If the Node Agent has a status of Stopped, then skip to the next step. ___ a. Open a command prompt and navigate to C:\WebSphere\AppServer\profiles\profile1\bin ___ b. Issue the stopNode command to stop the Node Agent and application servers stopNode.bat -stopservers ___ c. Wait for the Node Agent to stop. A successful stop will result in the following message being displayed: ADMU4000I: Server nodeagent stop completed. ___ 3. Install the MDB Sample. ___ a. Open a command window and navigate to C:\WebSphere\AppServer\profiles\dmgr\bin ___ b. Issue the command setupCmdLine.bat ___ c. Navigate to C:\WebSphere\AppServer\Samples\bin. ___ d. Issue the command install -cell dmgrCell -node node1 -server server1 - samples MessageDrivenBeans
WebSphere software- Copyright IBM Corporation 2005. All rights reserved. NOTE: This command is running a script through the wSAdmin interface and thus is case sensitive. Please enter the command exactly as shown e. A successful install results in the following message being displayed ADMA5013/: Application MDB Sample installed successfully 4. Start the Deployment Manager a. Open a command prompt and navigate to C: WebSpherelAppServerlprofilesldmgrbin b. Issue the startManager command to start the Deployment Manager startManager bat C. Wait for the Deployment Manager to start. A successful start will result in the ollowing message being displayed ADMU3000/ Server dmgr open for e-business process id is nnn 5. Start the Node Agent a. Open a command prompt and navigate to C: WebSpherelAppServerlprofileslprofile 1\bin b. Issue the startNode command to start the Node Agent and application servers startNode bat C. Wait for the Node Agent to start. A successful start will result in the following message being displayed ADMU3000. Server nodeagent open for e-business, process id is nnn 6. Start the Administrative Console a.openabrowserwindowandnavigatetohttp://localhost:9060/ibm/console b. Login with wsdemo 7. Start server1 a. Access the(Administrative Console)Navigation tree and locate the /- Servers tasks b. Click the Application Servers link Proof of Technology Lab 08-Service Integration and JMS Product Introduction Exploration(PI+E) Page 3 of 18
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 08 – Service Integration and JMS Product Introduction + Exploration (PI+E) Page 3 of 18 NOTE: This command is running a script through the WSAdmin interface and thus is case sensitive. Please enter the command exactly as shown. ___ e. A successful install results in the following message being displayed ADMA5013I: Application MDBSample installed successfully. ___ 4. Start the Deployment Manager. ___ a. Open a command prompt and navigate to C:\WebSphere\AppServer\profiles\dmgr\bin. ___ b. Issue the startManager command to start the Deployment Manager. startManager.bat ___ c. Wait for the Deployment Manager to start. A successful start will result in the following message being displayed: ADMU3000I: Server dmgr open for e-business; process id is nnn. ___ 5. Start the Node Agent ___ a. Open a command prompt and navigate to C:\WebSphere\AppServer\profiles\profile1\bin ___ b. Issue the startNode command to start the Node Agent and application servers startNode.bat ___ c. Wait for the Node Agent to start. A successful start will result in the following message being displayed: ADMU3000I: Server nodeagent open for e-business; process id is nnn. ___ 6. Start the Administrative Console ___ a. Open a browser window and navigate to http://localhost:9060/ibm/console ___ b. Login with wsdemo ___ 7. Start server1 ___ a. Access the (Administrative Console) Navigation tree and locate the [-] Servers tasks. ___ b. Click the Application Servers link
Copyright IBM Corporation 2004. All rights reserved. c. Click to enable the checkbox for server1 An application server is a server which provides services required to run enterprise applications. 团 Preferences Templates.( Start)stop ImmediateStopTerminate 同曾 Select Name c NodeC Version C Status (2 v serverl node1 6.0.0.1 8 TdSelect: cells: wasv6potCellol: nodes: node1:servers:server1 d. Click the Start button to start the server1 process 8. Ensure the MDB Sample is started a. Access the navigation tree in the Administrative Console and click on Applications Enterprise Applications Lists installed applications, A single application can be deployed onto multiple servers. Start Stop Install Uninstall Update Rollout Update F Remove File SelectName Status cy MDBSample b. If the MDBSample application is not started, select the check box and click Start
© Copyright IBM Corporation 2004. All rights reserved. Lab 08 – Service Integration and JMS Page 4 of 18 ___ c. Click to enable the checkbox for server1 ___ d. Click the Start button to start the server1 process. ___ 8. Ensure the MDB Sample is started ___ a. Access the navigation tree in the Administrative Console and click on Applications ÆEnterprise Applications ___ b. If the MDBSample application is not started, select the check box and click Start
WebSphere software- Copyright IBM Corporation 2005. All rights reserved. Part 2: Explore the Service Integration and JMS Resources. 1. Explore the Resources for the Service Integration Bus JNDI Namespace JMS ConnectionFactory Bus Application JMS Destination Code Server a. Access the navigation tree in the Administrative Console and click on Service Integration Buses b. Review the description for Buses a group of i pplica tegration bus supports riented stall New Appl bus at one of the messaging engines associated vith its bus members, e curity E Enviro DNewDelete 回的 囝 Description Messaging bus for samples 日 Service integration NOTE: that the node 1 Samples Bus has been created for all the samples installed on node1 that require the use of an SIBus C. Click on the node 1SamplesBus link d. The name of the Bus under General Properties is unique within the cell e. Under Additional Properties, Click on Bus members f. Review the description of a bus member. g. Notice there is one bus member, server1 in the current bus h. Click on the link Node=node1, server=server1 Proof of Technology Lab 08-Service Integration and JMS Product Introduction Exploration(PI+E) Page 5 of 18
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 08 – Service Integration and JMS Product Introduction + Exploration (PI+E) Page 5 of 18 Part 2: Explore the Service Integration and JMS Resources. ___ 1. Explore the Resources for the Service Integration Bus ___ a. Access the navigation tree in the Administrative Console and click on Service Integration Æ Buses ___ b. Review the description for Buses. NOTE: that the node1SamplesBus has been created for all the samples installed on node1 that require the use of an SIBus. ___ c. Click on the node1SamplesBus link ___ d. The name of the Bus under General Properties is unique within the cell ___ e. Under Additional Properties, Click on Bus members. ___ f. Review the description of a bus member. ___ g. Notice there is one bus member, server1 in the current bus ___ h. Click on the link Node=node1, Server=server1 JNDI Namespace JMS Destination JMS ConnectionFactory Application Code Bus Server ME