Appendix A. Sametime 8.5.2 Installation Worksheets
This appendix includes some sample worksheets that you can use for planning and installing Sametime. As the Sametime server installation involves the interdependencies on components among the servers, we have provided some sample worksheets to help you organize your installation and deployment. Worksheets that we have included include details for the following:
Sametime cells/nodes
Sametime DB2 instances
Sametime administrator passwords
Sametime installation preparation checklists
Sample worksheets
The following are sample worksheets for preparing, planning, or for use during the installation of the Sametime server environment. These can be used as a reference and later as part of your server documentation.
Sametime server hostnames
You will have to frequently refer to the fully qualified domain name of your Sametime server during your install and will not be able to change the hostnames you choose post installation. You should arrange to have these added to your domain name server prior to the installation.
Note
Note that the Meeting Server and Proxy Server cannot have the same fully qualified hostname. Also, all servers need to share a domain for Single Sign-On to work across the environment.
Sametime server hostnames | |
---|---|
SSC server: | |
DB2 server: | |
LDAP server: | |
Sametime Community Server: | |
Sametime Proxy Server: | |
Sametime Media Manager Server: | |
Sametime Meeting Server: | |
Sametime Advanced Server: | |
Sametime TURN Server: | |
Sametime Bandwidth Manager Server: |
Sametime server information
Frequently, the Sametime or Domino administrators may not be the people managing the operating system of the Sametime servers. However, during the installation process, you may be required to restart the operating system. In addition, as you build the deployment plans for each server, you will be prompted to set an administrative username and password. This worksheet lists the operating system, administrative user ID, and passwords that you may use to log into the different server operating systems.
Sametime server information | |||
---|---|---|---|
Sametime server name |
Operating system |
Admin user ID |
Admin password |
SSC server: | |||
DB2 server: | |||
LDAP server: | |||
Sametime Community Server: | |||
Sametime Proxy Server: | |||
Sametime Media Manager Server: | |||
Sametime Meeting Server: | |||
Sametime Advanced Server: | |||
Sametime TURN Server: |
N/A |
N/A | |
Sametime Bandwidth Manager Server: |
LDAP Server
The Sametime server architecture references an LDAP server throughout the installation process. Be sure that prior to installation, you have the proper hostname, bind credentials, and port necessary to access the server.
LDAP server | |
---|---|
Deployment name: | |
Hostname: | |
Bind credentials: | |
LDAP base query: | |
Bind credential Password: | |
Port: | |
LDAP server type: |
Sametime server components
During the Sametime server installation, you will have many instances where you have to refer to the DB2 server, the SSC server, or many of the other Sametime servers. We are providing worksheets here for use during the server and the related DB2 database installation and configuration. Although we have listed only one table for DB2 server details, the full Sametime installation requires DB2 databases for many components. If you choose to install these databases on different DB2 servers or instances, we suggest you duplicate the following table as necessary.
DB2 server | |
---|---|
Hostname: | |
DB2 admin ID: | |
DB2 admin password: | |
Port: | |
SSC DB name: | |
Meeting DB name: | |
Advanced DB name: | |
Gateway DB name: |
SSC server | |
---|---|
Hostname: | |
DB2 database name: | |
SSC/WAS admin ID: | |
SSC/WAS admin password: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Port(s): |
Sametime Community Server | |
---|---|
Deployment name: | |
Hostname: | |
SSC hostname: | |
SSC admin ID: | |
SSC admin password: | |
Port: | |
HTTP Tunneling enabled: Yes/No |
Sametime Proxy Server | |
---|---|
Deployment name: | |
Hostname: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Admin ID: | |
Admin password: | |
Port: | |
Proxy IP to add to Community Server: |
Sametime Media Server | |
---|---|
Deployment name: | |
Hostname: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Admin ID: | |
Admin password: | |
Port: |
Sametime Meeting Server | |
---|---|
Deployment name: | |
Hostname: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Admin ID: | |
Admin password: | |
Port: | |
DB2 database name: | |
DB2 hostname: |
Sametime Advanced Server | |
---|---|
Deployment name: | |
Hostname: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Admin ID: | |
Admin password: | |
Port: | |
DB2 database name: | |
DB2 hostname: |
Sametime Gateway Server | |
---|---|
Deployment name: | |
Hostname: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Admin ID: | |
Admin password: | |
Port: | |
DB2 database name: | |
DB2 hostname: |
Sametime Bandwidth Server | |
---|---|
Deployment name: | |
Hostname: | |
Node name: | |
Cell name: | |
WAS app profile name: | |
Admin ID: | |
Admin password: | |
Port: | |
DB2 database name: | |
DB2 hostname: |
Sametime TURN Server | |
---|---|
Hostname: | |
Path to | |
Port: |