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.

For more information about how to change the JVM parameters for a particular AppNode in an AppSpace, see Setting JVM Parameters for the AppNode Manually .

The following changes are made:

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, ( see Usecase 1), or at the AppSpace level, (See Usecase 2), then those settings 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 are applied to the particular AppNode and there is no impact on the other AppNodes.

New AppNodes

There is no impact on the AppNodes created.