Configuring OpenPages on IBM WebSphere to run as a Windows Operating System Service

Technote (FAQ)


Question

What are the steps an IT administrator can use to configure OpenPages to run as Windows services when using IBM WebSphere as the application server.

Cause

OpenPages 6.2 does not automatically create windows services when using IBM WebSphere® Application Server.

Answer

You can configure an OpenPages® and workflow cluster on WebSphere® Application Server to run as services on the Windows operating system. When WebSphere Application Server clusters run as a service, the cluster automatically restarts after a failure. Also, cluster member processes remain active after you log out from your Microsoft Windows system account.

On the OpenPages administrative system:

  1. Log on as an administrator.
  2. Click: Start > All Programs > Accessories, and right-click Command Prompt > Run as Administrator.
  3. From the command prompt, go to the <WAS_HOME>\bin directory, and run the following command on the OpenPages administrative application server:
    wasservice -add OpenPagesDmgr -servername dmgr -profilePath "<OP_HOME>\profiles\OpenPagesDmgr" -wasHome "<WAS_HOME>" -logFile "<OP_HOME>\profiles\OpenPagesDmgr\logs\dmgr\startServer.log" -logRoot "<OP_HOME>\profiles\OpenPagesDmgr\logs\dmgr"
  4. Run the following command on the OpenPages administrative application server:
    wasservice -add IBPMDmgr -servername dmgr -profilePath "<WORKFLOW_HOME>\profiles\IBPMDmgr" -wasHome "<WAS_HOME>" -logFile "<WORKFLOW_HOME>\profiles\IBPMDmgr\logs\dmgr\startServer.log" -logRoot "<WORKFLOW_HOME>\profiles\IBPMDmgr\logs\dmgr"
  5. Run the following command:
    wasservice -add <HOST_NAME>-OPNode1 -servername nodeagent -profilePath "<OP_HOME>\profiles\<HOST_NAME>-OPNode1" -wasHome "<WAS_HOME>" -logFile "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\nodeagent\startServer.log" -logRoot "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\nodeagent"
  6. Run the following command:
    wasservice -add <HOST_NAME>-OPNode1Server<SERVER#> -servername <HOST_NAME>-OPNode1Server<SERVER#> -profilePath "<OP_HOME>\profiles\<HOST_NAME>-OPNode1" -wasHome "<WAS_HOME>" -logFile "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\<HOST_NAME>-OPNode1Server<SERVER#>\startServer.log" -logRoot "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\<HOST_NAME>-OPNode1Server<SERVER#>"
  7. Run the following command:
    wasservice -add <HOST_NAME>-IBPMNode<SERVER#> -servername nodeagent -profilePath "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>" -wasHome "<WAS_HOME>" -logFile "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\nodeagent\startServer.log" -logRoot "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\nodeagent"
  8. Run the following command:
    wasservice -add <HOST_NAME>-IBPMNode<SERVER#>Server -servername <HOST_NAME>-IBPMNode<SERVER#>Server -profilePath "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>" -wasHome "<WAS_HOME>" -logFile "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\<HOST_NAME>-IBPMNode<SERVER#>Server\startServer.log" -logRoot "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\<HOST_NAME>-IBPMNode<SERVER#>Server"
  9. Repeat step 6, 7, and 8 for each application server*.

*Each application server can be installed vertically or horizontally.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

OpenPages GRC Platform

Software version:

6.2

Operating system(s):

Windows

Reference #:

1632750

Modified date:

2013-03-28

Translate my page

Machine Translation

Content navigation