4.3. Upgrading DX Content Router
4.3.1. Upgrading from 1.x
Installations with a previously installed Ubuntu-based version of DX Content Router have two
upgrade options. Administrators with replication downtime tolerance may choose to stop all DX
Content Router processes, install Red Hat Enterprise Linux (RHEL) over Ubuntu on the existing DX
Content Router Publisher and Replicator servers and then install and start both DX Content Router
services again on both servers. For environments with no downtime tolerance, administrators may
wish to install Red Hat and DX Content Router on a second, parallel set of Publisher and Replicator
servers and then wait for the Publisher 'Stream Events Found' count on the Publisher console
to match the count on the Ubuntu installation. After the counts match, the Ubuntu Publisher and
Replicator servers can be decommissioned.
Regardless of the chosen upgrade path, administrators must upgrade DX Storage to 4.0 or later
prior to upgrading DX Content Router to ensure compatibility. Administrators should temporarily
raise the Multicast Frequency to 50% from the Setting popup on the DX Storage admin console
to support faster population of the Publisher data store. Depending on the size of the source DX
Storage cluster, it may take several days for the Publisher data store to fully populate. Please
contact your designated support resource if you have further questions about upgrading DX Content
Router.
4.3.2. Upgrading from 2.x
Prior to upgrading, users must upgrade their operating system to Red Hat 5.5. Installations with a
2.0 or 2.1.x RedHat-based version of DX Content Router may then install the new 2.2 rpm over the
previous version using the same process and script as above for initial installation. If DX Storage is
also being upgraded, it is recommended that DX Content Router be upgraded prior so it is prepared
to handle any new DX Storage features. It is also recommended that all Replicators be upgraded
prior to the Publisher being upgraded for similar reasons. Both services must be restarted after they
are upgraded. Any modifications to the data format used by either process will be automatically
transformed during the first Publisher process execution after upgrading.
Integrators wishing to use the new 'syncToken' functionality described in the Enumerator API
chapter with an existing enumeration may take advantage of this new feature by simply passing a
syncToken query argument with an empty string on the first Next request following the upgrade.
Replicator will automatically make use of the token after upgrade with no action required.
In the event of an upgrade error, customers should contact their designated support resource for
downgrade instructions.
4.4. Removing DX Content Router
If you need to remove DX Content Router from a server, you should first ensure there are no
subscribers actively querying the Publisher for streams. The following command will then remove
the configuration files and software for DX Content Router:
# sudo /opt/caringo/contentrouter/contentrouter-uninstall.sh
Copyright © 2010 Caringo, Inc.
All rights reserved
14
Version 2.2
December 2010
Pagina afdrukken