Copyright IBM Corporation 2005. All rights reserved. 13. The next screen presents a summary of what will be installed. Click Next to begin 14. When the installation completes, you will be presented with the option to create a profile. Uncheck the Launch the Profile creation Wizard checkbox Installation wizard x Installation is complete The next step in the installation process is to create at least one run-time environment, known as a profle. Each profile contains either a deployment stand-alone application server WebSphere software Important: At least one profile must exist to have a functional installation. It is u create a profile now. If you do not create a profile file creation wizard or use the wasprofile one la ck Next Please read the information below Warning: This Installation is not yet operational To have an operational installation, you must create a run-time environment. If you want to create a runtime environment using the Profile creation wizard, click Back and select the checkbox for launching the wizard natively, you can launch the Profile creation wizard from the First steps console se the profile creation wizard launcher located in WebSphere, software C Program FilesuBMWebSpherelAppServerbinIProfileCreator On windows systems, a start menu entry is also available Otherwise click Next to continue Back Lab 01-ND Install and configuration 6of38
© Copyright IBM Corporation 2005. All rights reserved. Lab 01 – ND Install and Configuration Page 6 of 38 ____ 13. The next screen presents a summary of what will be installed. Click Next to begin the installation. ____ 14. When the installation completes, you will be presented with the option to create a profile. Uncheck the Launch the Profile creation Wizard checkbox. ____ 15. Click Next
WebSphere software- Copyright IBM Corporation 2005. All rights reserved. 16. This screen warns you that no profiles have been created yet. Click Next &Installation wizard Installation is complete First steps console The First steps console has links to the profile creation wizard the Migratio wizard and to other important information about Web Sphere Application Server Network Deployment v6 WebSpheresoftware r Launch the First steps cor s Back 17. Uncheck the Launch the First steps console box 18. Click Finish to complete the installation 19. To inspect the installed product, open a windows explorer window and navigate to C: WebSpherelAppServer 20. Repeat steps 1-3 of this exercise and select Snapshot 2 to return to the previously configured VMWare image for the next step of the exercise NOTE: This step is required because maintenance patches have been applied to the product install in Snapshot 2 oof of Technology ab 01-ND Install and Configuration Product Introduction Exploration(PI+E Page 7 of 38
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 01 – ND Install and Configuration Product Introduction + Exploration (PI+E) Page 7 of 38 ____ 16. This screen warns you that no profiles have been created yet. Click Next. ____ 17. Uncheck the Launch the First steps console box. ____ 18. Click Finish to complete the installation. ____ 19. To inspect the installed product, open a windows explorer window and navigate to C:\WebSphere\AppServer. ____ 20. Repeat steps 1-3 of this exercise and select Snapshot 2 to return to the previously configured VMWare image for the next step of the exercise. NOTE: This step is required because maintenance patches have been applied to the product install in Snapshot 2
Copyright IBM Corporation 2005. All rights reserved. Part 2: Profile Configuration The VMWare image for this lab is setup to be started from this step If you wish to walk through the product binary install, Go back to part 1 The wasprofile command line tool defines each Application Server instance of a Version 6 product You must run the wizard or the command line tool each time that you want to create an Application server instance(JVM). Administration is greatly enhanced when using V6 profiles instead of multiple product installs. Not only is disk space saved, but updating the product is simplified when you only maintain a single set of product core files. Also, creating new profiles is faster and less prone to error than full product installs, allowing a developer to create new profiles of the product for development and testing 1. Open a command prompt and change to the c: WebSpherelappServer bin directory 2. The listProfiles command allows you to see all of the profiles currently on this machine. On the command prompt issue the wasprofile -listProfiles command You should see no profile has been created yet 3. In your command prompt, change to C: lWebSpherelApp\bin\ProfileCreator 4. Issue the command pctwindows. exe, to start the profile creation wizard WebSphere,softwrare welcome to the Profile creation wizard for Version 6 This wizard creates run-time environments that are referred to as profiles.Each profile contains either a deployment manager, a administered by a deployment manager, or a stand- application server. At least one profile must exist to have a functional installation See the online information center for more information about the profile creation wizard or about setting up typical topologies for Application Servers httpjpublib.boulderibmcom/infocenterwws60help/indexs Install Shield Lab 01-ND Install and configuration 8of38
© Copyright IBM Corporation 2005. All rights reserved. Lab 01 – ND Install and Configuration Page 8 of 38 Part 2: Profile Configuration The VMWare image for this lab is setup to be started from this step. If you wish to walk through the product binary install, Go back to part 1. The wasprofile command line tool defines each Application Server instance of a Version 6 product. You must run the wizard or the command line tool each time that you want to create an Application server instance (JVM). Administration is greatly enhanced when using V6 profiles instead of multiple product installs. Not only is disk space saved, but updating the product is simplified when you only maintain a single set of product core files. Also, creating new profiles is faster and less prone to error than full product installs, allowing a developer to create new profiles of the product for development and testing. ____ 1. Open a command prompt and change to the C:\WebSphere\AppServer\bin directory. ____ 2. The listProfiles command allows you to see all of the profiles currently on this machine. On the command prompt issue the wasprofile –listProfiles command. You should see no profile has been created yet. ____ 3. In your command prompt, change to C:\WebSphere\AppServer\bin\ProfileCreator ____ 4. Issue the command pctWindows.exe, to start the profile creation wizard
Copyright IBM Corporation 2005. All rights reserved. 5. Click Next and select Create a deployment manager profile O Profile creation wizard 回区 WebSpheresoftwar Profile type selection A profile defines a run-time emironment Choose the type of profile that is best your needs ⊙ create a etting up a Network Deployment evironment is to nt manager. A deployment manager administers Create an Application Server profile e applications The Application Server can console and function indep Deom its own administrative cation servers and deployment managers, Alter an be federated into a cell and managed by the deployment manage Create a custom profile Installshield ≤Bak xt> Cancel 7. Enter a profile name of dmgr 8. Click Next 9. Keep the default profile Location 10. Click Next oof of Technology ab 01-ND Install and Configuration Product Introduction Exploration(PI+E Page 9 of 38
© Copyright IBM Corporation 2005. All rights reserved. Proof of Technology Lab 01 – ND Install and Configuration Product Introduction + Exploration (PI+E) Page 9 of 38 ____ 5. Click Next and select Create a deployment manager profile ____ 6. Click Next ____ 7. Enter a profile name of dmgr. ____ 8. Click Next. ____ 9. Keep the default profile Location ____ 10. Click Next
Copyright IBM Corporation 2005. All rights reserved. 11. Set the Node name and Cell name as shown in the graphic below. Keep the Host IN Profile creation wizard Node, host, and cell names a cell name for this profile. Refer the installation guide for detailed field descriptions and migration considerations lost Cell name marcEll Node name: The node name is for administration by the deployment manager. The name be unique within the cell Instal shieid Cancel 12. Click Next 13. This screen allows you to choose the port numbers for WebSphere and its associated components. Keep the defaults and click Next PROfile creation wizard The values in the following fields define the ports for the deployment manager To avoid run- time port conflicts ach port value is uniqu Administrative console port (Default 9060 Administrative console secure port ( Default 9043) Bootstrap port(Default 9809) SOAP connector port (Default 8879) CSIV2 ServerAuth listener port (Default 9403) 03 CSNV2 MultiAuth listener port(Default 9402) ORB listener port (Default 9100 9100 Cell discovery port Default 7277) Bak[No,_gmra」 Lab 01-ND Install and configuration
© Copyright IBM Corporation 2005. All rights reserved. Lab 01 – ND Install and Configuration Page 10 of 38 ____ 11. Set the Node name and Cell name as shown in the graphic below. Keep the Host name ____ 12. Click Next ____ 13. This screen allows you to choose the port numbers for WebSphere and its associated components. Keep the defaults and click Next