By default, the node agent is not registered as a service
when it is installed on Microsoft™ Windows™ or Linux™ using the Primary Node configuration
profile, so you must register it manually.
About this task
During installation of a Primary Node profile on Windows or Linux,
only the Application Server (STMeetingServer, STProxyServer, STMediaServer,
STAdvancedServer) is registered as a service. Manually register the
node agent as a service so that the servers start and stop in the
correct order.
Procedure
- Create the service using the WASService command as described
in the IBM® WebSphere® Application Server information
center topic, WASService command.
For example,
to create a service for the node agent, enter this command:
WASService -add %SVC_NAME_NA% -serverName nodeagent -profilePath
%WASHOME%\profiles\%APPPROFILENAME% -logFile %WASHOME%\profiles\
%APPPROFILENAME%\logs\%SERVICEVC_NAME_NA%.log -stopArgs "-username
%WASADMINID% -password %WASADMINPWD%" -encodeParams
- Set the dependency between the new node agent service and
the Application Server service to ensure that the node agent always
starts before the Application Server.
For example, on Windows, set the dependency by
entering this command:
sc config "STMeetingServer_service_name"
depend= "Node_agent_service_name"
- To remove a node agent, enter this command:
WASService
-remove Node_agent_service_name