cancel
Showing results for 
Search instead for 
Did you mean: 

Deployment Error

Former Member
0 Kudos

Hi guys,

I am new to module development which enhances an adapter capabilities. I am following the document "Step by step guide to develop a module for reading file name in a sender file adapter pdf". When I am deploying the EAR file from NWDS to J2EE Engine of XI server, I got the following deployment error.

***********************************************************************************************

[005]Additional log information about the deployment

<! LOGHEADER[START]/ >

<! HELP[Manual modification of the header may cause parsing problem!]/ >

<! LOGGINGVERSION[1.5.3.7162 - 630_SP]/ >

<! NAME[C:\usr\sap\ZXI\DVEBMGS00\SDM\program\log\sdmcl20070421175017.log]/ >

<! PATTERN[sdmcl20070421175017.log]/ >

<! FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/ >

<! ENCODING[Cp1252]/ >

<! LOGHEADER[END]/ >

May 21, 2007 11:20:17... Info: -


Starting deployment -


May 21, 2007 11:20:17... Info: Loading selected archives...

May 21, 2007 11:20:17... Info: Loading archive 'C:\usr\sap\ZXI\DVEBMGS00\SDM\program\temp\temp31784com.kk.FileModule.ear'

May 21, 2007 11:20:17... Info: Selected archives successfully loaded.

May 21, 2007 11:20:17... Info: Actions per selected component:

May 21, 2007 11:20:17... Info: Initial deployment: Selected development component 'com.kk.FileModule'/'sap.com'/'localhost'/'2007.05.21.22.45.49' will be deployed.

May 21, 2007 11:20:17... Info: Saved current Engine state.

May 21, 2007 11:20:17... Info: Error handling strategy: OnErrorStop

May 21, 2007 11:20:17... Info: Update strategy: UpdateAllVersions

May 21, 2007 11:20:17... Info: Starting: Initial deployment: Selected development component 'com.kk.FileModule'/'sap.com'/'localhost'/'2007.05.21.22.45.49' will be deployed.

May 21, 2007 11:20:17... Info: SDA to be deployed: C:\usr\sap\ZXI\DVEBMGS00\SDM\root\origin\sap.com\com.kk.FileModule\localhost\2007.05.21.22.45.49\temp31784com.kk.FileModule.ear

May 21, 2007 11:20:17... Info: Software type of SDA: J2EE

May 21, 2007 11:20:17... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

May 21, 2007 11:20:17... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

May 21, 2007 11:20:17... Error: Aborted: development component 'com.kk.FileModule'/'sap.com'/'localhost'/'2007.05.21.22.45.49':

Caught exception during access of archive "C:\usr\sap\ZXI\DVEBMGS00\SDM\root\origin\sap.com\com.kk.FileModule\localhost\2007.05.21.22.45.49\temp31784com.kk.FileModule.ear":

java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR C:\usr\sap\ZXI\DVEBMGS00\SDM\root\origin\sap.com\com.kk.FileModule\localhost\2007.05.21.22.45.49\temp31784com.kk.FileModule.ear to J2EE 1.3.

Exception is:

com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR C:\usr\sap\ZXI\DVEBMGS00\SDM\root\origin\sap.com\com.kk.FileModule\localhost\2007.05.21.22.45.49\temp31784com.kk.FileModule.ear to J2EE 1.3.

at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)

at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:443)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:295)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)

at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)

at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)

at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)

at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)

at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:128)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:127)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:96)

at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:57)

at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)

at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)

at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:81)

at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)

at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)

at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:280)

at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)

at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)

at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)

at java.lang.Thread.run(Thread.java:534)

Caused by: java.io.IOException: The following archives that are

described in the ear descriptor are not found in the ear:

SampleFileAdapterModule.jar,

Please check the ear content.

at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)

at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)

at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)

at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)

... 29 more

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)

May 21, 2007 11:20:17... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

May 21, 2007 11:20:17... Error: -


At least one of the Deployments failed -


***********************************************************************************************

please help me out, what exaclty is that error and how rectify that one.

Is there any other way to deploy my application into J2EE engine of XI server?

Advanced thanks,

Praveen Gujjeti

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member181985
Active Contributor
0 Kudos

Not answered still closing this thread.

bhavesh_kantilal
Active Contributor
0 Kudos

Praveen,

Reading the source filename inside your adapter module has been made very simple. The Article can be ignored and the note : 819761can be followed instead,

Regards

Bhavesh

former_member181985
Active Contributor
0 Kudos

Dear Bhavesh,

My intension is to built a sample module processor and understand the funtionality of it. Of course the sap note provided by you is useful.

As my problem is I am unable to deploy the EAR module into J2EE server of XI for the errors mentioned earlier.

Please help me in this regard.

Thanks,

gujjeti

Former Member
0 Kudos

Did you find the solution ?

Gabriel

Former Member
0 Kudos

Hi

The following should fix the problem

In the J2ee explorer view in NWDS,

Right click on the EAR project and select "Add module"

regards

krishna

Message was edited by:

Krishnamoorthy Ramakrishnan

prateek
Active Contributor
0 Kudos

Possible solutions,

1. Make sure you are able to login using administrator account.

2. If your administrator password is longer than 9 char

3. Make sure you are able to login to SDM in standalone mode.

4. Have a look here SAP Note 701654

5. http://listserv.sap.com/pipermail/linux.general/2005-May/004673.html

Regards,

Prateek

former_member91687
Active Contributor
0 Kudos

Hi,

>> <i>The following archives that are

described in the ear descriptor are not found in the ear:

SampleFileAdapterModule.jar,

Please check the ear content.</i>

The error mesage states that some contents of the EAR are missing, open the EAR file and check, else rebuild the EAR file and ensure that the necessary Jar files etc are available.

You can deploy the module either using the SDM or from NWDS by specifying the right port, host and with the necessary credentials.

Regards,

Chandra