cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Copied DC does't Deploy!!

srinivaskumar
Participant
0 Likes
337

Hi..

We Have a requirement like we have to copy standard ESS Dcs like PDATA or FAMILIYDATA Dcs to new DCs in to a NEW SCs..

And we have manually copies all the WDcomponenets and models and all.. now the DC is error free and built successfully..

buit the problem is when I try to deploy through SDM/NWDI it's not deploying the given below is the ERROR trace..

Can you please suggest based on the error trace what need to done so as to make it deploy!!

*Deployment Description IN NWDS😘

Apr 23, 2008 6:48:12 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:

[001]Deployment aborted

Settings

SDM host : atldhpr

SDM port : 56718

URL to deploy : file:/C:/DOCUME1/dalsm5/LOCALS1/Temp/2/temp18280celanese.comessgbl~pdata.ear

Result

=> deployment aborted : file:/C:/DOCUME1/dalsm5/LOCALS1/Temp/2/temp18280celanese.comessgbl~pdata.ear

Aborted: development component 'ess/gbl/pdata'/'celanese.com'/'LOKAL'/'0.2008.04.23.06.46.45'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application celanese.com/essgblpdata.. Reason: Clusterwide exception: Failed to deploy application celanese.com/essgblpdata. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application celanese.com/essgblpdata. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Deployment exception : The deployment of at least one item aborted

ERROR TRACE from PCD:-

Here is the Error Trace

Failed to get list of defined JCO clients for deployable object celanese.com/essgblpdata.

[EXCEPTION]

com.sap.tc.webdynpro.services.sal.deployment.api.WDSharingAccessException: Failed to get list of defined JCO clients for deployable object 'celanese.com/essgblpdata'.

at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getUsedJCOClients(DeployableObject.java:119)

at com.sap.tc.webdynpro.tools.explorer.OverviewView.refreshSystemContent(OverviewView.java:548)

at com.sap.tc.webdynpro.tools.explorer.OverviewView.refreshTree(OverviewView.java:506)

at com.sap.tc.webdynpro.tools.explorer.OverviewView.wdDoInit(OverviewView.java:125)

at com.sap.tc.webdynpro.tools.explorer.wdp.InternalOverviewView.wdDoInit(InternalOverviewView.java:252)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)

at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)

at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

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)

Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Unexpected deployable object type: celanese.com/essgblpdata. No Web Dynpro application.

at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:182)

at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getJCOClients(WebDynproRuntimeServiceImpl.java:313)

at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getUsedJCOClients(DeployableObject.java:117)

... 50 more

Thanks.

Srinivas.

Accepted Solutions (0)

Answers (3)

Answers (3)

srinivaskumar
Participant
0 Likes

Hi..

The links are helpful to migrate/copy a DC.. in my case, I am done with copying now it is built successfully and not deploying..

Since ess/pdata being a self - service application,

1. I see some properties attached to the application do i need to alter the properties of the appliocation?

2. Or Do i need to copy the FPM view/FPM application in PCD also??

Can we run any self service DC like PDATA/W4 etc etc with out copying the FPM views/FPM application in the PCD or am i missing some config in PCD or in R/3 Backend ?

Thanks,

Srinivas M

srinivaskumar
Participant
0 Likes

Hi Pradeep Thanks for your reply..

1. JCO:

I am using standard JCO destinations only!! and they are claready in green color.

2. Reference Comps:-

I copies all the WDcomponents of us/ess/pdata to my own since they have been copied as seperate I'm also sure that they have been added to DTR.

3. I have added the used DC references same as standard PDATA Dc.

So u thin i need to also copy pdata/cfg file?? to my new SC..

Do u have any idea?

Thanks,

Srinivas M

PradeepBondla
Active Contributor
0 Likes

HI,

you will need the following files to be checked into DTR

--cfg

--def

--Model folder

--src

--.dcdef

--test

regards,

Pradeep

PradeepBondla
Active Contributor
0 Likes

I hope below post will help you in understanding more...

regards,

Pradeep

reward for helpful posts...

PradeepBondla
Active Contributor
0 Likes

hi,

Your error trace clearly says.....

Hint: Are all referenced components deployed and available on the engine? are you using any external components ?

did you check your JCo's are working fine??

regards,

Pradeep