You can configure the nodeagent to run as a Windows service and if you are tired of starting your Maximo application server manually, then you can configure it so that it runs as a Windows service that starts automatically when a server is rebooted. To configure the WebSphere Application Server (MXServer) to run as a Windows service, complete the following:
- Change to the \bin directory where WebSphere is installed, for example:
C:\Program Files\IBM\WebSphere\AppServer\bin
- Run the following command:
wasservice -add MXServer -servername MXServer -profilePath "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01" -wasHome "C:\Program Files\IBM\WebSphere\AppServer" -logFile "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer\startServer.log" -logRoot "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer" -restart true -startType automatic
- Use a registry editor, such as Regedit, and open this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMWAS61Service - MXServer
- Create a Multi-String Value named DependOnService.
- Enter the value “IBMWAS61Service – ctgNode01_nodeagent” in this new key. This will make the MXServer application server service dependant on the node agent service starting first.
Much easier to use the WASServiceCmd batch file. It asks you for the parameters and then builds the command from your answers. It’s available from the IBM WebSphere guys if not bundled with Maximo.