Websphere Command References

                    Websphere Commands


Here is a quick guide about how to Start and Stop Application Server, Node Agent and Deployment Manager in WebSphere Application Server.

Stop Application Server:
Go to the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run:
./stopServer.sh <Server Name or JVM Name> -user <username> -password <password>

Stop Node Agent:



Go to the respective profile bin /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run:

./stopNode.sh -user <username> -password <password>

Stop Deployment Manager:


Go to the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin folder and run:

./stopManager.sh -user <username> -password <password>

or


./stopServer.sh <DMGR Server Name> -user <username> -password <password>

Start Deployment Manager


Go to the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin folder and run:

./startManager.sh

or

./stopServer.sh <DMGR Server Name>

Start Node Agent

Go to the respective profile bin /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run:

./startNode.sh

Start Application Server


Go to the respective profile bin /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run:

./startServer.sh <Server Name or JVM Name>


Manual Synch Node


We can manually synchronize a node with the Deployment Manager through the command
syncNode command. The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.


Go to the respective profile bin /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run:

  • Stop the Nodeagent as first step

./stopNode.sh -user <username> -password <password>
  • Run the below command to synch Node manually with DMGR

./synchNode.sh <DMGR HostName > <SOAP Connector Port> -user <username> -password <password>

Add Node:


The addNode command incorporates an application server installation into a cell.This will create a nodeagent .The node agent server is automatically started as part of the addNode command unless you specify the -noagent option. If you recycle the system that hosts an application server node, and did not set up the node agent to act as an operating system daemon, you must issue a startNode command to start the node agent before starting any application servers.

./addNode.sh <DMGR HostName > <SOAP Connector Port> -conntype SOAP -profileName  <Profile Name> -user <username> -password <password> -portprops <NodePort.txt>


Remove Node:


Remove nodes returns from WAS distributed administration cell to standalone application server installation

Syntax: Profile>bin>./ removeNode.sh <nodename> <deploymgrhost> <deploymgrport>
 
Example: /opt/IBM/WebSphere/AppServer/profilesCustom02/bin/removeNode.sh. –userName admin –password admin


Cleanup Node:


The cleanupNode command cleans up a node configuration from the cell repository.CleanupNode is used to clean the node when you have defined a node in cell config but node no longer exists. This is generally used when we are done with defederation.
 
Syntax: DmgrProfile>bin> ./cleanupNode.sh <nodename> <deploymgrhost> <deploymgrport>
 
Example: /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/cleanupNode.sh. myNode -trace -profileName mydmgr

Comments

Post a Comment

Popular posts from this blog

IBM WebSphere - Synchronize a node (syncNode)

Image
  IBM WebSphere - Synchronize a node (syncNode) Before we get into synchronization, let's talk about nodes and the master configuration. The master configuration is a collection of XML files that contain all sorts of information about a cell, such as the security settings and the applications in the cell. A node contains one or more WebSphere application servers. When a managed nodes is federated into the dmgr, the node needs to be synchronized with the master configuration so that the node is using the dmgr configuration. The synchronization is always from Dmgr to Nodes and it never happens vise versa. If you made any changes from the node side it will be cleared during next synchronization process. Let's consider a common example. You make some change in the WebSphere admin console, and you are presented wit the Save option. Selecting save updates the master configuration. This will cause the node to be out of sync with the master configuration. To know if a node is synchroni...
Read more

Daily usage Linux Commands for Any Middleware Administration

Daily usage Linux Commands for Any Middleware Administration Processes related: ------------------ $ ps -ef | grep <process_name> ----- will show the process ID of the proces $ ps -eaf --> to see the Process ID's $ telnet <hostname> <Port_Number> --> It is used to check whether port(server) is listening or not $ scp    -r     file_Name     username@hostname:path  ----- If you want to copy a file from one linux server to another sever $ kill -9 PID ----- Killing an unwanted process $ kill -3 PID ----- Used to take thredDump of the process $ ssh username@servername --> Command used to login to server $ nslookup <host_name> --> Query the nameserver for the IP address of the given HOST optionally using a specified DNS server (To identify the server ip_address by using nslookup command ) $ crontab Minute Hour DayOfMonth Month DayOfWeek (eg: 30 08 10 06 * /home/was/full-backup) ----- Used to scheduled a job on Li...
Read more

Backup and Restore of WebSphere Application Server configuration

                      Backup & Restore of IBM WebSphere Application Server Configuration Backup configuration in  WebSphere One of the major activity that we can perform in Websphere as a pre-requisites when ever we intended to perform any major configuration changes like Fix Pack upgrade ,Interim Fix upgrade, JDK upgrade etc. For any mission critical application, taking frequent backups is essential for recovering from severe errors. In the case of WebSphere Application Server, setting up of the application server environment is a demanding task and it is not an easy to repeat the setup if something bad happens. So, its wise to take backups whenever we make the first setup or when we do configuration changes. Depending upon our diskspace availability two types of backups is possible . 1) Full Backup A full backup can be performed by running the ./backupConfig command from the<WAS-ROOT>/bin di...
Read more