How to choose the best method

The choice of which method to use to define the location of jvalnnn.prop depends on your circumstances. No one method is better than another.

Choose the method that is best suited to your environment.
  • JVM system property - The advantages and disadvantages are similar to using a Global Environment Variable, but only apply when WebSphere Transformation Extender must initiate a Java Virtual Machine (JVM) to run the JVC. For example, this option does not work with Design Studio.

  • Global System Environment Variable - The main advantage with this method is flexibility. The location can be changed without any need to recompile WebSphere Transformation Extender maps or redeploy components. However, you must restart any running processes after you change the variable. For example, you might have to re-start the Launcher. A disadvantage is that the Global System Environment Variable is not a WebSphere Transformation Extender component. It is, instead, a system-wide variable, and internal security policies might prevent access to these settings.

  • validate_messages map - The main advantage with this method is that all configuration is contained within WebSphere Transformation Extender components, and as a result it might be easier to manage. The main disadvantage is that the map must be recompiled and redeployed, but this might not be an issue if the location seldom changes.
  • Default location - The default location method is the simplest method, and it might be the preferred option for backwards compatibility with existing configurations. The main disadvantage is you need to be aware of the default location, which varies between WebSphere Transformation Extender versions.