Home
Deploying
IBM® Sametime® consists of a variety of servers and clients, and can be deployed to suit many different environments. The deployment instructions are organized by feature set, beginning with the minimum components that are necessary to support instant messaging, and then expanding the deployment to include features such as audio and video support, and conferencing.
Deploying an instant messaging gateway for external communities
Clients in a local IBM® Sametime® community can communicate with users in other communities through the Sametime Gateway.
Configuring a Sametime® Gateway
Configure one or more IBM® Sametime® Gateway Servers.
Configuring Sametime® Gateway properties
You can put limits on sessions and subscriptions, and specify blacklist domains to check when Sametime® Gateway Server receives a subscription request. You can also add or edit custom properties for communities, connections, translation protocols, or message handlers.
Translation protocol additions
You can extend the IBM® Sametime® Gateway Server by adding translation protocols. Additional translation protocols expand the communities that the Sametime Gateway Server can connect with.

Translation protocol additions

You can extend the IBM® Sametime® Gateway Server by adding translation protocols. Additional translation protocols expand the communities that the Sametime Gateway Server can connect with.

A new translation protocol permits the Sametime Gateway Server to connect to additional instant messaging communities. A translation protocol needs to implement the API defined by the Sametime Gateway Server core. The core exposes an API for use by the translation protocol, and incudes documentation on how to use it. Your new translation protocol is responsible for connectivity with the corresponding presence servers. If the presence server supports distribution or fail over, the translation protocol is responsible for implementing these features. During deployment, the Sametime Gateway Server configuration must be updated to be made aware of the existence of the new translation protocol. Restart the Gateway to initiate the new translation protocol.