Environment Variables

You must set the important environment variables before installing TIBCO MDM.

Note:
  • It is recommended that you use ASCII characters for all file names. If these names include non-ASCII characters, copying the files from Windows to UNIX or Linux and vice versa may result in corruption of file names.
  • While setting environment variables on all platforms, if the ‘\’ character is used as a path separator instead of ‘/’, it leads to errors as ‘\’ is treated as an escape character.
  • For Simple install, set only JAVA_HOME environment variable.
  • For Typical install, set all the environment variables mentioned in the Environment Variables table.
Environment Variables
Variable Description
MQ_HOME Define MQ_HOME to point to the installation directory. It is recommended that you allocate at least 8 GB to this directory. In a clustered environment, each application server should point to a separate location.

Example: /home/tibco/mdm/version

MQ_LOG The location where log files will be generated (the recommended location is $MQ_HOME/log). In a clustered environment, each server should point to a separate location. Define MQ_LOG to point to this directory. A minimum of 1 GB should be allocated to this directory. The best practice is to change the default location such that the directory is not a sub-directory of MQ_HOME.

Example: $MQ_HOME/log

MQ_COMMON_DIR All standard configurations files for workflow and data validation as well as all customizations are stored in this directory. This directory also holds all files generated during normal application processing. It is shared by all application servers in the cluster, and should be mounted to each server. All disk space indicated in the section Hardware Configuration should be assigned to this directory, and the MQ_COMMON_DIR variable should be set. The best practice is to change the default location such that the directory is not a sub-directory of MQ_HOME.

Example: /home/tibco/mdm/version/common

If you plan to create a copy of the TIBCO MDM instance across operating systems (for instance, Linux to Windows or Windows to Linux) and if the path contains any non English characters, such a copy may not be possible. For example, using Japanese characters in the path.

MQ_CONFIG_FILE Points to $MQ_HOME/config/ConfigValues.xml. The values/parameters in this file can be set using the Configurator.

Example: /home/tibco/mdm/version/config/ConfigValues.xml

JAVA_HOME The directory where JRE/JDK is installed.

Example: /opt/jdkversion

EMS_HOME The directory where TIBCO EMS (or the messaging software) is installed.

Example: /home/tibco/ems

ANT_HOME The Directory path where ant is installed.

Example: /opt/antversion

Application Server Specific
WAS_HOME The directory where WebSphere is installed (required only if using WebSphere).

Example: /opt/WebSphere/AppServer

JBOSS_HOME For JBoss WildFly Application Server. Specify the path value until the root of the WildFly directory.

Example, E:\JBoss\wildfly-version.Final.

JBOSS_HOME (Simple Install) The directory where JBOSS is installed (required only if using simple installation).

Example: %MQ_HOME%\bin\wildfly-version.Final

BEA_HOME For WebLogic Application Server. Specify the path value of the WebLogic Application Server directory.
Example:
  • For Linux: /opt/bea
  • For Windows: G:/WebLogic/wlserver_version
Database Specific
ORACLE_HOME For Oracle database. The directory where Oracle is installed.
Example:
  • For Windows: /home/oracle/product/11g/db_1
  • On UNIX: $export ORACLE_HOME=/u01/app/oracle/product/version
LD_LIBRARY_PATH For Oracle database: $ORACLE_HOME/lib
NLS_LANG For Oracle database. Example:
  • On UNIX: 
    export NLS_LANG=AMERICAN_AMERICA.UTF8
  • On Windows: 
    set NLS_LANG=AMERICAN_AMERICA.UTF8
POSTGRESQL_HOME For PostgreSQL database. The directory where PostgreSQL is installed.

Example: $MQ_HOME/bin/pgsql

AS_HOME The directory where AS is located. By default AS is bundled with TIBCO MDM, if you have installed AS externally the specify the path of the location.

Example:$MQ_HOME/bin/as/version

OS The Operating system. For example, Linux.
DISPLAY This environment variable is used by X-Windows based applications. It points to a device capable of displaying an X-Windows based UI.
LD_ASSUME_KERNEL Used on the Linux platform to make Linux use the old Linux threads library, particularly required for Oracle installation (required only if Oracle is used as the database).
PATH This is a list of directories separated by a separator. When any command or program is executed, the OS tries to locate the program in the directories listed in PATH. If the program is not found in any of the directories, the OS cannot load and execute the program. The Separator character is ‘:’ for Unix and Linux platforms, and ‘;’ for the Windows platform.

Ensure that there is no space with the commas and colons between the program in the directories listed which are separated by ':' for Unix and Linux platforms, and ';' for the Windows platform.

SHLIB_PATH List of directories separated by a separator (see PATH) where a dynamic linker tries to find the libraries. Used on UNIX platforms.
LIBPATH List of directories separated by a separator (see PATH) where the Operating system as well as the application library files reside. Used on UNIX platforms.
NODE_ID Points to the current cluster member. Example: NODE_ID=Member1
TIBCO MDM REST API through Swagger UI
SWAGGER_MDM_HOST An IP address of the TIBCO MDM server on which you want to try out the TIBCO MDM REST APIs.
SWAGGER_MDM_PORT Port of the TIBCO MDM server on which you want to try out the TIBCO MDM REST APIs.