Thursday Tips - Sametime Installations Gone Awry?

I recently inherited a failed Sametime Complete 9.0 Installation that was stuck on the proxy server.

This would be the 3rd time in the last 2 years I have had the same exact circumstance.

Thank you all for bringing these to me. The commonality in each case was a reliance on the Zero to Hero 900+ slide deck. While it is a great guide to follow, especially if internally you need screen shot by screen shot directions, it lacks a few things that are kind of important.

It makes it very clear everything is on one server, if anyone read the slides, this is not very feasible for the average installation.Why is this an issue? Websphere needs to be installed on each machine but is not mentioned anywhere. SSO is not mentioned. Creating the services, and dependencies for those services is only partially mentioned.Naming everything sametime.org.com is not going to work either.

There are many more items to consider and think about, in short, if you don't know enough about what is missing, don't start down this path.

So for those getting stuck along the way, and have yet to call me for help, here are some pieces of information which may help you along the way. None of this is new but sometimes you just need a bunch of help all in one place.

I will presume you know enough to download any updates from IBM's Fix Central, how to install Websphere and the Installation manager and all the other components. If not, call me.

In no particular order:
SSO import, export of the LTPA token to/from Websphere and the Community Server details can be found here.

Keep in mind the token name must be syntax correct and the same name used throughout the process.
You may want some more details from this post:

When you need to create the Domino SSO Configuration, use this guide.

You can have multiple Domino SSO Configuration documents, just name them differently.

We needed to do this in 2 of the 3 cases because we used the same Domino domain for Community servers and :LDAP servers. This is one case where creating a new OU inside your domain may help you, check with your trusted advisor.

Need to create a Windows Service, and Dependencies so on startup it loads all the WAS and server items properly? You need the sc.exe command tool .

The syntax is not fun, and be very careful with the CAPS letters and lower case ones as any diffrences will not let this work, see this for a massive example.

Here is an example of how I did a few. You start at the bin directory (I used a D Drive) and then enter the text starting with "sc config " after the ">" remember long names and spaces in between words need the quotation marks:

Proxy Server itself and has a dependency of starting AFTER the local nodeagent:

D:\IBM\WebSphere\AppServer\profiles\con-stproSTPPNProfile1\bin>

sc config "IBMWAS

85Service - STProxyServer" depend= "IBMWAS85Service - con-stproSTPPNProfile1_nod
eagent"

 For the Sametime System Console (SSC) the Nodeagent has to start AFTER the Deployment Manager

sc config "IBMWAS
85Service - STConsoleServer_NA" depend= "IBM WebSphere Application Server V8.5 - STConsoleServer_DM"

If you need to remember the order of starting and stopping the Websphere Sametime Servers read this note.

Lastly, document that installation using my excel spreadsheet which you can get from this post of mine.