Java papi client 57 UserTransaction lookup fails

Question

Guys,
I am trying to write PAPI client which is to run from Tomcat and connecting to ALBPM 5.7 Enterprise which is on Weblogic 92.
I am able to do all operations how ever do see exceptions when PAPI tries to connect to News Topic.
Please let me know if some one has seen this problem in ALBPM5.7 and how it was resolved. I think fix may be in directory.properties by adding/removing some properties but dont know what.
Following is the error message
An error occurred when subscribing to the JMS Topic engine. Reason:'While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
Caused by: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
When I checked in directory database, I see following XML in FUEGO_CONFIG table
<?xml version="1.0" encoding="UTF-8"?>
<?fuego version="5.7 GA SP3" application="albpmenteprisej2ee"?>
<set>
     <configuration name="myengine_ENGINE_DB_FUEGOLABS_ARG" type="SQL" subtype="ORACLE">
          <property name="jdbc.pool.idle_timeout" value="5"/>
          <property name="oracle.driver_type" value="thin"/>
          <property name="oracle.dateEqualsTimestamp" value="false"/>
          <property name="jdbc.schema" value="myengine"/>
          <property name="jdbc.host" value="localhost"/>
          <property name="user" value="myengine"/>
          <property name="jdbc.port" value="1521"/>
          <property name="jdbc.pool.min" value="0"/>
          <property name="jdbc.pool.maxopencursors" value="50"/>
          <property name="oracle.sid" value="xe"/>
          <property name="password" value="&lt;encrypted&gt;gGocbn15UL8="/>
          <property name="jdbc.xa" value="false"/>
          <property name="jdbc.pool.max" value="10"/>
     </configuration>
     <configuration name="*myengine_J2EE_LOCAL_FUEGOLABS_ARG*" type="*J2EE*" subtype="*LOCAL_J2EE*">
          <property name="*javax.user.UserTransaction*" value="*java:comp/UserTransaction*"/>
     </configuration>
     <configuration name="myengine_J2EE_RUNTIME_FUEGOLABS_ARG" type="SQL" subtype="REMOTE_JDBC">
          <property name="lookupName" value="XAmyengineDS"/>
          <property name="jdbc.remote.type" value="ORACLE"/>
          <property name="j2ee.provider" value="myengine_J2EE_LOCAL_FUEGOLABS_ARG"/>
     </configuration>
     <configuration name="myengine_J2EE_FDI_FUEGOLABS_ARG" type="SQL" subtype="REMOTE_JDBC">
          <property name="lookupName" value="XAFDIDS"/>
          <property name="jdbc.remote.type" value="ORACLE"/>
          <property name="j2ee.provider" value="myengine_J2EE_LOCAL_FUEGOLABS_ARG"/>
     </configuration>
</set>
Following is my directory.properties (I have tweaked a bit to make it work)
# Directory configuration
# The following properties define the configuration for a directory provider.
# Do not modify the prefix of the properties. Always leave "directory.default."
directory.default.url=oracle://localhost:1521/schema=BEA_FDI,sid=XE
#directory.default.provider=oracle
#directory.default.connector-subtype=ORACLE
#directory.default.directory-res-ref-name=myengine_J2EE_FDI_FUEGOLABS_ARG
# preset properties.
directory.default.preset.datawarehouse.participant=administrator
directory.default.preset.engine.participant=administrator
directory.default.preset.portal-anonymous.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YqKhr3hkgQJeZK2sN9b9waFaN6N8S/fMtkcMRWpbMrUVCeXN8zvx7OLaGtCTBQ==
directory.default.preset.xobjects.participant=administrator
directory.default.preset.datawarehouse.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9Yp/TapxzhLBvmq3JAXqZ/pOgfmVZxXpleLmdse9pFPjhFG4SH4/hmKPhJg==
directory.default.preset.xobjects.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YrahnQoZYB8e7NkVzsFfeKe9qrv/oXpltEQYTDSxMrUVCeXN8zs=
directory.default.preset.engine.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YmixG3O3OYx0FW4CpqZf/pP8fnS8vEpQ6fpD8kG9FNGrZQhP
directory.default.preset.portal-anonymous.participant=administrator
# custom properties.
# fuego properties.
directory.default.jdbc-user=BEA_FDI
directory.default.jdbc-password=password
#directory.default.skip-auth=true
If you see I have commented following properties above which is basically referring to elements in XML which I have pasted above.
#directory.default.provider=oracle
#directory.default.connector-subtype=ORACLE
#directory.default.directory-res-ref-name=myengine_J2EE_FDI_FUEGOLABS_ARG
Similarly there is UserTransaction entry in FUEGO_CONFIG table xml as highlighted in bold.
Is there any fix/tweak in directory.properties which will resolve my problem?
Thanks in advance for helping.
Anil
Edited by: Anil Hemnani on 22-Apr-2010 23:30
Edited by: Anil Hemnani on 22-Apr-2010 23:30
Edited by: Anil Hemnani on 22-Apr-2010 23:31

Answer 1

Dear fellow forum members,
For future reference:
After a very very long time we received advise from SAP to perform actions we already suggested.....
We have ´hacked´ the keydb.xml file. We must say that SAP gave good detailed advise on which entries to change:
1#. Log on to ABAP and check what password was set for user "ADS_AGENT"
2#. Go to:
/tmp/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN/ADA/CENTRAL/CI/
1. Save a backup of "keydb.xml" first.
2. Find the following lines at the keydb.xml:
This solved the problem for our customer, so this question can be marked as answered by Casper (my colleague). We hope that SAP will launch a patch to solve this problem, as it has cost us a lot of time and we can imagine that other consultants are facing the same issues, as this seems to be a hashing mechanism that does not perform/work correctly.
Best regards,
Jan Laros