Web Application Properties

The computer where the Transformation Manager is running. Can be specified as a network name or an IP.

Default value = localhost

The port on which the Transformation Manager is running on the remote machine. This is an integer between 1025 and 65535.

Default value = 7071 (the default Transformation Manager listening port)

The port on which the Scheduler Manager is listening.

Default value = 7073

The request port of FME Notifier.

Default value = 7072

The length of time in seconds in which an FME Server connection remains idle before expiring from the connection pool.

If a value of less than or equal to zero is specified, there is no connection pooling.

Default value = 300

This is the minimal amount of time that a client must wait before sending another request. If a request is sent before that interval, it will be ignored. The time is specified in milliseconds.

Default value = 1000

The file name that the log files will have in common. The log files will have that name with a number before the dot (such as green.log => green1825841623.log).

A subdirectory can be specified before the file name. The base file path is stored in the messageLogger resource bundle, which is a messageLogger.properties file on the hard drive (under Resources/). The LOG_FILE_NAME content is simply appended to that path.

The default response format. See Configuring Service Response Format.

The locale of the service. If no value, the default system locale is used. If specified, the specified locale is used.

The language, country and variant are separated by underscores. Language is always lower case, and country is always upper case.

Examples: "en", "de_DE", "_GB", "en_US_WIN", "de__POSIX", "fr__MAC"

An optional list of space-separated FME Server host names. Two and only two host names are supported. Each host named must be running an FME Server. If this service cannot connect to (or loses its connection to) its primary FME Server, it will attempt to connect to the first FME Server system named in the list. If connection failure is similarly encountered with this system, this service will then attempt to connect to the next system in the list.

After this, a subsequent connection failure will trigger a final attempt by this service to connect to the original, primary FME Server system again. If this also fails, this service returns an error message to the client.

To use FAILOVER_SERVER_NAMES below, uncomment the line and replace <namelist> with a space-separated list of two FME Server host names. Do not include the angle-brackets in the namelist. For example:

FAILOVER_SERVER_NAMES=red green