Running the TCH connector

Monitoring

Any connector traffic can be captured and viewed by using IBM® App Connect Enterprise MessageCapture configurable service. This feature is not mandatory for running the connector but allows better problem determination, especially in a test environment. All monitoring definitions are integrated in the connector flow for creating the appropriate information when this service is defined. For more information about how to configure this service, see the IBM App Connect Enterprise documentation.

The recorded data about all messages that are exchanged with TCH RTPS can be viewed through the IBM App Connect Enterprise web console by selecting the DataCapture view service. A filter for the data to be stored can set by using the configuration value TCo_MonitoringLevel.

Logging

The connector logs all important situations for reviewing the way the connectors work. It includes failure situations or important information about the system and connection availabilities, signed on state, and quiescing mode (when enabled). When a user sends a command to the AdminCmd_Q queue, it is also recorded with its corresponding user ID. There is a configuration option for including system notification messages in the connector log.

Tracing

The connector provides fully configured IBM App Connect Enterprise trace nodes. When you have tracing turned on for all or dedicated connector instances, they write their particular activities to the configured trace file. Turn tracing off in production or for performance tests.