《IBM WebSphere Application Server》教程：L04-WASv6_WRD.pdf_大学文库

Copyright IBM Corporation 2005. All rights reserved IBM WebSphere Application Server Version 6: Proof of Technology Lab 04-Websphere Rapid Deployment What You should be able to do The objective of this lab is to provide an understanding of WebSphere Rapid Deployments(WRD) deployment automation features. Wrd gives administrators and developers a simpler and faster way to develop, deploy, construct, install, update, and uninstall a J2EE application. By configuring "watched"directory within the file system, installing an enterprise application is as easy as dropping the ear file into a folder This lab will entail configuring two styles of deployment automation. The first, called autoappinstall will automatically install, update, and uninstall an enterprise application on Web Sphere. You will add the file to the monitored directory, which will cause an install, then overwrite the file, which will cause an update, and finally remove the file which will cause an uninstall. In the final part of this lab you will construct another WRD deployment automation project. However, this new project will use the freeform style. Using this style you will place simple J2EE artifacts, like servlets, jsps, etc, inside the directory and WRD will automatically place those files in the correct J2EE project structure and install the application for you. You will then make updates by overwriting the individual J2EE artifacts instead of the having to overwrite the entire web module or enterprise application Lab requirements List of system and software required for the student to complete the lab Windows 2000 Professional Service Pack 4 is required for this lab exercise Web Sphere Application Server v6.0 has successfully installed The lab source files(LabFiles60. Zip)must be extracted to the root directory (i.e, C: Experience with previous versions of Web Sphere Application Server and the J2EE programming model are also required What you should be able to do At the end of this lab you should be able to Configure WebSphere Rapid Deployment for the autoappinstall deployment automation style Configure Web Sphere Rapid Deployment for the freeform deployment automation style Product Introduction+ Exploration(PI+E) Page 1 of 28

© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology L04 – WebSphere Deployment Automation and WRU Product Introduction + Exploration (PI+E) Page 1 of 28 IBM WebSphere Application Server Version 6: Proof of Technology Lab 04 - WebSphere Rapid Deployment What You Should Be Able to Do The objective of this lab is to provide an understanding of WebSphere Rapid Deployment’s (WRD) deployment automation features. WRD gives administrators and developers a simpler and faster way to develop, deploy, construct, install, update, and uninstall a J2EE application. By configuring a “watched” directory within the file system, installing an enterprise application is as easy as dropping the EAR file into a folder. This lab will entail configuring two styles of deployment automation. The first, called autoappinstall, will automatically install, update, and uninstall an enterprise application on WebSphere. You will add the file to the monitored directory, which will cause an install, then overwrite the file, which will cause an update, and finally remove the file which will cause an uninstall. In the final part of this lab you will construct another WRD deployment automation project. However, this new project will use the freeform style. Using this style you will place simple J2EE artifacts, like servlets, jsps, etc, inside the directory and WRD will automatically place those files in the correct J2EE project structure and install the application for you. You will then make updates by overwriting the individual J2EE artifacts instead of the having to overwrite the entire web module or enterprise application. Lab Requirements List of system and software required for the student to complete the lab. • Windows 2000 Professional Service Pack 4 is required for this lab exercise. • WebSphere Application Server v6.0 has successfully installed. • The lab source files (LabFiles60.zip) must be extracted to the root directory (i.e., C:\). • Experience with previous versions of WebSphere Application Server and the J2EE programming model are also required. What you should be able to do At the end of this lab you should be able to: • Configure WebSphere Rapid Deployment for the autoappinstall deployment automation style. • Configure WebSphere Rapid Deployment for the freeform deployment automation style

g Copynight IBM Corporation 2005. All nights reserved Introduction The J2EE 1. 4 application you will be using is a simple banking application named Web Sphere Bank. It is composed of an EJB, Web, and Application Client module. In the EJB module there is a session bean and an two entity beans. Before being able to fully use the application, you will need to create the database and tables required to run the application and create the datasource resource in WebSphere Application Server so your application can persist data to the database. You will be using a Cloudscape database which is a small footprint, object-relational database based purely on Java. It can be set up very easily and you can quickly test your application to ensure it is working properly. The EJB to RDB mappings and the deploy code have already been generated for you In the first part of the lab you construct the resources necessary to run the WebSphere Bank which the Web Sphere Bank application will use to persist data to the database. In the secong application. This entails creating a database using Cloudscape and then creating a datasourc part of the lab you will create a WRD deployment automation project using the autoappinstall style. This will create a monitored directory on your file system. Once it's configured you will place the Web Sphere Bank EAR file in the directory and verify that the application was installed by using the administrative console and accessing the application itself. However, this version of WebSphere Bank will not have any functionality to perform a transfer of funds or a retrieve balances. The next step will be to take a new Web Sphere Bank Ear file with transfer and file from the directory and check through the administrative console that the application a the at retrieve funds function and overwrite the old Web Sphere Bank EAR file. Again, you will verify tha the application did get updated. The final step of the autoappinstall style will be to remove t indeed, get uninstalled. In the final section of this lab you will create another WRD deployment automation project using the freeform style. You will be using a simple web application that contains one servlet. This level of simplicity will show you the basics of how the freeform style works Exercise Instructions Establish the WebSphere Environment 1. Ensure that the Deployment Manager(dmgr)is started a Open a command prompt and navigate to c: IWeb Sphere\\\ bin c Command Prompt C:\WebSphere \AppServer\profiles\dmgr\bin>. Proof of Technology L04-Web Sphere Deployment Automation and WRU age 2 of

© Copyright IBM Corporation 2005. All rights reserved Proof of Technology L04 – WebSphere Deployment Automation and WRU Product Introduction + Exploration (PI+E) Page 2 of 28 Introduction The J2EE 1.4 application you will be using is a simple banking application named WebSphereBank. It is composed of an EJB, Web, and Application Client module. In the EJB module there is a session bean and an two entity beans. Before being able to fully use the application, you will need to create the database and tables required to run the application and create the datasource resource in WebSphere Application Server so your application can persist data to the database. You will be using a Cloudscape database which is a small footprint, object-relational database based purely on Java. It can be set up very easily and you can quickly test your application to ensure it is working properly. The EJB to RDB mappings and the deploy code have already been generated for you. In the first part of the lab you construct the resources necessary to run the WebSphereBank application. This entails creating a database using Cloudscape and then creating a datasource which the WebSphereBank application will use to persist data to the database. In the second part of the lab you will create a WRD deployment automation project using the autoappinstall style. This will create a monitored directory on your file system. Once it’s configured you will place the WebSphereBank EAR file in the directory and verify that the application was installed by using the administrative console and accessing the application itself. However, this version of WebSphereBank will not have any functionality to perform a transfer of funds or a retrieve balances. The next step will be to take a new WebSphereBank EAR file with transfer and retrieve funds function and overwrite the old WebSphereBank EAR file. Again, you will verify that the application did get updated. The final step of the autoappinstall style will be to remove the file from the directory and check through the administrative console that the application did indeed, get uninstalled. In the final section of this lab you will create another WRD deployment automation project using the freeform style. You will be using a simple web application that contains one servlet. This level of simplicity will show you the basics of how the freeform style works. Exercise Instructions Establish the WebSphere Environment ____ 1. Ensure that the Deployment Manager (dmgr) is started. __ a. Open a command prompt and navigate to c:\WebSphere\AppServer\profiles\dmgr\bin

g Copynight IBM Corporation 2005. All nights reserved Part 1: WRD Deployment Automation"autoappinstall"style: WebSphere Bank In this part you will set up a WRD workspace that supports the Auto Application Install style. You will add an EAR file to the project, update it, and then remove it to see how the changes are reflected on the application server. The automatic application installation configuration creates a single monitored directory that listens for fully composed EAR files or application modules such as War files, EJB jar files, or stand-alone RAR files. If you place EAR files inside this monitored directory, the EAR is automatically deployed to the server. If you delete the EAR file from the monitored directory, then that application is uninstalled from the server. If you place WAR files or EJB jar files in the monitored directory, the rapid deployment tool generates the necessary EAR wrapper and then publishes that EAR file on the server. For RAR files, a wrapper is not created The stand-alone RaR files are published to the server 1. In the command prompt type md C: WRD to create a folder called WRD which will hold the WRD projects that will be defined 口区 : \We bSphere \AppServer\profiles\profile\bin )md C: \WRD \We bSphere \AppServer\profiles\profiled\bin) 2. Navigate to C: WebSphere\profileslprofile1 bin if not already there cd \WebSphere \AppServer\profiles \profile\bin 3. Configure the WRD Deployment Automation project using the"autoappinstall style a. At the command prompt type SET WORKSPACE=C: WRD and press enter. This will set the WRD workspace directory to the folder created in step 3 C: \e bSphere \AppServer\profiles \profile\bin >SET WORKSPACE=C: \RD C: \WebSphere\AppServerprofiles \profile\bin>. b. At the command prompt type wrd-config. bat -project " AutoInstall style " autoappinstall" and press Enter: Note:-project is the name of your WRD deployment automation project and-style is the style that applies to the project C. This command will execute for a minute as it starts to build the project. It will then ask for configuration parameters. You will need to enter the correct information for server Proof of Technology L04-Web Sphere Deployment Automation and WRU Page 7 of 28

© Copyright IBM Corporation 2005. All rights reserved Proof of Technology L04 – WebSphere Deployment Automation and WRU Product Introduction + Exploration (PI+E) Page 7 of 28 Part 1: WRD Deployment Automation “autoappinstall” style: WebSphereBank In this part you will set up a WRD workspace that supports the Auto Application Install style. You will add an EAR file to the project, update it, and then remove it to see how the changes are reflected on the application server. The automatic application installation configuration creates a single monitored directory that listens for fully composed EAR files or application modules such as WAR files, EJB jar files, or stand-alone RAR files. If you place EAR files inside this monitored directory, the EAR is automatically deployed to the server. If you delete the EAR file from the monitored directory, then that application is uninstalled from the server. If you place WAR files or EJB jar files in the monitored directory, the rapid deployment tool generates the necessary EAR wrapper and then publishes that EAR file on the server. For RAR files, a wrapper is not created. The stand-alone RAR files are published to the server. ____ 1. In the command prompt type md C:\WRD to create a folder called WRD which will hold the WRD projects that will be defined. ____ 2. Navigate to C:\WebSphere\AppServer\profiles\profile1\bin if not already there. cd \WebSphere\AppServer\profiles\profile1\bin ____ 3. Configure the WRD Deployment Automation project using the “autoappinstall” style. __ a. At the command prompt type SET WORKSPACE=C:\WRD and press enter. This will set the WRD workspace directory to the folder created in step 3. __ b. At the command prompt type wrd-config.bat –project “AutoInstall” – style “autoappinstall” and press Enter: Note: -project is the name of your WRD deployment automation project and –style is the style that applies to the project __ c. This command will execute for a minute as it starts to build the project. It will then ask for configuration parameters. You will need to enter the correct information for server