...
As a work around for this behavior, create a file called setupEnv.sh in the root of /opt/dm/mci, add the following environment variable definition to the profile of the user running MettleCI Workbench (usually mciworkb)this file and ensure it is owned by mciworb with permissions -rwxr-xr-x:
| Code Block |
|---|
export JAVA_OPTS=-Dcom.datamigrators.mettle.process.CommandRunner.libpath=$LD_LIBRARY_PATH OR for AIX: export JAVA_OPTS=-Dcom.datamigrators.mettle.process.CommandRunner.libpath=$LIBPATH |
Once this has been added to the MettleCI Workbench user’s profile, log in as the user and run the following commands /opt/dm/mci/setupEnv.sh has been created, restart MettleCI Workbench:
| Code Block | ||
|---|---|---|
| ||
# switch user, ensure profile is sourced
sudo su - mciworkb
# verify the environment variable is set as expected
echo $JAVA_OPTS
# restart the workbench service
sudo service dm-mettleci-workbench stop
sudo service dm-mettleci-workbench start |