you can work with servers either using a command line directly or through the Integrated Solutions Console (ISC). In general, it is simpler to work with the server through the ISC where you have a single interface and location to work with. Otherwise, starting 10 servers means issuing 10 command lines from 10 different locations. Consider always that a WebSphere Application Server server cannot be started unless its node agent is already started because it is the node agent that is responsible for starting and stopping the servers.
Let us start by looking at the ISC and what it can tell us about the servers. The items highlighted on the servers menu below are those we use most often.
WebSphere application servers shows you all WebSphere Application Server servers installed in the cell
Web servers show you any defined webservers such as an IHS server that are being managed from within this cell
WebSphere Application Servers
This is where you find all servers being used in you IBM Connections environment and any defined cluster instances. In the figure below, you can see a list of some of the servers in our large scale IBM Connections deployment.
Name is the name of the server and this cannot be changed. Name is defined during installation and this is what you use to identify the server when issue commands. The server name is case sensitive
The Node is the name of the instance that manages this server. You can see that we have multiple servers all managed by the same node in our installation. The role of the Node is to start and stop the servers and ensure the configuration held by the deployment manager is updated onto the servers. The name of the Node cannot be changed after installation.
Host Name is the location of the installed server. This is usually a fully qualified host name derived from the name of the physical or virtual server where the server was created. It is critical that this host name is resolvable from all servers within the cell. It is possible to change this host name after install by manually editing some XML files, however, this is not recommended. Therefore, ensure that your host names are correct before installing.
Version is the WebSphere Application Server version installed for this server. This cannot be changed but will automatically update if the server is upgraded or patched. Not all servers have to be running the same version but it is best practice for them to do so.
Cluster Name was defined during the earlier installation of IBM Connections. The Cluster Name cannot be changed post installation.
Status shows a green arrow if the server is running, a red cross if the server is stopped, and a question mark in a circle if the node agent for the server is stopped which prevents the ISC from querying the server status. A question mark also shows if the ISC has problems reaching the server, usually due to DNS or firewall issues.
From the menus you can select multiple servers and choose to stop, start ,or restart their instances. These options are only available if the server’s node agent is started and the server is showing either a "started" (green right arrow) or "stopped" (red X). The advantage of starting and stopping the servers from this screen is that multiple servers on different machines can be managed at once.
Alternatively, you can view the status of servers, start, and stop them from a command line on the server itself. To do this, connect to a command line on you system and navigate to the profile containing the server that you want to work with. All WebSphere Application Server profiles appear under the AppServer directory, In Windows, this is default to
C:\Program Files\IBM\WebSphere\AppServer\profiles. We do not recommend using the \program files\ path.
On Linux or AIX , the default is (case sensitive) /opt/IBM/WebSphere/AppServer/profiles .
The directory for the Deployment Manager profile is DMgr01 and for the Application Servers AppSrv01 . To manage an application server, you d navigate to
/AppSrv01/bin and run the following commands:
startServer.sh (or startServer.bat on Windows)
stopServer.sh (or stopServer.bat on Windows)
serverStatus.sh OR -all (or serverStatus.bat on Windows)
The stopserver and serverstatus commands prompt you for the WebSphere server credentials each time. If you want to avoid having to enter these continually, you can add them to the soap.client.props file in the \properties directory under each profile.
The menu Web Servers display the integrated IBM HTTP Servers that have been configured into the ISC , because these are not WebSphere Application Server servers, they have no node agents and should always show as either started (right green arrow) or stopped (red X). The web servers can be started and stopped from this screen using the menu buttons. You can also start and stop the web servers from a command line by passing the parameters “start” or “stop” to the command httpd (for Windows) and apachectl (for Linux / AIX). For example: