This section introduces the primary concepts we need when working with properties.
Property files form a baseline for the entire IBM TDI installation for all users on that computer. However, if your Solution Directory is different from the installation directory, we can have a set of text files in your Solutions Directory that mirror their counterparts in the installation directory. A property listed in any of those files override anything set in any of the global installation property files, including the...
Futhermore, a Java property set inside a Config file takes the highest precedence, and overrides anything in a global property file or the property files in the Solution Directory.
We can specify the Solution Directory in multiple ways:
In any other case, the first time we run the TDI Server, it makes a copy of all the property files into our Solutions Directory (it does not overwrite these files if they already exist). We can now tailor these files to our particular needs, without affecting the property files in the installation directory. The files remaining in the installation directory continue to form a baseline configuration for other instances of TDI.
The file global.properties is copied to a file called solutions.properties in your Solutions Directory. Other files, like Log4J.properties and the files in the amc and serverapi folders are copied under their own names.
For documentation purposes, the original global.properties file from the installation directory is copied to the <Solution directory>/etc folder; this file is not used for any other purpose.
The tdimiggbl tool helps you to migrate your global.properties file from one version of TDI to a higher version. See the following chapter Migrating.
Global properties are used to configure the TDI Server settings that are kept in a file called global.properties in the etc folder of the installation directory. All properties included in the global.properties file are listed with their default values and explained in this chapter. A reference to more detailed documentation is provided, where possible, in the beginning of the groups of properties. The Configuration Editor (CE) (ibmditk) and the TDI server) ibmdisrv) read the global.properties file on startup. This file is read and applied before a file called solution.properties from the Solution Directory is read.
Use of the property | Property | Default value | Description |
---|---|---|---|
Add our own .jar or .zip files | com.ibm.di.loader.userjars | c:\myjars | Specifies directories or jar files, separated by the Java Property "path.separator", which is ":" on Linux and ";" on Windows. Directories are searched recursively by the TDILoader for jar files containing classes and resources. Only files with a .zip or .jar extension are searched. |
Define cipher | com.ibm.di.securityTransformation | DES/ECB/NoPadding | Defines a cipher for the password-based encryption or decryption of TDI configurations. Changed in TDI 7.0. |
Enable config autoload | com.ibm.di.server.autoload | autoload.tdi | Looks for *.xml files in the directory specified by the "ibmdisrv -d" command. Executes each *.xml file found in the directory defined by -d. |
Solution properties typically override global.properties and are found in a file in your solution directory called solution.properties. The solution.properties file is by default a copy of the global.properties file, and we should edit the solutions.properties file when configuring TDI, because it is read last out of all the properties files. If we want to, we can delete properties in your solution.properties file and add property configuration statements that you specifically want to override the global.properties defaults.
Java properties are variables and settings of the Java Virtual Machine (JVM). Java log (Jlog) file properties are shown in Useful JLOG parameters.
A Java property set inside a Config file takes the highest precedence, and overrides anything in a global property file or the property files in the Solution Directory.
Property | Default value | Description |
---|---|---|
javax.net.debug | none | Sets debug mode for the JSSE provider. |
com.ibm.di.javacmd | none | Overrides the Java interpreter. |
com.ibm.di.installdir | none | Uses this path to the Java executable file when running AssemblyLines from the Configuration Editor. |
com.ibm.di.jvmdir | TDI_root/jvm | Defines the directory path where the JRE that TDI uses is installed. |
com.ibm.di.server.maxThreadsRunning | 500 | Sets this number of threads TDI. Must be set higher than 3 to have any effect. |
com.ibm.di.server.securemode | false | Sets the mode in which TDI is running. (standard or secure) |
com.ibm.di.server.keystore | testserver.jks | Names the keystore of the Server's SSL certificate. Renamed in TDI 7.0. |
com.ibm.di.server.key.alias | server | Names the key alias of the Server's SSL certificate. Renamed in TDI 7.0. |
{protect}-api.keystore.password | server (encrypted by default) | Provides the password for the server API keystore. Added in TDI 7.0. |
{protect}-api.key.password | Provides the key password. If not specified, uses server keystore password. Added in TDI 7.0. | |
com.ibm.di.server.encryption.keystore | testserver.jks | Names the keystore of the server encryption key. Added in TDI 7.0. |
com.ibm.di.server.encryption.key.alias | server | Provides the key alias of the server encryption key. Added in TDI 7.0. |
com.ibm.di.server.encryption.keystoretype | jks | Provides the type of the keystore that hosts the key used by the server for encryption. Added in TDI 7.0. |
com.ibm.di.server.encryption.transformation | RSA | Names the cryptographic transformation used by the server for encryption. Can be set to either "RSA" (public key encryption) or to some secret key transformation. Added in TDI 7.0. |
com.ibm.di.server.fipsmode.on | false | Enables or disables FIPS standards in TDI. If this property is set to true, TDI runs in FIPS-compliant mode. For more information on FIPS mode, see Added in TDI 7.0. |
com.ibm.di.default.bind.address | * | The default bind address for the whole TDI Server - the components and the Server API. |
System properties are stored in the System Store instead of being stored in an external properties file such as solution.properties. Certain system properties and Java properties are read-only. These system properties are shown in the respective Property Stores (for example, System Store). Attempting to modify these read-only properties has no effect. See also System Store.