Table of Contents

Search

  1. Preface
  2. PowerExchange Installation and Upgrade Overview
  3. Installation Planning
  4. Upgrade Planning
  5. Installing and Upgrading PowerExchange on IBM i
  6. Installing and Upgrading PowerExchange on Linux and UNIX
  7. Installing and Upgrading PowerExchange on Windows
  8. Installing and Upgrading PowerExchange on z/OS
  9. Appendix A: Upgrade Considerations
  10. Appendix B: PowerExchange Environment
  11. Appendix C: Manual Installation on IBM i

Installation and Upgrade Guide

Installation and Upgrade Guide

Considerations for PowerExchange Environment Variables

Considerations for PowerExchange Environment Variables

You can define PowerExchange environment variables to specify the location of PowerExchange message log, configuration, and license files. By moving these files from their default locations and using environment variables to point to the new locations, you can make upgrading easier and locating the files easier.
The following table lists the environment variables and the files to which they point:
Environment Variable
Points to
DETAIL_LOGPATH
PowerExchange message log file
PWX_CONFIG
PowerExchange DBMOVER configuration file
PWX_LICENSE
PowerExchange license key
The following table shows the default locations of the PowerExchange message log file, DBMOVER configuration file, and license key file in 32-bit and 64-bit PowerExchange environments:
PowerExchange File
Default Location in 32-bit PowerExchange
Default Location in 64-bit PowerExchange
Message log file
Current working directory
Current working directory
DBMOVER configuration file
bin32 subdirectory of the installation directory
Installation directory
License key file
bin32 subdirectory of the installation directory
Installation directory
In some cases you might run 32-bit and 64-bit Windows versions of PowerExchange on the same machine. For example, you might run the PowerCenter Developer and the PowerCenter Integration Server on the same machine. In this case, the Developer client invokes 32-bit PowerExchange executables to access metadata, and the Integration Service invokes 64-bit PowerExchange executables to run workflows that connect to PowerExchange sources.
If you define PowerExchange environment variables to point to PowerExchange files, the environment variables apply to the files used by both 32-bit and 64-bit versions of PowerExchange. If you prefer to maintain separate DBMOVER or message log files for 32-bit and 64-bit versions of PowerExchange, you can keep the default locations and not define environment variables. You can also define the LOGPATH statement in the DBMOVER configuration file to specify a unique path and directory for PowerExchange message log files on a Windows system. If you also specify a value in the DETAIL_LOGPATH environment variable, the environment variable overrides the LOGPATH statement.

0 COMMENTS

We’d like to hear from you!