IBM WebSphere Group List Server Component, Version 6.1.0.1 Readme

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this fix pack

Fix and update history

This fix pack includes cumulative APAR LI71413. The APAR includes the following fixes:

Software compatibility

Installation requirements

Hardware requirements

Hardware requirements for Group List Server are included in the information center and have not changed since version 6.1.0. Refer to the following information for details:

http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/index.jsp?topic=/com.ibm.glm.doc/com_prereqs.html

Software requirements

Software requirements for Group List Server are included in the information center and have not changed since version 6.1.0. Refer to the following information for details:

http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/index.jsp?topic=/com.ibm.glm.doc/com_prereqs.html

Installation instructions

Before you begin, run the following command to decompress the Group List Server fix pack:

  tar –zxvf IBM_WebSphere_Group_List_Server_6.1.0.1.tar.gz

After running the command, the following files should have been extracted:

Installing the Group List Management Self Care portlet

  1. Verify that you have the following file needed for the installation from the fix pack: GLMAdmin.war
  2. Log in to the Integrated Solutions Console.
  3. In the navigation panel, click Applications> Enterprise Applications.
  4. Click the checkbox next to the already installed GLMAdmin_war application.
  5. Click the Update button.
  6. Ensure the radio button for Replace the entire application is selected.
  7. Type the path to the GLMAdmin.war file from the fix pack.
  8. Type a context root for the portlet. The context root will be combined with the defined servlet mapping,GLMAdmin, in order to compose the full URL that users type to access the portlet. For example, if the context root is MyContext, the URL is http://host:port/MyContext/GLMAdmin
  9. Click Next > Next.
  10. If installing in a cluster, ensure that the appropriate clusters and servers are selected.
  11. Click Next > Finish.
  12. Click Save to master configuration.
  13. Verify Group List Management Self Care is correctly installed by opening a browser to the following Web address:

    14. http://host_name:port/context_root/GLMAdmin/

  14. When you access this URL, you will be prompted to enter a user_name and password. Type the user_name and password of a user who is the member of the group mapped to the GLMAdminPortlet role.

Deploying IBM WebSphere Group List Server Component

  1. Verify that you have the following file needed for the installation from the fix pack: GroupListMgr.ear
  2. Log in to the Integrated Solutions Console.
  3. In the navigation panel, click Applications > Enterprise Applications.
  4. Click the checkbox next to the Group List Server application, which is already installed.
  5. Click the Update button.
  6. Ensure the radio button for Replace the entire application is selected.
  7. Enter the path to the GroupListMgr.ear file from the fix pack.
  8. Click Next > Next.
  9. If installing in a cluster, ensure that the appropriate clusters and servers are selected.
  10. Click Next > Finish.
  11. Click Save to master configuration.

Configure a new cache instance

  1. Log in to the Integrated Solutions Console.
  2. Click Resources > Cache Instances > Object cache instances.
  3. Select cell_name for the scope.
  4. Create the GLMXcapURICache:
    1. Click New.
    2. Select cell_name for the scope.
    3. Type GLMXcapURICache for the Name.
    4. Type services/cache/com/ibm/glm/xcapuricache for the JNDI name.
    5. Type 10000 for the Cache size
    6. Deselect the Dependency ID Support checkbox.
    7. If Group List Server is clustered:
      • Select the Enable cache replication check box.
      • Select GLMCacheReplication from the Full group replication domain drop-down list.
    8. Click OK.
  5. Click Save to save changes to the master configuration.

Define new optional configuration parameters if needed

There is a new optional configuration parameter, acceptContactHeaderValue, which you can define to enable changes in the default behavior of the Group List Server.

Parameter name = acceptContactHeaderValue
type = java.lang.String
default value = null
When defined, an Accept-Contact header will be added to SIP NOTIFY requests. The value of the header will be set to the value defined in this configuration parameter.
Example: If the configuration parameter value is set to *;type="application/xcap-diff+xml" then the following header will be provided as part of the SIP NOTIFY requests:
Accept-Contact: *;type=”application/xcap-diff+xml”

To create the new parameter, complete the following steps:

  1. Log in to the Integrated Solutions Console.
  2. Click Resources > Resource Environment > Resource Environment Providers.
  3. Click Group List Manager.
  4. Click Custom Properties.
  5. Click the New button.
  6. Enter the appropriate Name and value.
  7. From the Type drop-down list, select the appropriate type.
  8. Click OK button.
  9. Click Save to save changes to the master configuration.

Updates, limitations, and known problems

Updates, limitations, and known problems about Group List Server are documented in technotes on the IBM Software Support Web site: http://www-306.ibm.com/software/pervasive/presenceserver/support/

As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. Each of the following links launches a customized query of the live Support knowledge base. To create your own query, go to the Advanced search page.

All technotes for Group List Server Version 6.1.0.1