Unable to deploy Webservice through NWDI

Question

I have created a DC for Webservice and after activate the DC
able to view the Webservice at Visual Administration>server>services-->deploy -->application , and the status of the webservcie was started but the Webservice does not exist in WebServiceNavigator ((http://<hostname>:<portno>/index.html)
and click on WebserviceNavigator).
Please find the Default Trace log
java.rmi.RemoteException: Error in getting status of application WEB SERVICE PORTS:
/AdminPartySrvc/AdminPartySrvc
- webservices : Application WEB SERVICE PORTS:
/AdminPartySrvc~AdminPartySrvc
- webservices is not deployed on cluster element Server 0 0_87195 and it is not possible to get its status.
     at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1387)
     at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.getApplicationStatus(DeployRuntimeControlImpl.java:409)
     at sun.reflect.GeneratedMethodAccessor502.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Answer 1

Friends,
I looked at the javadocs for axis and came to know the following points
bq. quote: \\ ----- \\ Gets the axis configuration object by loading the repository. The order of initialization is according the the following precedence: \\ If the parameter axis2.repository.path is present, this folder is used as the location to the repository. \\ Otherwise, if the parameter axis2.repository.url is present, the URL is used as the location to the repository. \\ Otherwise, when both of the above init parameters are not present, the web applications WEB-INF folder is used as the folder for the repository -----
When I have deployed the application in weblogic 9.2 the directory structure is as follows
bq. code: \\ ----- \\ {noformat}domain-name \\ |- servers \\ |-Trac \\ |- data \\ |- logs \\ |- security \\ |- stage \\ |- tmp \\ |- .internal \\ |- WLinternal \\ |- WLuser \\ |- Trac \\ |- ptntnw \\ |- public \\ |- war \\ |- axis2-web \\ |- META-INF \\ |- WEB-INF \\ |- classes \\ |- conf \\ |- modules \\ |- services{noformat} \\ -----
conf folder has axis2.xml and services folder has all the services I had deployed. Now if I mention absolute path in web.xml for axis2.xml.path and absolute path for axis2.repository.path then everything works fine.. I am able to see all the webservices I have deployed when I hit the above url.
Can anyone tell me how can I specify the relative path? If I dont specify any init param tag in web.xml, still it doesnt work.
Can anyone please help me ?
Thanks
Rohit.
Edited by: Rohit_India on Dec 11, 2008 10:02 PM