The use of environment variables in MFT properties

From IBM® WebSphere MQ Version 7.5, it is possible for environment variables to be used in Managed File Transfer properties that represent file or directory locations. This allows the locations of files or directories used when running parts of the product, to vary depending on environment changes. For example, which user is running the process.

The following properties accept file or directory locations and can therefore contain environment variables:

• agentSslKeyStore
• agentSslKeyStoreCredentialsFile
• agentSslTrustStore
• agentSslTrustStoreCredentialsFile
• cdNodeKeystoreCredentialsFile
• cdNodeTruststoreCredentialsFile
• cdTmpDir
• cdNodeKeystore
• cdNodeTruststore
• commandPath
• connectionSslKeyStore
• connectionSslKeyStoreCredentialsFile
• connectionSslTrustStore
• connectionSslTrustStoreCredentialsFile
• coordinationSslKeyStore
• coordinationSslKeyStoreCredentialsFile
• coordinationSslTrustStore
• coordinationSslTrustStoreCredentialsFile
• exitClassPath
• exitNativeLibraryPath
• javaCoreTriggerFile
• sandboxRoot
• transferRoot
• wmqfte.database.credentials.file

Example

In this example on a Windows system, a user fteuser using an environment variable of USERPROFILE:

wmqfte.database.credentials.file=%USERPROFILE%\\logger\\mqmftcredentials.xml

Resolves to the following file path:

C:\Users\fteuser\logger\mqmftcredentials.xml

In this example on a UNIX system, a user fteuser using an environment variable of HOME:

transferRoot=$HOME/fte/

Resolves to the following file path:

/home/fteuser/fte/