IBM Support

WebSphere 8.5.5 and Maximo 7.5: Creating Windows Services

Technical Blog Post


Abstract

WebSphere 8.5.5 and Maximo 7.5: Creating Windows Services

Body

Finishing up from the last blog post, it's time to create Windows services. Otherwise you will always have to have a session logged into the Windows server to start the three Maximo-related services (Dmgr, nodeagent, MXServer).

You can follow the instructions in the installation guides found here to create Windows services manually using WASService.exe, or you can use the nifty WASServiceHelper interactive command-line interface tool now included with WebSphere 8. (With WAS 6 and 7, it was a downloadable product called WASServiceCmd.exe.) This tool lets you create the correct command string for WASService.exe to run without guessing what the values should be.

Using the examples from my WAS 8.5.5 installation, let me show the session I ran to create the first service (ctgCellManager01).
In my installation, note that (a) I have two Deployment Manager instances because the first one was used to run the Migration Tool, (b) LDAP security is enabled (through Tivoli Directory Services) and (c) I do not use a separate service account to run the Maximo WAS services.
When finished, I will have two services:
- Deployment Manager (dmgr) service for ctgDmgr02 will be called ctgCellManager01.
- Node Agent (nodeagent) service for ctgAppSrv01 will be called nodeagent.

There is no need to create a MXServer service. All Maximo server automatic start/restart should be handled in the Monitoring Policy section of the server definition in the WebSphere console (Automatic restarting of WebSphere Services). Using WASServiceHelper, this is handled by setting the Restart Policy to 1.

Start the program from the WebSphere AppServer bin directory.

C:\Program Files (x86)\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

dmgr

-------------------
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

And it's done!

After creating the nodeagent service, here's what my Windows services look like now. (I will later remove the WebSphere services for CellManager and nodeagent and then uninstall WebSphere 7.0.)image

After this is completed, you will need to configure your WebSphere Plug-in for Maximo.

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

UID

ibm11113771