IBM WebSphere XML Document Management
Server Component, Version 7.0.0.0 Interim Fix 6 Readme
© Copyright International Business Machines
Corporation 2012. All rights reserved. US Government Users
Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
This interim fix is a cumulative fix which
includes all the latest changes for the IBM® WebSphere® XML Document Management
Server (XDMS), Version 7.0.0.0. This interim fix is recommended for all
customers with an XDMS 7.0 installation.
This interim fix is installed using the WebSphere
Update Installer as well as some manual updates.
Interim Fix 006:
Interim Fix 005:
Interim Fix 004:
Interim Fix 003:
Interim Fix 002:
Interim Fix 001:
The supported software products and version numbers for XDMS are documented in the information center. This interim fix runs with the same software except as noted below.
Note: Beginning with Interim
Fix 4 XDMS, when used with Oracle database as the backend, will function only
if the Oracle database version is 11.2 or higher. Customer’s using Oracle database version lower than 11.2
should not migrate to Interim Fix 4 or 5.
Software requirements for XDMS Interim Fix 6 are
consistent with the details included in the information center, except for the information
on the supported databases. Beginning with XDMS Interim Fix 5, only Oracle 11.2
or higher versions are supported. Oracle database 11.1.0.7, as mentioned in the
XDMS information center, is no longer supported.
Refer to the information center for further
details about software requirements: http://publib.boulder.ibm.com/infocenter/wtelecom/v7r0m0/topic/com.ibm.xdms.doc/com_sw_prereqs.html
The IBM WebSphere XDMS 7.0.0.0 Interim Fix 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 the installation, ensure that:
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 Interim
Fix, complete the following steps:
Note: Due to a date formatting issue in the XDMS 7.0.0 Interim Fix 5 packaging, there are two exceptions (ParseException and NullException) logged into the WebSphere UPDI result logs when installing the XDMS 7.0.0 Interim Fix 5 pak file. The exceptions should not prevent the XDMS 7.0.0 Interim Fix 5 from being successfully installed, and therefore can be ignored.
The XDMS Core OSGI bundle is
installed in was_root/plugins/com.ibm.ws.xdms_7.0.0.jar. Run the update installer for the XDMS 7.0.0.0
Interim Fix 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.
·
AppSrv0n/bin/osgiCfgInit.sh
·
AppSrv0n/bin/clearClassCache.sh
The Shared Enablers XDMS is an all-in-one application EAR
that contains all of the AUIDs from every other XDMS
application. The EAR included with the XDMS 7.0.0.0 release was not fully supported
and some bugs have been fixed in the EAR. In order to take advantage of these
fixes, the EAR that was installed by the XDMS 7.0.0.0 installer needs to be
redeployed with a version from the Interim Fix.
Note: was_root is the
installation root directory for WebSphere Application Server Network Deployment.
By default, this directory is:
The XDMS 7.0.0.0 release required the use of the Oracle
thick (OCI) driver. This required the user to install the full Oracle client on
all Websphere servers running XDMS. This Interim Fix
releases the dependency on the Oracle thick driver and full Oracle client
installation and allows XDMS to use the Oracle thin driver. There are memory
leaks present using the thick driver. Therefore, the thin driver is required
after installing this Interim Fix.
Note: This only needs to be done for XDMS setups using Oracle. This step can be skipped if XDMS 7.0.0.1 has already been installed.
If you are installing for first time, ignore any instructions for installing the Oracle thick client on the servers.
·
For
example:
If you already have an existing XDMS installation using the Oracle thick driver prior to installing the XDMS V7.0.0 Interim Fix 4, execute the following steps to switch to the Oracle thin driver.
· ORACLE_HOME TNS_ADMIN CLASSPATH LIBPATH LD_LIBRARY_PATH
·
For example:
Note: This only needs to be done for XDMS setups with Oracle.
The listed Oracle patches are only available for Oracle V11.1.0.7 on the Linux x86_64 operating system from the Oracle metalink2 patch Web site. For the other Oracle supported operating system platforms, contact Oracle support for the listed Oracle patches.
The following Oracle patches need to be installed onto the
Oracle database:
Note: This only needs to be done for XDMS setups with Oracle.
The XDMS 7.0.0.0 release had a restriction that rls-service documents could only contain one service
element each. This restriction is removed with the new database scripts. Also,
the index has been changed to take advantage of the Oracle XMLIndex
functionality.
Warning: Rerunning the database scripts will drop old tables and delete any existing documents.
If Aggregation Proxy is deployed on
WebSphere Application Server 7, the custom properties for the HttpDigestTAI interceptor, related to LDAP, are no more
required. The presence of these properties will not affect the functionality of
Aggregation Proxy, however its recommended to remove these properties from the
WebSphere Application Server admin console.
Note : This step needs to performed
only if the Interim Fix is applied over XDMS 7.0.0.0 release and can be skipped
if XDMS 7.0.0.1 has been installed.
Steps to re-configure HttpDigestTAI interceptor:
1.
Aggregation
Proxy Application is not already installed :
a.
Create a
cluster and server for the Aggregation Proxy EAR (refer to the Preparing the
Environment section of the XDMS information center)
b.
Run the
XDMS installer from the media, and install the Aggregation Proxy application.
2.
Navigate
to WebSphere Application Server administration console > Global security
>Trust association > Interceptors
3.
Click on
“com.ibm.glm.http.security.tai.HttpDigestTAI”
4.
Check
all the properties beginning with “Ldap”
and click on Delete
5.
Click on
Apply
6.
Click
Save to save changes to the master configuration
7.
Restart
Aggregation Proxy server(s).
These changes apply to, only when
the Aggregation Proxy application is deployed on a WebSphere Application Server
7 environment and should not be made if the deployment is done on a
WebSphere Application Server 6.1.x environment.
Post XDMS Interim Fix004, a
UA-Profile Event based Subscription to an entire directory, will send, as part
of the Initial Notify, the information of all the files, currently located
within the directory, to the client. This is opposed to the previous behavior
where only the directory details were sent back, without the details of the
files contained in it. With this change the content of the Initial Notify for
UA-Profile Event based subscriptions will be similar to the one obtained during
the Initial Notify for XCAP-DIFF Event based directory level subscriptions,
with the only exception that “doc-selector” attribute will
be used, instead of “sel”, in the Initial Notify, to indicate the file
information.
If the custom clients, used for
receiving the Initial Notify, are not configured to accept entire file list
information, it will be required to modify them, to enable them to handle the
new content in the Initial Notify.
Examine the SystemOut.log
of each application server running an XDMS Enabler. Search for “IBM WebSphere XML Document
Management Server”.
[
-------------------------------------------------------
IBM WebSphere XML Document Management
Server 7.0.0.0
Build
Level: 20120711_0504 07/11/2012 05:04
Licensed Materials - Property of IBM
5724-O05
© Copyright IBM Corp. 2006, 2012 All
Rights Reserved.
-------------------------------------------------------
Ensure
that the Build Level matches 20120711_0504
The configuration for XDMS is the same as that
described in the information center, except as specified in either the XDMS 7.0
Readme (WebSphereProductsForTelecomReadme.html) or this Readme.
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&uid=swg27016067&loc=en_US&cs=UTF-8〈=en
When XDMS is used with Oracle (version 11.2 or higher) as the backend database, the following drawbacks might persist:
Note: IBM intends to address these issues in subsequent releases of the XDMS product.
Additional 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.
The following terms are trademarks of
International Business Machines Corporation in the
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
Linux is a registered trademark of Linus Torvalds in the
Java and all Java-based trademarks are trademarks
of Sun Microsystems, Inc. in the
Other company, product, or service names may be
trademarks or service marks of others.