Reviewing the checklist for deploying meetings
Review this checklist before installing the meetings feature.
Checklist for deploying meetings | |
---|---|
Deployment type | These instructions deploy a single Meeting Server in the intranet. |
Sametime®product required | Sametime Conference |
Review system requirements | IBM Sametime 9 System Requirements |
Review the release notes | IBM Sametime 9 Release Notes |
Prerequisites |
|
Review planning documentation | |
Complete capacity worksheets | Complete Capacity and sizing planning along with geography planning. |
Complete installation worksheets | Use the Sametime meetings worksheets to identify DNS-registered host names, database names, IP addresses, ports to open, and credentials. |
Assign fully qualified host names to computers | Ensure that all host names can be resolved in DNS. If DNS is not available then list all fully qualified server names and IP addresses from all servers in the hosts file and publish this file to all servers. |
Not covered by this deployment | These instructions do not cover installing instant messaging, audio and video, external access to meetings, or steps for expanding your deployment for high availability and failover. |
Administrative user names | DB2 administrator: This user is created during installation of the DB2 server in the operating system. Do not create the user in advance. It is the user for all IBM Sametime related components using DB2 to access their databases. Be sure to match the password policy requirements of the operating system. WebSphere administrator: This is the user to access the WebSphere Application Server components and to administer the system. This user must not exist in your LDAP directory. You can use the same user name and password for all components or different names and passwords. |