Reviewing the checklist to deploy Sametime Gateway

Deploy Sametime® Gateway to connect users to external communities.

Table 1. Deployment Summary
Checklist for deploying Sametime Gateway
Deployment type	These instructions deploySametime Gateway to connect with other instant messaging communities, including other Sametime Gateway communities.
Sametime product required	Sametime Communicate, Sametime Complete
Review system requirements	IBM® Sametime 9 System Requirements
Review the release notes	IBM Sametime 9 Release Notes®
Prerequisites	Deploy instant messaging
Review planning documentation	Planning a Sametime Gateway deployment Sametime Gateway deployments SametimeGateway Sizing Guide Determining which installation packages you need
Complete installation worksheets	Use the Sametime Gateway 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 instant messaging, meetings, audio and video, external access to chat, or steps for expanding your deployment for high availability and failover.
Administrative user names	Domino® administrator: This user is created during installation of Domino for the IBM Sametime Community Server. It is a best practice to not use a existing administrative account because it is the account with that the IBM Sametime System Console communicates with the Community Server. 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. LDAP Bind User: This is a user account in your LDAP directory. This account is used to connect in authenticated mode to the LDAP server to get all required attributes. It is possible to connect anonymously to the LDAP but then it does not work with some LDAP systems or the LDAP server requires special configuration to allow anonymous bind.