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

Environment Variables That Point to PowerExchange License, Configuration, and Message Log Files on Linux, UNIX, and Windows

Environment Variables That Point to PowerExchange License, Configuration, and Message Log Files on Linux, UNIX, and Windows

The PowerExchange installation program installs configuration and license files in the installation directory. To make upgrading to a new PowerExchange version as easy as possible, you can move these files to a different location.
Also, PowerExchange creates message log files in the current working directory by default. You can create message log files in a directory that is separate from your current working directory so that you can find the message log files more easily.
You can use environment variables to point to the new locations of the DBMOVER, license key, and message log files.
The following table lists the environment variables and the files to which they point:
Environment Variable
Points to
DETAIL_LOGPATH
PowerExchange message log files
PWX_CONFIG
PowerExchange DBMOVER configuration file
PWX_LICENSE
PowerExchange license key
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 Linux, UNIX, or 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!