Table of Contents

Search

  1. Preface
  2. PowerExchange CDC Publisher Overview
  3. Installing and Upgrading PowerExchange CDC Publisher
  4. PowerExchange CDC Publisher Key Concepts
  5. PowerExchange Change Capture Environment
  6. Target Messaging Systems
  7. Configuring PowerExchange CDC Publisher
  8. Streaming Change Data
  9. Monitoring PowerExchange CDC Publisher
  10. Administering PowerExchange CDC Publisher
  11. Command Reference for the Command-Line Utilities
  12. Avro Schema Formats
  13. Message Reference

User Guide

User Guide

Upgrading PowerExchange CDC Publisher

Upgrading PowerExchange CDC Publisher

If PowerExchange CDC Publisher is currently installed, you can use this procedure to upgrade to a new PowerExchange CDC Publisher version.
The upgrade procedure adds the new installation without deleting or overwriting the previous installation. This strategy allows you to copy the information defined for your existing instances to the new installation incrementally, as needed. Also, if you need to fall back to the older version, it is still available until you uninstall it.
Before you upgrade the product, perform the following tasks:
  • Read the
    PowerExchange CDC Publisher Release Notes
    to determine if any upgrade issues exist.
  • Verify that your system is compatible with the software requirements of the new version.
  1. Download the PowerExchange CDC Publisher installation file for your operating system to a directory other than the current PowerExchange CDC Publisher installation directory.
    Retain the installation file so that you can use it to upgrade other PowerExchange CDC Publisher installations if necessary.
  2. Shut down the PwxCDCPublisher process if it is running. To do so, run the PwxCDCAdmin command with the SHUTDOWN parameter.
    You do not need to stop PowerExchange CDC processing or Apache Kafka.
  3. Unzip or extract the installation file for the new PowerExchange CDC Publisher version. Typically, the file is extracted to a directory other than the existing PowerExchange CDC Publisher installation directory.
    The software is extracted into a version-specific root installation directory so that it does not overwrite your previous installation. You can rename the new installation directory, for example, from "pwxcdcpub
    vrm
    .win_x64" to "PowerExchangeCDCPublisher_
    vrm
    ." Alternatively, you can rename the previous installation directory and then use its original name as the name of the new installation so that you do not have to change the PWXPUB_HOME environment variable value, if set.
  4. If you defined the PWXPUB_PUB environment variable, ensure that the environment variable points to the new installation.
  5. If you have a new license key file, ensure that the PWX_LICENSE environment variable points to the new file.
  6. Copy the instance
    X
    directories that you use from the previous installation to the new installation. Confirm that all of the subdirectories under each instance are also copied, including the config subdirectory that contains the PowerExchange CDC Publisher configuration files.
    You can copy the instance
    X
    directories to the new installation incrementally, as they are needed.
  7. If the new CDC Publisher version contains new or changed configuration properties, update the CDC Publisher configuration files in the config subdirectory as needed.
    To determine if CDC Publisher properties changed, see the PowerExchange CDC Publisher documentation.
  8. To verify that the upgrade succeeded, restart the PowerExchange CDC Publisher process and then run the PwxCDCInfo command with the STATUS parameter.
    By default, the Publisher process starts from the last checkpoint position. If you want to start the Publisher process from a different position, issue the PwxCDCPublisher command with the RESTART parameter. For more information, see PwxCDCPublisher Utility - Command and Parameters.
    For information about running the PwxCDCInfo command with the STATUS parameter, see PwxCDCInfo Utility - Command and Parameters.

0 COMMENTS

We’d like to hear from you!