Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration

Real-Time Collaboration Gateway replaces Sametime SIP Gateway

The SIP Gateway and SIP Connector which were delivered with earlier releases of Lotus Sametime are

not included with Lotus Sametime 7.5. The ability to share presence and exchange text-based instant

messages previously provided by these components are now being provided by the new IBM Lotus

Real-Time Collaboration Gateway.

The Real-Time Collaboration Gateway is an extensible platform built on WebSphere Application Server,

and allows various real-time collaboration communities such as IBM Lotus Sametime and public instant

messaging (IM) services to share presence and exchange text-based instant messages with each other.

The Real-Time Collaboration Gateway receives messages from one or more communities, checks their

legitimacy, translates them if necessary, and forwards them to their destination.

Enabling the Real-Time Collaboration Gateway functionality requires the installation of separate

components which will be available shortly after the general availability of Lotus Sametime 7.5. As more

information becomes available, it will be posted on the Lotus Sametime home page:

http://www.ibm.com/lotus/sametime

When the Real-Time Collaboration Gateway is available for Sametime 7.5, you will be able to view the

IBM Lotus Real-Time Collaboration Gateway information center at:

http://publib.boulder.ibm.com/infocenter/rtchelp/v1r0/index.

Until the RTC Gateway is released, customers who want to continue using SIP to communicate with other

communities should follow the steps in technote #1244026 before upgrading their server to Sametime

7.5:

http://www.ibm.com/developerworks/lotus/support/

Sametime 7.5 does not provide a virus scanner

Sametime 7.5 does not provide a virus scanner. However, Sametime 7.5 can be configured to call a

third-party virus scanning program before transferring a file.

Do not choose "Always" as the value for "Virus scan files before transferring" in Sametime Administration

unless you have acquired and deployed a virus scanning program.

UIM Client file transfer overview

The UIM client can transfer files by either one of two methods: via the server (RTC), or via peer to peer

(P2P). The method is chosen programmatically at runtime and depends on server, as well as client,

settings.

Server file transfer (RTC)

When this method is used, the UIM client will call upon the Real-Time Collaboration (RTC) API to transfer

the file. The RTC layer then communicates directly with the Sametime server, and passes the file through

the server, to the receiving user. RTC file transfers honor the existing Sametime user policies for

allow/disallow file transfer, maximum size of file allowed, and file types disallowed from transfer.

Peer-to-peer file transfer (P2P)

When this method is used, the UIM client will attempt to connect directly to the chat partner's machine,

and transfer the file if a successful connection is established. P2P file transfers bypass all Sametime user

policy checks. In order to be able to use this transfer method, the user's sametime.properties file must

contain the p2p flag (filetransferP2pAllow) set to 'True'. This file can be found in the UIM client

install directory.