Recovering from Network Outages and TIDManager Server Downtimes

When an adapter configuration is configured in the remote TIDManagement mode, the TIDManager server must be running to perform TIDManagement operations. The adapter configuration cannot process any transaction if it is unable to communicate with the TIDManager server. Thus availability of the TIDManager server is critical for remote TIDManagement mode.

  • Outbound TIDManagement

    In case of the remote TIDManagement for outbound configurations, if the TIDManager server is not running or it cannot be reached because of the network outages, an error occurs upon receiving a transaction from the SAP system. The error message is

    2014 Sep 10 07:37:59:423 GMT -0700 R3AdapterConfiguration Error [Adapter] AER3-000102 TID operation timed out 6A785778253F540FC9030CDA.

    The transaction itself is not lost and it is maintained in the tRFC queue of the SAP system. The SAP system periodically tries to push out the transaction and clear the queue. If communication with the TIDManager server is restored, normal processing continues.

    Note:

    Transactions maintained in the tRFC queue are retried as long as they are configured for the corresponding RFC destination and the transaction has not been retried manually. If the transaction is retried manually and there is still an issue with connecting to the outbound adapter configuration, the transaction cannot be retried by the SAP system.

  • Inbound TIDManagement

    In case of the remote TID Management for inbound configurations, if the TIDManager server is not running or it cannot be reached because of the network outages, an error occurs upon receiving an IDoc from the TIBCO environment. The error message is

    2014 Sep 10 07:28:27:057 GMT -0700 R3AdapterConfiguration Error [Adapter] AER3-000493 Remote TIDManager server unreachable.

    The AER3-000493 error is also published as a Hawk Notification that can be subscribed to from TIBCO Hawk.

    The value specified in the TIDManager Client Retry Count field in the Advanced tab of the Adapter for SAP Configuration editor determines the number of times the adapter configuration tries to invoke the TID operation on the TIDManager server before concluding that the TIDManager server is indeed unreachable.

    Once the TIDManager server is found to be unreachable, the Subscriber adapter cannot proceed with posting the IDoc. The IDoc cannot be confirmed to the sending application in the TIBCO environment as it results in message losses.

    Hence, upon detection of this situation, the adapter configuration suspends all its Subscription Service services, does not confirm received IDocs to the TIBCO environment, and goes into a silent retry mode to try and reconnect to the TIDManager server. This is achieved by pinging the TIDManager server periodically. The adapter continues to remain in this suspended state till it establishes communication with the TIDManager server again.

    The value specified in the TIDManager Client Retry Interval field determines the time interval in milliseconds between any two ping attempts to the TIDManager server.

Contents
Search Results