Support Article
Manifest file not working on J2EE 6.0 specifications
SA-8222
Summary
ChordiantEJB Project - Manifest file not working on J2EE 6.0 specifications during FS6.9 migration.
During the EJB-Upgrade process to EJB specs 3.1 of ChordiantEJB-Project we have a problem within manifest file: ibm-ejb-jar-ext.xml.
<session name="EJBGatewayServiceBMT">
<start-at-app-start value="true"></start-at-app-start>
<bean-cache activation-policy="ONCE"></bean-cache>
<resource-ref name="chordiantNoXAds_jxw" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="DEFAULT"></resource-ref>
<resource-ref name="chordiantNoXAds_qrst" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="DEFAULT"></resource-ref>
<resource-ref name="chordiantNoXAds_userprofile" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="DEFAULT"></resource-ref>
<resource-ref name="chordiantNoXAds_jxb" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="DEFAULT"></resource-ref>
<resource-ref name="chordiantNoXAds_jxcore" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="DEFAULT"></resource-ref>
<local-transaction boundary="BEAN_METHOD" resolver="APPLICATION" unresolved-action="COMMIT"></local-transaction>
</session>
Development Environment: RAD v. 8.5
Within the "bean-cache" Tag, there is a new value "timeout" expected. How comes that this tag didn't get upgraded properly? Do you have a suggestion value for this tag ?
Error Messages
Not Applicable
Steps to Reproduce
Migrating from:
CFS v. 6.5
Development: RAD 7
Production: WAS 7 / DB2 v. 9.5 FP 10 / LDAP, IE 9 FP 9.0.34 / JDK-JRE 1.7.0_65
Migrating to:
CFS v. 6.9
Development: RAD v. 8.5 (maybe RAD v. 9.1 if CFS will be approved for the RAD 9.1 platform.)
Production: WAS 8.5 / DB2 v. 10 / LDAP, IE 11 / JDK-JRE 1.8
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment. On comparing the provided files with the OOTB, below files showed differences:
- Manifest.mf
- ibm-ejb-jar-ext.xml
Resolution
The XML-Schema did not validate the Manifest-XML. The order of the below tag was changed.
Prepend <start-at-app-start value="true"/> to "resource-ref".
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.