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