Name of the Informatica domain. You can set the domain name with the -dn option or the environment variable INFA_DEFAULT_DOMAIN. If you set a domain name with both methods, the -dn option takes precedence.
Required if the domain uses Native or LDAP authentication. User name to connect to the domain. You can set the user name with the -un option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un option takes precedence.
Optional if the domain uses Kerberos authentication. To run the command with single sign-on, do not set the user name. If you set the user name, the command runs without single sign-on.
Required if you specify the user name. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence.
Required if the domain uses LDAP authentication. Optional if the domain uses native authentication or Kerberos authentication. Name of the security domain to which the domain user belongs. You can set a security domain with the -sdn option or the environment variable INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods, the -sdn option takes precedence. The security domain name is case sensitive.
If the domain uses native or LDAP authentication, the default is Native. If the domain uses Kerberos authentication, the default is the LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
gateway_host1:port gateway_host2:port ...
Required if the gateway connectivity information in the domains.infa file is out of date. The host names and port numbers for the gateway nodes in the domain.
Optional. Amount of time in seconds that infacmd attempts to establish or re-establish a connection to the domain. You can set the resilience timeout period with the -re option or the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If you set the resilience timeout period with both methods, the -re option takes precedence.
Required. Name of the Logger Service.
Required. Name of the node where you want the Logger Service to run.
License to assign to the service. If not already provided, required before you can enable the service.
Optional. If the PowerCenter environment is configured for high availability, this option specifies the name of the backup node.
Optional. Parameters to include when you start the Logger Service. Separate the parameters with the space character.
You can include the following parameters:
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 records, the Logger Service deletes these records. Enter N to warm start the Logger Service from the restart point that is indicated in the CDCT file.
Default is N.
Specifies the full path and file name for any dbmover.cfg configuration file that you want to use instead of the default dbmover.cfg file. This alternative configuration file takes precedence over any alternative configuration file that you specify in the PWX_CONFIG environment variable.
Specifies the path and file name for the Logger Service configuration file. You can also use the cs parameter to specify a Logger Service configuration file that overrides the default
pwxccl.cfg file. The override file must have a path or file name that is different from that of the default file.
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.
not encrypt PowerExchange Logger log files, do not enter an encryption password.
Specifies the full path and file name for any license key file that you want to use instead of the default
license.key file. The alternative license key file must have a file name or path that is different from that of the default file. This alternative license key file takes precedence over any alternative license key file that you specify in the PWX_LICENSE environment variable.
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.
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, you must provide the full path only if the file does
not reside in the installation directory. Include quotes around any path and file name that contains spaces.
Port on which the Logger Service listens for commands from the Service Manager.