Skip to Content

Task 4.5 Run the File-AID Execution Server in 64 Bit JVM on Linux

After installing BMC Compuware File-AID/EX, a change must be made to go.sh in the dme folder to turn on 64-bit mode.

Warning

Failure to first stop the execution server will result in having an engine running on both the old port and the new port, which makes it difficult to determine which engine to shut down since there is no port designation to indicate which engine goes with which port.

  1. Change the Java JRE path to point to a JRE that has 64-bit support. See more details for specific versions of operating system below.

    Warning

    JREs can be downloaded at http://www.oracle.com/technetwork/java/index.html. Contact your system administrator for assistance in locating and installing an appropriate JRE.

  2. After this change to dme/go.sh is complete, stop the execution server and restart it. When the execution server restarts, it should display the following to stdout along with other logging information:

    sun.arch.data.model: 64

If the number displayed is 64, the execution server is running in 64-bit mode. If the number displayed is 32, it is still running in 32-bit mode and this is not supported.

Instructions for Changing JRE Bitness for Particular Versions of OS

For Linux

On 64-bit Linux, it is necessary to point to a separate 64-bit Java JRE.

  1. To verify that Java is running in 64-bit mode, run it with the '-version' parameter. For example:/usr/java/bin# java -version
    openjdk version "1.8.0_181"
    OpenJDK Runtime Environment (build 1.8.0_181-b13)
    OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
  2. Update the location of Java in dme/go.sh to point to this 64-bit Java.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Compuware Topaz Enterprise Data 20.06