How can you figure out the name format for STLinks so that it doesn't need to call the resolver
Category Sametime Technote
With Sametime Links there is a command that displays the awareness state for users, the command is typically something like this:
writeSametimeLink("CN=Carl Tyler/OU=US/O=Instant","Carl Tyler",false)
The first parameter is the UserId for the person, the second parameter is the display name you want used for the person, and the last option is if you want the name to be resolved by Sametime.
Basically you want to avoid using the resolve option of true, as this puts a burden on the Sametime Server (which is already struggling with the Notes 6.5 and later awareness calls) so try and leave the resolver alone. By not calling the resolver, you'll have less impact on the server and the awareness state for the user will also display quicker on the page. Typically the STUserID is the canonical name of the user, so for example, Carl Tyler/US/Instant is CN=Carl Tyler/OU=US/O=Instant, seems easy enough, but what if you're using LDAP? Well then the name format typically changes to something like CN=Carl Tyler,OU=US,O=Instant.
But let's say you're still having problems, and you're not sure what format your Sametime server is seeing (as this can be tweaked in the Sametime config). The easiest way is to get a page working where you login to Sametime Links, and adding an additional function to the page that shows you your logged in STUserID, then form this you should be able to work out what the other user name formats are. Here is the function to add to your STLinks page:
function STLinksLoggedIn(myUserId, myUserName){
alert("ST Links Applet Logged in with UserID " + myUserId + " and the display name " + myUserName);
}
With Sametime Links there is a command that displays the awareness state for users, the command is typically something like this:
writeSametimeLink("CN=Carl Tyler/OU=US/O=Instant","Carl Tyler",false)
The first parameter is the UserId for the person, the second parameter is the display name you want used for the person, and the last option is if you want the name to be resolved by Sametime.
Basically you want to avoid using the resolve option of true, as this puts a burden on the Sametime Server (which is already struggling with the Notes 6.5 and later awareness calls) so try and leave the resolver alone. By not calling the resolver, you'll have less impact on the server and the awareness state for the user will also display quicker on the page. Typically the STUserID is the canonical name of the user, so for example, Carl Tyler/US/Instant is CN=Carl Tyler/OU=US/O=Instant, seems easy enough, but what if you're using LDAP? Well then the name format typically changes to something like CN=Carl Tyler,OU=US,O=Instant.
But let's say you're still having problems, and you're not sure what format your Sametime server is seeing (as this can be tweaked in the Sametime config). The easiest way is to get a page working where you login to Sametime Links, and adding an additional function to the page that shows you your logged in STUserID, then form this you should be able to work out what the other user name formats are. Here is the function to add to your STLinks page:
function STLinksLoggedIn(myUserId, myUserName){
alert("ST Links Applet Logged in with UserID " + myUserId + " and the display name " + myUserName);
}
| Permalink | 
