How to configure TIDManager fault tolerance for TIBCO ActiveMatrix (R) Adapter for SAP?
Article ID: KB0071574
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
SAP Adapter TIDManager can be configured in fault tolerance mode using EMS “exclusive” queue. Additionally need to ensure all TIDManager instances use only one TID file.
Environment:
===========
version 6.0.0
Resolution
NOTE:
The information mentioned here is not compatible with the ThreadPool property for the the SAP Adapter 7.x Tidmanager. If using SAP Adapter 7.x Tidmanager. Please use the SDK Fault Tolerance instead. For the setup detail, please refer to the TIBCO ActiveMatrix® Adapter for SAP 7.3.1 document:
https://docs.tibco.com/pub/adr3/7.3.1/doc/html/TIB_adr3_configuration_deployment/advanced_topics.16.07.htm
Resolution:
The following shows the steps for configuring the fault tolerance mode for outbound TIDManager and Adapter:
1). Create exclusive queue in EMS.
a). Create “SAP.TIDMANAGER” queues in the EMS server with tibemsadmin utility.
b). Set the “exclusive” property for the queue:
addprop queue SAP.TIDMANAGER exclusive
2). Create TIDManager Configuration which uses the newly created JMS queue as transport:
a). Create the TIDManager Configuration in the project.
b). In the project panel, select R3TIDManagerCOnfiguration -> Advanced -> Sessions folder
c). In the folder, add a new GenericSession, select Session Type as JMS, click Apply Button, rename it as TIDManagerJMSSession, use JMS Queue as transport, save the project.
d). Select the TIDManagerJMSSession folder, add a Server, specify the Destination as SAP.TIDMANAGER
e). Select R3TIDManagerCOnfiguration, in General tab, use the newly created Server for field “TID Manager Server”.
f). In the General tab of the TID Manager Configuration, assign a service level global variable for the “TID Filename” field. (We need to modify the file name variable when we deploy the TID Manager on different machines).
3). Configure SAP Adapter to use the remote TIDManager Instance:
a). Create the SAP Adapter Configuration.
b). In the Adapter Services tab of adapter instance, use remote TID Manager
c). In the project panel, select R3AdapterConfiguration -> Advanced -> Sessions folder.
d). In the folder, add a new GenericSession, select Session Type as JMS, click Apply Button, rename it as TIDManagerJMSSession, use JMS Queue as transport, save the project.
e). Select the TIDManagerJMSSession folder, add a Client, specify the Destination as SAP.TIDMANAGER, specify the Invocation Timeout(ms) as 5000 (it cannot be 0 because of a known issue).
f). Go back to Adapter Services tab of Adapter Instance, select the newly added JMS client for field “TID Manager Client”
4). Configure the shared file area if we want to deploy the TIDManager instances on different machines. For example a NFS shared storage for Linux machines.
5). Deploy the TID Manager on the machines. We must modify the TID filename variable for each instance of TID Manager so that they reference to same file in the shared file location. (Please make sure all the instances have the permission to write the TID file on the shared storage).
6). Start all the instances of TID Manager. They will now run in FT mode.
It is a similar process to configure fault tolerance for inbound TIDManager and Adapter. Please note to use a different queue destination, for example: SAP.TIDMANAGER.INBOUND.
The information mentioned here is not compatible with the ThreadPool property for the the SAP Adapter 7.x Tidmanager. If using SAP Adapter 7.x Tidmanager. Please use the SDK Fault Tolerance instead. For the setup detail, please refer to the TIBCO ActiveMatrix® Adapter for SAP 7.3.1 document:
https://docs.tibco.com/pub/adr3/7.3.1/doc/html/TIB_adr3_configuration_deployment/advanced_topics.16.07.htm
Resolution:
The following shows the steps for configuring the fault tolerance mode for outbound TIDManager and Adapter:
1). Create exclusive queue in EMS.
a). Create “SAP.TIDMANAGER” queues in the EMS server with tibemsadmin utility.
b). Set the “exclusive” property for the queue:
addprop queue SAP.TIDMANAGER exclusive
2). Create TIDManager Configuration which uses the newly created JMS queue as transport:
a). Create the TIDManager Configuration in the project.
b). In the project panel, select R3TIDManagerCOnfiguration -> Advanced -> Sessions folder
c). In the folder, add a new GenericSession, select Session Type as JMS, click Apply Button, rename it as TIDManagerJMSSession, use JMS Queue as transport, save the project.
d). Select the TIDManagerJMSSession folder, add a Server, specify the Destination as SAP.TIDMANAGER
e). Select R3TIDManagerCOnfiguration, in General tab, use the newly created Server for field “TID Manager Server”.
f). In the General tab of the TID Manager Configuration, assign a service level global variable for the “TID Filename” field. (We need to modify the file name variable when we deploy the TID Manager on different machines).
3). Configure SAP Adapter to use the remote TIDManager Instance:
a). Create the SAP Adapter Configuration.
b). In the Adapter Services tab of adapter instance, use remote TID Manager
c). In the project panel, select R3AdapterConfiguration -> Advanced -> Sessions folder.
d). In the folder, add a new GenericSession, select Session Type as JMS, click Apply Button, rename it as TIDManagerJMSSession, use JMS Queue as transport, save the project.
e). Select the TIDManagerJMSSession folder, add a Client, specify the Destination as SAP.TIDMANAGER, specify the Invocation Timeout(ms) as 5000 (it cannot be 0 because of a known issue).
f). Go back to Adapter Services tab of Adapter Instance, select the newly added JMS client for field “TID Manager Client”
4). Configure the shared file area if we want to deploy the TIDManager instances on different machines. For example a NFS shared storage for Linux machines.
5). Deploy the TID Manager on the machines. We must modify the TID filename variable for each instance of TID Manager so that they reference to same file in the shared file location. (Please make sure all the instances have the permission to write the TID file on the shared storage).
6). Start all the instances of TID Manager. They will now run in FT mode.
It is a similar process to configure fault tolerance for inbound TIDManager and Adapter. Please note to use a different queue destination, for example: SAP.TIDMANAGER.INBOUND.
Issue/Introduction
How to configure TIDManager fault tolerance for TIBCO ActiveMatrix (R) Adapter for SAP?
Feedback
Yes
No
Powered by
