Activate or deactivate TCH 3.0 support
You can configure whether support for the TCH 3.0 specification is active in your environment.
Before you use TCH 3.0 in a production environment, you need to review the TCH 3.0 specification and documentation understand whether it supports your requirements. For more information, see TCH 3.0 support.
To use TCH 3.0, you must get the TCH 3.0 XML Schema Definitions (XSDs) from TCH and deploy them into the FTM for Immediate Payments IBM® App Connect Enterprise runtime. The new XSDs replace the current TCH XSDs that are being used. The TCH 3.0 XSDs that were tested are compatible with the prior TCH XSDs.
| Category | Key | Value |
|---|---|---|
| TCH | ACTIVATE_3.0 | The timestamp when the TCH 3.0 specification is to be activated. Specify the
timestamp in Coordinated Universal Time and in the following format YYYY-MM-DDTHH:MM:SSZ. For
example, 2023-09-23T12:35:18Z. |
By default, the value for the ACTIVATE_3.0 key is set to Null, which
means that TCH 3.0 is active. Or, you can set the value to a timestamp that is the
date and time that you want the TCH 3.0 specification to become active. If you do
not want to activate or use the TCH 3.0 specification, set the value to a timestamp
that is in the distant future. You can update this value at any time if Immediate Payments is
configured to poll for, and reload, configuration changes.
In either mode, if the correct TCH 3.0 XSD is deployed, FTM needs to accept and process any incoming message from TCH.
However, for outgoing messages, TCH 3.0 fields need to be suppressed if TCH 3.0 is not defined as active. FTM does not reject or fail outgoing messages due to validation in this context, and it ignores content that is not currently allowed.