IBM Support

Maximo: Create Windows Service for Node Agent in WebSphere Application Server

Question & Answer


How do I creating a Windows Service for the Node Agent in WebSphere Application Server?


The WebSphere Node Agent created in the WebSphere Administration Console can be added as Windows services. When completed, the Node Agent startst when the machine is booted without needing manually to start the Node agent.
Start the program from the WebSphere AppServer bin directory.

C:\Program Files\IBM\WebSphere\AppServer\bin>wasservicehelper

Menu Options :

1  Add new or update existing WebSphere service (minimum parameters required)
2  Add new or update existing WebSphere service (all parameters)
3  Remove WebSphere service
4  Status of WebSphere service
5  Tracing WASServices

Select number next to the options
(default 1)[q to Quit]:1

Profile :

1 ctgDmgr01
2 ctgDmgr02
3 ctgAppSrv01

Select number next to the profile [q to Quit]:2

Servers :

1 dmgr

Hint: If the application server is running in an ND environment then only the nodeagent and deployment manager servers should be started as a Windows service.

Warning: In an ND environment, starting the application server as a service may fail under certain conditions where its nodeagent is running.

Select number next to server [q to Quit]:1


Service Name :
Type in a Service Name (e.g hostnameNode01)
[q to Quit]:ctgNode01
Service Name : ctgNode01

Restart Policy :

1  Automatic: Restarts this service if it fails
2  Manual: Restart manually if service fails

Select number next to restart policy
(default 1)[q to Quit]:1

Start Type :

1  Automatic: Starts this service when the operating system starts or when the service is called for the first time.
2  Manual: Requires the service to be started manually using Windows services panel.

Select number next to start type
(Default 1)[q to Quit]:1

*** WebSphere Security ***
Hint: Userid needs to be a member of an administrative role with authority to stop a server such as Admin or Operator roles
NOTE: When WebSphere Security is enabled a userid and password is required in order to be able to stop the service

Is WebSphere SECURITY enabled?
default N)[Y/N][q to Quit]:Y

Username :wasadmin

Password: [wasadmin password]

Please re-enter password for verification: [wasadmin password]

Log on user :

Note: Use this option if you wish to run the service as a domain user account.
Userid should be a domain user id with administrative rights, act as part of the operating system, and log on as service privileges on local system.
default N)[Y/N][q to Quit]:N

Execute :

WASService.exe -add "ctgNode01" -serverName "dmgr" -profilePath "C:\Program Files (x86)\ibm\WebSphere\AppServer\profiles\ctgDmgr02" -encodeParams -stopArgs "-username wasadmin -password *****" -startType automatic -restart true

Execute command now?
(default=Yes) [Y/N][q to Quit]:Y
There is no need to create a MXServer service. WASServiceHelper sets the Restart Policy to 1. All Maximo server automatic start and restart is handled in the Monitoring Policy section of the server definition in the WebSphere console. 

[{"Type":"SW","Line of Business":{"code":"LOB02","label":"AI Applications"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"ARM Category":[{"code":"a8m50000000CbCvAAK","label":"System->System Related"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.0;7.6.0;7.6.1"},{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWT9A","label":"IBM Control Desk"},"ARM Category":[{"code":"a8m500000008b3TAAQ","label":"Miscellaneous Category (Portal, UI, Maximo, Install)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.0;7.6.0;7.6.1","Type":"SW"}]

Document Information

Modified date:
20 May 2021