Modifying Environment Variables

The method that you use to modify environment variables depends on the Transformer installation type:
Tarball installation started manually from the command line
When you start Transformer manually from the command line on any operating system, edit the $TRANSFORMER_DIST/libexec/transformer-env.sh file to modify environment variables.

Use a text editor to edit the transformer-env.sh file. Some of the environment variables in the file are commented out and do not reflect the default values. Be sure to uncomment the line when you change a variable value.

After you edit the file, restart Transformer from the command prompt to enable the changes.

Note: Do not restart Transformer from the user interface after modifying environment variables.
RPM installation started as a service on operating systems that use the SysV init system
When you start Transformer as a service on CentOS 6, Oracle Linux 6, or Red Hat Enterprise Linux 6, edit the $TRANSFORMER_DIST/libexec/transformerd-env.sh file to modify environment variables.

Use a text editor to edit the transformerd-env.sh file.

After you edit the file, restart Transformer to enable the changes.

RPM installation started as a service on operating systems that use the systemd init system
When you start Transformer as a service on CentOS 7, Oracle Linux 7, or Red Hat Enterprise Linux 7, edit the /usr/lib/systemd/system/transformer.service file to modify environment variables.
Override the default values in the transformer.service file using the same procedure that you use to override unit configuration files on a systemd init system. For an example, see "Example 2. Overriding vendor settings" in this systemd.unit manpage.
After overriding the default values, use the following command to reload the systemd manager configuration:
systemctl daemon-reload

Then restart Transformer to enable the changes.