[TechNote] How to start or stop an Enterprise application that is deployed into a cluster using wsadmin scripting tool

How to start or stop an Enterprise application that is deployed into a cluster using wsadmin scripting tool

Problem(Abstract)

It is not possible to start or stop the application from cluster scope directly when using the wsadmin scriping tool.
To start or stop the application running in a cluster, the user must run wsadmin scriping start or stop commands for all the cluster members separately.

Resolving the problem

Here is an example to start or stop an Enterprise application in a cluster setup using the wsadmin scripting tool:

• Connect to Deployment Manager:
  /profile_install_root/bin>wsadmin.sh/bat
  
• Identify the application manager MBean for the server where the application resides, and assign it to the appManager variable.
  
  wsadmin> set appManager [$AdminControl queryNames
  cell=mycell,node=mynode,type=ApplicationManager,process=member1,*]
  
• This command returns the application manager MBean (output):
  Example:
  WebSphere:name=ApplicationManager,process=member2,platform=dynamicproxy,node=vik
  ram2Node08,version=6.1.0.13,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=vikram2Cell02,spec=1.0
  
• To start the application:
  wsadmin> $AdminControl invoke $appManager startApplication AppName
  
• To stop the application:
  wsadmin> $AdminControl invoke $appManager stopApplication AppName
  
• Repeat the above two steps for all cluster members in a cluster by specifying right nodename and member names