TIBCO Adapter for Kenan/BP v5.2.0 supports Kenan/BP 12.0
book
Article ID: KB0086772
calendar_today
Updated On:
Products
Versions
TIBCO Adapter for Kenan/BP
-
Not Applicable
-
Description
Description: The TIBCO Adapter for Kenan/BP v5.2.0 is now supported with Kenan/BP 12.0 on the following platforms:
- HP-UX 11i on PA-RISC
The following changes need to be made in the adapter properties file (default location: $TIBCO_HOME/adapter/adkenan/5.2/bin/adkenan.tra) for the adapter to work with Kenan/BP 12.0
- The %BSDSITE% variable should reflect the new installation path of the API-TS client.
Old value: tibco.env.BSDSITE %ARBORDIR%/bsdm_site New Value: tibco.env.BSDSITE %ARBORDIR%/site_specific/apits/javaclient
- The custom class path entry (tibco.env.CUSTOM_CP_EXT) has to be changed to reflect the following values: %BSDSITE% %BSDSITE%/lib. $ORACLE_HOME/lib %ARBORDIR%/site_specific/lib %ARBORDIR%/bsdm_site/lib
Old Value: tibco.env.CUSTOM_CP_EXT %ARBORDIR%:%TUXDIR%/lib:%ARBORDIR%/bsdm_site:%ARBORDIR%/bsdm_site/lib:%TIB_ADKENAN_HOME%/examples/KenanCustomCallOut/CustomClasses New Value: tibco.env.CUSTOM_CP_EXT tibco.env.CUSTOM_CP_EXT /u01/app/oracle/product/10.2.0/db_1/lib:%ARBORDIR%/site_specific/lib:%ARBORDIR%/bsdm_site/lib:%TUXDIR%/lib:%BSDSITE%:%BSDSITE%/lib:%TIB_ADKENAN_HOME%/examples/KenanCustomCallOut/CustomClasses
(The Oracle path provided here is specific to a particular installation. You would need to replace /u01/app/oracle/product/10.2.0/db_1 by the location of your Oracle Home).
- The CUSTOM_LIB_PATH should include the java folder under bsdm_site.
For example: tibco.env.CUSTOM_LIB_PATH %BSDSITE%/java
Known Issues ============ For Kenan/BP 12.0, the adapter palette stalls when using the UDT tool to configuring the Ordering or WorkOrder UDT objects. This is caused by recursive references in the object schemas. The palette stalls for 1 minute and then you can continue to perform other operation. This does not affect other functionality of the adapter configuration.
Impact ====== Performance Degradation
Cause ====== This stall is caused by recursive references in the object schemas.
Workaround: =========== Configure these UDT objects directly using the CustomerUdtRequest.xsd, and add the following "‘Ref’ element to the request.xsd manually: