For users of previous versions of the IBM® XDMS product,
there are several issues to consider when migrating your existing
configuration to the current version.
After you have migrated from the previous version to version
7.0,
you will want to test your system to ensure a successful migration.
It is recommended that you consider all of the following factors:
- Verify that both versions of the OSGi bundle are running properly
on WebSphere® Application Server.
- Verify that the 7.0 nodes
are updating the databases properly.
- Verify that your Resource Environment Provider (REP) properties
are being recognized.
- Verify that the filter classes and helper functions are the same
as those used in the previous version.
- Verify that the SIBus notification is functioning properly.
- Verify that your authorization policy documents–which control
authorization–are still specifying the correct node selector template.
If existing authorization policy documents specify a node selector
template that uses one attribute, and the policy has been changed
during the upgrade to use another attribute, then all of the authorization
policy documents must be updated to conform to the new attribute.
(For more information about authorization policy documents, refer
to the topic Policy based authorization.)
If any of these conditions are not met, then it is a good
practice to use dual release clusters. A version 7.0 clone
of the existing production cluster is deployed, and then you can reroute
traffic from the existing cluster to the new version 7.0 cluster.
The document database can be shared between the dual release clusters
so that the same documents in the previous cluster can also be managed
in the new version 7.0 cluster.
Coexistence with other components
IBM XDMS version
7.0 can
interoperate with the following software:
- Aggregation Proxy,
version 7.0 or
version 6.2
- Shared List application, version 7.0 or
version 6.2
- Presence Rules application, version 7.0 or
version 6.2
- IBM WebSphere Presence
Server Component,
version 7.0 or
version 6.2
- IBM XDMS,
version 7.0 or
version 6.2
When you run
IBM XDMS,
version
7.0 together
with
IBM XDMS version
6.2 – either in the same cluster or across different clusters – be
aware of the following limitations:
- Session Initiation Protocol (SIP) Sessions are not replicated
or forwarded from one release cluster to another. Therefore, if you
reroute from the previously existing cluster to the new 7.0 cluster,
your old subscriptions are lost.
- SIP Notification does not cross release clusters. If there is
a subscription to a document in the previously existing cluster but
the same document is modified in the new version 7.0 cluster,
the subscriber will not be notified because the SIP Notification does
not cross over between the clusters and vice versa.
- You may need to double the number of IBM XDMS servers.
Migrating applications
If you used version
6.2 of IBM XDMS to
develop applications and you plan to upgrade to version 7.0,
contact your IBM representative
for advice on migrating the applications.