This topic describes how to start application servers.
Before you begin
Starting an application server on an Application Server node that is not part of a deployment manager cell can also automatically start the JMS server process. Before starting an application server that is configured to automatically start the JMS server process, ensure that the following WebSphere MQ messages are not being suppressed by the message processing facility (MPF):
CSQV086E CSQY022I CSQY003I CSQX022I CSQM132I CSQ9022I CSQX017I CSQ3104I CSQ3106E
If you are running multiple servers, be sure the debug port is properly set. If multiple servers on the same node have the same debug port set, the servers could fail to start. See Java virtual machine settings for more information on how to change the debug port.
Why and when to perform this task
Starting a server starts a new server process based on the process definition settings of that server's configuration.If you created a new server definition using a Base WebSphere Application Server, you cannot start, stop, or manage the new server using the administrative console that you are using to control the original base application server.
After you start an application server, other processes might not discover the running application server immediately. Application servers are discovered by the node agent. Node agents are discovered by the deployment manager. Node agents usually can discover local application servers quickly but it can take a deployment manager from 2 to 60 seconds to discover a node agent.
If you are using clusters, note that the Initial State property of the Application Server subcomponent (Servers > Application Server > server_name > Server Components > Application Server) is not intended to be used to control the state of individual servers in the cluster at the time the cluster is started. It is intended only as a way to control the state of the Application Server subcomponent of a server. It is best to start and stop the individual servers of a cluster using the Server options of the Administrative Console or command line commands (startServer and stopServer).
There are several options for starting an application server:
If the node agent for the node on which the application server resides is not running, run the startNode command and then run the startServer command.
If the node agent does not start, run the startNode command and then run the startServer command. Once a node agent completely stops running and remains stopped, you cannot remotely start the node agent from the Node Agents page. You must run the startNode command to start the node agent on the node where it runs.
To start the application server with standard Java debugging enabled:
Before you start any of the application servers, you must verify that all resource managers that are required by your application (DB2, CICS, etc) are available. You must also start all prerequisite subsystems.
Note: This command should be all upper case and should all be on one line (it is shown above on two lines because of space considerations only). For example,
S BBO5ACR.BBOS001,ENV=SY1.SY1.BBOS001
The following messages indicate that the control region is up:
$HASP100 BBO5ACR ON STCINRDR $HASP373 BBO5ACR STARTED BBOO0001I WEBSPHERE FOR Z/OS CONTROL PROCESS BBODMNB/SY1/BBOC001/BBOS001 IS STARTING. IRR812I PROFILE BBO*.* (G) IN THE STARTED CLASS WAS USED TO START BBOS001S WITH JOBNAME BBOS001S. $HASP100 BBOS001S ON STCINRDR $HASP373 BBOS001S STARTED +BBOO0004I WEBSPHERE FOR Z/OS SERVANT PROCESS BBODMNB/SY1/BBOC001/BBOS001 IS STARTING. +BBOO0020I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS SERVANT PROCESS BBOS001. BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS BBOS001.
S <dmn_proc>,JOBNAME=<dmn_jobname>, ENV=<cell_shortname.Node_shortname.daemon_instancename>
Note: This command should all be on one line (it is shown above on two lines because of space considerations only).
Following is an example of the messages that are displayed during daemon startup:
BBOO0001I WEBSPHERE FOR Z/OS CONTROL PROCESS BBODMNB/SY1/BBOC001/BBOS001 IS STARTING. IRR812I PROFILE BBO*.* (G) IN THE STARTED CLASS WAS USED TO START BBO5DMN WITH JOBNAME BBO5DMN. $HASP100 BBO5DMN ON STCINRDR $HASP373 BBO5DMN STARTED BBOO0007I WEBSPHERE FOR Z/OS DAEMON BBODMNB/SY1/BBODMNB/SY1 IS STARTING. IEC130I STEPLIB DD STATEMENT MISSING ITT102I CTRACE WRITER BBOWTR IS ALREADY ACTIVE. BBOO0215I PRODUCT 'WAS FOR Z/OS' SUCCESSFULLY REGISTERED WITH IFAED SERVICE. BBOO0015I INITIALIZATION COMPLETE FOR DAEMON SY1.
S <Srv_Reg_Proc>,JOBNAME=<Server_shortname>, ENV=<Cell_shortname.Node_shortname.Server_shortname>
Note: This command should all be on one line (it is shown above on two lines because of space considerations only).