Oracle JAVA policy provides a free 6 month support for a release. After 6 months, customers must pay for licensing.
Control-M supports and provides Open JDK product starting with release 9.0.19.100, which replaces the Oracle JDK.
Application plugins that are not bundled in Control-M Application Pack have a separately planned migration path to OpenJDK, detailed below. For plugins that are not bundled in Application Pack, BMC supports the use of customer provided JAVA whether the Java is an Open JDK or is a customer paid license to Oracle JDK, subject to conditions provided below.
This article provides the procedure for supporting a customer's own JDK with application plugins that are not included in Application Pack.
BMC does not support major versions of JAVA that are not certified first. (v.w.x.y - v.w. constitute major release)
All patch levels above minimum documented release levels are supported but should undergo thorough testing prior to going into product,
Below is information regarding how to change a Control-M environment to point to your own supplied version of JAVA.
JRE cannot be upgraded to a higher major release than the one that the product was certified. (1.8.x)
JRE shipped with Control-M can be upgraded with a minor release. (For example: from 1.8.0.25 to 1.8.0.116)
JRE shipped with Control-M plugins can be replaced with an independently installed version as long as the new version meets the above requirements.
Changing 32bit for 64bit or vice versa is not supported.
The table below shows if JRE is required for main processes and the upgrade policy.
|
Plug-Ins outside the Application Pack
|
JRE required for main process
|
Comments
|
|
Control-M for SAP Process Integration
|
Yes
|
|
|
Control-M for PeopleSoft
|
Yes
|
|
|
Control-M for Web Services, Java and Messaging
|
Yes
|
|
|
Control-M for SAP
|
Yes
|
|
|
Control-M for Cloud
|
Yes
|
|
|
Control-M for Hadoop
|
Yes
|
9.0.18 and below. 9.0.19 is part of the AP
|
|
Control-M for IBM Cognos
|
No
|
|
|
Control-M for IBM InfoSphere DataStage
|
Yes
|
|
|
Control-M for Informatica
|
Yes
|
9.0.19 and below (9.0.19.100 will part of AP)
|
|
Control-M for Oracle Business Intelligence
|
Yes
|
|
|
Control-M for Oracle E-Business Suite
|
Yes
|
|
|
Control-M for Oracle Retail
|
Yes
|
|
|
Control-M for SAP Business Objects
|
Yes
|
|
|
Control-M Managed File Transfer
|
Yes
|
9.x (BMC_JAVA_HOME is not supported for 9.0.19 and below.
|
|
Control-M Advanced File Transfer
|
Yes
|
8.2.0.400 and above supports Open JRE. Versions below support only Oracle JRE
|
This procedure will instruct you how to use your own JRE instead of the JRE that is embedded in Control-M
Notes:
- For Windows installations, in the steps below, when it says to create a symbolic link named JRE that points to the new JRE - instead of creating a link, the new JRE version should be installed directly into the JRE directory.
- Additionally, for both Unix and Windows, you should create an empty file named ‘jreupdatedbycustomer.txt’ in the JRE directory. This will allow the fix pack installation to eliminate any JRE updates if this file exists.
- For AFT 8.2.x and MFT 9.0.18 and above refer to KA 000178940
- For Control-M Web Services API (not Control-M for Web Services), rename the "JRE" to "JRE.old" and then copy the new JRE to <Control-M API home>\JRE.
To work with alternative JRE:
- Login to the Control-M/Agent account which contains the Application plugin.
- Go to
- $HOME/ctm/cm/<Application> directory if Agent installed as standalone.
or
- $HOME/ctm_agent/ctm/cm/<Application> directory in case the Agent was installed as part of the Control-M Server.
- Identify version and architecture of JRE install:
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
- Rename the JRE directory:
Rename JRE directory to JRE_org and JRE_64 directory to JRE_64_org
Some of the directory platform path may be specified as JRE_64
- Download and install JRE:
Ensure that OpenJRE or the version of Oracle JRE you are downloading and installing meets all the requirements specified, including that the Major version stays the same and architecture (32bit/64bit) stay the same, etc. See above for requirements.
- Create symbolic link to your JRE:
- Under your specific plugin directory, create a symbolic link named JRE that points to your new JRE
- Ensure the name of the link is identical to the original name
- Control-M for AFT will support OpenJDK from Control-M for Advance File Transfer version 8.2.00.400. Prior to this version only Oracle JRE is supported.
To import SSL certificates to the new JRE CA certified keystore (for CMs connecting to applications over SSL)
- Navigate to <agent_home>/ctm/cm/<Application>/JRE/bin/ and run the command:
./keytool -importkeystore -srckeystore ../../JRE_<orginal>/lib/security/cacerts -srcstorepass <srcstorepass> -destkeystore ../../JRE/lib/security/cacerts -deststorepass <deststorepass> -srcalias <source_certificate_alias_name>
Note: To find the alias name of the existing certificate you can run the following command:
./keytool -list -v -keystore ../../JRE_<original>/lib/security/cacerts
- To verify the certificate imported successfully to the new keystore please run the command:
./keytool -list -v -keystore ../../JRE/lib/security/cacerts
Enter the password ("changeit" is the default password) and make sure the alias name exists. - Repeat steps above for all certificates.
JRE_<original> should be replaced with JRE_org or JRE_64_org