Associating a Bandwidth Manager server with a Windows Service

Associate the IBM® Sametime® Bandwidth Manager servers with a Microsoft™ Windows™ service so that you can configure the Bandwidth Manager servers to start when Windows starts.

Procedure

  1. Check whether the server is running. Open the Task Manager, click Processes. Check for java.exe.
  2. Right click the java.exe process and click End Process.
    Note: If there is more than one java.exe file, complete step 2 for each of them.
  3. Create a batch file to create the services and assign the name createservices.bat.
  4. Copy this text and substitute the actual profile directory name for AppSrv01.
    set PROFILE_PATH=X:\IBM\WebSphere\AppServer\profiles
wasservice.exe -add BWMServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\AppSrv01" -logRoot "%PROFILE_PATH%\AppSrv01\logs\nodeagent"
wasservice.exe -add BWMServerPrimaryNode -serverName BWMserver1 -profilePath "%PROFILE_PATH%\AppSrv01" -logRoot "%PROFILE_PATH%\AppSrv01\logs\BWMserver1"

    Example for Secondary Nodes: 

    set PROFILE_PATH=X:\IBM\WebSphere\AppServer\profiles
wasservice.exe -add BWMServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\AppSrv01" -logRoot "%PROFILE_PATH%\AppSrv01\logs\nodeagent"
wasservice.exe -add BWMServerSecondaryNode -serverName BWMserver2 -profilePath "%PROFILE_PATH%\AppSrv01" -logRoot "%PROFILE_PATH%\AppSrv01\logs\BWMserver2"
  5. Substitute the server's name where you see BWMerver1.
  6. Place the createservices.bat file on the server under the X:\IBM\WebSphere\Appserver\bin directory.
  7. Use a command prompt and run the createServices.bat file.

    Step 7 is successful if you see the NodeAgent and AppServer services added successfully.

  8. Use Notepad to open the soap.client.props file in X:\IBM\WebSphere\AppServer\profiles\profilename\properties.
  9. Add the wasadmin username and password to the following parameters:

    com.ibm.SOAP.loginUserid=username

    com.ibm.SOAP.loginPassword=password

  10. Save and close the file.
  11. Correct the Log On tab of the service.
    1. Open the Services, and look for the two new services.
      • IBM WebSphere® Application Server V## - MediaServerNodeAgent
      • IBM WebSphere Application Server V## - MediaServerPrimaryNode
    2. Double-click on the service. Click Log On" and make sure it is set to "Local System account". Click OK.
    3. Change the start up type to Automatic.
  12. Start the NodeAgent service first, then start the Primary Node.
  13. Check the logs to be sure the server started up without errors.

    Node agent Llogs are located here: X:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent

    In the NodeAgent's startserver.log: ADMU3000I: check for this message:

    Server nodeagent open for e-business; process id is 3588

    AppServer logs are located here: X:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\BWMserver1

    In the AppServer's startserver.log: ADMU3000I: check for this message:

    Server STMediaServer open for e-business; process id is 3520

  14. Create dependencies for services by completing these steps:
    1. Launch the Windows registry
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ service name for the node agent
      Note: Substitute the real services name for your node agent.
    3. Double click DisplayName and copy the Value data field to your clipboard. The contents of the Value field are used in the next step.

      For example: IBM WebSphere Application Server V8.5 - MediaServerNodeAgent

    4. In the navigation pane, navigate to the AppServer instance
    5. Right click in the content pane and choose New > String Value.
    6. Assign the name DependonService.
    7. After the key has been created, double-click on it and paste your clipboard into the Value data field.
    8. Restart Windows for the setting to take effect.

      When windows comes back up, the services should be started and the server running.