TM1RunTI configuration file

TM1RunTI can function with or without a configuration file.

If a configuration file is specified, its parameters are read first.

Parameters specified on the command line are then used to override those obtained from the configuration file. When a configuration file is read, TM1RunTI first obtains parameters from the [TM1RunTI] section of the configuration file.

If a connect parameter is present, then parameter values are obtained from the associated [Connect <name>] section and used to override anything read from [TM1RunTI].

A -connect parameter can also be provided on the command line, and overrides any connect parameters found in the configuration file.

The configuration file contains:

  1. A single TM1RunTI section.
  2. One or more sections defining the TurboIntegrator processes that may be run.
  3. Zero or more sections defining connection parameters.

All entries must start at column 1. Lines beginning with # are treated as comments.

Section names must be enclosed in square brackets [ ]. If a section name is repeated, only the first one is used.

Parameters within a section:

Parameter values need to be enclosed in quotes (") if they contain whitespace.

Connect sections

To facilitate easy maintenance for different server environments such as development, test and production, connection parameters for each environment can be specified in separate sections. Each section is named using the prefix "Connect -" followed by a user defined name. For example:

[Connect – Production]

[Connect – Test]

[Connect – Development]

Process sections

Multiple process sections are permitted. Each section is named to match a process in the server.

Each TurboIntegrator process section is used to define the parameters of the TurboIntegrator process and their default values.

If there are multiple process sections with the same name, only the first one is used.

Example configuration file

This example shows the [TM1RunTI] section and a section for a single TurboIntegrator process ("my_ti_process"). The parameters and their default values, which may be overridden by parameters provided on the command line, are defined below each section header.

[TM1RunTI]
process=my_ti_process
connect=Production

[Process - my_ti_process]
num1="value1"
stringX="value2"
stringY="value3"

[Connect – Production]
adminhost=
server=MyTM1server
user="MyTM1AdminServer"
pwdfile="c:\tm1_admin_area\passwords\tm1_password.txt"
AdminSvrSSLCertAuthority=.\ssl\applixca.pem
AdminSvrSSLCertID=tm1adminserver
AdminSvrSSLCertRevList=
CAMNamespace=LOCAL_NTLM

Processing logic

Configuration parameters and command line parameters are processed in the following fashion:

  1. If specified by -i, the configuration file is opened and any connect option specified in [TM1RunTI] is processed first.
  2. Any other parameters in [TM1RunTI] are then processed and may override those specified by the connect parameter.
  3. The command line parameter -connect is processed next, if present. It loads values from the associated [Connect - <connection_name>] section of the config file, overriding any values loaded by the preceding steps.
  4. The remaining command line parameters are processed.

For example, if you save the configuration file in the preceding example with the name tm1tools.config and then you execute the following:

tm1runti –i ".\tm1tools.config" –passwordkeyfile c:\keystore\prodkey.dat –connect prodsystem

Since the -i parameter was provided, the tool would do the following:

  1. Open the config file and load the [tm1runti] section
  2. Upon seeing the connect parameter in [tm1runti], load the parameter values from [Connect - testsystem]
  3. Process the command line parameters:
    1. Upon seeing the connect parameter, load the parameters from [Connect – prodsystem]
    2. Replace the value for passwordkeyfile.

Configuration filename and location

The command line parameter -i can be used to specify a configuration filename. This is particularly useful if several Cognos® TM1® servers are supported in the environment, as a different configuration file can be used for each server and like-named processes in different servers can be defined with different parameters.

Parent topic: Using TM1RunTI