WebSphere software- Copyright IBM Corporation 2005. All rights reserved. IBM WebSphere Application Server Version 6.0: Proof of Technology Lab 03-Application Management What This exercise is about Web Sphere Application Server v6.0 provides various features which can be used to manage your J2EE 1.4 applications. This exercise will have you update a J2EE 1.4 application using various methods Web Sphere Application Server Version 6 provides facilities for assembling and deploying J2EE Enterprise Applications. This lab exercise will introduce you to the Application Server Toolkit (AST)and guide you through the process of installing an application into WebSphere. You will also become acquainted with some Web Sphere application serving features, as well as perform some common systems administration tasks using the browser based Administrative Console and command line administrative tools The Application Server Toolkit is made up of five components: Eclipse workbench, Assembly Toolkit, Debug component, Distributed Profiling component, and the Logging tools In this exercise, you will be using the Eclipse workbench and Assembly Toolkit components What you should be able to do At the end of this lab you should be able to Use the asT to inspect and make changes to an applications configuration Configure and install applications using the Administrative Console Update applications in Web Sphere Application Server v6 Create and Install Enhanced ears oof of Technology Lab 03-Application Management Product Introduction Exploration(PI+E Page 1 of 42
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 03 – Application Management Product Introduction + Exploration (PI+E) Page 1 of 42 IBM WebSphere Application Server Version 6.0: Proof of Technology Lab 03 - Application Management What This Exercise is about WebSphere Application Server v6.0 provides various features which can be used to manage your J2EE 1.4 applications. This exercise will have you update a J2EE 1.4 application using various methods. WebSphere Application Server Version 6 provides facilities for assembling and deploying J2EE Enterprise Applications. This lab exercise will introduce you to the Application Server Toolkit (AST) and guide you through the process of installing an application into WebSphere. You will also become acquainted with some WebSphere application serving features, as well as perform some common systems administration tasks using the browser based Administrative Console and command line administrative tools. The Application Server Toolkit is made up of five components: Eclipse workbench, Assembly Toolkit, Debug component, Distributed Profiling component, and the Logging tools. In this exercise, you will be using the Eclipse workbench and Assembly Toolkit components. What You Should Be Able to Do At the end of this lab you should be able to: • Use the AST to inspect and make changes to an application’s configuration. • Configure and install applications using the Administrative Console • Update applications in WebSphere Application Server v6. • Create and Install Enhanced Ears
Copyright IBM Corporation 2005. All rights reserved. Exercise Instructions This lab is divided into for Part One: Introduction to the Application Server Toolkit Part Two: Testing the deployed Default Application Part Three: Updating an Application using the Administrative Console Part Four: Introduction to enhanced ear Assumptions This workshop requires that the following products are installed WebSphere Application Server Version 6(ND) Application Server Toolkit (AST) The instructions for this exercise assume that the installation is being performed on a machine If you installed Web Sphere Application Server on another drive or directory, you will needto where the installation directory for Web Sphere Application Server is c: IWeb Sphere lApp Serv make appropriate allowances when following directions. The AST has been pre- installed on your machine and is ready for use in this exercise
© Copyright IBM Corporation 2005. All rights reserved. Lab 03 – Application Management Page 2 of 42 Exercise Instructions This lab is divided into four parts: Part One: Introduction to the Application Server Toolkit Part Two: Testing the deployed Default Application Part Three: Updating an Application using the Administrative Console. Part Four: Introduction to Enhanced Ear. Assumptions: This workshop requires that the following products are installed: - WebSphere Application Server Version 6 (ND) - Application Server Toolkit (AST) The instructions for this exercise assume that the installation is being performed on a machine where the installation directory for WebSphere Application Server is c:\WebSphere\AppServer. If you installed WebSphere Application Server on another drive or directory, you will need to make appropriate allowances when following directions. The AST has been pre-installed on your machine and is ready for use in this exercise
WebSphere software- Copyright IBM Corporation 2005. All rights reserved. PART ONE: Introduction to the Application Server Toolkit (AST) During this part of the exercise you will use the Application Server Toolkit to explore and make changes to a J2EE Enterprise Application. The DefaultApplication, which is one of the sample applications supplied with Web Sphere Application Server, will be used for this exercise. You will use the original Default Application. ear for input to AST, modify the EAR. then save the changes in a separate EAR file. The Default Application consists of a Web Module and an EJB Module. The Web Module contains(3)servlets and several (resource and class)files, while the ejB Modules contains a single Entity Bean that uses Container Managed Persistence. The Entity Bean is bound to the default datasource that uses the Cloudscape database for persistence 1. Launch the Application Server Toolkit a. Use the Windows Start menu to launch the Application Server toolkit. Click Start→ Programs→| BM Web Sphere→ Application Server Toolkit,v6.0÷ Application Server Toolkit Select a workspace BM WebSphere Application Server Toolkit, V6.0 stores your projects in a directory called a workspa Select the workspace directory to use for this session Workspace: E TBMiWebSpherelASTworkspacel Browse Use this as the default and do not ask again OK Cancel b. Accept the default workspace and click OK. oof of Technology ab 03-Application Management Product Introduction Exploration(PI+E Page 3 of 42
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 03 – Application Management Product Introduction + Exploration (PI+E) Page 3 of 42 PART ONE: Introduction to the Application Server Toolkit (AST) During this part of the exercise you will use the Application Server Toolkit to explore and make changes to a J2EE Enterprise Application. The DefaultApplication, which is one of the sample applications supplied with WebSphere Application Server, will be used for this exercise. You will use the original DefaultApplication.ear for input to AST, modify the EAR, then save the changes in a separate EAR file. The DefaultApplication consists of a Web Module and an EJB Module. The Web Module contains (3) servlets and several (resource and class) files, while the EJB Modules contains a single Entity Bean that uses Container Managed Persistence. The Entity Bean is bound to the default datasource that uses the Cloudscape database for persistence. ___ 1. Launch the Application Server Toolkit. ___ a. Use the Windows Start menu to launch the Application Server toolkit. Click StartÆProgramsÆIBM WebSphereÆApplication Server Toolkit, V6.0ÆApplication Server Toolkit ___ b. Accept the default workspace and click OK
Copyright IBM Corporation 2005. All rights reserved. 2. Introduction to the ast workbench a. If you are not familiar with the Eclipse workbench, you might want to go through the Overview to get an understanding of the functions and capabilities of the Application Server Toolkit (AST). Otherwise, skip this step and go to the Workbench(step d b. Click on the globe icon to go to the overview a Resource-IBM WebSphere Application Server Toolkit,V6.0 Eile Edit Navigate Search Project Run Window He Welcome to Websphere Application Server Toolkit Version 6.0 c. Follow the links for the ast and workbench basics tutorials ab 03-Application Mar Page 4 of 42
© Copyright IBM Corporation 2005. All rights reserved. Lab 03 – Application Management Page 4 of 42 ___ 2. Introduction to the AST Workbench ___ a. If you are not familiar with the Eclipse workbench, you might want to go through the Overview to get an understanding of the functions and capabilities of the Application Server Toolkit (AST). Otherwise, skip this step and go to the Workbench (step d.) ___ b. Click on the Globe icon to go to the Overview ___ c. Follow the links for the AST and Workbench Basics Tutorials
Copyright IBM Corporation 2005. All rights reserved. d. Click on the Workspace icon on the right hand upper corner of the welcome eResource-IBM WebSphere Application Server Toolkit, v6. 回x1 Fie Eat Navigate Search Project Run window Hep Welcome to Web Sphere Application Server Toolkit Version 6.0 e. The Workbench has perspectives and views. The name of the active perspective is shown in the title of the window In this case. resource should be the active perspective and Navigator is the active view. Using the Workbench window toolbar, you should open a J2EE perspective f. from the ast toolbar, click Window ,Open Perspective Othe Ep Resource-1BM WebSphere Application Server Toolkit, V6.0 File Edit Navigate Search Project Run Heb Open Perspective n Cvs Repository Exploring Show View 4 Profiling and Logging Close Perspective Eu Team synchronizing Close All Perspectives oof of Technology ab 03-Application Management Product Introduction Exploration(PI+E Page 5 of 42
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 03 – Application Management Product Introduction + Exploration (PI+E) Page 5 of 42 ___ d. Click on the Workspace icon on the right hand upper corner of the welcome screen ___ e. The Workbench has perspectives and views. The name of the active perspective is shown in the title of the window. In this case, Resource should be the active perspective and Navigator is the active view. . Using the Workbench window toolbar, you should open a J2EE perspective. ___ f. From the AST toolbar, click Window Æ Open Perspective Æ Other
opyright IBM Corporation 2005. All rights reserved. g. Select the J2EE perspective from the available options 中5 elect Perspective cvsicVS Repository Exploring Data *Debug Log Adapter 时 ya Browsing JAva Type Hierarch w Plug-in Developmen 3. Create the Enterprise Application Project a. From the AsT toolbar, click File,Import File Edit Navigate Search Project Run Window Help +分+N中势·o.9,0,。一 Corl+s save A Save A H+5+5 Refresh Switch Workspace. ben External File. tn Import. b. The Import window is displayed, with several import source options c. Click Ear F click Next. The Enterprise Application Import dialogue is displayed ab 03-Application Management 6of42
© Copyright IBM Corporation 2005. All rights reserved. Lab 03 – Application Management Page 6 of 42 ___ g. Select the J2EE perspective from the available options. ___ 3. Create the Enterprise Application Project ___ a. From the AST toolbar, click File Æ Import ___ b. The Import window is displayed, with several import source options ___ c. Click Ear File. ___ d. Click Next. The Enterprise Application Import dialogue is displayed
Copyright IBM Corporation 2005. All rights reserved. e. Click the browse button for ear File Enterprise Application Import Import an Enterprise Application project based on selected resources f. Navigate to C: IWeb Sphere\App Server\InstallableApps g. Click DefaultApplicationear h. Click the Open button Look int installable Apps a]sibwsimschannell 此 Application. ear Da] sibwsimschannel2ea a DynacacheEs ef aivtApp Type: EAR File fphereTP, ear a]PerfServletApp Size: 123 KB Dekp|圆 query,ear a]sdoRepository,ear My Documents]sibwsauthbean,ear asibwshtt a]sibwshttpchannel2 My Computer File name DefaultApplication My Network P Files of . The Enterprise Application Import dialogue window is redisplayed with values filled in for the Default Application J2EE Application j. Click Finish You have just created the DefaultApplication Enterprise Application project. It consists of J2EE application components, resources, and deployment information The Project Explorer panel should now look similar to the following image oof of Technology Lab 03-Application Management Page 7 of 42
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 03 – Application Management Product Introduction + Exploration (PI+E) Page 7 of 42 ___ e. Click the Browse button for Ear File. ___ f. Navigate to C:\WebSphere\AppServer\InstallableApps ___ g. Click DefaultApplication.ear ___ h. Click the Open button ___ i. The Enterprise Application Import dialogue window is redisplayed with values filled in for the DefaultApplication J2EE Application. ___ j. Click Finish. You have just created the DefaultApplication Enterprise Application project. It consists of J2EE application components, resources, and deployment information. The Project Explorer panel should now look similar to the following image:
Copyright IBM Corporation 2005. All rights reserved. J2EE-IBM Websphere Application Server Toolkit, Y6.0 File Edt Navigate Search Project Run Window Help ( e Enterprise Applications 中 Application Client Projects 由 C Connector Proje 中 CS EJB Project 中 C Dynamic Web Projects Other Projects #-Co Databases e servers An Enterprise Application may consist of EJB Modules, Web Modules, a Resource Adapter, Application Clients, Security Roles, Files, and Deployment Descriptors. The Default Application consists of Deployment Descriptor information, a Web Module (DefaultWebApplication) and an EJB module(Increment) 4. Introduction to the Application Deployment Descriptor a. Access the Project Explorer Pane File Edit Navigate Search Project Run Window Help e。s」·0·8·,s少」 H. Resource 日- Default Appia Edi Deployment Descriptor: Default Application.ear>> 中-□ Modules O Project Utilty JARs 中□ Utility JARs +C META-INF t-C Application Client Projects b. Expand Enterprise Applications Default Application C. Double click the Deployment Descriptor DefaultApplication ear entry, to open the deployment descriptor in the Deployment Descriptor Editor ab03-Applicat tion Management
© Copyright IBM Corporation 2005. All rights reserved. Lab 03 – Application Management Page 8 of 42 An Enterprise Application may consist of EJB Modules, Web Modules, a Resource Adapter, Application Clients, Security Roles, Files, and Deployment Descriptors. The DefaultApplication consists of Deployment Descriptor information, a Web Module (DefaultWebApplication) and an EJB module (Increment). ___ 4. Introduction to the Application Deployment Descriptor ___ a. Access the Project Explorer Pane. ___ b. Expand Enterprise Applications Æ Default Application ___ c. Double click the Deployment Descriptor: DefaultApplication.ear entry, to open the deployment descriptor in the Deployment Descriptor Editor
WebSphere software- Copyright IBM Corporation 2005. All rights reserved. You can use the Deployment Descriptor Editor to change certain deployment properties of the Enterprise Application. For instance, you can add modules and security information, as well as change Web Sphere bindings and extensions information d. Press the F1 key to display help information on the Deployment Descriptor Editor e. Click the Link for Application deployment descriptor editor Use the Overview page of the Application deployment descriptor editor to view and set properties for the enterprise application k也m时 D Creating an enterprise application project f. Review the help information for the Editor g. Close the Help Window The DefaultApplication EAR Deployment Descriptor file is displayed in the editor h. Click the Overview tab to ensure that the Overview page is active in the editor ication Server Toolkit, V6.0 ie Edit Navigate Search Project Run Window Heb 图G丽“丽」赖·0·9·%,」 =d Deployment Descriptor: DefaultApp -General Information Edweb Defaul:WebApplcation,war Description:This is the IBM WebSphere Application Server Defaul -J Security Roles 4 t-C Appication Client Projects Detals iCons Smal: 由与 Dynamic Web Projects C-CO Databases tCo Database Servers owing are extension properties for the Websphere Appication Server Read nterval second(s) Securty Extended Services Deployment Source I: Description Resource Folder Location oof of Technology Lab 03-Application Management Product Introduction Exploration(PI+E Page 9 of 42
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 03 – Application Management Product Introduction + Exploration (PI+E) Page 9 of 42 You can use the Deployment Descriptor Editor to change certain deployment properties of the Enterprise Application. For instance, you can add modules and security information, as well as change WebSphere bindings and extensions information. ___ d. Press the F1 key to display help information on the Deployment Descriptor Editor. ___ e. Click the Link for Application deployment descriptor editor ___ f. Review the help information for the Editor ___ g. Close the Help Window The DefaultApplication EAR Deployment Descriptor file is displayed in the editor. ___ h. Click the Overview tab to ensure that the Overview page is active in the editor
Copyright IBM Corporation 2005. All rights reserved. i. Observe that the DefaultApplication contains two(2) modules Web DefaultWebApplication. war and ejB Increment jar j. Click the Details button next to the Modules. This action will make the Module page active in the editor. You can use the Module page to add, edit, browse, and emove EJB, Web, Application, etc. modules from the enterprise application. You can also use this page to add utility JAR files to the Enterprise Application project k. Click the Web DefaultWebApplication war module Observe the context root for the Default Application is'/ Note: A context root is the default relative path to static Web content. It is used to create the URL that links to Web resources in a static Web project. In order to change the Context root, you will need to use the Properties sheet for the DefaultWebApplication The capability to change the Context root will be demonstrated in a subsequent section of this exercise m. Close the Application Deployment Descriptor editor. If the Save Resource dialogue is displayed, click No 5. Introduction to the Web Deployment Descriptor a. Expand Dynamic Web Projects- DefaultWebApplication b. Double Click Deployment Descriptor: Default Web Application to open the Web Deployment Descriptor Editor ab 03-Application Mar Page 10 of 42
© Copyright IBM Corporation 2005. All rights reserved. Lab 03 – Application Management Page 10 of 42 ___ i. Observe that the DefaultApplication contains two (2) modules: Web DefaultWebApplication.war and EJB Increment.jar. ___ j. Click the Details button next to the Modules. This action will make the Module page active in the editor. You can use the Module page to add, edit, browse, and remove EJB, Web, Application, etc. modules from the enterprise application. You can also use this page to add utility JAR files to the Enterprise Application project. ___ k. Click the Web DefaultWebApplication.war module. ___ l. Observe the context root for the DefaultApplication is ‘/’. Note: A context root is the default relative path to static Web content. It is used to create the URL that links to Web resources in a static Web project. In order to change the Context root, you will need to use the Properties sheet for the DefaultWebApplication. The capability to change the Context root will be demonstrated in a subsequent section of this exercise. ___ m. Close the Application Deployment Descriptor editor. If the Save Resource dialogue is displayed, click No. ___ 5. Introduction to the Web Deployment Descriptor ___ a. Expand Dynamic Web Projects Æ DefaultWebApplication ___ b. Double Click Deployment Descriptor: Default Web Application to open the Web Deployment Descriptor Editor
