You define the Java configuration options in the TRANSFORMERJAVAOPTS environment variable. When defining Java configuration options, avoid defining duplicate options. If you do define duplicates, the last option passed to the JVM usually takes precedence. JAVAOPTS is the standard environment variable that some servers and other java apps append to the call that executes the java command. For example in tomcat if you define JAVAOPTS='-Xmx1024m', the startup script will execute java org.apache.tomcat.Servert -Xmx1024m.
Java is a very popular programming language which provides a different component in order to run, develop Java applications. JRE or Java Runtime Environment is used to run Java application. JDK or Java Development Kit is used to develop Java applications. In this tutorial, we will learn how to set up Java, JRE, and JDK operating system path variables in order to work properly.
Before starting the configuration we have to locate the JRE or JDK path. JRE or JDK generally installed on the Program Files or Program Files(x86) directory under the Java directory like below.
and under the Java directory the JDK is residing.
Now we have learned the path of the Java, JRE or JDK installation. We can set this path as Java HOME_PATH environment variable. We will open the computer properties with by running sysdm.cpl in the Run menu like below. We can also open it from the File Explorer -> Computer -> Right Click.
In the system properties, we will navigate to the Advanced tab which provides the Environment Variables button like below.
Below we can see the environment variables menu where we will create the JAVA_HOME system variable and set the path accordingly. We click to the New in order to create a new system variable.
Here we will set the Variable Name as JAVA_HOME and the Variable Value the path or Java, JRE or JDK which is C:Program FilesJavajdk-12 in this example. Then we will click OK.
If we want to run java.exe or similar executables provided by JRE or JDK we have to add the path of Java in the Path variable like below. We select the system variable named Path and click to the Edit.
Here we click to New which will add a new line to the existing values.
Here we will set the bin folder path which is C:Program FilesJavajdk-12bin in this example.
Then we will click OK and OK in the environment variables screen which will save and activated new path configuration.
We can check the new path configuration simply opening a new command line interface MS-DOS. Then just type java -version which will execute java.exe with the -version option. We can see the current java binary version by running it.
JavaScript must be enabled in order to use this site.
Please enable JavaScript in your browser and refresh the page.
This section lists the environment variables that can used for TIBCO BusinessWorks™ Container Edition application deployment.
Java_opts Environment Variable Definition
| Environment Variable | Default Values | Description |
|---|---|---|
| BW_LOGLEVEL | ERROR | Used to set a log level for the TIBCO BusinessWorks™ Container Edition application. The default value is ERROR. Supported values are:
|
| BW_ENGINE_THREADCOUNT | 8 | Used to set engine thread count for the TIBCO BusinessWorks™ Container Edition application. |
| BW_ENGINE_STEPCOUNT | -1 | Used to set engine step count for the TIBCO BusinessWorks™ Container Edition application. |
| BW_APPLICATION_JOB_FLOWLIMIT | n/a | Used to set flow limit for TIBCO BusinessWorks™ Container Edition application. |
| APP_CONFIG_PROFILE | default | Name of the application profile that is to be used from a configuration management system such as ZUUL, Spring Cloud Config and so on. |
| BW_PROFILE | n/a | Used to set the name of the BusinessWorks profile from the application. |
| BW_JAVA_OPTS | n/a | Used to set Java properties that are used at run time. The properties are specified using name-value pairs and are separated by spaces. For example, BW_JAVA_OPTS='-Dname=value -Dname=value' |
| MASHERY_SERVICE_CONFIG | Applications can pass TIBCO Mashery configuration through the MASHERY_SERVICE_CONFIG environment variable. The value of the environment variable is a JSON string with the required TIBCO Mashery configuration. For more information, see Integrating with TIBCO Mashery. | |
| ENABLE_SERVICE_DIRECT_REGISTRATION | false | If set to true, an application will be registered using its host IP and port instead of the application route. |
| CONSUL_SERVER_URL | Used to set Consul server configuration. For example, CONSUL_SERVER_URL=http://127.0.0.1:8085.This must be set if you intend to use Consul for application configuration or for service registration and discovery. | |
| EUREKA_SERVER_URL | Used to set Eureka server configuration. For example, EUREKA_SERVER_URL=http://127.1.0.1:8080/eurekaThis must be set if you intend to use Eureka for service registration and discovery. | |
| CF_TARGET | None | To add an Elastic Runtime self-signed certificate automatically at runtime, set CF_TARGET to the API endpoint of your Elastic Runtime instance. For example, CF_TARGET=https://api.cf.demo.com. This is useful when using Spring Cloud Services in your application. |
| BW_JMX_CONFIG | n/a | Used to set JMX configuration (JMX port) for monitoring TIBCO BusinessWorks™ Container Edition application. For example, BW_JMX_CONFIG: 8050 |
| BW_JAVA_GC_OPTS | -XX:+UseG1GC | Used to set JAVA GC configuration. The value should be one of the standard Java GC VM Options. For example, BW_JAVA_GC_OPTS: -XX:+UseParallelGC |
| DISABLE_BWCE_EAR_VALIDATION | False | Used to deploy the ActiveMatrix BusinessWorks 6.x application EAR file on TIBCO BusinessWorks Container Edition without converting project to Container Edition and rebuilding EAR file from TIBCO Business Studio for BusinessWorks Note: Ensure that the ActiveMatrix BusinessWorks 6.x EAR file is exported. ActiveMatrix BusinessWorks 6.x EAR file should only have TIBCO BusinessWorks Container Edition supported activities and features. |
| BREAK_CIRCUIT_ON_404_ERROR | True | Used to change the behavior of the Circuit Breaker functionality. By default, circuit breaks for 404 (Not Found) error code. It does not break the circuit for 404 error code on specifying the value of the variable as false. |
| SPRING_CLOUD_CONFIG_VAULT_TOKEN | n/a | Used to pass the Vault token for Pivotal Platform application, while using Vault as backend for Spring Cloud Config. |
| CUSTOM_LOGBACK | False | Used for customizing logs. |