Products | Versions |
---|---|
TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | 7.x |
Issue : Remote TIDManager getting Timed out.
Error String
2017 Apr 25 20:48:18:309 GMT +0530 R3AdapterInstance01 Warn [Adapter] AER3-970276 Server Exception:
Gateway Host: 10.108.80.143
Gateway Service: sapgw00
Program ID: tibcosupport02
Error Message: check TID fault: Remote TIDManager timeout
Cause: The remote TIDManager timeout states that there is no response returned by the Remote TID manager to the SAP adapter. This error generally occurs whenever there is configuration issues in the project. Below are the following two scenarios which will make the adapter throw the above error.
1. Remote TIDManager is not configured : If you have selected the TID Manager to be remote instead of local under the Adapter Services tab for the SAP Adapter instance configuration, then make sure that you have done the configuration for the remote TID Manager too. Failing to do so will cause the above exception.
Refer to the following images for reference.
2. Different transport selected for TID Manager client and server : The above exception can also happen if you have selected different transports for both the TID Manager client and server. Under the Adapter Services tab in the SAP Adapter Instance configuration, if the TID Manager client is using a transport as JMS, then while configuring the TID Manager, make sure to select JMS as a transport for the TID Manager server. Likewise, if you have configured the TID Manager client to use RV as a transport then when configuring the TID Manager, make sure to select RV as a transport for the TID Manager server. If the TID Manager client and server use different transport mechanisms then the TID Manager will get timed out and will throw the exception.
Refer to the following images for reference.
Note that all of the above images are provided in the file image.zip attached to this KB.
1). If using a Remote TID Manager then configure the TID Manager properly.
2). Make sure that the TID Manager client and server uses the same transport, i.e., either RV client/RV server or JMS client/JMS server.