Running a 64-bit Execution Server on HP-UX, AIX, and Solaris

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

In the go.sh line similar to the following:

JAVA_PGM="/usr/java/1.x.x/15/bin/java"

(where x.x refers to the appropriate Java version)

change the Java JRE path to point to a JRE that has 64-bit support.

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

HP-UX

1. On 64-bit HP-UX, in the go.sh line similar to this: 
   JAVA_PGM="/usr/java/1.x.x/08/bin/java" 
   (where x.x refers to the appropriate Java version) 
   add the '-d64' command-line parameter to Java to start it in 64-bit mode. For instance, the line above can simply be changed to:
   JAVA_PGM="/usr/java/1.x.x/08/bin/java -d64"

2. To verify that Java is running in 64-bit mode, run it with the '-version' parameter. 

   ->/usr/java/1.x.x/08/bin/java -d64 -version java version "1.x.x.08"

   Java(TM) 2 Runtime Environment, Standard Edition (build 1.x.x.08-

   _04_may_2007_06_31)

   Java HotSpot(TM) 64-Bit Server VM (build 1.x.x.08 jinteg:05.04.07-09:34 PA2.0W (aCC_AP), mixed mode)

   (where x.x refers to the appropriate Java version)

   The text, 64-Bit Server, indicates that it is running in 64-bit mode. 

   Important

   If the HP-UX Java installation does not support the '-d64' parameter, point to a separate 64-bit Java JRE. Contact the system administrator for assistance in locating such a version of Java.

AIX

On 64-bit AIX, 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. 

   ->/usr/java/1.x.x_64/10/bin/java -version java version "1.x.x"

   Java(TM) 2 Runtime Environment, Standard Edition (build pap64dev-20090707 (SR10))

   IBM J9 VM (build 2.3, J2RE 1.x.x IBM J9 2.3 AIX ppc64-64 j9vmap6423-20090707

   (JIT enabled)

   J9VM - 20090706_38445_BHdSMr JIT  - 20090623_1334_r8

   GC   - 200906_09)

   JCL  - 20090705

   (where x.xrefers to the appropriate Java version)

   The text, ppc64-64, indicates that it is running in 64-bit mode.

2. Update the location of Java in dme/go.sh to point to this 64-bit Java.

Solaris

1. On 64-bit Solaris, in the go.sh line similar to this: 
   JAVA_PGM="/usr/java/1.x.x/15/bin/java" 
   (where x.x refers to the appropriate Java version)
   add the '-d64' command-line parameter to Java to start it in 64-bit mode. For instance, the preceding line can simply be changed to:
   JAVA_PGM="/usr/java/1.x.x/15/bin/java -d64"

2. To verify that Java is running in 64-bit mode, run it with the '-version' parameter. 

   ->/usr/java/1.x.x/15/bin/java -d64 -version

   java version "1.x.x_15"

   Java(TM) 2 Runtime Environment, Standard Edition (build 1.x.x_15-b04)

   Java HotSpot(TM) 64-Bit Server VM (build 1.x.x_15-b04, mixed mode)

   (where x.x refers to the appropriate Java version)

   The text, 64-Bit Server, indicates that it is running in 64-bit mode. 

   Important

   If the Solaris Java installation does not support the '-d64' parameter, point to a separate 64-bit Java JRE. Contact the system administrator for assistance in locating such a version of Java.

Restart and Verify the Execution Server

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

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.