Troubles with the creation of New Custom Adapter f...

Former Member · ‎04-02-2009

Hi guys !!!

I have some troubles with the creation of a new custom adapter for NW 7.1. I have followed some pdf and notes, like :

[Upgrade an SAP NetWeaver PI 7.0 Adapter to SAP NetWeaver PI 7.1|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0667f56-96c7-2b10-0e9a-c40fbd523f4d]

note : 1004000

I have all the materials to make the custom Adapter ( like file .sca with all .rar and .sda , like file sample_ra.rar with all the file .java, like all the libs for the projects ) and I have make it !!! But, when I try do deploy it, i recieve a warning that i don't understand, this is the warning :

##################################################################################

S U M M A R Y

~~~~~~~~~~~~~~~~~~~

Successfully deployed: 0

Deployed with warnings: 1

Failed deployments: 0

~~~~~~~~~~~~~~~~~~~

1. File:C:Users maienzaDesktopCreazione del SDAPI71_AF_myFirstCustomAdapter_ver_2.0.sda

Name:PI71_AF_myFirstCustomAdapter_ver_2.0

Vendor:sap.com

Location:SAP AG

Version:7.1007.20090310105326.0000

Deploy status:Warning

Version:NEW

Description:

1. Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :

[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0.

No one of the [EJBContainer] containers, which processed it, returned deployed component names.

The registered containers in this moment were [CTCContainer, com.sap.caf.um.metadata, com.sap.security.ume, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].

Possible reasons :

1.An AS Java service, which is providing a container, is stopped or not deployed.

2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.

at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)

at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:149)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)

at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)

at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)

at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)

at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)

at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)

at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)

at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)

at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)

Result

Status:Warning

##################################################################################

I have see in the nwa if there are some applications or services that are stopped but all the necessary it's started, just one question : in the pdf for upgrade from 7.0 to 7.1 no one speaks about ejBean or about a creation of it ... it's necessary an ejBean ?? Beacause in the file .sda of the file .sca that i have downloaded there are more of the adapter with ejBean ....

Antonello

stefan_grube · ‎04-02-2009

If there is no error, try if your adapter runs anyway.

The services are not started during deployment, they will be started when used the first time.

The adapters are no EJBs. They call EJBs, but these EJBs need not to deployed the same time. The sample adapter use the same EJBs, which are part of the File/JMS adapter.

Regards

Stefan

Troubles with the creation of New Custom Adapter for NW 7.1

Accepted Solutions (0)

Answers (1)

Answers (1)

Re: CF Deployment Error: Error getting tenant t0

Feature Request: Allow Process Intelligence Consum...

Re: [XSLT]: Dynamic rows creation and values(in co...

Re: Connecting SAP CAP with SAP Cloud ALM

Re: How to configure alerts in Time and Material J...