IBM WebSphere XML Document Management Server Component, Version 6.2.0.1 iFix 1 Readme

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

Contents

 

About this iFix

This iFix is a cumulative fix which includes all the latest changes for the IBM® WebSphere® XML Document Management Server (XDMS), Version 6.2.0.1. This iFix is recommended for all customers with an XDMS 6.2 installation.

This iFix is installed using the WebSphere Update Installer as well as some manual updates.

Fix and update history

This iFix includes the following APARs and fixes.

iFix 001

APAR LI73484 – This APAR resolves the following situation:

The CSCF may substitute the SIP Request URI with an alternate proxy server hostname and port that is specified within the "Contact:" header. The XDMS may use the SIP Request URI to identify the XUI for directory level SUBSCRIBE requests. If the "Contact:" header substitution occurs, then the original SIP Request URI that identifies the XUI is lost for subsequent SUBSCRIBE requests. The SIP Request URI thus identifies an erroneous XUI which typically results in a 403 response code because the user will not have access to the alternate XUI.

fix pack 001

APAR LI73028 – This APAR contains the following fixes:

Limitations

  1. WebSphere Application Server 6.1 forces all authenticated user IDs to lowercase.  Therefore, asserted identities that are sent for either the IMS Connector SIP or HTTP Trust Association Interceptor (TAI) will be converted to lowercase.  With this limitation, all user IDs created within the user repository such as LDAP must be defined in lowercase.
  2. In certain situations, the SIBus listener bean can be loaded faster than the XDMS servlets can initialize.  A NullPointerException may be thrown from com.ibm.xdms.sip.utils.SIPNotifyListenerBean.onMessage(SIPNotifyListenerBean.java:97).  Please restart the server in this case.
  3. If the virtual host setting for your Enterprise Application is different from the default_host, after running the Enterprise Application Update task (see installation instructions below) the virtual host setting is reset to default_host. Please write down your virtual host setting prior to running the Enterprise Application Update task. After the update is complete, reconfigure the virtual host to your previous value.

Software compatibility

 

Viewing the Changed File.list in the Update Installer .pak file

Update installer .pak files are delivered in .zip format. To view the contents of a .pak file, use any archiving tool that can read .zip files. The Java jar tool can also extract the files.list file from the .pak file.

To view the contents, type jar -tf iFix_name.pak

To extract the files.list, type jar -xf iFix_name.pak repository/xdms.core/files.list

Next, you can use an editor to view the files.list, which lists all of the files to be changed for the .pak file.

Installation requirements

Software requirements

Software requirements for XDMS are included in the information center. Refer to the following information for details:

http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.xdms.doc/prerequisites_c.html

In addition to the prerequisites listed in the information center, the following maintenance fixes are required:

WebSphere Application Server Network Deployment, Version 6.1.0.11

Installation instructions

The IBM WebSphere XDMS 6.2.0.1 iFix will refresh the local files on the WebSphere Application Server (WAS) installed file system.  However, you must manually load the new files into the WebSphere Application Server by following this procedure.

Before you begin

Before you begin the installation, ensure that:

Apply the iFix

You must log in with the same root user authority level when unpacking a fix, a fix pack, or a refresh pack. To apply the iFix, complete the following steps:

  1. Download the IBM WebSphere XDMS 6.2.0 iFix 1 update installer package 6.2.0.1-WS-WAS-IMS-XDMS-IF000001.pak into the was_root/updateInstaller/maintenance directory.
  2. Start the update installer as described by WebSphere and select the XDMS iFix to be installed.
  3. Repeat for each server running IBM WebSphere XDMS 6.2, including the Deployment Manager and Aggregation Proxy servers.

Reload the XDMS core OSGI bundle

The XDMS Core OSGI bundle is installed in was_root/plugins/com.ibm.ws.xdms_6.2.0.jar.  Run the update installer for the XDMS 6.2.0.1 iFix on all WebSphere Application Servers running an XDMS Enabler, including the server hosting the Deployment Manager and the Aggregation Proxy.  Then run the following steps to reload the OSGI bundle on each server.

  1. Stop all running application servers.
  2. Stop all running node agents.
  3. Stop all deployment managers.
  4. For each node profile (e.g. AppSrv01, AppSrv02), execute the following scripts:

·         AppSrv0n/bin/osgiCfgInit.sh

·         AppSrv0n/bin/clearClassCache.sh

  1. Repeat for each server running IBM WebSphere XDMS 6.2, including the deployment manager and Aggregation Proxy servers.

Update the enterprise applications

After all the XDMS Core OSGI bundles have been reloaded (see above), the Enterprise Applications for the XDMS should be updated once from a server that has been updated with the latest XDMS 6.2.0.1 iFix.

  1. Start the deployment manager.
  2. Start the node agent.
  3. Log in to the Integrated Solutions Console.
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.

Where:

      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default is 9043.

Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.

    1. Enter an administrator user ID and password.
    2. Click Log in.
  1. Use the Enterprise Application Update task to update the IBMSharedListXdms.ear.
    1. Click Applications > Enterprise Applications.
    2. Check the checkbox for IBMSharedListXdms_EAR and click Update.
    3. Under the “Replace the application” section, browse to the location of the IBMSharedListXdms.ear file. The default location is was_root/installableApps/xdms/.
    4. Leave the context root blank.
    5. Click Next.
    6. Accept the defaults on the Select installation options panel.
    7. Click Next.
    8. Ensure that the SharedListXDMS and SIPNotify modules are deployed to the SharedListCluster.  Otherwise,
      • Select the SharedListXDMS and SIPNotify modules.
      • Select SharedListCluster from the Clusters and Severs list.
      • Click Apply. Verify that the server name for both modules should deploy to the SharedListCluster.
    9. Click Next.
    10. Click Finish.
  2. Click Save to save to the master configuration.
  3. Use the Enterprise Application Update task to update the IBMPresenceRulesXdms.ear.
    1. Click Applications > Enterprise Applications.
    2. Select the checkbox for IBMPresenceRulesXdms_EAR and click Update.
    3. Under the “Replace the application” section, browse to the location of the IBMPresenceRulesXdms.ear file. The default location is was_root/installableApps/xdms/.
    4. Leave the context root blank.
    5. Click Next.
    6. Accept the defaults on the Select installation options panel.
    7. Click Next.
    8. Ensure that the PresenceRulesXDMS and SIPNotify modules are deployed to the PresenceRulesCluster.  Otherwise,
      • Select the PresenceRulesXDMS and SIPNotify modules.
      • Select PresenceRulesCluster from the Clusters and Severs list.
      • Click Apply. Verify that the server name for both modules should deploy to the PresenceRulesCluster.
    9. Click Next.
    10. Click Finish.
  4. Click Save to save to the master configuration.
  5. Use the Enterprise Application Update task to update the IBMXdmsAggregationProxy.ear.
    1. Click Applications > Enterprise Applications.
    2. Check the checkbox for XdmsAggregationProxy and click Update.
    3. Under the “Replace the application” section, browse to the location of the IBMXdmsAggregationProxy.ear file. The default location is was_root/installableApps/xdms/.
    4. Leave the context root blank.
    5. Click Next.
    6. Accept the defaults on the Select installation options panel.
    7. Click Next.
    8. Ensure that the AggsProxyWeb module is deployed to the AggProxyCluster.  Otherwise,
      • Select the AggsProxyWeb module.
      • Select AggProxyCluster from the Clusters and Severs list.
      • Click Apply. Verify that the server name of the module is deployed to the AggProxyCluster.
    9. Click Next.
    10. Click Finish.
  6. Click Save to save to the master configuration.
  7. Start the clusters or application servers running the XDMS Enablers.      

Verify the installation

Examine the SystemOut.log of each application server running an XDMS Enabler.  Search for “IBM WebSphere XML Document Management Server”.

 

[1/25/08 17:22:49:230 EST] 0000000a osgi          I

        -------------------------------------------------------

        IBM WebSphere XML Document Management Server 6.2.0.1

        Build Level: 20080610_1720 2008-06-10 17:20

        Licensed Materials - Property of IBM

        5724-O05

        M-) Copyright IBM Corp. 2006, 2007 All Rights Reserved.

        -------------------------------------------------------

 

Ensure that the Build Level matches 20080610_1720 2008-06-10 17:20.

Configuration instructions

The configuration for XDMS is the same as that described in the information center, except as specified in either the XDMS 6.2 Readme (WebSphereProductsForTelecomReadme.html) or this Readme.

Tune the XDMS as recommended by the XDMS Performance Tuning Guide.pdf

For optimal and proper performance of your XDMS installation, download the tuning guide and follow the instructions found here:

http://www.ibm.com/support/docview.wss?rs=3248&context=SSWJLZ&q1=tuning&uid=swg27011071&loc=en_US&cs=utf-8&lang=en

DB2 SIBus database store transaction log full

If you have configured your XDMS SIBus to use a datastore for JMS transaction messages, then it is recommended that you disable the AUTORUNSTAT for the XDMSIB database in DB2. Otherwise you may see transaction log full messages. The following command disables auto_runstats (assuming that you run as the DB2 administrator). 

 

db2 update db cfg for XDMSSIB using auto_runstats OFF

 

Updates, limitations, and known problems

Updates, limitations, and known problems about XML Document Management Server are documented in technotes on the IBM Software Support Web site: http://www.ibm.com/software/pervasive/xdms/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. The following link launches a customized query of the live Support knowledge base. To create your own query, go to the Advanced search page.

Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, WebSphere, DB2 Universal Database, and AIX

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.