Tibco ESI Timeout

ptc-4482159 · ‎Aug 27, 2009

We are currently testing/developingour PDMLink - SAP R/3 solutionusing PTC's ESI with Tibco.

After trying to edit the OOTB Tibco process (in Designer)by replacing the CSAP_MAT_BOM_MAINTAIN with our own homegrown ZESI_MAT_BOM_MAINTAIN in the BOM change section, our invocation of ZESI_MAT_BOM_MAINTAIN is timing out with the following error information:

<activityerrors>
<ns0:timeoutexception xmlns:ns0="<a" href="http://schemas.tibco.com/bw/plugins/ae/5.0/aeExceptions">http://schemas.tibco.com/bw/plugins/ae/5.0/aeExceptions">
<msg>Timeout waiting for reply.</msg>
<msgcode>BW-AE-100014</msgcode>
<errormessage>Timeout waiting for the reply</errormessage>
</ns0:timeoutexception>
</activityerrors>

All other calls from Tibco to SAP are working correctly in our project. Does anyone else here use the ESI solution from PTC? Does anyone have experience in Tibco that can enlighten me to why this timeout is occuring?

Thanks.

my185027 · ‎Aug 27, 2009

Garrett,

Attached find TAN on this issue which should resolve this issue.

Regards,

Rehan

Solution Details - TAN 140604
Solution ActionsRefresh DataSubscribe to this SolutionSolution140604TypeTANCreated Date10-Mar-2008Last Updated13-May-2008

TitleTIBCO Designer Times Out When Running Adapters From DesignerDetailsDescriptionTIBCO adapters are not fully supported in testing mode and may time out if you attempt to do any customizations using TIBCO Designer. If you run the adapters from designer, you may not be able to debug / run the business logic process from designer. See Additional Information.Additional InformationUse the following workaround to run the adapters from TIBCO Administrator to customize and debug the business logic processes from the designer.

Pre-requisites:

- You have used MICU to deploy the SAP_ESI_Solution application successfully.
- Adapter services are up and running from the TIBCO administrator.
- Process Archive (Process Engine) is stopped from administrator.

1. Find the correct values for the Domain and Deployment properties, using the Administrator's deployed SAP_ESI_Solution Application.

- The Deployment Name property contains DomainName-DeploymentName format. The Deployment Name can be found at:
Application Management->SAP_ESI_Solution -> Configuration-> Edit Application Configuration ->General ->Application Parameter

Note: The file designer.tra needs to be updated with <tbico_home>>/esi/bin; <tbico_home>>/esi/lib value for the following properties.
tibco.env.CUSTOM_PATH,
tibco.env.CUSTOM_CP_EXT,
tibco.env.CUSTOM_PALETTE_PATH

2. In the TIBCO Designer convert <<tibco_home>>/esi/dat/ESI_SAP_TIB_5_4_DAT_8_0_M040_16.dat file to multi file project (refer 8.0M040 ESI Customization Guide for SAP)

3. In the TIBCO Designer close the project.

4. Using a Text Editor, open the ConvertedProjectfolder/defaultVars/defaultVars.substvar file

5. In the defaultVars.substvar file Update the following Global Variable values, using the domain and deployment values of the deployed ‘SAP_ESI_Solution‘ application.

<globalvariable>
<name>Deployment</name>
<value><<needs to=" be=" modified=" for=" e.g.=" sap=">> </value>
<deploymentsettable>true</deploymentsettable>
<servicesettable>false</servicesettable>
<type>String</type>
<modtime>1128355698459</modtime>
</globalvariable>
<globalvariable>
<name>Domain</name>
<value><<needs to=" be=" modified=" for=" e.g.=" i3503=">></value>
<deploymentsettable>true</deploymentsettable>
<servicesettable>false</servicesettable>
<type>String</type>
<modtime>1128355698303</modtime>
</globalvariable>

6. Save and close the file.

7. Open converted project in the designer.

8. Configure all Global Variables (Domain and Deployment Global Variables are read only from designer).

9. Run the BW processes in test mode. You do not need to start the adapter using show Adapter tester from designer.