New Documentation

   

Control-M Automation API Documentation has moved to a new location, with a new design to enhance ease of use.

Setting the Java Environment Variable

Before you perform setup or install for the first time, you must set the Java environment variable, which points to an external Java installation. For a list of supported Java vendors, see Control-M Compatibility with External Java Vendors.

Note

  • If you are using external Java on SUSE, see 000396918.

  • The Java installation directory must contain the bin directory and the Release file.

  • (Windows only) You cannot set the Java environment variable on a network.

  • On UNIX:
    • From a command line, type one of the following:
      • sh/bash: export BMC_INST_JAVA_HOME=/home/<java_11_directory>
      • csh/tcsh: setenv BMC_INST_JAVA_HOME /home/<java_11_directory>
  • On Windows:
    • From a command line, type the following:
      set BMC_INST_JAVA_HOME=”C:\Program Files\<java_11_directory>

Note

If you are installing in automatic or console mode, set the Java environment variable in the command, as follows:

  • UNIX: setup.sh -silent <xml_path>/<filename.xml> -BMC_INST_JAVA_HOME <java_path>
  • Windows: setup.exe -silent <xml_path>\<filename.xml> -BMC_INST_JAVA_HOME <java_path>

Control-M Compatibility with External Java Vendors

The following table lists the operating system, architecture, and Java vendors that you can use for Control-M:

Operating System

Architecture

Java Vendor

Version

AIX 

PowerPCIBM11.0.12 or higher

Linux 

PowerPC
  • Eclipse
  • IBM 
11.0.12 or higher

Linux 

s390x
  • Eclipse
  • IBM 
11.0.12 or higher

Linux 

x86_64
  • Eclipse
  • Oracle
  • Azul
11.0.12 or higher

Solaris 

Sparc
  • Oracle
  • Bellsoft
11.0.12 or higher

Windows 

x86_64
  • Eclipse
  • Oracle
  • Azul
11.0.12 or higher
Was this page helpful? Yes No Submitting... Thank you

Comments