Page History

...

Component Example:

Figure 2: Screenshot of Service microservice Details in Applications taken from the Dashboard

...

Reducing the maximum allocated memory helps in deploying more components, but keeping the value too low can cause out of memory errors.

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 JVM_PARAMS value, as described in the previous section, clicking No in Update all Service Instances dialog box applies the setting only to the presently selected Service Microservice Instance(s). Clicking Yes provides Select Service Instance window where the same setting can be applied to multiple Service Microservice Instances from all the Event Processes.

Figure 4: Updating Service Microservice Instances

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

Using same JVM settings in Multiple Environments

...

When it is clear that certain services microservices in a particular environment are good to be in a different Launch Mode, these components can be made to stick to the preferred launch mode by changing the default value by editing their service microservice in the Execution tab.

To change the default Launch Mode of a particular component:

1. In the Micro Service Repository panel, right-click the service/component microservice for which default Launch Mode has to be changed and click Edit.
   
   
   Figure 8: 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 9: changing the default Launch mode

...