Usecase 3
Changing the JVM settings in the file bwappnode-<AppNodeName>.tra, gives you a micro level control over each AppNode.
This use case is useful when the requirements for each AppNode are different. You can manage the AppNodes independent of any changes in the other TRA files. When you want to change the JVM parameters for a particular AppNode in an AppSpace, you can change the properties directly, as mentioned in the section Setting JVM Parameters for the AppNode Manually .
The following changes will take place:
Existing AppNodes
- Before setting the JVM Parameters - If not specified explicitly, the default values of JVM parameters for each AppNode are applicable. These values are commented out by default. These are the settings that an AppNode takes when created, and if the JVM parameters are already set at the bwcommon.tra or bwappnode.tra level, (refer Usecase 1), or at the AppSpace level, (refer Usecase 2), then those settings will take effect.
- After changing the JVM parameters and without restarting of AppNodes - No changes in the AppNode settings.
- After changing the JVM parameters and AppNode restart - The changes will be applied to the particular AppNode and there will be no impact on the other AppNodes.
Copyright © Cloud Software Group, Inc. All rights reserved.