Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Engineering 10.5.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Application Service Guide

Application Service Guide

Back Next

PowerExchange Logger Service Configuration Properties

PowerExchange Logger Service Configuration Properties

The following table describes the configuration properties of a Logger Service:
Service Process
Read only. The type of PowerExchange process that the service manages. For a Logger Service, this value must be Logger.
Start Parameters
Optional. Parameters that you can specify when you start the Logger Service. If you specify more than one parameter, separate them with a space character.
Parameter descriptions:
  • coldstart={Y|
    N
    }
    Indicates whether to cold start or warm start the Logger Service. Enter Y to cold start the Logger Service. If the CDCT file contains log entries, the Logger Service deletes these entries. Enter N to warm start the Logger Service from the restart point that is specified in the CDCT file. If no restart information exists in the CDCT file, the Logger Service ends with an error.
    Default is N.
  • config=
    directory
    /
    pwx_config_file
    Specifies the full path and file name for a dbmover configuration file that overrides the default
    dbmover.cfg
     file. The override file must have a path or file name that is different from that of the default file. This override file takes precedence over any configuration file that you optionally specify in the PWX_CONFIG environment variable.
  • cs=
    directory
    /
    pwxlogger_config_file
    Specifies the full path and file name for a Logger Service configuration file that overrides the default pwxccl.cfg configuration file. The override file must have a path or file name that is different from that of the default file.
  • encryptepwd=
    encrypted_password
    A password in encrypted format for enabling the encryption of PowerExchange Logger log files. With this password, the PowerExchange Logger can generate a unique encryption key for each Logger log file. The password is stored in the CDCT file in encrypted format. For security purposes, the password is not stored in CDCT backup files and is not displayed in the CDCT reports that you can generate with the PowerExchange PWXUCDCT utility.
    If you specify this parameter, you must also specify coldstart=Y.
    If you specify this parameter and also specify the ENCRYPTEPWD parameter in the PowerExchange Logger configuration file, pwxccl.cfg, the parameter in the configuration file takes precedence. If you specify this parameter and also specify the ENCRYPTPWD parameter in the PowerExchange Logger configuration file, an error occurs.
    You can set the AES algorithm to use for log file encryption in the ENCRYPTOPT parameter of the pwxccl.cfg file. The default is AES128.
    For optimal security, Informatica recommends that you specify the encryption password when cold starting the PowerExchange Logger rather than in the pwxccl.cfg configuration file. This practice can reduce the risk of malicious access to the encryption password for the following reasons: 1) The encryption password is not stored in the pwxccl.cfg file, and 2) You can remove the password from the command line after a successful cold start. If you specify the encryption password for a cold start and then need to restore the CDCT file later, you must enter the same encryption password in the RESTORE_CDCT command of the PWXUCDCT utility.
    To
    not
     encrypt PowerExchange Logger log files, do not enter an encryption password.
  • license=
    directory
    /
    license_key_file
    Specifies the full path and file name for a license key file that overrides the default
    license.key
     file. The override file must have a path or file name that is different from that of the default file. This override file takes precedence over any license key file that you optionally specify in the PWX_LICENSE environment variable.
  • specialstart={Y|N}
    Indicates whether to perform a special start of the PowerExchange Logger. A special start begins PowerExchange capture processing from the point in the change stream that you specify in the pwxccl.cfg file. This start point overrides the restart point from the CDCT file for the PowerExchange Logger run. A special start does not delete any content from the CDCT file.
    Use this parameter to skip beyond problematic parts in the source logs without losing captured data. For example, use a special start in the following situations:
    • You do not want the PowerExchange Logger to capture an upgrade of an Oracle catalog. In this case, stop the PowerExchange Logger before the upgrade. After the upgrade is complete, generate new sequence and restart tokens for the PowerExchange Logger based on the post-upgrade SCN. Enter these token values in the SEQUENCE_TOKEN and RESTART_TOKEN parameters in the pwxccl.cfg, and then special start the PowerExchange Logger.
    • You do not want the PowerExchange Logger to reprocess old, unavailable logs that were caused by outstanding UOWs that are not of CDC interest. In this case, stop the PowerExchange Logger. Edit the RESTART_TOKEN value to reflect the SCN of the earliest available log, and then perform a special start. If any of the outstanding UOWs that started before this restart point are of CDC interest, data might be lost.
    Valid values:
    • Y. Perform a special start of the PowerExchange Logger from the point in the change stream that is defined by the SEQUENCE_TOKEN and RESTART_TOKEN parameter values in the pwxccl.cfg configuration file. You must specify valid token values in the pwxccl.cfg file to perform a special start. These token values override the token values from the CDCT file. Ensure that the SEQUENCE_TOKEN value in the pwxccl.cfg is greater than or equal to the current sequence token from the CDCT file.
      Do not also specify the coldstart=Y parameter. If you do, the coldstart=Y parameter takes precedence.
    • N. Do not perform a special start. Perform a cold start or warm start as indicated by the coldstart parameter.
    Default is N.
In the config, cs, and license parameters, provide the full path only if the file does
not
 reside in the PowerExchange installation directory. Include quotes around any path and file name that contains spaces.
SVC NODE Port Number
Specifies the port on which the Logger Service connects to the PowerExchange Logger.
Use the same port number that is in the SVCNODE statement of the DBMOVER file.
0 COMMENTS
We’d like to hear from you!