Troubleshoot Collaboration Center

 

+
Search Tips   |   Advanced Search

 

Enable logging

You can specify logging in the WebSphere Administrative Console for...

To enable logging.

  1. Open the WebSphere Portal Administrative Console... 
    http://yourPortalServer.yourDomain.com:9090/admin

    .,..and log in as an administrator.

  2. Select...

    Troubleshooting | Logs and Trace | WebSphere_Portal | Diagnostic Trace

  3. Select the check box...

    Enable trace with the following specification

  4. In the text box in the Trace Specification row, type or paste desired logging parameters, separating them with a colon. For example, to log all Collaborative Services operations, enter...
    com.lotus.cs.*=all=enabled

  5. Click Apply, then Close.

  6. Back in the Administration console, click Apply, Save, and then Save again to save changes to the Master Configuration.

  7. Restart the portal server.

The resulting traces will be written to the following file:

PORTAL_ROOT/log/trace.log

 

Parameters to enter for logging specific components

Awareness (Collaborative Services) and collaborative portlets other than People Finder

com.lotus.cs.*=all=enabled

People Finder and WebSphere Member Manager

com.ibm.websphere.wmm.*=all=enabled:com.ibm.ws.wmm.*=all=enabled:WSMM=all=enabled:com.lotus.ap.portlets.*=all=enabled

Person tag and Person menu

com.ibm.wkplc.*=all=enabled

 

People Finder portlet, people awareness, and Person menu problems

Portlet Uses stlinks applet to support awareness? Uses Person tag to support awareness? Other awareness configuration
Notes and Domino
Yes
Yes
Chat and awareness features can be added by modifying portlet edit mode properties
People Finder
No
Yes
No
Common Mail
No
Yes
No
Common Calendar
No
Yes
No
Domino Web Access
Yes
No
Chat and awareness features can be added by configuration of Lotus Instant Messaging server
Team Workplaces
Yes
No

Inline Team Workplaces
Yes
No
Chat and awareness features can be added by configuration of Lotus Team Workplace server
Lotus Instant Messaging Contact List
Yes
No

Who Is Here
Yes
No

Lotus Web Conferencing
Yes
No

Lotus My Team Workplaces
Yes
No

Search Center
No
Yes

 

Problem: People Finder displays a default Help message instead of quick search controls

Solution: Remove any fields that People Finder is configured by default to display that do not also exist in the LDAP directory configured to work with the portal

If you see the following Help message in People Finder, it means its default configuration needs to be corrected. 

People Finder is an online corporate directory that lets users search for 
and view a colleague's contact information and position in the organization's 
structure.

Perform the following tasks:

  1. Log into the portal as an administrator.

  2. Verify that WebSphere Member Manager (WMM) has been installed and configured correctly in your portal.

  3. Open People Finder configuration mode (click the wrench icon).

  4. For each field you see listed in red under the error message "Attribute_field_name was not found in the directory," examine every section of the portlet for references to the field, deselect it in the Attributes and Display Formats table on the Configuration Basics page, and delete the field in any sections where it appears.

    For details on deleting fields, click the Help (question mark) icon in People Finder.

    If all fields do not disappear after you click Apply Changes Now, return to configuration mode and examine sections for occurrences you may have missed. For example, the Person Record page contains multiple sections under the Select a Section label.

 

Problem: Show Person Record does not appear for some users as an action on the Person menu

Solution: Make sure users have appropriate access to the hidden page for People Finder. This access should be granted when People Finder is installed, but verify an administrator has not accidentally deleted the page, or modified users' access to it.

Perform the following tasks:

  1. Log into the portal server as an Administrator.

  2. Select Administration --> Portal User Interface --> Manage Pages.

  3. Under Context Root, locate the page lotus.workplace.hidden.page.PeopleFinder.

  4. Give users access to this page. Users will not see any additional pages in in portal, but they should see the Show Person Record action on the Person menu.

If the problem continues to occur, read the following technote for alternative solutions:

Technote 1174638 People Finder Portlet Does not Display 'Show Person Record' Menu Choice

You can also use Search at IBM Support to find technotes by number.

 

Problem: People Finder shows a message saying it is unavailable

Solution: The 'Portlet is unavailable' message usually appears because the portlet configuration cannot be read.

If you have modified People Finder configuration using Configuration mode, restore the portlet to its default configuration. Perform these tasks:

  1. Log in to the portal as an administrative user.

  2. Go to the Administration tab.

  3. Select Portlet Management --> Portlets.

  4. Search for the People Finder portlet.

  5. In the set of icons for the portlet, click the wrench (Configure portlet) icon.

  6. In the list under Parameters and Values, click the trash can icon for the Config_Complete parameter. This deletes the entire parameter, not just the value specified for the parameter.

  7. Click OK to save changes to the portlet.

  8. Restart the portal server.

 

Problem: People Finder shows no results or tells the customer to try searching later

When a Quick or Advanced search yields more results than are set for the maximum, customers see no results or an error. The number of results returned is the smaller of the two values set in the portlet's configuration area and the server's wmm.xml file.

Solution: Allow more search results.

Adjust the setting for the maximumsearchresultsattribute in the portal server's wwm.xml file and in the portlet's configuration parameters.

 

Problem: The Organization View in the Person Record page does not work properly

Solution: Ensure correct configuration of the Manager attribute in the directory.

If the Organization View for found people does not display properly, ensure that the Manager attribute in the people records of the People Finder directory is specified properly. The Manager attribute must use the DistinguishedName (dn), not the CommonName (cn) or other user-visible value, of a found person's manager. The DistinguishedName (dn) must be valid for all LDAP servers configured to work with Collaboration Center.

 

Problem: Odd-looking values appear in the Manager and Assistant fields

Solution: Make sure the fields have the correct display format.

The LDAP server probably stores the Manager and Assistant attribute values in DistinguishedName (dn) format, a type of unique identifier in LDAP. When, in the Configuration Basics task in People Finder configuration mode, you select the Manager and Assistant (or Secretary) attributes to appear as fields in the People Finder portlet, remember to select Other Person Link as the Display Format for these fields.

 

Problem: The Person Record or Organization View for a found person cannot be opened from a person link in a portlet other than People Finder

Solution: Map attributes between LDAP directories.

The Person menu can be used from other portlets to display a found person's Person Record or Organizational View. But if the source portlet is using a different LDAP directory from the one being used by People Finder, there may be no match if the personal identity attributes of the LDAP directories apply disparate name formats.

To resolve this discrepancy between identity mismatches, you can use the ibm-awarenessPerson attribute to add a link from the People Finder LDAP into another LDAP when person name attributes use different name formats to establish identity.

For example, if the Notes and Domino portlet (configured as Notes View) or the Lotus My Team Workplaces portlet uses a Domino LDAP Directory, the users in the Domino LDAP Directory are probably identified by their Domino DistinguishedNames format, cn=Scott Jones,ou=my_company. If, on the other hand, the People Finder portlet uses an LDAP directory other than Domino, that same person is recognized with a DistinguishedName (dn.) format that might be uid=ssmith,ou=hq,o=my_company. You can create a link between the two different LDAP directories by mapping attributes.

 

Problem: Conflicts occur in People Finder due to concurrent updates by multiple users

The People Finder portlet's Configuration mode has no locking mechanism to prevent update conflicts and overrides by multiple users.

Solution: Consider implementing a plan whereby only one administrator or designer is configuring the People Finder at a given time. Scheduling and communicating single-user sessions for configuring the People Finder will alleviate the potential for lost work.

 

Problem: E-Mail address links may have different behavior in People Finder than in other portlets such as Notes and Domino

The default specification for the attribute E-mail address (ibm-primaryEmail) in the People Finder portlet causes the Send E-Mail action on the Person menu (available on people links in People Finder) to open a new mail message in the HTML-based mail application specified in the user's browser. This may not match behavior of the same action on the Person menu in portlets such as Notes and Domino (when configured as Notes Mail).

Solution: In Configuration mode in the People Finder portlet, specify the display format "People link" for the E-mail address attribute.

 

Problem: Selecting a name and selecting Add to Instant Contacts from the Person menu does not work

Solution: Advise users to launch and log in to their Lotus Lotus Instant Messaging and Web Conferencing client software separately

 

Problem: Adding a name to an empty contact list may require two attempts

In any collaborative portlet, if a user opens the Person menu from a person links and selects Add to Instant Contacts for a group that does not currently have any names, the name may not immediately display in the group list.

Solution: Advise the user to select the command a second time.

 

Lotus My Team Workplaces portlet problems

Problems with the Lotus My Team Workplaces portlet might be the result of faulty configuration of the Lotus Team Workplace server or the portlet.

 

Problem: My Lotus Team Workplaces portlet cannot connect to the Lotus Team Workplace server

Solution: The following error message in the My Lotus Team Workplaces portlet... 

Connection to QuickPlace Server could not be established

...is usually the result of one of the following configuration conditions:

  • The portal user ID is not recognized by the Lotus Team Workplace server.

  • Single Sign-on (SSO) is not set up properly.

  • The Lotus Team Workplace server...

    http://yourServer.yourDomain.com:80

    ...is not running the QPServlet.

  • A Reverse Proxy setting is enabled for Pinnacor Portlets; when this setting is enabled, the My Team Workplaces portlet becomes unable to contact the Lotus Team Workplace server.

To find the reason for the error, follow this procedure:

  1. Make sure your portal ID is current and recognized by the Lotus Team Workplace server.

  2. To test SSO between Team Workplaces and WebSphere Portal, log in to the portal as an administrator and go to... 

    http://yourTeamWorkplaceServer.yourDomain.com/quickplace

    If your name does not appear at the top left corner of the screen, SSO is not working. Resolve SSO issues before proceeding.

  3. To make sure the QPServlet is correctly installed and configured, go to... 

    http://yourTeamWorkplaceServer.yourDomain.com/servlet/QPServlet?actionType=69

    The browser should return a message similar to the following message: 

    QPServlet:LCS Build [Version][Date][WPS build stream]=[KS3224wa][0302.2600][5.1]
Posted Build
Use with QP3.0.1
SESSION
68=whoami
ActionType=6969&s=searchstring

    If the message above (or similar) is not returned, review, and if necessary, repeat the procedure on adding the QPServlet.

  4. Make sure there is no reverse proxy setting enabled for Pinnacor Portlets, or if there is, obtain a fix for this issue from IBM Support. This proxy server is set for the entire JVM, and, without the available fix, prevents the Lotus Collaborative portlets from being able to contact the Lotus Team Workplace server.

    For information on enabling a proxy server for the Pinnacor portlets, see the following technote:

Technote 1114624 Configure Pinnacor Portlets to Display Data

For additional information on troubleshooting the server connection...

 

Problem: Lotus My Team Workplaces portlet does not appear when first deployed

Solution: If the Lotus My Team Workplaces portlet does not appear when you first deploy it, try the suggestions listed for the problem above ("My Lotus Team Workplaces portlet cannot connect to the Lotus Team Workplace server"), especially making sure that the QPServlet is running.

 

Problem: Authentication to the Lotus Team Workplace server is challenged

If you attempt to open a Team Workplace from the Lotus My Team Workplaces portlet, and you see a message requring you to authenticate, then something is incorrectly configured with SSO between WebSphere Portal and the Lotus Team Workplace server.

Solution: To troubleshoot your configuration, read the following technote:

Technote 1158269 Troubleshoot WebSphere Portal, Sametime, QuickPlace and Domino SSO Issues

You can also use Search at IBM Support to find technotes by number.

 

Problem: PlacesForMember cannot be initialized

This error appears in the My Team Workplaces portlet, 

PlacesForMember could not be initialized via QuickPlaceService

and includes the server hostname and user credentials.

Solution: Perform one or more of the following tasks:

  • Modify the configuration parameters shown in the error window and restart WAS.

  • Reinstall the portlet, and log in to the portal again.

  • If you see this error again, and the user credentials are valid for logging in to the Lotus Team Workplace server, verify at least one Team Workplace exists for the user in question.

  • If user ID is null, an authentication problem exists with the SSO token. Refer to the topics that address portal authentication with single signon.

 

Problem: Portlet content is missing or questionable

Solution: Try logging out and logging in again to the portal.

If the information displayed in the portlet is not synchronized with information on the Lotus Team Workplace server, click Refresh to clear the portlet cache.

 

Problem: Attribute values invalid according to the specified TLD

The appserver-out.log reports this problem - 

TWP=>doView cached Exception: JSPG0126E: 
Attribute value invalid according to the specified TLD

Solution: Verify that the latest Collaborative Services files are installed:

Make sure that you have installed (or updated) the latest version of the Collaborative Services files on the Lotus Team Workplace server:

  • The Collaborative Services Java archive, cs.jar

  • The People Awareness Sametime Links JavaScript file, pa_stlinks.js

  • The Person tag language definition file, people.tld

The Collaboration Center installation program looks for the latest version of these files, which are installed with WebSphere Portal.

 

Problem: No Team Workplaces display in portlet

If portlet users do not see a list of their Team Workplaces (My Workplaces) in the default view of the Lotus My Team Workplaces portlet, they should see the message "You do not belong to any workplaces." When users join one or more workplaces, the workplaces to which they belong will appear in the My Workplaces list.

Solution: Perform one of the following tasks:

  • Make sure that you have added users to the membership lists of existing Team Workplaces.

  • Create new Team Workplaces and add the new members using correct user Ids.

 

Problem: What's New and My Tasks views do not display the pages of inner rooms

If you have created a Team Workplace that has inner rooms, the My Team Workplaces portlet does not show pages from inner rooms in the views What's New and My Tasks.

Solution: Redesign workplaces that are sources for the portlet without inner rooms.

 

Problem: A limitation with the Lotus Team Workplace API causes page content to display incorrectly

If you search or open the My Pages view of a Team Workplace, you will notice that the columns of Page, Workplace, and Author have additional, unexpected content. In addition, sometimes pages in a Team Workplace display no links. Links are suppressed in Team Workplace pages rendered by the portlet when invalid URLs are returned from the Lotus Team Workplace server.

Solution: TBD

 

Problem: Tasks in My Team Workplaces portlet must be assigned to individuals, not to groups

If you assign a Team Workplace task to a group, members of the group will not see the task in the My Tasks view of the My Team Workplaces portlet.

Solution: Make sure that you always assign tasks in My Team Workplaces to a specific person.

 

Problem: Searches using wildcard characters return no results

Lotus Team Workplace 3.0.x does not support wildcard searches using the asterisk (*) or question mark (?).

Solution: Advise users to avoid these characters while searching.

 

Problem: Searching for My Team Workplaces before and after a certain date includes the specified date

The Lotus My Team Workplaces portlet returns results for searches before and including the specified date, while Lotus Team Workplace returns results before and excluding the specified date. Similarly, the portlet returns results for searches after and including the specified date, while Lotus Team Workplace returns results after and excluding the specified date. Solution: Advise users whose searches return unexpected results of these differences.

 

Problem: Searching for the title of a Team Workplace returns no matches

Lotus Team Workplace 3.0.x domain search does not include the titles of Team Workplaces in the search index. Therefore, when a user tries to search for a Team Workplace by its title, the portlet will always display the No Matches Found message.

Solution: Advise users to search only for content in pages of their Team Workplaces.

 

Problem: Lotus My Team Workplaces does not work if secure sockets layer (SSL) protocol is enabled

If you have configured the My Team Workplaces portlet to run on a server configured to run secure sockets layer protocol (HTTPS), workplaces will not appear in the portlet nor will they be available for search.

Solution: Avoid configuring your Lotus Team Workplace server with SSL.

 

Lotus Web Conferencing portlet problems

Problems with the Lotus Web Conferencing portlet might be the result of faulty configuration of the Lotus Web Conferencing server or the portlet.

 

Problem: Cache properties affect portlet performance

The Collaboration Center installation program sets the LotusMeetings caching properties used by the Web Conferencing portlet.

Solution: Perform one or both of the following tasks:

  • Verify that the default settings for cache properties are correct.

  • (Optional) Modify the cache settings to improve portlet performance.

To view or modify LotusMeetings cache properties, follow these steps:

  1. Open the file CacheManagerService.properties from the following location: 
    PORTAL_ROOT/shared/app/config/services/

  2. Verify that the following lines appear with the default values shown here: 
    # LotusMeetingsProperties cache properties
cache.LotusMeetingsProperties.enabled=true
cache.LotusMeetingsProperties.lifetime= 2592000
cache.LotusMeetingsProperties.size=10000
cache.LotusMeetingsProperties.replacement=moderate
cache.LotusMeetingsProperties.admit-threshold=0

  3. Add these lines if you do not see them in the CacheManagerService.properties files.

  4. If necessary, edit the default values to boost the performance of the portlet.

  5. If you edit the file, restart the portal server.

You can also adjust the setting of the cache.lifetime.in.seconds property in the LotusWebConferencingUI.properties file. By default, this setting causes the portlet to check the Lotus Web Conferencing server approximately every half hour (2000 seconds) to see if any new meetings have been scheduled. For a very active Lotus Web Conferencing server, one that hosts a high volume of meetings, you might need to decrease this number for more frequent checks. For a less active Lotus Web Conferencing server, one that hosts fewer meetings, you might need to increase this number for infrequent checks.

To adjust the cache.lifetime.in.seconds property, follow these steps:

  1. Open the LotusWebConferencingUI.properties file in a text editor.

  2. Scroll to the comment line: 
    # DO NOT TRANSLATE ANY OF THE MESSAGES BELOW THIS POINT

  3. After that comment line, find the cache.lifetime.in.seconds property: 
    # How often to update the cache (2000 seconds = approx 1/2 hour)
    # For 1000 meetings on the ST server
    # it takes 1000-2000 seconds to retrieve all meeting properties
    cache.lifetime.in.seconds = 2000

  4. Edit the variable as needed to set the frequency of checks that the Web Conferencing portlet makes against the Lotus Web Conferencing server that hosts meetings.

  5. Save and close the LotusWebConferencingUI.properties file.

  6. Restart the portal server for the changes to take effect.

 

Problem: Web Conferencing portlet does not respond immediately when first deployed in the portal

The first time you deploy the Web Conferencing portlet in the portal, the portlet needs to load all of the meeting information from the Lotus Web Conferencing server. This process takes approximately 1 to 2 seconds for each meeting hosted on the Lotus Web Conferencing server. Therefore, when the portlet is installed in the portal and added to a page of the portal, it will not respond immediately.

Solution: The amount of time needed before the portlet responds in a portal page depends on the number of meetings hosted on the Lotus Web Conferencing server. For example, if there are 1,000 meetings hosted on the Lotus Web Conferencing server, expect the Web Conferencing portlet to take approximately 30 minutes to load. If you have configured multiple Lotus Web Conferencing servers using clustering to balance workload, this wait time will be reduced.

 

Problem: Searching for a meeting yields no results

Solution: If portlet users do not see meetings displayed in the portlet after a significant period of time, check the following requirements and conditions:

  • The Lotus Web Conferencing server must be up and running.

  • The PurgeMeeting agent should be enabled on the Lotus Web Conferencing server, as described in the configuration prerequisites for the Lotus Web Conferencing portlet.

  • The values specified for the portlet configuration parameters SametimeSSLX and SametimePortX must be correct.

 

Problem: Authentication to Sametime Meeting Center is challenged

Users of the Web Conferencing portlet may be prompted for their credentials (user name and password combinations) when they try to access the Sametime Meeting Center.

If the SSO token is not being shared properly between the portal server and the Lotus Web Conferencing server, portlet users might be re-challenged for their credentials when using the Lotus Web Conferencing portlet in the following contexts:

  • Attending a meeting

  • Testing a meeting

  • Replaying a meeting

  • Access the Sametime Meeting Center

Solution: Verify that SSO is working properly between the portal server and the Lotus Web Conferencing server. Perform the following steps:

  1. Launch your browser and log in to the portal with your user name and password.

    Example: http://yourPortalServer.yourDomain.com/wps/portal

  2. In the same browser session, type the URL for your Lotus Web Conferencing server.

    Example: http://yourWebConferencingServer.yourDomain.com/stcenter.nsf

  3. Click Attend a Meeting.

    If you see your name at the top right corner of the screen, SSO is working properly.

    If your name does not appear at the top left corner of the screen, SSO is not working. Resolve SSO issues before proceeding. Read the following technote:

Technote 1158269 Troubleshoot WebSphere Portal, Sametime, QuickPlace and Domino SSO Issues
You can also use Search at IBM Support to find technotes by number.

 

Problem: Poor performance hinders portlet use

Solution: Check the cache properties of the portlet and the Sametime Meeting agents that control performance factors. Perform the following tasks:

  • Ensure that the PurgeMeeting agent is set appropriately, as described in the configuration prerequisites for the Lotus Web Conferencing portlet.

  • Check the settings for the LotusMeetings caching properties used by the Web Conferencing portlet, specifically the cache size and cache objects lifetime, as described in Cache properties affect portlet performance.

 

Problem: Web Conferencing portlet does not display properly

Solution: Try checking the LotusWeb ConferencingUI.properties file to see the default UI settings and the location of JSPs that render the views of the portlet. You will also need to know the location of the portlet JSPs if you intend to customize the portlet.

To verify and edit the default settings of the LotusWebConferencingUI.properties file, follow these steps:

  1. Open the LotusWebConferencingUI.properties file in a text editor.

  2. Scroll to the comment line: 
    # DO NOT TRANSLATE ANY OF THE MESSAGES BELOW THIS POINT

  3. After that comment line, find the following properties to verify and edit, if necessary:

    You can change the path to a JSP that renders a main view of the portlet: 

    #Main JSPs 
    ResultURI = /jsp/html/ViewResult.jsp
    DetailURI = /jsp/html/ViewDetail.jsp
    NewMeetingURI = /jsp/html/ViewNewMeeting.jsp
    EditMeetingURI = /jsp/html/ViewNewMeeting.jsp
    EditURI = /jsp/html/Edit.jsp
    ConfigureURI = /jsp/html/Configure.jsp
    ErrorURI = /jsp/html/Error.jsp
    MessageURI = /jsp/html/ViewMessage.jsp

    You can change the path of a JSP that renders a particular element of a view: 

    #JSP location
    jsp.detail = /jsp/html/Detail.jsp
    jsp.menu = /jsp/html/Menu.jsp
    jsp.list = /jsp/html/List.jsp
    jsp.search = /jsp/html/Search.jsp
    jsp.menu.list= /jsp/html/ListMenu.jsp
    jsp.menu.top.list = /jsp/html/ListMenuTop.jsp
    jsp.newMeeting = /jsp/html/NewMeeting.jsp
    jsp.menu.edit = /jsp/html/EditMenu.jsp
    jsp.menu.newMeeting = /jsp/html/NewMeetingMenu.jsp
    jsp.menu.detail = /jsp/html/DetailMenu.jsp
    jsp.menu.search = /jsp/html/SearchMenu.jsp
    jsp.message = /jsp/html/Message.jsp
    jsp.menu.message = /jsp/html/MessageMenu.jsp

    You can change the path of a JSP that renders the images used by the portlet: 

    # Image locations
    image.go = /images/go
    image.back = /images/close
    image.back.small = /images/lt-an-canceliconsmall 
    image.next = /images/next
    image.previous = /images/previous
    image.save = /images/register
    image.error = /images/error
    image.divider = /images/divider
    image.dot = /images/dot
    image.attachment = /images/attachment
    image.new.meeting = /images/add
    image.advanced.meeting = /images/meetingcenter
    image.test.meeting = /images/lt-an-testmtgicon
    image.edit.meeting = /images/edit
    image.delete.meeting = /images/delete
    image.information = /images/inlineHelp
    image.reset = /images/reset

    You can change the properties that specify the Lotus Web Conferencing server port ID and the enablement of Secure Sockets Layer (SSL): 

    # Default port and SSL values
    default.st.port = 80
    default.st.useSSL = no

  4. Edit the properties as needed.

  5. Save and close the LotusWebConferencingUI.properties file.

  6. Restart the portal server for the changes to take effect.

 

Problem: Web Conferencing portlet yields password errors when users try to create or search for meetings

Users who attempt to create a new meeting or search for an existing meeting may see one of the following errors in the portlet:

  • "Passwords cannot contain special characters. Enter a different password."

  • "Unable to access Sametime due to incorrect logon"

Solution: Read and try the suggested solutions in the following technote:

Technote 1170825 Password Errors When Using Web Conferencing Collaboration Center Portlet

You can also use Search at IBM Support to find technotes by number.

 

Problem: Meeting attachments sometimes do not appear in the Web Conferencing portlet

Solution: If your meeting contains attachments and these attachments do not appear when you open the meeting using the Web Conferencing portlet, verify that the Lotus Instant Messaging and Web Conferencing server has both the Sametime 3.0 Service Pack 1 (SP1) and any necessary hotfixes that correct this problem.

 

Who Is Here portlet problems

Problems with the Who Is Here portlet might be the result of faulty configuration of the Lotus Instant Messaging server or the portlet.

 

Problem: When the Who Is Here portlet is on the same page as Inline Team Workplaces, and the Lotus Team Workplace server is release 3.1, names may appear twice in the Who Is Here contact list

Solution: Advise users not to add the Who Is Here portlet to the same portal page as Inline Team Workplaces.

 

Lotus Instant Messaging Contact List portlet problems

Problems with the Lotus Instant Messaging Contact List portlet might be the result of faulty configuration of the Lotus Instant Messaging server, the portlet, or the user's browser software.

 

Problem: Lotus Instant Messaging Contact List portlet is not completely accessible with JAWS screen reader

Users of the JAWS screen reader software may have difficulty selecting radio buttons in the Lotus Instant Messaging Contact List portlet.

Solution: Use screen reader software other than JAWS.

 

Notes and Domino portlet problems

Problems with the Notes and Domino portlet might be the result of faulty configuration of the Domino server that contains source database(s) for the portlet, the portlet, or the user's browser software. Some problems occur only in instances of the portlet whose portletType parameter is configured with specific values, such as NOTESVIEW.

 

Problem: Notes portlets of certain types do not resolve the Domino mail server and database for authenticated portal users when the corporate LDAP service is not Domino LDAP

When Domino LDAP is not configured as the Domino Directory for the Collaborative Services service for WebSphere Portal, the Notes and Domino portlet, when configured with a portlet type of either MYINBOX, MYCALENDAR, or MYTODO, may fail to resolve the mail file and mail server information. Consequently, the portlet displays an ERROR MAILINFO link. Clicking the error link results in another error message indicating that portlet content cannot be displayed because the Notes server does not recognize the user name and password used to log in to the portal.

Solution: Advise portal users that they must edit the properties of any Notes and Domino portlet they use to access their mail, and manually specify the server and database names for their source mail database.

 

Problem: In the Notes and Domino portlet configured with a portletType of MYINBOX, hiding either the File size or Attachment icon column may cause XML error

If users edit the portlet properties and, under Show:, deselect either or both the File size or Attachment icon column, the portlet may display an XML error.

Solution: Advise users to leave both of these columns selected (showing) in the properties.

 

Problem: Deleting a document in one instance of the Notes and Domino portlet does not refresh other instances of the portlet that are above it on the portal page

This problem can occur when multiple instances of the Notes and Domino portlet, deployed on the same portal page, display the same document in the same source Notes database. If a user deletes a document from a portlet that is below another portlet displaying the same document, any portlets above do not refresh to show the deletion.

Solution: Advise users to delete the document from the first portlet deployed on the page, and the portlets below it will refresh.

Note: In some situations users, or you as portal administrator if you populate portal pages, should always place certain portlet types above others on a portal page. For example, if the first instance of Notes and Domino is configured with a portlet type of MYCALENDAR and the second is configured with a portlet type of MYTODO, showing the same source database, deleting documents from the My ToDo portlet will not refresh the My Calendar portlet because it is above the My ToDo portlet. Users also cannot delete documents directly from the My Calendar portlet, so this arrangement is not useful. The My Calendar portlet should always be placed below a My ToDo portlet displaying the same source database.

 

Problem: In the Notes and Domino portlet, specifying view or server names by typing may not work

If users edit the Notes and Domino portlet and attempt to add a view by typing a visible view title such as "All Documents," the view may not be saved in the portlet. In addition, typing a view or server name that contains a double quote (") character does not work.

Solution: Advise users to select view and server names from the drop-down lists provided instead of typing names. Also, if users are familiar with Notes database design and know view alias names (for example, ($All) instead of All Documents), typing an alias name works to specify a view.

 

Problem: In the Notes and Domino portlet, no error message appears when users attempt to add views to which they have no access in the source database

Solution: If a user cannot add views to this portlet from a specific database, examine the ACL of the source database and correct it if it is set to No Access for the user.

 

Problem: In the Notes and Domino portlet, options that open new windows in the Lotus Notes client software may function improperly if Notes is not already launched

If users edit the properties of the portlet and specify Lotus Notes, if available for the View documents in option, but do not launch the Note client software ahead of time, login errors may occur, or view focus may be incorrect, when users take actions, such as creating a mail message, that require Lotus Notes to open a new window.

Solution: Advise users to launch the Lotus Notes client software, and enter their Notes password, before using the Notes and Domino portlet when the Lotus Notes, if available option is specified.

 

Problem: Difficulty editing repeating tasks or calendar documents in the Notes and Domino portlet

If the Notes and Domino portlet displays a To Do view or Meetings view, editing repeating tasks or calendar documents (for example, meetings) requires specific steps. For example, when a user selects a repeating item and then selects Edit from the drop-down list under the Actions (down arrow) icon, a dialog box may display dates incorrectly so that a single instance of the task cannot be selected. In addition, editing the parent document of a set of repeating items causes problems in the way Notes manages the documents.

Solution: To edit any repeating item, users must select one of the instances of the item (not the parent item) and select Open, instead of Edit, from the Actions drop-down list. Selecting Open displays a dialog box where users can specify which repeating item they want to edit. In some cases the dialog box does not appear; if this happens, users can edit only the first repeating item.

 

Problem: Cannot always save changes to sorting preference when editing properties of Notes and Domino portlet

Changes to the sorting preference in the edit properties may not be saved, or if saved, may not affect behavior in the view mode of the portlet. For example, if a user edits a Notes and Domino portlet configured with a portlet type of MYINBOX, selects Ascending for sorting, and clicks Save, the change is lost and the preference is set back to Descending.

Solution: In view mode, users can click the header of any column that sorts, for example a Date or Due column, to sort the column.

 

Problem: Edits to title of Notes and Domino portlet may persist even when user clicks Cancel

Solution: If the Notes and Domino portlet is configured with a portlet type of MYCALENDAR or MYINBOX, and users edit the portlet title, advise them to make sure the title is correct before saving changes to the portlet properties.

 

Problem: In Notes and Domino portlet configured with MYCALENDAR portlet type, the New Calendar Entry button may create incorrect document

If the Domino server hosting the mail database is running R5, the New Calendar Entry button always creates an Appointment, not a calendar entry, even if the user selects a different calendar document, such as Meeting, from the Entry type drop-down list.

Solution: Advise users who want to create calendar documents other than Appointments to click the Launch Application button and use the New button at the top of the window to specify the type of calendar document.

 

Problem: In some portal configurations, drop-down lists for selecting server and database for the Notes and Domino portlet display incorrectly

If the portal configuration runs SSL, does not support DIIOP, or restricts access to Java, JavaScript, or COM run by portal users, editing properties for the Notes and Domino portlet may not work correctly. Users may notice drop-down lists for selecting a source Notes server and database painting incorrectly with check mark icons out of place, obscuring buttons at the bottom of the screen.

Solution: Users can still make entries in the drop-down lists, and click buttons such as Done at the top of the screen.

 

Problem: In the Notes and Domino portlet, deleting calendar documents directly does not allow proper workflow

When the Notes and Domino portlet is configured to display a calendar or meetings view, selecting Delete from the Actions drop-down list for a document deletes the document, but does not properly manage the deletion. For example, deleting a meeting does not inform invitees that the meeting has been canceled.

Solution: Advise users to select Open instead of Delete from the Actions drop-down list, and then click the Delete action in the separate browser window that appears.

 

Problem: In the Notes and Domino portlet, the icon for creating new documents does not work if specified form has a space character in its name

This problem occurs when users set up a view in a Notes and Domino portlet, specify an icon for creating documents, specify a form that has a space in its name, and also set the View documents in option to Lotus Notes, if available.

Solution: Advise users to specify only forms that have no space characters in their names in the source Notes database. If necessary, ask the database designer to adjust form names.

 

Problem: Cannot use an HTTP/HTTPS port setting other than the default for the Domino server that is the data source for the Notes and Domino portlet

If the administrator of the Domino server that contains Notes databases that are data sources for the portal changes the http or SSL (https) port number of the Domino server, the Notes and Domino portlet displays errors and fails to load properly.

Solution: The administrator of the Domino server must make certain that the http/https port number matches the default for the portlet types MYINBOX, MYTODO, and MYCALENDAR; there is no way to specify a non-default port number for these types of portlets. For the other types of the Notes and Domino portlet, the port number can be appended to the server name. But making the port number match the default for the portlets is less error-prone.

 

Problem: In Notes and Domino portlet, selecting Switch ID causes unexpected behavior

There are several problems.

  • The portlet re-displays in the maximized state after switching ID, and may cause users to assume other portlets have disappeared from the current page.

  • When the portletType is set to MYINBOX, switching ID between users who have different releases of source mail (for example, Domino 6.03 and Domino 6.5) can cause the view to appear blank. Also, when columns are specified to display people awareness and launch documents, the settings may change to inappropriate columns.

Solution: Take one of these actions:

  • To correct the problem with maximizing, advise users to click the Restore icon in the title bar of the portlet after switching to a different ID in this portlet.

  • To correct the problem with the blank view of mail, remove the portlet from the portal page and re-add it.

  • To correct the problem with column settings, avoid using Switch ID; advise each user to log into the portal.

 

Domino Web Access portlet problems

Problems with the Domino Web Access portlet might be the result of faulty configuration of the Domino server, the portlet, or the user's browser software.

 

Problem: Logging out of the Domino Web Access (iNotes) portlet also logs out of WebSphere Portal

Solution: If users of the functional areas All or Welcome in this portlet see a Logout button, advise them not to click the button -- doing so logs out of the WebSphere Portal session.

 

Problem: Some parameters for Domino Web Access portlet may disappear when saving portlet configuration

If a portal administrator edits and saves the Domino Web Access (iNotes) portlet configuration using Portlet Management, three parameters that are blank by default -- PortNumber, UseReverseProxyString, and reverseProxyPortNumber -- disappear from the list of parameters for the portlet.

Solution: To specify values for any of these parameters, type the parameter's name in the blank left field at the bottom of the list, type the desired value in the right field, and click the Add button.

 

Problem: Cannot create calendar entries in Domino Web Access portlet when source database design is UseiNotesTemplate

If users' source mail databases have the UseiNotesTemplate design, and the Domino server is earlier or later than Domino 6.01, users of the Domino Web Access portlet cannot create calendar entries directly in the portlet. Solution: Advise users to click Launch Application and create calendar entries in the new window that opens.

 

Problem: Domino Web Access portlet fails with combination of IBM Edge server and Domino R5 mail server

The IBM Edge Server is not compatible with the version of SSO used on a Domino R5 server, and SSO is required for the Domino Web Access portlet.

Solution: If you deploy the Domino Web Access portlet in your portal, verify the Domino server where all users' mail databases are stored is running R6, and that the database design inherited by the databases is R6.

 

Problem: Notes and Domino portlet set with new parameter can cause loss of access to iNotes mail design

The UseiNotesTemplate parameter, when enabled in the Notes and Domino portlet, allows iNotes users to access their iNotes mail through the Notes and Domino portlet and take advantage of people awareness in the portlet.

However, if a user adds an instance of the Notes and Domino portlet that is not enhanced with this parameter, and the Domino Web Access (iNotes) portlet to the same portal page, and then uses the Notes and Domino portlet to access mail that uses the iNotes design, both the Notes and Domino portlet and the Domino Web Access portlet fail to load the iNotes mail design, and provide only the Notes mail design.

Solution: If your collaborative portal is new and you have not yet set up user access for creation of portlets, the simple solution is to prevent users of the Domino Web Access (iNotes) portlet from adding instances of the Notes and Domino portlet to their pages, so that these two portlets will never coexist.

If you have an existing portal where users already have access to add portlets, and have added instances of the Notes and Domino portlet that are not configured with the new UseiNotesTemplate parameter, any users whose source mail has the iNotes design and who attempt to access their mail using the Notes and Domino portlet will encounter the error. Take the following steps:

  • Advise users not to mix instances of these two portlets on pages. Users should rely on the appropriate portlet for their source mail database.

  • If all your users have iNotes mail designs, remove instances of the Notes and Domino portlet that do not have the UseiNotesTemplate parameter from availability for future deployment.

  • On any page where a user has encountered the error, to correct the error on that page, deploy a new instance of the Domino Web Access portlet, and create a new mail memo in the portlet.

 

Problem: The Domino Web Access (iNotes) portlet does not support the use of Netegrity SiteMinder single sign-on

When the portal is configured to use SiteMinder, the Domino Web Access portlet cannot access its source database and displays an error message.

Solution: Do not use the Domino Web Access portlet in a portal configured with SiteMinder.

 

Problem: Cursor focus can be incorrect when entering user name for Domino Web Access portlet

In portlets that use the iFrame feature, when users type in a text input field using Microsoft Internet Explorer, cursor focus can unexpectedly shift to areas of the portlet outside the field. This happens when the iFrame points to a Web site that automatically moves focus to a text input field, and users move in or out of edit mode, or maximize or minimize the portlet.

Solution: Advise users to click inside any input field before typing.

 

Domino Document Manager portlet problems

Problems with the Domino Document Manager portlet might be the result of faulty configuration of the Domino server running Lotus Domino Document Manager software, the portlet, or the user's browser software.

 

Problem: Cursor focus can be incorrect when entering user name for Domino Document Manager portlet

In portlets that use the iFrame feature, when users type in a text input field using Microsoft Internet Explorer, cursor focus can unexpectedly shift to areas of the portlet outside the field. This happens when the iFrame points to a Web site that automatically moves focus to a text input field, and users move in or out of edit mode, or maximize or minimize the portlet.

Solution: Advise users to click inside any input field before typing.

 

See also

Home | Support | Terms of use | Feedback

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.