Friday, January 3, 2014
Wednesday, December 25, 2013
Thursday, December 12, 2013
Lotus Sametime users within the same Lotus Domino domain (and even across different domains) can see one another, as long as their "home" servers are aware of the existence of other Lotus Sametime servers through a "Community."
To ensure that your servers are aware of one another, create Sametime connection documents in both directions (i.e. Server A -> Server B and Server B -> Server A) using the Domino administrator client.
To check whether your Lotus Sametime servers can see other members of the community:
- Open a Web browser, go to the Sametime Web Administration Utility (http://yourserver/stcentre.nsf and choose the "Administer the server" link).
- Expand the "Configuration" heading and then choose the "Connectivity" option.
- When the "Configuration - Connectivity" page opens, click the "servers in the Community" tab.
- If you see both Server A and Server B under the "Meeting Servers that are connected" section, your servers should be able to communicate with one another.
To create the Lotus Sametime connections:
- Start your Domino administrator client.
- Go to the Configurations Tab.
- Expand the server's Twistie and choose Connections.
- On the Action Bar, choose "Add Connection," make the connection type "SameTime," complete the Source (Server A) and Destination (Server B) server fields, and add an optional network address for the destination server.
- Now add another connection document going in the other direction.
I have seen this occurring when the Sametime server utilizes LDAP authentication, rather than Domino authentication to log-in.
If you are using this configuration, change the connection settings in your location document from "Automatically" to "Manual," disconnect from the Sametime session and try to log in again. In the username and password window, try either your short name (as specified in the Domino Directory) or your e-mail address, in conjunction with your Internet password.
As an example, rather than logging onto Sametime through Notes as "Mathew Newman/iteam," try either "mnewman" or "email@example.com."
The easiest way to confirm that your Lotus Sametime servers are members of the same community is to check the "Community" settings in the Lotus Sametime Web administration client.
- Open a Web browser, go to the Sametime Web Administration Utility (http://yourserver/stcenter.nsf and choose the "Administer the server" link), expand the "Configuration" heading and then choose the "Connectivity" option.
- When the "Configuration - Connectivity" page opens, click the "servers in this community" tab.
- If you see both the primary server and secondary server under the "Meeting Servers that are connected" section, your Lotus Sametime servers should be able to communicate with one another.
I'm going to go out on a limb here, and suggest that you will not see both servers in this section. From the description of your setup, I'm guessing that your infrastructure is that your primary server is on one machine and your secondary server is on a separate machine.
But from what you have indicated, both servers are members of the same Lotus Domino domain ("member of the primary Sametime server at the time of installation"). This means that the servers already "trust" one another -- being members of the same organization. They are therefore able to see all servers and users within the domain, because the Sametime servers share the same Domino directory.
A Domino domain is a collection of servers and users who share the SAME Domino directory (names.nsf/ Public Address Book, etc). An organization is a security mechanism for creating and identifying entities (servers/users) within the Lotus Domino domain.
If both servers are members of the same Domino domain, then you simply need to create a Sametime connection document in your Domino directory, similar in the way to creating a replication connection document.
- In your Domino Administrator client, go to the configurations tab, expand the Server's Twistie and then choose "Connections."
- On the Action Bar, choose "Add Connection", make the connection type "Sametime", complete the Source (Primary server) and Destination (Secondary server) server fields and add an optional network address for the destination server.
- Add another connection document going in the other direction.
Give your system a little while to detect the new configuration, and you should see both Lotus Sametime servers listed as "Connected."
If your servers are not part of the same Lotus Domino domain, then you will need to do a little more work:
- Cross certify the two servers , so that the servers trust one another.
- Configure Directory Assistance on both Lotus Sametime servers, so the servers can access one another's directories.
- Create the Lotus Sametime connection documents described above, so the Lotus Sametime servers can communicate.
From "The ABCs of enabling Notes and Domino applications with Sametime," by John Fiola, consultant, Lotus, which originally appeared in the Sept./Oct. edition of The View.
If you choose to host Sametime-enabled Notes applications from a Sametime server, no special server setup is required. The Sametime server can be installed on Windows NT.
If you want to serve Sametime-enabled applications from a Domino server, you will have to do the following:
1. Install the Sametime server. When you install the Sametime server, three databases are created that are used for deploying Sametime applications: the Secrets database (StAuthS.nsf), the Tokens database (StAuthT.nsf) and the VPUserInfo database (VPUserInfo.nsf).
The Tokens and Secrets databases handle authentication and log in to the Sametime servers for the users of a Sametime-enabled application.
The VPUserInfo database stores information used to restrict whom a user can see or who can see the user. This information is configured with the Connect client. Restrictions apply to both the Connect client and to applications through which the user may connect.
2. Replicate databases to the Domino application server. The Secrets database and the Tokens database must be replicated from the Sametime server onto the data directory of the Domino server, maintaining the same file names as on the Sametime server.
Unlike the Secrets database, the Tokens database doesn't have to be regularly replicated to the application server, but it is recommended that you replicate it at least once. The file names must be maintained because the Sametime agents have these file names hard-coded into them.
The VPUserInfo database does not need to be replicated onto the Domino application server. Access restrictions will be checked when the user logs in to the Sametime server.
Once a Domino application server is Sametime-enabled with the Tokens and Secrets databases, it can host multiple Sametime-enabled databases. You do not need to put new replicas of the Tokens and Secrets databases onto the application server each time you create a new database.
- Open the "VPUserinfo.nsf" database located on your Lotus Sametime server and locate the record for your user.
- Check to see that there is only one instance of this user in the Sametime VPUserInfo database.I have seen instances where even though the records should be stored in canonical format, a user has had multiple Lotus Sametime records that confuse who is actually logging in, and what their individual settings are.
- Delete the record(s) for this user. I should warn you though that, there is a side effect -- the user will lose the buddy list they have created.
- Log the user into your Lotus Sametime server through the Sametime Connect client or Browser Connect client. The user should have a new (blank) buddy list.
- Check the user's Lotus Sametime configuration by choosing the "Options" menu, and then "Who can see if I am online."
- Make sure the setting is "Everybody can see if I am online." Add a new person or group to the Sametime buddy list, and then check to make sure the user can chat normally.