Ruleset webservice: error during deployment EAR file on the java server

[Former Member]

Hi,

I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).

During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:

<h5>

-

---

S U M M A R Y

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

Successfully deployed: 0

Deployed with warnings: 1

Failed deployments: 0

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

1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear

Name:DeclaratieCheckRulesetEAR

Vendor:sap.com

Location:localhost

Version:2008.03.12.12.02.09

Deploy status:Warning

Version:NEW

Description:

1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning

2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] 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 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tc_brmsfacade] with type [application], which is not active on the server.

Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?

-> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tc_brmsfacade.

The sap.com/tc_brmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.

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

Possible reasons :

1.Empty or incorrect application, which is not recognized by registered containers.

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

3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].

server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tc_brmsfacade] with type [application], which is not active on the server.

Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?

at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

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

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

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

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

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

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

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

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

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

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

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

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

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:91)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tc_brmsfacade.

The sap.com/tc_brmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.

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

Possible reasons :

1.Empty or incorrect application, which is not recognized by registered containers.

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

3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about 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:158)

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

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

at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)

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

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)

at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)

at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)

... 36 more

]]

Result

Status:Warning

-

---

</h5>

Development Infrastructure:

- development configuration: local development

- development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)

Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:

- Created a ruleset (including two rules and one decision table) (development configuration: saptest)

- Build and deploy the ruleset on the java server...

- Created a dummy web module (development configuration: local development)

- Added 3 dependencies (references) to the dummy web module:

- References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)

- References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)

- References 3: tc/brms/ facade (selection on design time, deploy time and runtime)

- Dummy web module -> sync used DC's

- Build dummy web module

After that I started the Web Service Generation Tool and created the EAR file....

1) NWDS -> window -> show view -> others -> deploy view -> deploy view

2) Added the EAR file to External Deployable Archives

3) deployed the file to the java server... then the warning occurs...

How can I resolve this error?

<h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tc_brmsfacade] with type [application], which is not active on the server.

Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>

And...

<h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tc_brmsfacade.

The sap.com/tc_brmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>

Can somebody help me with this problem?

Kind regards,

Martin Gerritsen

[artigopalan]

Hello Martin Gerritsen,

This is Arti from the PM team.

It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -

You need to access the JavaEE Applications running on your AS. To do this -

1. Open the nwa portal

2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications

3. Search for the brms related applications available on the server.

In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.

I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.

Regards,

Arti