Copyright IBM Corporation 2005. All rights reserved. Stop any server processes that have a status of StaRtEd by executing the stop Server command for each server Syntax to stop the default Application Server(server1) C: IWeb\App Server\bin>stop Server server1-profile Name profile Syntax to stop the Node Agent(nodeagent) C: Web Sphere \App Server bin>stop Server nodeagent-profileName profile Syntax to stop the Deployment Manager(dmgr) C: IWeb Sphere\AppServer bin> stopServer dmgr Note: Since the Deployment Manager is default profile, you do not need to specify the profile Name as an optional parameter on the stop Server command 2)Create a standalone Application Server profile a) Issue the wasprofile command to create a standalone Application Server node C: WWebSphereApp Server\bin>wasprofile-create-profileName samplesProfile profile Path C: Web App Server profiles samplesProfile template P ath C: Web Sphere App Server profile Templates default -cellName samples cell-hostName wasv6pot-node Name samplesNode command prompt. It will take several minutes for completion of the comman a Note: The above command should be entered as a single line in your Windows b)a successful completion of the wasprofile command will result in message INSTCONFSUCCESS. Success: The profile now exists 3)Install additional sample applications for the standalone Application Server(samplesProfile) profile that you just created Note: By default, only the DefaultApplication and PlantsByWeb Sphere samples are deployed on a standalone Application Server. In order to deploy additional applications from the Samples Gallery, you will need to run an install command. Although individual sample applications can be installed using the install command you will install all samples in the Samples Gallery during this exercise. This is achieved by running the install command without parameters a) Initialize the windows command line environment to execute commands for the Navigate to the tbin directory of the samples profile cd WWebSpherelAppServerlprofileslsamplesProfilelbin Run the setup CmdLine command to initialize the environment b)Navigate to the samples installation directory cd WWebSpherelAppServerlsampleslbin Lab 02-System Administration© Copyright IBM Corporation 2005. All rights reserved. Lab 02 – System Administration Page 2 of 28 Stop any server processes that have a status of STARTED by executing the stopServer command for each server. __ Syntax to stop the default Application Server (server1). C:\WebSphere\AppServer\bin>stopServer server1 –profileName profile1 __ Syntax to stop the Node Agent (nodeagent). C:\WebSphere\AppServer\bin>stopServer nodeagent –profileName profile1 __ Syntax to stop the Deployment Manager (dmgr). C:\WebSphere\AppServer\bin> stopServer dmgr Note: Since the Deployment Manager is default profile, you do not need to specify the – profileName as an optional parameter on the stopServer command. 2) Create a standalone Application Server profile. __a) Issue the wasprofile command to create a standalone Application Server node. Note: The above command should be entered as a single line in your Windows command prompt. It will take several minutes for completion of the command. __b) A successful completion of the wasprofile command will result in message: INSTCONFSUCCESS: Success: The profile now exists. 3) Install additional sample applications for the standalone Application Server (samplesProfile) profile that you just created. Note: By default, only the DefaultApplication and PlantsByWebSphere samples are deployed on a standalone Application Server. In order to deploy additional applications from the Samples Gallery, you will need to run an install command. Although individual sample applications can be installed using the install command, you will install all samples in the Samples Gallery during this exercise. This is achieved by running the install command without parameters. __a) Initialize the Windows command line environment to execute commands for the samplesProfile. __ Navigate to the \bin directory of the samples profile. cd \WebSphere\AppServer\profiles\samplesProfile\bin __ Run the setupCmdLine command to initialize the environment. setupCmdLine __b) Navigate to the samples installation directory. cd \WebSphere\AppServer\samples\bin