Running Sametime components as Windows services 

Before you begin

• Act as part of the operating system
• Log on as a service
  
  

Procedure

1. Use a text editor to create a file named createservices.bat with the following contents.
   
Note that the path in your deployment might be different. Each line that starts with wasservice.exe should be on one line in your batch file.



cd \Program Files\IBM\WebSphere\AppServer\bin

set PROFILE_PATH=C:\Progra~1\IBM\WebSphere\AppServer\profiles

wasservice.exe -add ConsoleServerDM -serverName dmgr -profilePath

 "%PROFILE_PATH%\STSCDMgrProfile" -logRoot "%PROFILE_PATH%\STSCDMgrProfile\logs\dmgr" 

  " -username wasadmin -password password " 

wasservice.exe -add ConsoleServerNodeAgent -serverName nodeagent -profilePath

 "%PROFILE_PATH%\STSCAppProfile" -logRoot "%PROFILE_PATH%\STSCAppProfile\logs\nodeagent"  

  " -username wasadmin -password password " 

wasservice.exe -add ConsoleServerPrimaryNode -serverName STConsoleServer -profilePath

 "%PROFILE_PATH%\STSCAppProfile" -logRoot "%PROFILE_PATH%\STSCAppProfile\logs\

 STConsoleServer" " -username wasadmin -password password

 " wasservice.exe -add ProxyServerDM -serverName dmgr -profilePath

 "%PROFILE_PATH%\STPDMgrProfile" -logRoot "%PROFILE_PATH%\STPDMgrProfile\logs\dmgr" 

  " -username wasadmin -password password " 

  wasservice.exe -add ProxyServerNodeAgent -serverName nodeagent -profilePath

 "%PROFILE_PATH%\STPAppProfile" -logRoot "%PROFILE_PATH%\STPAppProfile\logs\nodeagent" 

  " -username wasadmin -password password " 

  wasservice.exe -add ProxyServerPrimaryNode -serverName STProxyServer -profilePath

 "%PROFILE_PATH%\STPAppProfile" -logRoot "%PROFILE_PATH%\STPAppProfile\logs\

  STProxyServer" " -username wasadmin -password password " 

  wasservice.exe -add MeetingServerDM -serverName dmgr -profilePath

 "%PROFILE_PATH%\STMDMgrProfile" -logRoot "%PROFILE_PATH%\STMDMgrProfile\logs\dmgr" 

  " -username wasadmin -password password " 

  wasservice.exe -add MeetingServerNodeAgent -serverName nodeagent -profilePath

 "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\nodeagent" 

  " -username wasadmin -password password " 

  wasservice.exe -add MeetingServerProxy -serverName STMeetingHttpProxy -profilePath

 "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\

  STMeetingHttpProxy" " -username wasadmin -password 

  password " 

wasservice.exe -add MeetingServerPrimaryNode -serverName STMeetingServer -profilePath

 "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\

  STMeetingServer" " -username wasadmin -password 

  password " 

wasservice.exe -add MediaServerDM -serverName dmgr -profilePath

 "%PROFILE_PATH%\STMSDMgrProfile" -logRoot "%PROFILE_PATH%\STMSDMgrProfile\logs\dmgr" 

  " -username wasadmin -password password " 

  wasservice.exe -add MediaServerNodeAgent -serverName nodeagent -profilePath

 "%PROFILE_PATH%\STMSAppProfile" -logRoot "%PROFILE_PATH%\STMSAppProfile\logs\nodeagent" 

  " -username wasadmin -password password " 

  wasservice.exe -add MediaServerPrimaryNode -serverName STMediaServer -profilePath

 "%PROFILE_PATH%\STMSAppProfile" -logRoot "%PROFILE_PATH%\STMSAppProfile\logs\STMediaServer"  

  " -username wasadmin -password password " 



When you install a cell profile instead of a network deployment cluster, the name of the profile itself will be different, usually by appending the host name of the machine. For example, your Sametime® Meeting Server's host name might be zeta-stmeet. Also, your path name might be different. For example, you might not have Program Files in your path. In this case the batch file would look like this:



PROFILE_PATH=C:\ibm\WebSphere\AppServer\profiles

wasservice.exe -add MediaServerDM -serverName dmgr -profilePath

 "%PROFILE_PATH%\zeta-stmeetMeetingDMProfile1" -logRoot "%PROFILE_PATH%\

  zeta-st851MeetingDMProfile1\logs\dmgr"



Note: STMDMgrProfile has been changed to zeta-stmeetMeetingDMProfile1. You must update the script to reflect the unique path to each component.

2. Run the file from the C drive to automate creation of the WebSphere® Application Server services.
   
Note: If you've installed to a different drive letter, modify the file.

3. (Optional) To remotely create and start a service from the command line, you can use the SC tool (Sc.exe) included in the Resource Kit as described on the Microsoft Support site.
   

Results

/profiles/profilename/properties/soap.client.props

com.ibm.SOAP.loginUserid=wasadmin

com.ibm.SOAP.loginPassword=waspassword

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.iseries.doc/info/iseriesnd/ae/tsec_manencpwdprop.html