Integration Server 11.1 | Microservices Runtime Guide | Configuring Microservices Runtime | Specifying the JDK or JRE for Microservices Runtime
 
Specifying the JDK or JRE for Microservices Runtime
Microservices Runtime must point to a Java location. By default, Microservices Runtime points to the location of the JRE installed at the same time you installed Microservices Runtime. If necessary, you can specify a different location.
Before you specify the location of Java for Microservices Runtime, determine whether you need to specify the location of the JDK or the JRE. If you intend to use Microservices Runtime to develop and compile Java services on Microservices Runtime, specify the location of the JDK. If you will not be using this installation of Microservices Runtime to compile Java services, you can specify the location of a JRE.
*To specify the Java location for Microservices Runtime
1. Edit the setenv.bat/sh file in one of the following ways:
*In the install\bin folder:
1. Navigate to Software AG_directory\install\bin and use a text editor to open the setenv.bat/sh file.
2. Change the JAVA_HOME and JRE_HOME parameters to specify your JDK or JRE installation directory.
SET JAVA_HOME=<path_to_your_java_installation>
SET JRE_HOME=<path_to_your_java_installation>
Note:
Changing the location in install\bin causes other products using the same install folder to also use the modified JDK or JRE.
*In the Integration Server_directory\bin folder:
1. Navigate to Integration Server_directory\bin and use a text editor to open the setenv.bat/sh file.
2. Set the value for JAVA_HOME and JRE_HOME to specify your JDK or JRE installation directory explicitly before the code to set JAVA_DIR.
SET JAVA_HOME=<path_to_your_java_installation>
SET JRE_HOME=<path_to_your_java_installation>
IF "%JRE_HOME%" == "" (
SET JAVA_DIR="%JAVADIR%"
) ELSE (
SET JAVA_DIR="%JRE_HOME%"
)
2. Save and close the file.
3. Restart Microservices Runtime.
Note:
If you change the Java location and you use Microservices Runtime to develop and compile Java services, you must also change the value of the watt.server.compile configuration parameter.