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. Appendix A: Command Reference for the Command-Line Utilities
  12. Appendix B: Avro Schema Formats
  13. Appendix C: Custom Pattern Formats
  14. Appendix D: Message Reference

User Guide

User Guide

Customizing the PowerExchange CDC Publisher Configuration Files

Customizing the PowerExchange CDC Publisher Configuration Files

PowerExchange CDC Publisher provides sample configuration files in the
pwxcdcpbub_root_installation
/samples
subdirectory. These files contain the basic CDC Publisher properties that you will need to set. For special circumstances, Informatica technical staff might request that you set additional properties.
The following sample configuration files are provided:
  • cdcPublisherAvro.cfg
    . Contains properties that specify the Avro schema format and the data serialization method and encoding for messages that contain change data.
  • cdcPublisherCommon.cfg
    . Contains properties that define the PowerExchange CDC Publisher host and port.
  • cdcPublisherKafka.cfg
    . Contains properties related to the target messaging systems.
  • cdcPublisherPowerExchange.cfg
    . Contains properties related to accessing PowerExchange extraction maps and change data.
You can copy the sample configuration files to the
pwxcdcpub_root_installation
/instance
X
/config
subdirectory and then customize the copies of the files. The files contain comments that describe each property. The PowerExchange CDC Publisher will read only the configuration files that are in the config subdirectory.
For PowerExchange CDC Publisher to recognize a file as a configuration file, the file must have the file name extension
.cfg
. Also, the file content must begin with
# Configuration
on the first or second line in the file.
No sample configuration file is available for the Custom Pattern Formatter. You create the Custom Pattern Formatter configuration files in a location that the CDC Publisher can access. They do not require the
# Configuration
comment.
You can include all configuration properties in one file or create alternative subsets of properties in multiple configuration files. Informatica recommends that you use multiple configuration files that logically group the properties, similar to the sample configuration files. You can then copy and re-use the properties that do not change across multiple instances and migration paths, and customize only the properties that need to change because of changes to your CDC Publisher environment. For example, you might want to customize the PowerExchange-related extraction properties and Kafka target properties when migrating PowerExchange CDC Publisher from a test environment to a production environment but retain the Avro-related properties.
Do not include the same property in multiple configuration files. If the same property appears with different values in multiple configuration files, the PowerExchange CDC Publisher will issue an error.

0 COMMENTS

We’d like to hear from you!