Skip to Content
0
Former Member
Feb 18, 2009 at 09:46 AM

Deployment problem for MDM related projects

23 Views

Hello All,

I have a web dynpro project and a EAR project. These both projects make access to MDM servers. I have a code to connect to this MDM servers in both DC projects. But when a deploy the web dynpro project from NWDS, i get the error. An extract of error from log file:

-


.............

...........

Result

=> deployed with warning : file:/C:/DOCUME1/kukn/LOCALS1/Temp/1/temp5930140028875642697chevrondcwd_eph_config.ear

Finished with warnings: development component 'dc/wd_eph_config'/'/...:

Caught exception during application startup from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Error occurred while starting application ../dc/wd_eph_config and wait. Reason: Clusterwide exception: server ID 6540250:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application "../dcwd_eph_config'' for startup. Reason=Clusterwide exception: Failed to start dependent library ''com.sap.mdm.tech.mdm4j'' of application ''../dcwd_eph_config''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine?

at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1421)

at .........

-


This happens when i deploy this project on local WAS. I have NW04 SP17. However this same project is working fine on dev/staging/prod servers before i started modiying.

so my question is:

1. If i checkin the code, will it work perfectly in development server? There are no build errors. So should the deployment happen on development server ?

2. If i want to test it locally, do i need something more on my local WAS ?

any thoughts?

thanks in advance,

kunal kotak