Deploying ear file to Web AS server

Hi,
I am trying to deploy the ear file from Netweaver Developer Studio using "Administrator " user. After Successfull deployment I logon to Enterprise portal server, immediatelty asked passwd expired & change password.I have changed that!
Then I logged into Visual admin with changed password...
But i was able to logon to SDM Remote GUI without changing SDM passwd
once again i deployed same application after password changes and it is giving
<b>deployment abort exception</b>
Dec 13, 2006 1:10:17 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[021]Deployment aborted
Settings
SDM host : stcecommdv2
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/KALADH1.NAG/LOCALS~1/Temp/temp28154simpleEAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/KALADH1.NAG/LOCALS~1/Temp/temp28154simpleEAR.ear
Aborted: development component 'simpleEAR'/'sap.com'/'localhost'/'2006.12.13.08.20.50':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [stcecommdv2] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted
Later I have changed SDM password..then also displays same Deployment Abort Exception
How to do local deployment using "remotegui"
Please help me!!!!
Thanks
Kaladhar

Hi Kaladhar,
See this thread same problem but solved:
Re: An Deploy Problem about Credentials.
Regards, Suresh KB

Similar Messages

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

Urgent :- Unable to deploy EAR file in Oracle application server

Hello folks,
I am trying to deploy an application containing jsps and servlets
packaged into EAR using ant. However when am trying to do so by using
the Deploy EAR option in the Enterprise manager, it throws the
following error -
"Invalid J2EE application file specified - Jar file:
/var/tmp/jar47241.tmp is missing its standard xml descriptor located at
META-INF/ejb-jar.xml"
I suspect that something could be wrong with regards to the way the ear
file has been created.
Please if someone could pin point the problem and help me understand
the the above error message , it will be of great help to me and I d
really appreciate this.
Many Thanks,
Ramn.

Hello,
I try to deploy an ear file (contains jar and war files) in Oracle Application server in linux, but the time is so long. The same file I deploy in a OAS in windows and the deploy time was 2 minutes, but in linux I leave the hole night and the session close and the deploy in unable.
I don't know if I need configure an especial option in the OAS in Linux, how I can load my ear file.
The OAS in windows was installed with oc4j options only, but the OAS in linux was full installation
Please help me....
Thanks.

Geting error when deploy ear file on Oracle Application Server

Hi,
i m trying to deploy EAR on Oracle Application Server but i m getting ther Error
Operation failed with error: Missing class: oracle.adf.controller.v2.lifecycle.PagePhaseListener Dependent class:
any body know that what is this error
plz help me
Harish

What version of JDeveloper are you using? And what version is your app server?

Deploying ear file in Sun app server

[#|2004-10-15T12:46:20.781+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=11;|
javax.management.InstanceAlreadyExistsException: com.sun.appserv:j2eeType=ResourceAdapter,name=StartUpConnector.rar,ResourceAdapterModule=StartUpConnector.rar,J2EEApplication=null,J2EEServer=server,category=runtime
     at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:460)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1418)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:944)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:345)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:505)
     at com.sun.enterprise.admin.meta.MBeanRegistry.instantiateMBean(MBeanRegistry.java:528)
     at com.sun.enterprise.management.util.J2EEManagementObjectManager.instantiateAndRegisterRuntimeMBean(J2EEManagementObjectManager.java:787)
     at com.sun.enterprise.management.util.J2EEManagementObjectManager.createRARMBean(J2EEManagementObjectManager.java:2317)
     at com.sun.enterprise.server.ApplicationLoader.createLeafMBean(ApplicationLoader.java:222)
     at com.sun.enterprise.server.AbstractLoader.loadRars(AbstractLoader.java:660)
     at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:122)
     at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:96)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:205)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:156)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:480)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:448)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:432)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:299)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:107)
     at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3880)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
     at com.sun.enterprise.admin.server.core.mbean.config.AdminBase.invoke(AdminBase.java:86)
     at com.sun.enterprise.admin.server.core.mbean.config.ConfigMBeanBase.invoke(ConfigMBeanBase.java:680)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.phasing.DeploymentService.multicastEvent(DeploymentService.java:341)
     at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:284)
     at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:115)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:105)
     at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:35)
     at com.sun.enterprise.tools.admingui.handlers.DeploymentHandler.deploy(DeploymentHandler.java:98)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.invokeHandler(DescriptorViewHelper.java:785)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.dispatchEvent(DescriptorViewHelper.java:731)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.execute(DescriptorViewHelper.java:250)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewBeanBase.execute(DescriptorViewBeanBase.java:187)
     at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:308)
     at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:822)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:760)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:780)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:590)
     at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:951)
     at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:622)
     at com.sun.enterprise.tools.guiframework.view.BaseServlet.processRequest(BaseServlet.java:186)
     at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:480)
     at com.sun.enterprise.tools.admingui.AdminGUIServlet.doPost(AdminGUIServlet.java:65)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:768)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil|#]
[#|2004-10-15T12:46:20.796+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=11;|.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:536)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:305)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
|#]

Did you do a asadmin list-components or the equivalent from the gui? It looks like your rar is already deployed based on the stacktrace

Error while deploying .EAR file Error 500 Internal server error

While trying to run an application on NWCE i got this error.
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:654)
    at com.sap.engine.boot.loader.ResourceMultiParentClassLoader.loadClassLocal(ResourceMultiParentClassLoader.java:198)
    at com.sap.engine.boot.loader.MultiParentClassLoader.findClassInLoaderGraph(MultiParentClassLoader.java:306)
    at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256)
    ... 60 more

The error has been resolved by changing the compiler version for JAVA from 6.0 to 5.0 as I was using JDK5.0.

Problem while deploying the ear file in sap itc server

error loading archive
manifest attributes are missing while deploying ear file in sap itc server
attribute key location is missing
attribute key vendor is missing

error loading archive
manifest attributes are missing while deploying ear file in sap itc server
attribute key location is missing
attribute key vendor is missing

WLST script deploy EAR File in Weblogic Server

Hi,
Can any one help me providing the steps to deploy EAR file using WLST Script.
Thanks in Advance.
Regards
Balaji S

You can use the deploy command, for example,
deploy('DeploymentName', path=LocationOfYourEARFile, targets='A Cluster or a Server');A complete example can be found here: http://middlewaremagic.com/weblogic/?p=6329
And the reference: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13813/reference.htm#i1024284

Got this error after deploying ear file into OC4J server.

Hello Frnsz,
Can any one help to resolve the following error :)
Got this error after deploying ear file into OC4J server.
2008-06-04 14:57:58.551 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/pager-taglib.tld
2008-06-04 14:57:58.566 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.566 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-bean.tld
2008-06-04 14:57:58.598 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.598 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-html.tld
2008-06-04 14:57:58.629 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.629 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-logic.tld
2008-06-04 14:57:58.660 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.660 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-nested.tld
2008-06-04 14:57:58.691 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.691 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-tiles.tld
2008-06-04 14:57:58.723 NOTIFICATION Binding web application(s) to site default-web-site ends...
2008-06-04 14:57:58.723 NOTIFICATION Application Deployer for MyEarProject COMPLETES. Operation time: 3422 msecs
2008-06-04 14:58:04.895 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.910 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.926 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.942 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.957 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:05.020 NOTIFICATION J2EE JSP-0008 Unable to dispatch JSP Page : Exception:oracle.jsp.parse.JspParseException: /WEB-INF/jsp/login.jsp: Line # 2, <%@ taglib uri="/WEB-INF/tld/struts-html.tld" prefix="html"%>
Error: java.lang.ClassNotFoundException: org.apache.struts.taglib.html.MessagesTei
Cheers,
Cap

Cross posted in correct forum
[http://forum.java.sun.com/thread.jspa?threadID=5302192]

EXCEPTION in deploying ear file on weblogic server 11g

Hi, I am trying to deploy an ear file on the weblogic server 11g(10.3.5) application installed successfully but when i tried to start application to listen service requests its throws exceptions and application state changed from prepared to failed
I have unchecked the check box Auto generate and synchronize weblogic JDBC descriptors during deployment in application properties under the deployment node. I also have created same jdbc datasource with name Connection1 and JINDI name jdbc/Connection1 on my weblogic server.
Exceptions that application throwing are.
Message icon - Error weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: No credential mapper entry found for password indirection user=hr for data source Connection1
But when I tried to deploy this from jdeveloper deployment console directly on the server it deployed successfully and starts listening requests.
please give me solution of this problem.
Thanks in advance
Edited by: Rao on Nov 29, 2012 10:22 AM
Edited by: Rao on Nov 29, 2012 10:23 AM

I have resolved this exception. Exception occur due wrong settings in weblogig_Application.xml file remove Data source information from this file and provide datasource on weblogic server.

Error while deploying .ear file on the oracle 10g Application server

While deploying the ITS.ear or any other .ear file thru the application server console the screen shows the deploying screen continuously without any errors.The screen shows uploading the .ear file without any errors.Can somebody help me out it 's very urgent
Thanks in advance.

Hello,
I asked you about the amount of AS instances because currntly I'm working on a clustering issue likewise. Nevertheless, your issue looks like a browser cache problem, have you tried different browsers to perform your deployment tasks? what about ant tasks?
hope it helps,
RB

Error while deploying EAR file on OC4J 10.1.3.3

Hi all,
I am facing following error on OC4J while deploying EAR file
Error occurred during initialization of VM
Could not reserve enough space for object heap
07/12/31 17:47:21 oracle.oc4j.admin.internal.DeployerException: Error compiling :C:\exp\warid1link\oc4j\j2ee\home\applications\CustomerServ
ices SMS API\customerservicesapi: Syntax error in source or compilation failed in: C:\exp\warid1link\oc4j\j2ee\home\application-deployments\
CustomerServices SMS API\customerservicesapi\com\warid\sms\runtime\CSSMSAPI_Service_SerializerRegistry.java
07/12/31 17:47:21 at com.evermind.server.http.WrapperClassGenerator.generateWebServiceArts(WrapperClassGenerator.java:104)
07/12/31 17:47:21 at com.evermind.server.http.HttpApplication.generateWebServiceArtifacts(HttpApplication.java:8469)
07/12/31 17:47:21 at com.evermind.server.http.HttpApplication.populateLoaderWithWebServicesDeploymentCache(HttpApplication.java:5701)
07/12/31 17:47:21 at com.evermind.server.http.HttpApplication.populateLoader(HttpApplication.java:5629)
07/12/31 17:47:21 at com.evermind.server.http.HttpApplication.initClassLoader(HttpApplication.java:5568)
07/12/31 17:47:21 at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:731)
07/12/31 17:47:21 at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
07/12/31 17:47:21 at com.evermind.server.Application.getHttpApplication(Application.java:570)
07/12/31 17:47:21 at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.jav
a:1987)
07/12/31 17:47:21 at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1906)
07/12/31 17:47:21 at com.evermind.server.http.HttpSite.addHttpApplication(HttpSite.java:1603)
07/12/31 17:47:21 at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:238)
07/12/31 17:47:21 at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:99)
07/12/31 17:47:21 at oracle.oc4j.admin.internal.ApplicationDeployer.bindWebApp(ApplicationDeployer.java:547)
07/12/31 17:47:21 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:202)
07/12/31 17:47:21 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
07/12/31 17:47:21 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
07/12/31 17:47:21 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
07/12/31 17:47:21 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
07/12/31 17:47:21 at java.lang.Thread.run(Thread.java:534)
2007-12-31 17:47:21.625 NOTIFICATION Application Deployer for CustomerServices SMS API FAILED.
2007-12-31 17:47:21.625 NOTIFICATION Application UnDeployer for CustomerServices SMS API STARTS.
2007-12-31 17:47:21.640 NOTIFICATION Removing all web binding(s) for application CustomerServices SMS API from all web site(s)
07/12/31 17:47:21 SEVERE: ProgressObjectImpl.reportError Error compiling :C:\exp\warid1link\oc4j\j2ee\home\applications\CustomerServices SM
S API\customerservicesapi: Syntax error in source or compilation failed in: C:\exp\warid1link\oc4j\j2ee\home\application-deployments\Custome
rServices SMS API\customerservicesapi\com\warid\sms\runtime\CSSMSAPI_Service_SerializerRegistry.java
oracle.oc4j.admin.jmx.shared.exceptions.InternalException: Error compiling :C:\exp\warid1link\oc4j\j2ee\home\applications\CustomerServices
SMS API\customerservicesapi: Syntax error in source or compilation failed in: C:\exp\warid1link\oc4j\j2ee\home\application-deployments\Custo
merServices SMS API\customerservicesapi\com\warid\sms\runtime\CSSMSAPI_Service_SerializerRegistry.java
at oracle.oc4j.admin.jmx.shared.deploy.NotificationUserData.<init>(NotificationUserData.java:107)
at oracle.oc4j.admin.internal.Notifier.reportError(Notifier.java:429)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:123)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:534)
Caused by: oracle.oc4j.admin.internal.DeployerException: Error compiling :C:\exp\warid1link\oc4j\j2ee\home\applications\CustomerServices SM
S API\customerservicesapi: Syntax error in source or compilation failed in: C:\exp\warid1link\oc4j\j2ee\home\application-deployments\Custome
rServices SMS API\customerservicesapi\com\warid\sms\runtime\CSSMSAPI_Service_SerializerRegistry.java
at com.evermind.server.http.WrapperClassGenerator.generateWebServiceArts(WrapperClassGenerator.java:104)
at com.evermind.server.http.HttpApplication.generateWebServiceArtifacts(HttpApplication.java:8469)
at com.evermind.server.http.HttpApplication.populateLoaderWithWebServicesDeploymentCache(HttpApplication.java:5701)
at com.evermind.server.http.HttpApplication.populateLoader(HttpApplication.java:5629)
at com.evermind.server.http.HttpApplication.initClassLoader(HttpApplication.java:5568)
at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:731)
at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
at com.evermind.server.Application.getHttpApplication(Application.java:570)
at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1987)
at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1906)
at com.evermind.server.http.HttpSite.addHttpApplication(HttpSite.java:1603)
at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:238)
at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:99)
at oracle.oc4j.admin.internal.ApplicationDeployer.bindWebApp(ApplicationDeployer.java:547)
at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:202)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
... 4 more
2007-12-31 17:47:28.109 NOTIFICATION Application UnDeployer for CustomerServices SMS API COMPLETES.
07/12/31 17:47:28 WARNING: DeployerRunnable.run Error compiling :C:\exp\warid1link\oc4j\j2ee\home\applications\CustomerServices SMS API\cus
tomerservicesapi: Syntax error in source or compilation failed in: C:\exp\warid1link\oc4j\j2ee\home\application-deployments\CustomerServices
SMS API\customerservicesapi\com\warid\sms\runtime\CSSMSAPI_Service_SerializerRegistry.java
oracle.oc4j.admin.internal.DeployerException: Error compiling :C:\exp\warid1link\oc4j\j2ee\home\applications\CustomerServices SMS API\custo
merservicesapi: Syntax error in source or compilation failed in: C:\exp\warid1link\oc4j\j2ee\home\application-deployments\CustomerServices S
MS API\customerservicesapi\com\warid\sms\runtime\CSSMSAPI_Service_SerializerRegistry.java
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:126)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:534)
2007-12-31 18:21:46.234 WARNING Caught exception: java.lang.reflect.InvocationTargetException.
Regards,
Imran Raza Khan

Looks strange, but do you have blanks in your path names? Don't do that. Cause pain only.
--olaf

Getting error while deploying EAR file???

Hi Everyone,
My Jdev version is 11.1.2.3.0.
I have developed one ADF application and successfully deployed into stand alone web logic server from Jdeveloper itself(By creating application server in Jdeveloper and deployed directly from Jdeveloper).
But when i undeployed the application from server and tried to deploy from server itself from the same EAR file its showing below error after clicking on Activate changes:
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error weblogic.application.ModuleException:
Message icon - Error java.security.PrivilegedActionException: weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: No credential mapper entry found for password indirection user=ABC for data source XYZ"
Any suggestions will be really useful.
Thanks.

Looks like you are not using jdbc datasource but jdbc url. You should use jdbc data source as the connection type. right click on your application module and select 'Configurations...' then edit the configurations and select 'jdbc datasource' from the list box.
Then you should edit the applications deployment descriptor (you find this in the application properties) and remove the check mark from the 'Auto generate and synchronize ...'. This means that you have to define the data source on the stand alone server as jdev now does not do this your you (with the wrong credentials). This is the way to go when you deploy to a stand alone server as you can't guarantee that the connection information is allways the same for all servers you deploy to (e.g. production uses a different DB).
Timo

Error while re deploying .ear file in .eap project

Hi Every one,
i developed ejb module ,It Exposed to as Webservice .
I Deployed .ear file into server got result successfully.
Now i made changes in EJb module by adding some other methods .
Then i perform build a Ejb Archive, EAp project Archive.
Next deployed into server .
getting error as follow.
Application alias [WebServiceNew/Config1] for application [sap.com/MA_EAR] already exists in the HTTP Provider Service
what are the things i need to change for getting sucess.

hi ,
go to the undeploy perspective, and select ur web services , add to the undeploy list and undeploy it .
delete the webservice model and generate the code , build and deploy it again to the server.
hope ur problem get resolved
thanks and regards

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
     Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
     Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

Deploying ear file to Web AS server

Similar Messages

Maybe you are looking for