How to specify a jvalccyy.prop file location

The location for the jvalccyy.prop file can be specified in a number of ways. The following options are available, and are shown in the sequence which the JVC will use to locate jvalccyy.prop.

Note: To set up the jvalccyy.prop file for the ITX Design Server, see the instructions for the swiftMTjvcConfig.tar.gz file that are contained in the release notes.

1. Use a JVM system property

Specify the location by using a JVM system property called "DTX_SWIFT_CONFIG_DIR" that contains the fully qualified path of the directory containing the jvalccyy.prop file.

JVM system properties are set by using the -D option. This can be specified in a number of ways:

Update the config.yaml file with this command:

[JVM Options]optionN=-<install_dir>/packs/financial_payments_vn.n.n.n/swift/mt/jvc/maps

where N is the next available option number.

Example:

[JVM Options]option1=-<install_dir>/packs/financial_payments_v9.0.1.0/swift/mt/jvc/maps

When using IBM Integration Bus, you can use the following command to add the JVM System Property DTX_SWIFT_CONFIG_DIR to the IBM Integration Bus Execution Group:
```
mqsichangeproperties < BrokerName > -e < ExecutionGroupName > -o ComIbmJVMManager -n jvmSystemProperty -v"-DDTX_SWIFT_CONFIG_DIR=<absolute_directory>" 
```
To check the jvmSystemProperty value of the JVM Option that is defined for the IBM Integration Bus Execution Group, use the following IBM Integration Bus command:
```
mqsireportproperties < BrokerName > -e < ExecutionGroupName > -o ComIbmJVMManager -n jvmSystemProperty
```

2. Use the Global System environment variable

To use this method, specify the location using a global environment variable called DTX_SWIFT_CONFIG_DIR that contains the fully-qualified path of the directory containing jvalccyy.prop. For example, when using the Command Server, set DTX_SWIFT_CONFIG_DIR by using the Windows SET command or the UNIX EXPORT command.

3. Use the validate_messages map

To use this method, set the rule for element JvalPropPath in Output Card 1 to the directory containing jvalccyy.prop. For example, ="c:/jvc/jvalccyy.prop"

4. Use the default location

To specify use of the default location, set the map rule for item "JvalPropPath" in "validate_messages" to =NONE.

jvalccyy.prop is installed in <install_dir>/packs/financial_payments_vn.n.n.n/swift/mt/jvc/maps for all versions of ITX.

For Transformation Extender V8.n, the jvalccyy.prop file can be located in any directory, but the map calling the JVC must be located in the same directory as jvalccyy.prop.

For ITX V.9.5 jvalccyy.prop must be moved to the following location:

Windows - <install_dir>
Linux® - <install_dir>/bin

How to choose the best method

The choice of method to use to define the location of the jvalccyy.prop is entirely dependent on individual circumstances, and no one method is better than another. Choose the method that is best suited to your environment.

As a guide, here is a brief summary of the advantages and disadvantages of the different methods:

JVM System Property - The advantages and disadvantages are similar to those of using a Global Environment Variable, but apply only when ITX has to initiate a Java™ Virtual Machine (JVM) to run the JVC. For example, this option will not work with ITX Design Server.
Global System Environment Variable - An advantage with this method is flexibility. The location can be changed without any need to recompile ITX maps or redeploy ITX components. You would, however, need to restart any running process, such at Launcher, after any changes are made to the variable. A disadvantage is that this is not an ITX component but a system-wide variable, and internal security policies may prevent access to these settings.
"validate_messages" map" - The main advantage with this method is that all configuration is contained within ITX components, so it might be simpler to manage. The main disadvantage is that the map must be recompiled and redeployed, but this may not be an issue if the location rarely changes.
Use the default location - This is the simplest method, and might be the preferred option for backwards compatibility with existing configurations. The main disadvantage is that you need to be aware of the default location, which varies between ITX versions.