« 10 years later and R5 I AM shirts are now fashionable! | Main| Did anybody else notice real player ads start popping up? »

Sametime 8.5 Windows Service Installer

Category
One of the things that took me by surprise when I first installed the Sametime 8.5 Betas was that none of the new Sametime servers get installed as Windows Services (hmm did I bitch about this in a previous blog entry?).  I found this task tedious enough to keep performing whenever I setup a new server that I created a little utility to automate the process.

This utility works best for those environments where you've installed all the ST 8.5 components on a single server as a kind of trial environment.  It's unsupported, use at your own risk, no warranty implied etc.  But it has worked well for me, and saved me a fair bit of time.


Sametime 8.5 Windows Service Installer - towards bottom of the page

Comments

Gravatar Image1 - @Carl,

What credentials does this tool use to create the services ? I mean the WebSphere credentials not the OS credentials.

(the -userid and -password options on the WASService command.)

Gravatar Image2 - @1 Hi Sjaak, it's the wasadmin and password account.

Gravatar Image3 - Hi Carl!

Great tool, with some hurdles.
Selections in the dialog are confused with the script: if you select Mediaserver-Profile the script runs for Meeting-Server and inverse.
when you select "Meeting..." or "Media..." in the dialog, the script runs for "STWASmeeting...".

I think it is a great tool, but you should make a notice about this paths settings.

Best regards,

Michael Emoticon

Gravatar Image4 - Hello. I am completely new to Websphere and Sametime.

I tried to install ST8.5 on Websphere and followed the instructions step-by-step.
I have managed to install the Meeting Server and System Console and everything was working fine until I rebooted the server and the continued with the Media Manager installation.

After the server rebooted I realized that I could not get the Websphere server and Applications, specifically Sametime System Console running.

I looked in the logs startServer.log and SystemOut.log and found the error message:

{ Link }
ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in zOS) and other log files under C:\Program Files\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\STConsoleServer should contain failure information.

{ Link }
00000000 WsServerImpl E WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up and running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused: connect:host=st85cmp.intranet.gr,port=9900 vmcid: IBM minor code: E02 completed: NoEmoticon Emoticon Emoticon Emoticon Emoticon Emoticon

Gravatar Image6 - I am stuck & not able to add proxy node agent as service .. too complex the manual command for me.. plz send me the script - contact.sudesh@gmail.com

Gravatar Image7 - @6 the latest versions of Sametime add the windows services automatically.

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::rolleyes:;-)