Dell DX6004S DX Content Router Release Notes - Page 6

Application and Configuration Notes

Page 6 highlights

installation and then restart both Publisher and Replicator services. Any modifications to the data format used by either process will be automatically transformed during the first Publisher process execution after upgrading. In the event of an upgrade error, customers should contact their designated support resource for downgrade instructions. 1.5. Application and Configuration Notes Special attention should be paid to the following items when utilizing Content Router. • Consistency and Latency in Console Reporting Stream events within DX Content Router are discovered, evaluated for rules applicability and communicated to subscribers by several different processes. The statistics reported on the Publisher console are synthesized from each of the separate processes but may not be exactly aligned as each process records and reports status independently. Also, console statistics are not updated immediately with every stream event as there is additional time required to process events into their appropriate queue(s). Copyright © 2010 Caringo, Inc. All rights reserved 3 Version 2.2 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6

Copyright © 2010 Caringo, Inc.
All rights reserved
3
Version 2.2
December 2010
installation and then restart both Publisher and Replicator services. Any modifications to the data
format used by either process will be automatically transformed during the first Publisher process
execution after upgrading.
In the event of an upgrade error, customers should contact their designated support resource for
downgrade instructions.
1.5. Application and Configuration Notes
Special attention should be paid to the following items when utilizing Content Router.
Consistency and Latency in Console Reporting
Stream events within DX Content Router are
discovered, evaluated for rules applicability and communicated to subscribers by several different
processes. The statistics reported on the Publisher console are synthesized from each of the
separate processes but may not be exactly aligned as each process records and reports status
independently. Also, console statistics are not updated immediately with every stream event as
there is additional time required to process events into their appropriate queue(s).