Dependencies not included during deployment in JDev3.0

At the Advanced configuration I have included
the package name or the classes name to be included into the archive file but this
does not seem to work.
There is no problem when using JDev2.0.
Is there anyone else facing this problem?

Similar Messages

Content Selector is not loading during deployment

Hi Alll,
I am using weblogic portal 10.2 and MySQL 5.0.
I have created content selector during developement using workshop.
and deployed the same EAR in Staging server.
But content selector is not loaded after deployment.
I got confirmation after checking adminconsole ->> Content Selectors(Which will be displayed in home page of admin console after login)
And i can see that , other changes ,,JSP Changes...are reflected as part of deployment.
Please let me know what might be the poblem,for not loading content selector??
Is there any number of restrictions on number of content selectors for an environment??
Srinivas

hi
production mode does have the behavior you see, and there are good reasons why this must be so.
You mean to say, we need to propagate Content selectors from STAGING to PRODUCTION??Yes you need to propagate from an environment which has all the data you want correctly to your production environment. You can scope the propagation to only Content Selectors (if you want, the documentation has data how you can do this) and you can run this via GUI or via ANT.
regards
deepak

DTD not available during deployment

Hello
We had a problem that during the deployment of our ear, some dtd's of struts where not accessible on the internet. It seems that xml files are validated, during deployment, so the application was not deployed properly.
Is there a way to either :
- configure the container that no validatio should be done when deploying the ear
- put the dtd in the application itself, so we don't depend on the struts site wether we can deploy or not
grtz
Chris.

The problem is I am trying to use JavaMail in an EJB and it gives me the error if I create a javax.mail.Session. If I comment out the Session, deployment is fine. I am thinking that maybe the problem is I am using 8i version 8.1.5 and it only supports java 1.1.8.

Class not found during deployment

I'm getting "class not found during deserialization of descriptor" during deployment of an EJB. What does this mean?

The problem is I am trying to use JavaMail in an EJB and it gives me the error if I create a javax.mail.Session. If I comment out the Session, deployment is fine. I am thinking that maybe the problem is I am using 8i version 8.1.5 and it only supports java 1.1.8.

CLASSPATH not taken during deployment

I created an ejb and while deploying I get error.
Following are the steps done
- did "ejbc" of the class files and created a jar(jar A) file.
(for an jb).
- The utility classes are wrapped into another (jarB).
- The jarA is deployed in "C:\iPlanet\ias6\ias\JAR"
while jarB is in a different directory.
When the jarA is opened using the deployment tool, i get an error
"The following entries are incorrectly packaged or have external
dependencies".
When I try to deploy it the tool spits out errors saying that the
utility files in jarB could not be found.
I updated the CLASSPATH in the registry under SOFTWARE\iPlanet\6.0\Java.
and also SOFTWARE\iPlanet\6.0\CCS0\SYSTEM_JAVA\GX_CLASSPATH.
Later I restarted the server and also the machine but with no
success.
Environment
===========
ias6.0SP3
Windows2000
Am I missing something here.!!!!
Thanks in advance
Chandu

Hi,
On the Windows platform you will have to add the JAR files to the
IAS_CLASSPATH in deploytool.bat. This is one way. Another way is to open up
deploytool and go to Edit>Preferences and set the complete path for your Jar
file. Click on apply and it will include the classes in the Jar file into
its classpath.
Rgds,
Irfan.
Chandu wrote:
I created an ejb and while deploying I get error.
Following are the steps done
- did "ejbc" of the class files and created a jar(jar A) file.
(for an jb).
- The utility classes are wrapped into another (jarB).
- The jarA is deployed in "C:\iPlanet\ias6\ias\JAR"
while jarB is in a different directory.
When the jarA is opened using the deployment tool, i get an error
"The following entries are incorrectly packaged or have external
dependencies".
When I try to deploy it the tool spits out errors saying that the
utility files in jarB could not be found.
I updated the CLASSPATH in the registry under SOFTWARE\iPlanet\6.0\Java.
and also SOFTWARE\iPlanet\6.0\CCS0\SYSTEM_JAVA\GX_CLASSPATH.
Later I restarted the server and also the machine but with no
success.
Environment
===========
ias6.0SP3
Windows2000
Am I missing something here.!!!!
Thanks in advance
Chandu

ResourceAdapter not found during deployment using WL 7.0 SP2

Hi,
          Am using WL 7.0 SP2 on Win2k w/ JDK 1.4.
          Am using the non-managed mode (wherein the admin server is also the managed-server).
          Am trying to deploy my RA. On uploading the RAR using
          the admin console, I get the following error (from the server.log):
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer Initiating a deployment task with id 8 for application bs-ra
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer preparing application bs-ra on vspl-dev-server
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer prepared application bs-ra on vspl-dev-server
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Management Configuration changes for domain saved to the repository.
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer activating application bs-ra on vspl-dev-server
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Connector Initializing connection pool for resource adapter BookStore-
          Resource Adapter_eis/BSResourceAdapter.
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error Deployer Unexpected error was encountered during the deployment proce
          ss.
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error Deployer The Slave Deployer failed to complete the deployment task wi
          th id 8 for the application bs-ra.
          java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter
               at java.lang.Class.getMethods0(Native Method)
               at java.lang.Class.getDeclaredMethods(Class.java:1034)
               at java.beans.Introspector$1.run(Introspector.java:847)
               at java.security.AccessController.doPrivileged(Native Method)
               at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:845)
               at java.beans.Introspector.getTargetEventInfo(Introspector.java:551)
               at java.beans.Introspector.getBeanInfo(Introspector.java:289)
               at java.beans.Introspector.getBeanInfo(Introspector.java:76)
               at weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java:402)
               at weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectionFactory(ConnectionPoolManager.java:64)
               at weblogic.connector.deploy.ConnectorDeployer.activate(ConnectorDeployer.java:315)
               at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:221)
               at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1662)
               at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1087)
               at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1074)
               at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1110)
               at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
               at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          --------------- nested within: ------------------
          weblogic.management.ManagementException: 149233 - with nested exception:
          [java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter]
               at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:834)
               at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1180)
               at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
               at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Warning Deployer Failures detected initiating weblogic.management.ManagementE
          xception: 149233 - with nested exception:
          [java.lang.NoClassDefFoundError: javax/resource/spi/Resource
                                                                                              Adapter] task for application Activate application bs-ra on
          vspl-dev-server
          Jun 9, 2003 5:32:32 PM EDT vspl-dev-server Info Management Configuration changes for domain saved to the repository.
          Jun 9, 2003 5:32:36 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
          ceAdapter.
          Jun 9, 2003 5:32:39 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
          ceAdapter.
          Jun 9, 2003 5:32:47 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
          ceAdapter.
          Jun 9, 2003 5:32:48 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
          ceAdapter.
          There are two things I observer here.
          1. The ResourceAdapter class does not seem to be found by Weblogic. It's part of the javax.resource.spi package.
          I checked the weblogic.jar archive in the WL-HOME/server/lib folder. It does not seem to have the class. Why ?
          2. It complains about the ManagedConnectionFactory not being found. Am assuming that if the RA was deployed
          in the first place, I would not have seen this error (coz, the ManagedConnectionFactory would have been
          deployed in the previous step). Right ?
          I did observe that WL 7.0 supports only JCA 1.0. In JCA 1.0's (public) API, there is no mention of the
          javax.resource.spi.ResourceAdapter class, though the spec talks about it. ??
          Note: I had designed and implemented my RA as per JCA 1.5 (but nothing 1.5-specific, I guess).
          Any ideas ?
          thanks,
          raghu


I figured it out. Darn simple.
          My ManagedConnectionFactory implementation referenced ResourceAdapter as
          it has to implement the ManagedConnnectionFactory interface of JCA 1.5.
          In JCA 1.0 (which is supported by WL 7.0 & 8.1), the ResourceAdapater
          is undefined. Hence, the classloading problem.
          Sorry for any confusion.
          raghu
          raghu h wrote:
          > Hi,
          >
          > Am using WL 7.0 SP2 on Win2k w/ JDK 1.4. Am using the non-managed mode
          > (wherein the admin server is also the managed-server).
          >
          > Am trying to deploy my RA. On uploading the RAR using
          > the admin console, I get the following error (from the server.log):
          >
          >
          >
          > -----------------------------------------------------------------------------------------------------------------
          >
          >
          > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info
          > Deployer Initiating a deployment task with id 8 for
          > application bs-ra
          > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info
          > Deployer preparing application bs-ra on
          > vspl-dev-server Jun 9, 2003 5:32:31 PM EDT
          > vspl-dev-server Info Deployer prepared application
          > bs-ra on vspl-dev-server Jun 9, 2003 5:32:31 PM EDT
          > vspl-dev-server Info Management Configuration
          > changes for domain saved to the repository. Jun 9, 2003 5:32:31 PM
          > EDT vspl-dev-server Info Deployer activating
          > application bs-ra on vspl-dev-server Jun 9, 2003 5:32:31 PM
          > EDT vspl-dev-server Info Connector
          > Initializing connection pool for resource adapter BookStore-
          >
          > Resource Adapter_eis/BSResourceAdapter.
          >
          > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error
          > Deployer Unexpected error was encountered during the
          > deployment proce
          >
          > ss.
          >
          > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error
          > Deployer The Slave Deployer failed to complete the deployment
          > task wi
          >
          > th id 8 for the application bs-ra.
          >
          > java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter
          > at java.lang.Class.getMethods0(Native Method)
          > at java.lang.Class.getDeclaredMethods(Class.java:1034)
          > at java.beans.Introspector$1.run(Introspector.java:847)
          > at java.security.AccessController.doPrivileged(Native Method)
          > at
          > java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:845)
          > at java.beans.Introspector.getTargetEventInfo(Introspector.java:551)
          > at java.beans.Introspector.getBeanInfo(Introspector.java:289)
          > at java.beans.Introspector.getBeanInfo(Introspector.java:76)
          > at
          > weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java:402)
          >
          > at
          > weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectionFactory(ConnectionPoolManager.java:64)
          >
          > at
          > weblogic.connector.deploy.ConnectorDeployer.activate(ConnectorDeployer.java:315)
          >
          > at
          > weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:221)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1662)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1087)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1074)
          >
          > at
          > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1110)
          >
          > at
          > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
          >
          > at
          > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          > --------------- nested within: ------------------
          > weblogic.management.ManagementException: 149233 - with nested exception:
          > [java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter]
          > at
          > weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:834)
          >
          > at
          > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1180)
          >
          > at
          > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
          >
          > at
          > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Warning
          > Deployer Failures detected initiating
          > weblogic.management.ManagementE
          >
          > xception: 149233 - with nested exception:
          >
          > [java.lang.NoClassDefFoundError: javax/resource/spi/Resource
          >
          > Adapter] task for application Activate application bs-ra on
          >
          > vspl-dev-server
          >
          > Jun 9, 2003 5:32:32 PM EDT vspl-dev-server Info
          > Management Configuration changes for domain saved to the
          > repository. Jun 9, 2003 5:32:36 PM EDT vspl-dev-server
          > Error Connector ManagedConnectionFactory not found for
          > jndiName eis/BSResour
          >
          > ceAdapter.
          >
          > Jun 9, 2003 5:32:39 PM EDT vspl-dev-server Error
          > Connector ManagedConnectionFactory not found for jndiName
          > eis/BSResour
          >
          > ceAdapter.
          >
          > Jun 9, 2003 5:32:47 PM EDT vspl-dev-server Error
          > Connector ManagedConnectionFactory not found for jndiName
          > eis/BSResour
          >
          > ceAdapter.
          >
          > Jun 9, 2003 5:32:48 PM EDT vspl-dev-server Error
          > Connector ManagedConnectionFactory not found for jndiName
          > eis/BSResour
          >
          > ceAdapter.
          >
          > -------------------------------------------------------------------------------------------------------------
          >
          >
          >
          > There are two things I observer here. 1. The ResourceAdapter class does
          > not seem to be found by Weblogic. It's part of the javax.resource.spi
          > package.
          > I checked the weblogic.jar archive in the WL-HOME/server/lib folder. It
          > does not seem to have the class. Why ?
          > 2. It complains about the ManagedConnectionFactory not being found. Am
          > assuming that if the RA was deployed
          > in the first place, I would not have seen this error (coz, the
          > ManagedConnectionFactory would have been
          > deployed in the previous step). Right ?
          >
          > I did observe that WL 7.0 supports only JCA 1.0. In JCA 1.0's (public)
          > API, there is no mention of the
          > javax.resource.spi.ResourceAdapter class, though the spec talks about
          > it. ??
          >
          >
          > Note: I had designed and implemented my RA as per JCA 1.5 (but nothing
          > 1.5-specific, I guess).
          >
          > Any ideas ?
          >
          > thanks,
          > raghu
          >
          >
          >
          >

Management Point did not install during deployment

I found the 2007 client installed on this server prior to the install. I removed the client with /uninstall... however after the installation of CM 2012 the managment point did not install. It pointed me to the mpmsi.log. Below is that log. Has anyone run
into this issue before?
=== Verbose logging started: 2/25/2014 15:58:05 Build type: SHIP UNICODE 5.00.9600.00 Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
MSI (c) (C4:40) [15:58:05:347]: Resetting cached policy values
MSI (c) (C4:40) [15:58:05:347]: Machine policy value 'Debug' is 0
MSI (c) (C4:40) [15:58:05:347]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (C4:40) [15:58:05:348]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (C4:40) [15:58:08:348]: Failed to grab execution mutex. System error 258.
MSI (c) (C4:40) [15:58:08:350]: Cloaking enabled.
MSI (c) (C4:40) [15:58:08:350]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (C4:40) [15:58:08:350]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (C4:40) [15:58:08:351]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C4:40) [15:58:08:351]: MainEngineThread is returning 1618
=== Verbose logging stopped: 2/25/2014 15:58:08 ===
MSI (s) (80:58) [15:58:11:836]: User policy value 'DisableRollback' is 0
MSI (s) (80:58) [15:58:11:836]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:58) [15:58:11:837]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (80:58) [15:58:11:837]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (80:58) [15:58:11:844]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:58) [15:58:11:860]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (80:58) [15:58:11:867]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (80:58) [15:58:11:881]: Destroying RemoteAPI object.
MSI (s) (80:60) [15:58:11:889]: Custom Action Manager thread ending.

MSI (c) (C4:40) [15:58:08:348]: Failed to grab execution mutex. System error 258.
This normally means there is another install process in progress. So please restart the computer and try again. If no avail, check whether there is a process name msiexec running.
Juke Chou
TechNet Community Support

Project librarys not included in WAR file with deployment (WEB-INF/lib)

Using JDeveloper 9.0.5.2
Project Libraries are not included in WEB-INF/lib when deploying. Although the files are selected in the deployment file at 'Contributors'. Within the 'filter' the .jar files are missing.
To solve it i have to register again (i have already made the librarys project library's) the files within Tools->ManageLibrarys as user library's.
The other workaround is to make the library's System Library's within the project.
In my opinion it is a bug that you must include the project librarys as user librarys within the 'LibraryManager'

Unfortunately no, the issue with output folder being ignored occurs only with example apps bundled with Workshop product.
You can try the following workaround:
- In Workshop, Project > Properties - Java Build Path, switch to Source tab - "Remove the source folder listing" - Click OK and dismiss Properties window.
- Project > Properties - Java Build Path > Source Tab, add the same source folder entry - Click OK
- Export as WAR
With this you should see the class files bundled under output directory structure (Ex: WEB-INF/classes).

.ear file is not including all the required files for deployment

While deploying from JDeveloper, some of the files (eg. <Project>.cpx file, .class file) are not included in the .ear file.
Pls help.

Is the .ear file deployed with the Deploy to EAR file selection?

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

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 [tcbrmsfacade] 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/tcbrmsfacade.
     The sap.com/tcbrmsfacade 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 [tcbrmsfacade] 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/tcbrmsfacade.
     The sap.com/tcbrmsfacade 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 [tcbrmsfacade] 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/tcbrmsfacade.
     The sap.com/tcbrmsfacade 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

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

CreateProcess exception during deployment...

I've read an old article describing this problem with getting the following dump:
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:66)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:144)
at weblogic.utils.Executable.exec(Executable.java:108)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:545)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:202)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
during deployment. And the answer was that the shell executing
the javac gets a command-line that is too long.
The problem appears when adding new beans (which bean is not
important, just the number of beans).
We're running WLS 6.0sp1 and WindowsNT 4.0 sp6.
Is there a way to get the command window to accept longer
command-lines? Is there some way to configure the WLS not
to include all files in a single javac-command?
TIA!
/Mikael Arctaedius

??? I think he said that Windows doesn't support command lines over a certain
length and he gave you a suggestion as to how to work around it.
Bill
Mikael Arctaedius wrote:
In short, BEA does not support WLS under Windows?
That some news!
/Mikael Arctaedius
"Cameron Purdy" <[email protected]> wrote:
On Windows, use mappings or subst, change paths from
"i:\somedir\someotherdir\somelongerdir\whatever.jar" to "j:\whatever.jar".
Or do the build on Linux or Solaris and it will work.
I'm sorry that there is no other "solution"
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Mikael Arctaedius" <[email protected]> wrote in message
news:[email protected]...
I've read an old article describing this problem with getting thefollowing dump:
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:66)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:144)
at weblogic.utils.Executable.exec(Executable.java:108)
atweblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.jav
a:545)
atweblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372)
atweblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:202)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
during deployment. And the answer was that the shell executing
the javac gets a command-line that is too long.
The problem appears when adding new beans (which bean is not
important, just the number of beans).
We're running WLS 6.0sp1 and WindowsNT 4.0 sp6.
Is there a way to get the command window to accept longer
command-lines? Is there some way to configure the WLS not
to include all files in a single javac-command?
TIA!
/Mikael Arctaedius

ClassNotFound error during deployment of ADF fusion web applications

Hi All,
We have a fusion ADF web application to be deployed on a stand alone weblogic server. The weblogic server has the default AdminServer and one more extended domain. Both the domains have got ADF runtime libraries installed. When the EAR file is deployed on AdminServer using weblogic administration console, the app works perfectly fine. However, when we try to deploy the same EAR file on the other domain, we get the following error:
java.lang.NoClassDefFoundError: oracle/jdeveloper/db/adapter/DatabaseProvider.
This is being referenced by connections.xml in ADF-META-INF. If we include the corresponding jar file in our class path, the app runs fine.
I have the following doubts:-
1) Is the error due to the fact that we missed any of the steps for configuring ADF runtime libraries on the extended domain. If not, any particular reason for this error?
2) Our application uses data sources for connections and we have configured AM's and the weblogic server for the same. I understand that connection information for every AM is stored in bc4j.xcfg. In such a case, do we need connections.xml that is automatically included in the EAR file. If this is not needed, any steps to exclude it during deployment.

Hi,
Can you check if the solution given in this thread is of any help for you?
What does this message mean?
-Arun

Upgrade - SAP will not restart during MAIN_NEWBAS/STARTSAP_NBAS phase

We are upgrading from 4.7 to NW 7.0 (SP#5)
SAP will not restart during the phase MAIN_NEWBAS/STARTSAP_NBAS
We had to manually apply the kernel (NW 7.2 -#63 - NON UC). This looks OK when we calll DW -version. The T03 system will not start either through the upgrade tool or manually. There is no useful log in
\usr\sap\T03\DVEBMGS15\work
The upgrade tool reports this error.
Checks after phase MAIN_NEWBAS/STARTSAP_NBAS were negative!
Last error code set: RFC call to subst_get_uvers failed with key
RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed Connect_PM GWHOST=CSIAS9, GWSERV=sapgw15, SYSNR=15
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'CSIAS9:3315' not reached
TIME Wed Aug 31 15:09:36 2011
RELEASE 720 COMPONENT NI (network interface)
VERSION 40 RC -10
MODULE nixxi.cpp
LINE 2898
DETAIL NiPConnect: 165.156.101.209:3315
SYSTEM CALL connect
ERRNO 79 ERRNO TEXT Connection refused
COUNTER 550
Thanks
Matt

Thanks Rene, I have updated the ticket with the required information. In the mean time I am interested if anyone else had had a similar problem during an upgrade. We did have an initial error with the crtsidusr command ( setting CLASSICUSERCONCEPT + removing some of the SPCAUT) seemed to fix that. At this point the upgrade failed and we had to manually APYSAPKRN, the log shoewed it wanted the NON UC which was odd as we are including the UC in the upgrade.
Thanks

Parked invoices not includes in report

Hi
Object: ABAP program ZCAMU_INV_DOWNLOAD
That program downloads invoices created during a month
Problem: Program downloads only invoices created from transaction MIGO (Invoice Creation) or MR8M (Invoice Cancellation). If an invoice has been created from MIR7 (Park Invoice), it is not included, and it should be.
Request: include data from transaction MIR7 (Park Invoice)
rgds
Arjun

Hi,
probably the SELECT contains a filter on field FKART of VBRK table.
Bye
Andrea
Rewards if it helps

How can i NOT include top level keyword in the metadata of an image?

Hello,
I want to know how can i NOT include top level keyword in the metadata of an image. I know there is an option for not applying a keyword to an exported image, but is there an option for not applying the top level keyword to the actual image?
I have organized my geographical (by location) keywords like this:
Places
USA
New York
Miami
Spain.
If i add geographical keywords to all my images, all my images will have the keyword "Places", i dont think that it have any sence to have all your images with one keyword. How can i fix this? Any sugestion? i will appreciate it a lot any help or information that you could give me.
Excuse my english, i know it is not good. I hope that you could understand me.
Thanks,
Marcelo :)

Explicitly excluding a keyword only applies when "exporting". Unfortunately, there's currently no way to stop the keyword being written to the file when "Save Metadata to File" command is used. The natural reaction of users to this difference is to suggest that it is stupid. Nevertheless, there are good reasons why the difference exists:
1. "Export" creates a new file whereas "Save Metadata to File" writes the metadata back into the existing file.
2. There are very good reasons why certain keywords should not be written to file, and the example given in the OP is one. Saving metadata to file is more often used as means of backing up important image related metadata, independently of the catalog or allowing the metadata to be visible in other aplications. It would be rare that such a file would be shared with a third party, so the reason for not including certain keywords is less obvious. Actually, not including it can result in no end of confusion and grief. For example, if the top level (or any keyword) was excluded during the save metadata process then the other keywords would be orphaned when image is imported back into the catalog (e.g. buiding a new catalog).
The development team are aware of the need, in some circumstances, to exclude certain keywords when save metadata command is used. How and when the issue is resolved, without adding even more confusion/complexity, is some way off.

Dependencies not included during deployment in JDev3.0

Similar Messages

Maybe you are looking for