IBM JRE provides IBM® SDK, Java™ Technology Edition, Version 8. Unless otherwise configured, the version of Java that will be used is specified in config/ibm_jre.yml. See the license section for restrictions that relate to the use of this image. For more information about IBM® SDK, Java™ Technology Edition and API documentation, see the IBM Knowledge Center.
Licenses for the products installed within the buildpack:
IBM® SDK, Java™ Technology Edition, Version 8: International License Agreement for Non-Warranted Programs.
For general information on configuring the buildpack, including how to specify configuration values through environment variables, refer to Configuration and Extension.
The JRE can be configured by modifying the config/ibm_jre.yml file in the buildpack fork. The JRE uses the Repository utility support and so, it supports the version syntax defined there.
To use IBM JRE instead of OpenJDK without forking java-buildpack, set environment variable and restage:
cf set-env <app_name> JBP_CONFIG_COMPONENTS '{jres: ["JavaBuildpack::Jre::IbmJRE"]}'
cf restage <app_name>| Name | Description |
|---|---|
repository_root |
The URL of the IBM JRE repository index (details). |
version |
The version of Java runtime to use. |
It is recommended to use the following Transport Layer Security (TLS) options for IBM JRE version 8 and above:
cf set-env <app_name> JAVA_OPTS '-Dcom.ibm.jsse2.overrideDefaultTLS=true'
The JRE can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the resources/ibm_jre directory in the buildpack fork.
To add custom SSL certificates, add your cacerts file to resources/ibm_jre/jre/lib/security/cacerts. This file will be overlayed onto the IBM JRE distribution.
The total available memory for the application's container is specified when an application is pushed.The Java buildpack uses this value to control the JRE's use of various regions of memory and logs the JRE memory settings when the application starts or restarts.
Note: If the total available memory is scaled up or down, the Java buildpack will re-calculate the JRE memory settings the next time the application is started.
The user can change the container's total memory available to influence the JRE memory settings. Unless the user specifies the heap size Java option (-Xmx), increasing or decreasing the total memory available results in the heap size setting increasing or decreasing by a corresponding amount.
The user can configure the desired heap ratio (-Xmx) by changing the heap_ratio attribute under jre in config/ibm_jre.yml and the buildpack calculates the -Xmx Memory Setting based on the total memory available.
The container's total memory is logged during cf push and cf scale, for example:
state since cpu memory disk details
#0 running 2017-04-10 02:20:03 PM 0.0% 896K of 1G 1.3M of 1G