This guided activity takes you through the steps of creating a deployment plan, which collects information that pre-populates installation screens.
® database and an LDAP server, and have run the guided activities for connecting to the
database and to the LDAP server.
Meeting Server. To install a cluster of servers, create one deployment plan for the primary node and one for all secondary nodes you plan to install.
- Plan a product installation.
In the Install Sametime Meeting Server portlet, click Create a New Deployment Plan, and then click Next.
- Deployment Name.
Give the deployment plan a unique, recognizable name, which will be shown only in the Sametime System Console, and then click Next.
The name should include the installation and node type, such as stMeeting_primary. You can include multibyte characters, symbols, and spaces in the name. The name can be up to 256 characters and is not case sensitive.
- Deployment Product Version Selection.
Select the product version you want to install, and then click Next.
- Choose the configuration type.
Select Primary Node if this is the first server of its type. Select Secondary Node for additional servers. Then click Next.
The Cell option is reserved for special-use cases in which the server must be self-contained. If you select Cell, you must provide a host name, user ID, and password when prompted to do so.
- Node Federation at Install Time.
This panel appears if you selected Primary Node or Secondary Node. You can only federate one Primary Node for this type of server in the cell. Select the Sametime System Console cell that will manage this server and then click Next.
Attention: Each Deployment Manager (including the Sametime System Console when it is used as a Deployment Manager) can support one cluster of each Sametime product. For example, a single Deployment Manager can support a Sametime Proxy server cluster, a Media Manager cluster, and a Meeting server cluster. To create additional clusters for a particular product, install the first server using Cell as the configuration type, which designates it as the Deployment Manager and the primary node for the cluster.
- WebSphere® Profile Settings.
- Type the fully qualified host name of the server where you will be installing the Sametime server.
- Enter a user name that does not contain any spaces to be used as the WebSphere Application Server administrator on the Sametime server. Supply a password, and then click Next.
If you must create a user name that contains a space, you may notice that the system console portlet does not appear in the WebSphere Application Server Integrated Solutions Console for the first time. This can be resolved by restarting the system console.
Important: This must be a unique user ID that does not exist in the LDAP directory.
- Choose a database for this deployment. This panel appears if you selected Primary node or Cell as the configuration type.
Select the Sametime Meeting Server database that you configured with the Sametime System Console activity, and then click Next.
- Connect to an LDAP Server. This panel appears if you selected Cell as the configuration type.
Select the LDAP directory that you configured with the Sametime System Console guided activity, and then click Next.
- Deployment Summary.
Review the summary screen, and then click Finish.
The deployment plan is ready to be used for the server installation. If you need to make any changes, click Modify an Existing Deployment Plan and update the plan. All changes must be made prior to running installation.