Page History

...

In Fiorano Dashboard, the split-up of Heap and Non-Heap Memory usage for each Server Type and CCP enabled components are available.

Server Example:
Image Modified
Figure 1: Screenshot of Server Status in Dashboard

Component Example:
Image Modified
Figure 2: Screenshot of microservice Details in Applications taken from the Dashboard

...

Memory used by a component can be restricted or expanded based on the requirement. This can be done by appending appropriate "–Xms" and "-Xmx" values Maximum Heap Size (-Xms) and Initial Heap Size (-Xmx) values with JVM_PARAMS value present in Runtime Arguments tab under Properties.Image Removed

Image Added
Figure 3: Example: -DLOG_TOSTREAM=true –Xms40m –Xmx128m

...

Anchor
Using same JVM settings in Multiple Service Instances Using same JVM settings in Multiple Service Instances

Using same JVM settings in Multiple Microservice Instances

After changing the pressing Enter to apply the changes made in JVM_PARAMS value, as described in the previous section, clicking No in Update all Service Instances dialog box applies the setting settings only to the presently selected Microservice Instance(s). Clicking Yes provides Select Service Instance window where the same setting can be applied to

To apply the same settings for multiple Microservice Instances from all the Event Processes.Image Removed
,

1. Select the Update service instances from all Event Processes checkbox; the Yes button gets active.
2.  Click Yes; Select Service Instance dialog box appears.
3. Select the Service Instances to which the same JVM settings need to be applied and press OK.

Image Added
Figure 4: Updating Microservice Instances

Anchor
Using same JVM settings in Multiple Environments Using same JVM settings in Multiple Environments

Using same JVM settings in Multiple Environments

To use a particular JVM _Params setting parameter across environments, save the configuration as 'named configuration' bu performing the following actions:

1. In Configuration Repository window, right-click Runtime Arguments folder and click Add Configuration.
2. In the Add New Configuration dialog box, choose the preferred environment name from the Environment drop-down.
3. Provide a name for the configuration in the Name field, choose the required environment, and click Next.
   Image Removed
   Image Added
   Figure 5: Configuring Named Configuration
   
   
4. Click

   In the Runtime Arguments Configuration panel, provide the required values and Java Home and click Finish to save the named configuration for the chosen environment

   Image Removed
   

   Tip
   title Java Home
   To access Java from a different location or to access a different java version Java Home path may be changed by adding the value for JAVA_HOME property below the JVM_PARAMS property.

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

   
   Image Added
   Figure 6: Saving Named Configuration

Change Default JVM Configurations for Separate Process Components

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

JVM Parameter Configurations

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

1. Open Preferences dialog box from 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.

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

   
    Image Added
   Figure 7: Changing JVM parameter values
    

4. Click OK to complete the JVM configuration.

Setting Java Home

Java Home needs to be set separately, which can be done in 3 different ways as explained below.

From Profile Manager in eStudio

To set Java Home for running separate Process components, 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
   
   Image Added
   Figure 8: Changing Java Home in Profile Mangement perspective
   
   
3. Save the profile (Click _{Image Added} 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
   
   Image Added
   Figure 9: Changing Java Home in Connection Mangement perspective
   
   
3. Save the profile (Click _{Image Added} 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_CONFIF and MESSAGE_BUS_CONFIG tags:
   
   

   Code Block
   <EVENT_PROCESS_CONFIG JavaHomeForSeparateProcessComponents="C:\Program Files\Java\jdk1.7.0_55" ObjectName="Fiorano.Esb.Peer.Core:ServiceType=ProcessManager,Name=EventProcessManager,type=config"/>

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

   
   Image Added
   Figure 10: Changing Java Home in Profile configuration file
   
   

3. Save the file and restart the server.

Anchor
Configuring Properties Configuring Properties

Configuring Execution Type

This section provides guidelines on Managing System Resources across Peer Servers together with recommendations on in-memory execution. The number of components running on a Peer Server must be optimized to optimize the load on that Peer Server and to utilize machine resources effectively. Launch Options - Separate Process and In-memory are discussed below.

...

Launch Mode can be changed to 'In Memory' from Execution Type drop-down present in the Execution tab under Properties.

Figure 711: In Memory Execution Type

...

1. In the Micro Service Repository panel, right-click the microservice for which default Launch Mode has to be changed and click Edit.
   
   
   Figure 812: Navigating to ServiceDescriptor.xml page to change default Launch mode

   Note
   If the Micro Service Repository panel is not found in the eStudio screen, open it from Window > Show View.

2. Click Execution tab present at the bottom of the ServiceDescriptor.xml page.

3. Scroll right and select the required Launch Mode from the Preferred drop-down present under Launch Configuration section.
4. To apply the changes made, click Save (else click File > Save or press CTRL+S).
   
   
   Figure 913: changing the default Launch mode

...