Technote

(FAQ)

WebSphere Commerce 6.0 APAR or fix pack cannot be applied at the instance level due to an error related to DataSourceFor10CMPBeans or DataSourceFor10EJBModules.

After successfully applying an APAR or fix pack to the product installation directory, you receive errors similar to one of the following errors while applying an APAR or fix pack to your instance: 1) deployWCEar: [wsadmin] profileName=demo registry=D:\apps\IBM\WEBSPH~1\APPSER~1\properties\profileRegistry.xml [wsadmin] profileHome=D:\apps\IBM\WebSphere\AppServer\profiles\demo [wsadmin] WASX7209I: Connected to process "server1" on node WC_demo_node using SOAP connector; The type of process is: UnManagedProcess [wsadmin] Not output parameters [wsadmin] Deploying WC_hive to WAS from C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/wcupdate/WC_demo.ear [wsadmin] attrs=-operation update -contents C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/wcupdate/WC_demo.ear -usedefaultbindings -nodeployejb [wsadmin] WASX7017E: Exception received while running file "D:\apps\IBM\WebSphere\CommerceServer60/config/deployment/scripts/deployEar.jacl"; exception information: com.ibm.websphere.management.exception.AdminException [wsadmin] javax.management.MBeanException [wsadmin] com.ibm.websphere.management.exception.AdminException [wsadmin] com.ibm.websphere.management.application.client.AppDeploymentException: AppDeploymentException: [ADMA0092E: An unexpected exception occurred while preparing task DataSourceFor10CMPBeans. Check the server machine First Failure Data Capture tool (FFDC) for more information.] [wsadmin] java.lang.NullPointerException [wsadmin] java.lang.NullPointerException: java.lang.NullPointerException BUILD FAILED file: D:/apps/IBM/WEBSPH~1/COMMER~1/config/DEPLOY~1/xml/DEPLOY~1.XML:199: Java returned: 105 2) WASX7327I: Contents of was.policy file: grant codeBase "${application}" { permission java.security.AllPermission; }; WASX7017E: Exception received while running file "/QIBM/ProdData/CommerceServer60/config/deployment/scripts/deployEar.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "DataSourceFor10EJBModules ADMA0004E: A Validation error occurred in task Specifying the default data source for EJB 1.x modules. The JNDI name is not specified for module WebSphereCommerceServerExtensionsData with URI WebSphereCommerceServerExtensionsData.jar,META-INF/ejb-jar.xml. The data source must be specified for each container-managed persistence (CMP) bean belonging to this module. "

Cause

The deployment of EJB modules was done incorrectly (for example, a missed step) in the past. Answer

Redeploy your custom assets by following the documentation included in the information center. In particular this problem is caused by incorrect deployment of customized EJB modules. You must ensure your EJB modules are properly deployed. It is also very important that other assets are deployed correctly. In general, if you do not follow the correct deployment procedures, your customizations may be removed when installing APARs or fix packs.. Step #1 Remove the customized modules from the WebSphere Commerce J2EE application. You can find examples on how to remove a module here http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/com.ibm.commerce.developer.doc/tasks/tdpdeploying_j2ee_assets_entire.htm Step #2 Properly package and deploy your custom assets Package custom J2EE assets http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/com.ibm.commerce.developer.doc/tasks/tdppackaging_custom_ear.htm Package your module without EJB backend conversion Note that Step #2 here is very important! http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/com.ibm.commerce.developer.doc/tasks/tdeejb_jar_wo_conversion.htm To deploy the entire EJB Module: Deploying J2EE assets for an entire module http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/com.ibm.commerce.developer.doc/tasks/tdpdeploying_j2ee_assets_entire.htm Step #3 After successfully deploying your EJB modules, you should now be able to install the APAR(s) or fix pack on your instance.

 

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21271503