Logging categories

The logging categories provide a variety of debugging information for the Connection Manager. The Launcher uses them to determine which severity levels and components to debug.

For descriptions and examples of the logging categories, see Logging Category Descriptions .

IgnoreGPFs

Use this setting to ignore system exceptions during processing so that only the map fails as opposed to the system.


IgnoreGPFs={0|1}
Option
Description
0
Disables the option, which means the system will fail upon encountering an exception.
1
Enables the option so that exceptions are ignored on connection threads and therefore a map failure occurs instead of a system failure.

This is the default setting.

ShareConnectionThreads

The ShareConnectionThreads setting allows multiple connections on the same thread. There are three levels of sharing to specify the criteria used for sharing threads. Each value is described in the following table. This setting is disabled by default.


ShareConnectionThreads=n
Option
Description
0
Disables the sharing option, which means each connection gets its own thread.
1
Enables sharing for GTX only. Only connections with GTX will get combined to the same thread.

Idle

Use this setting to specify global default settings for all adapters or specify settings for individual adapters.

The Idle setting creates a background map thread with the purpose of periodically searching the connection pools, locating connections with idle time greater than the value specified by Idle, and then removing them. This allows connections to be disconnected even when no map is running.

The Connection Manager shuts down the idle thread gracefully when running under a Launcher or Command Server. In an API environment that invokes maps that use Java-based adapters (such as JMS, Java™ Class, and JALE), you might wait additional idle seconds after a shutdown request. This delay occurs only when the custom application does not explicitly shut down WebSphere® Transformation Extender by using the Java-based terminateAPI routine or the C-based mpiTermAPI routine.

  • To specify default settings for all adapters, use Idle=n
  • To specify settings for individual adapters, use Idlexxx=n
    Option
    Description
    0
    Disables the use of idle settings for adapters.
    n
    Number of seconds to allow a connection to be idle before automatically disconnecting.
    xxx
    Adapter type where xxx represents the command line alias for the adapter. Example values for typical adapters include:
    DB
    Database Adapters
    MQS
    IBM® WebSphere MQ (server) Adapters
    MQSC
    IBM WebSphere MQ (client) Adapters
    ALE
    ALE Adapters
    FTP
    FTP Adapters

    For example, IdleMQS=30 sets the connection idle limit for IBM WebSphere MQ adapters to 30 seconds.

    See the Resource Adapters documentation for more information.

Soft Limit (SLim)

Most servers place a limit on the number of clients that can be connected. WebSphere Transformation Extender generally shares a server with other clients, and therefore should not be able to use all available connections. The Resource Manager provides two limit parameters: SLim (soft limit) and HLim (hard limit). Either or both of these parameters can be used to specify a maximum number of connections. Existing connections are only removed when a new one is required.

The SLim setting is a soft (advisory) limit. This number can be exceeded at peak load, but SLim tries to limit the number of idle connections at all other times. Limits are only checked when opening a connection, so it is possible to have a greater number of idle connections.

The global SLim value is by default set to 4 and is used if any other limit for the number of connections is not set.

  • To specify global default settings for all adapters, use Slim=n
  • To specify settings for individual adapters, use SLimXXX=n
    Option
    Description
    n
    Number of idle connections. Default is 4.
    xxx
    Adapter type where xxx represents the command line alias for the adapter. Example values for typical adapters include:
    DB
    Database Adapters
    MQS
    IBM WebSphere MQ (server) Adapters
    MQSC
    IBM WebSphere MQ (client) Adapters
    ALE
    ALE Adapters
    FTP
    FTP Adapters

    For example, SLimMQS=30 sets the soft limit for IBM WebSphere MQ adapters to 30 idle connections.

    See the Resource Adapters Library for adapter documentation.

Hard Limit (HLim)

The HLim setting is a hard (mandatory) limit. This number will not be exceeded. Connections are placed in a pending state rather than exceed this number.

  • To specify global default settings for all adapters, use: Hlim=n
  • To specify settings for individual adapters, use: HLimXXX=n
    Option
    Description
    n
    Maximum number of connections. Default is 0 (unlimited).
    xxx
    Adapter type where xxx represents the command line alias for the adapter. Example values for typical adapters include:
    DB
    Database Adapters
    MQS
    IBM WebSphere MQ (server) Adapters
    MQSC
    IBM WebSphere MQ (client) Adapters
    ALE
    ALE Adapters
    FTP
    FTP Adapters

    For example, HLimMQS=30 sets the hard limit for IBM WebSphere MQ adapters to 30 connections.

Min

The Min setting specifies a minimum number of connections to keep. When a limit (SLim or HLim) is exceeded, idle connections will be removed until no more than this value remains (if possible).

  • To specify default settings for all adapters, use Min=n
  • To specify settings for individual adapters, use MinXXX=n
    Option
    Description
    n
    Minimum number of connections to keep. The default setting is 0, which means there is no limit set.
    xxx
    Adapter type where xxx represents the command line alias for the adapter. Example values for typical adapters include:
    DB
    Database Adapters
    MQS
    IBM WebSphere MQ (server) Adapters
    MQSC
    IBM WebSphere MQ (client) Adapters
    ALE
    ALE Adapters
    FTP
    FTP Adapters

Keep

Use this setting to specify the time, in seconds, an idle connection is expected to remain valid. Connections that idle longer than this are tested prior to being used. If the test fails or is not supported, the connection is not reused.

The Keep setting is an efficiency measure and represents some amount of time to assume that the connection is valid without a test. If the idle time of the connection (amount of time since it was last used) is less than the Keep value, then the Resource Manager does not attempt to verify connection validity.

Last used refers to the timestamp when the connection was last assigned to a map. Whether it was used successfully or not is not considered because it is assumed that an unsuccessful attempt is a temporary condition, not a permanent failure.

This setting should only be used for adapters that implement ValidateConnection.

Do not use the KEEP setting with the FTP adapter. When used with the FTP adapater, the KEEP setting causes unpredictable results.

  • To specify global default settings for all adapters, use: Keep=n
  • To specify settings for individual adapters, use: Keepxxx=n
    Option
    Description
    n
    Specify how many seconds an idle connection is expected to remain valid. Default is 0, which disables connection testing. A value of -1 will force a test every time, but this is not recommended.
    xxx
    Adapter type where xxx represents the command line alias for the adapter. Example values for typical adapters include:
    DB
    Database Adapters
    MQS
    IBM WebSphere MQ (server) Adapters
    MQSC
    IBM WebSphere MQ (client) Adapters
    ALE
    ALE Adapters
    FTP
    FTP Adapters

    For example, KeepMQS=30 sets the Keep period for IBM WebSphere MQ adapters to wait 30 seconds for idle connections.

    Note: As an example, if you are executing maps using an IBM WebSphere MQ (server) adapter at least once every 10 seconds, a setting of KeepMQS=10 results in the connection not being tested because they are used before they expire.

See the Resource Adapters Library for adapter documentation.

HSleep

The HSleep setting is the specified polling interval used to check resource availability. The value is the cycle time (in seconds) for checking connection availability. The default value is 2 and if specified should be as follows: 0<HSleep<HLimTimeout.

Note: No validation of this value is performed. Unexpected values for this setting can cause unpredictable results.

HSleep=n
Option
Description
n
Number of cycle time seconds for checking connection availability.

Default value is 2 seconds.

Note: The number of retries is the HLimTimeout value divided by the HSleep value.

HLimTimeout

The HLimTimeout setting specifies a maximum amount of time (in seconds) that a map waits for a new connection to become available before failing the map. If not specified, HLimTimeout defaults to infinite.


HLimTimeout=n
Option
Description
n
Number of seconds that a map waits for a new connection to become available before failing the map.

Default value is infinite.

PollWaitTimeMin

The PollWaitTimeMax and PollWaitTimeMin parameters enable you to configure a polling interval that is used by adapters to detect events. If the interval is not specified, the default value is used.

Note: If this value is too small, such as below 50 milliseconds, CPU usage can go up during the idle time when the Launcher is waiting for an event.

PollWaitTimeMin=n
Option
Description
n
Minimal polling interval in milliseconds.

Default setting is 2000.

PollWaitTimeMax

The PollWaitTimeMax and PollWaitTimeMin parameters enable you to configure a polling interval that is used by adapters to detect events. If the interval is not specified, the default value is used.


PollWaitTimeMax=n
Option
Description
n
Maximal polling interval in milliseconds.

Default setting is 10000.