148 IBM WebSphere Everyplace Access V5, Volume IV: Advanced Topics
When the SIA synchronization request is a Sametime instant message:
– When the Sametime client is not running, the request is discarded and,
therefore, lost.
– The Sametime client intercepts the SIA synchronization requests and
forwards them to the WebSphere Everyplace Access client for processing.
– All the regular Sametime instant messages are forwarded to the
Sametime connect client.
4.2 Sample scenario with server-initiated actions
This scenario sends commands to a user’s device when new e-mail messages
arrive in an inbox. After receiving this messages, the device connects to
WebSphere Everyplace Access and synchronizes the new e-mail messages.
The user in this example is Manuel. The example configures two delivery
channels for Manuel. The first delivery channel is Sametime, which is used by
the second delivery channel, SIA, to send the commands to the device.
4.2.1 Requirements for this scenario
To use this scenario, the delivery channel for Lotus Sametime must be
configured. Furthermore, the user should be part of the Intelligent Notification
Service group.
To make sure the Sametime delivery channel is configured, open the
notificationManagerConfig.xml file, which is located in ins_home\config\xml
directory, where ins_home is in the installation directory C:\Program
Files\WebSphere\INS. Sametime should be available as a delivery channel.
To be able to use Intelligent Notification Services, the user has to be a member
of the Intelligent Notification Services user group. This group is defined during
the installation. In the sample installation, it is called insusers. If the user is not a
member of this group, the user will not see the Intelligent Notification Services
tab in the portal.
To use the Mail and Calender Services, the Intelligent Notification Services user
ID needs access to all mail files that it should monitor. To ensure this access:
1. Open Lotus Notes and log in as manuel.
2. Open the mail file for manuel.