Environments

The tree in the main screen shows all the server installations on your system.

Each ITP/Server installation has three sub trees: Services, Servers, and Environments which give you specific information about the installation and enable you to configure them.

In this section, the sub tree Environment is explained.

ITP/Server must know certain runtime connection configuration values in order to run ITP Models. These values are organized in environments. In which environment an ITP Model is run can be passed as a parameter to the commands ITPRun or ITPRunCrtRun, or set in the ITP/OnLine COM API or HTTP Front-end. If no environment is passed, the ITP Model is run in the default environment. The default environment can be set on the environments tab of the ITP/Server Administrator.

Environments must exist in ITP/Server before they can be passed. A fatal error will occur and the ITP process will be stopped when a non-existing environment is passed as a parameter.

Configuration levels

The ITP/Server Administrator offers four levels of connection configuration.

1. You can configure most settings globally on environments level, that is for all DIDs in all environments containing entries using a specific Connection type. Global settings can be configured on the Connection tabs on Environments level.
2. Settings can also be configured for one single environment. This level can be configured by selecting an environment.
3. Connections can be configured per DID within an environment. This level can be configured by selecting a DID in the appropriate environment.
4. Connections can be configured per DID Module within a DID within an environment. The level can be configured by selecting a DID Module in the DID on the appropriate environment.

In the ITP/Server Administrator each level is represented by its own icon:

	Global setting
	Setting on Environment level
	Setting on DID level
	Setting on DID module level

ITP/Server searches these levels in reverse order; DID Module setting, DID setting, Environment setting, and Global setting. ITP/Server uses the first value it encounters. If ITP/Server cannot find a value for a specific setting it will try to use a meaningful default. If this is not possible an error or warning is generated.

Combining Connection types in one DID

In one DID you can combine several Connection types. Each DID module uses its own Connection type. Consequently you can combine settings for multiple Connection types in the DID specific settings. In the ODBC Connection, Notes Connection, Oracle Connection, and the XML File Connection it is possible to specify DID Module specific settings. This means that you can have more than one connection to a database, data source or server per ITP Connection.

For the other connection types, DIDs are limited to one connection per Connection type. It is for example not possible to access multiple AS/400's in one DID.

Note

The ITP/Document Processors have to be restarted to carry through changes made to environments.