Resolving Problems with Business Cards

If business cards are not displaying user information as expected, check the server configuration, then the client, and finally, the business cards themselves.

About this task

Checking the server configuration

Check and validate the configuration on the storage repository you use with the Sametime® Community Server. A configuration problem is the most likely cause of problems with Business Cards. For more information, see the appropriate section in Setting up business cards.

Checking the UserInfo servlet on the client

The UserInfo servlet on the client receives and responds to client requests. The servlet must be working correctly to provide the requested details for Business Cards.

Follow these steps to verify that the UserInfo servlet is responding correctly.

Procedure

  1. Determine the distinguished name (DN) of the user whose Business Card you want to view. Here are sample DNs of the various directory types:
    • Domino® directory: cn=sametime User/O=RENOVATIONS
    • Active directory: cn=Sametime User, cn=users,dc=austin,dc=renovations,dc=com
    • TDS directory: uid=Sametime user,ou=Austin,o=RENOVATIONS
  2. Compose a URL to simulate the HTTP request that the client makes to retrieve details for a Business Card, for example:
    protocol://host_name/servlet/UserInfoServlet?operation=3&setid=1&UserId=User_DN
  3. where:
    • protocol = http or https
    • host_name = Fully qualified host name of the Sametime server
    • User_DN = The full distinguished name of the user for whose information you are seeking
    Examples
    • Domino Directory: http://sametime.example.com/servlet/UserInfoServlet?operation=3&setid=1&userId=cn=Sametime User/O=renovations
    • Active Directory: http://sametime.example.com/servlet/UserInfoServlet?operation=3&setid=1&userId=cn=Sametime User,cn=users,dc=austin,dc=renovations,dc=com
    • TDS Directory: http://sametime.example.com/servlet/UserInfoServlet?operation=3&setid=1&userId=cn=uid=Sametime User,ou=Austin,o=RENOVATIONS
    Note:
    • The name "UserInfoServlet" is case sensitive.
    • Do not use apostrophes or quotation marks in the URL.
    • Do not use spaces in the URL for the UserInfo servlet operation. Spaces are translated as %20 in the URL, and the servlet will not produce a result.
    • The following example includes a space between "Sametime" and "User": http://sametime.example.com/servlet/UserInfoServlet?operation=3&setid=1&userId=cn=Sametime User/O=IBM. The space is then translated as %20, which is inserted before the word "User" to represent the space: http://sametime.example.com/servlet/UserInfoServlet?operation=3&setid=1&userId=cn=Sametime%20User/O=IBM
  4. Enter the URL you've composed into a web browser's address field and view the result.
  5. If you do not see the details you are expecting to see, enable tracing for the UserInfo servlet:
    • Stop the Community Server.
    • Edit or add the setting USERINFO_DEBUG_LEVEL=5 in the [debug] section of sametime.ini file.
    • The trace file is in the Trace folder. It will have a name and format like UserInfo_091021_1818.txt for the UserInfo Server Application and UserInfoHTTP_091231_2240.txt for the UserInfo servlet.
    • Restart the Community Server.
    • When the server is fully started, send an HTTP request using a web browser to activate the servlet.
  6. An UNKNOWN error for the "user id" means the user ID specified could not be located. The most common reasons for this error are:
    • An incorrect user distinguished name has been specified.
    • The directory in which the user is located is not reachable/searchable.

What to do next

Checking the client

If the UserInfo servlet on the client is responding correctly, enable client-side tracing to determine what is happening on the client. Follow the instructions in Logging and tracing on the Sametime Embedded and Connect Clients.