Changing default settings for Separate Process microservices

To set default JVM parameters for newly added microservices, Service Options need to be changed in Window preferences and Java Home needs to be set in the FPS profile.

JVM Parameter Configurations

To change default JVM parameters, perform the following actions in eStudio:

1. Open Preferences dialog box from the Window menu.
    
2. Navigate through Fiorano > Orchestration and click Service Options tab.
    

3. In the service Options tab, expand the Memory Tuning section, provide the Maximum Heap Size and Initial Heap Size values as per requirement.

   Icon

   Provide prefix "m" for the values as these are represented in MBs.

   
   Figure 1: Changing JVM parameter values
    

4. Click OK to complete the JVM configuration.
   
   
5. Create an event process and drag the required microservice to the Orchestrator editor. Right-click the microservice and click the Properties option.
   
   
6. In the Runtime Arguments tab, notice that the JVM_PARAMS property values are auto-populated.
   
   
   Figure 2: JVM parameter values autopopulated in microservice runtime arguments

Setting Java Home for all Separate Process microservices globally in Peer Profiles

Java Home for all Separate Process microservices can be set globally in Peer profiles in 3 different ways as explained below.

From Profile Manager in eStudio

To set Java Home for running Separate Process microservices, perform the following actions in the eStudio Profile Management perspective after stopping the peer server:

1. Open FPS profile and navigate through Fiorano > Esb > Peer > Core
    
2. Select the EventProcessManager node and provide the absolute Java Home path in JavaHomeForSeparateProcessComponents property. Example: C:\Program Files\Java\jdk1.7.0_55
   
   
   Figure 3: Changing Java Home in Profile Mangement perspective
   
   
3. Save the profile (Click the Save  button or press CTRL+S) and restart the server.

From Server Connections in eStudio

To perform the same operation as above with the server running, perform the following actions in the eStudio Connection Management perspective:

1. Logon to FPS-JMX node and navigate through JMX Connection > Fiorano > Esb > Peer > Core > ProcessManager > EventProcessManager.
    
2. Select Config node and provide the absolute Java Home path in JavaHomeForSeparateProcessComponents property. Example: C:\Program Files\Java\jdk1.7.0_55
   
   
   Figure 4: Changing Java Home in Connection Mangement perspective
   
   
3. Save the profile (Click the Save  button or press CTRL+S).

From the Configuration file in the profile

Stop the server and perform the following actions:

1. Open the Configs.xml file from the location FioranoHome\esb\server\profiles\<ProfileName\FPS\conf

2. Append the following text anywhere within the Container tag, preferably between JETTY_SERVICE_CONFIG and MESSAGE_BUS_CONFIG tags:

   Icon

   The path "C:\Program Files\Java\jdk1.7.0_55" provided for the JavaHomeForSeparateProcessComponents property is just an example. Change it accordingly.

   
   
   Figure 5: Changing Java Home in Profile configuration file
   
   

3. Save the file and restart the server.

Setting Java Home for Specific Separate Process microservices

By default, separate process microservice will be launched using Java used by the peer server. But if the JavaHomeForSeparateProcessComponents property (see Figure 3) is configured in the peer profile, it takes the higher priority.

To run a microservice with a specific Java version or use different Java version other than the one being used by the peer server, set the JAVA_HOME parameter in the Runtime Arguments in the microservice Properties panel.

To set JAVA_HOME for a specific microservice, perform the following actions in eStudio:

1. Right-click the microservice and click the Properties option.
2. In the Runtime Arguments tab, provide the java installation path under Value for the JAVA_HOME argument.
3. Save the event process.
   
   
   Figure 6: Changing Java Home in the Runtime Arguments property of the microservice