Gabriella Davis 2 March 2010 12:59:20Time to share another Sametime 8.5 install experience with you in the hope it saves you some time doing your own. Last week I was doing an install for a customer where we wanted the following configuration (all on Linux)
Box 1 Sametime Community Server on Domino
Box 2 DB2 9.5 Server
Box 3 Sametime 8.5 including SSC, Proxy, Media Manager and Meeting Server
The install order for Sametime 8.5 in that circumstance would be
- Community Server
- Proxy Server
- Media Manager
- Meeting Server
Since the SSC is the first WAS component to be installed, it always installs in its own Cell profile which means it has its own deployment manager and node agent. If you also install the other servers (Proxy, Media and Meeting) in their own Cell profiles on the same server they also have their own deployment manager and node agent - but why would you do that when you can use the deployment manager you already have in place for the SSC? In fact the documentation here (Sametime 8.5 Install Guide Pt 1 Page 102) specifically says
"Choose the configuration type.
Select the profile type for this installation, and then click Next:
Pilot use: Select Cell Profile.
Add this server to the Sametime System Console cell by selecting the appropriate Network Deployment option.
v First server of this type: Select Network Deployment - Primary Node. v Additional server of this type: Select Network Deployment - Secondary Node.
If you will use the Lotus Sametime System Console as the Deployment Manager for a Lotus Sametime Proxy Server cluster, there is no need to install a Lotus Sametime Proxy Server with the Deployment Manager option.'
So I'm not running a 'pilot', I'm running production and I want to use the SSC deployment manager - I choose "Network Deployment - Primary Node" - right? WRONG. If you do that then the install will just 'stall' about 90% in - same with Media Manager or Meeting Server. After about 10 days troubleshooting with IBM support it turns out that "Production" means "Installing each component on a separate box" whereas "Pilot" means "Installing everything on one box". The only possible way to install all WAS components on one box as many, many, many people want to is to install each one in its own cell profile, generating a separate deployment manager and node agent for each - a total of 6 additional unnecessary servers.
IBM have raised a SPR to update the documentation and explain that you can only use the SSC deployment manager and install into primary nodes if you use a different box for each application. That takes me from the 1 server I had originally in Sametime 8.0.2 , through the 3 servers I wanted to have for Sametime 8.5 (but which IBM considers 'pilot') to the minimum 6 servers required for production! However it does answer another question people have asked me about why, if the SSC is meant to manage all servers, can you not see the other servers in the admin interface when logging into the SSC. The answer is that if you install all the servers on one box , each in its own cell profile and so each with its own deployment manager and generating 8 separate Profile folders and 13 running servers; each is then managing its own configuration through its own admin interface
SSC on https://
Media Manager on https://
Proxy Server on https://
Meeting Server on https://
So the current installation documentation should read:
"If you're planning to install multiple components onto the same server you must use the cell profile option when creating the deployment plans. The Network Deployment - Primary Node option is only applicable if you are installing each component onto a separate server"
I hope that helps
- Comments