Applied Workaround for BUG:5871305, unable to deploy ear file

Hi,
I have upgraded Oracle 10g AS from 10.1.3.1 to 10.1.3.3.I am using admin_client.jar to deploy the ear file. After deployment, application gave error during start. The errors were related to apache.commons.logging. I applied the workaround provided on metalink note: 460448.1. I applied the changes in orion-application.xml file:
<imported-shared-libraries>
          <remove-inherited name="apache.commons.logging" />
     </imported-shared-libraries>
Now, upon deploying the ear file with the changes, its giving error during deployment:
oracle.oc4j.admin.deploy.api.J2EEDeploymentException: Operation failed with error:
Error parsing orion-application.xml at /u00/app/ora10gas/product/10.1.3.1/OracleAS_1/j2ee/main/application-deployments/coverzones: Fatal error at line 90 offset 25 in file:/u00/app/ora10gas/product/10.1.3.1/OracleAS_1/j2ee/main/applications/coverzones/: .<Line 90, Column 25>: XML-20201: (Fatal Error) Expected name instead of =.
I have searched a lot on metalink and on google about this error and have not got any pointers to look for root cause.
Oracle App Server Gurus, kindly help on this
regards
Raj

HI Jaap,
I checked the orion-application.xml file and I didn't found any typo error or syntax error in the specific xml tag for <imported-shared-libraries>. Below is the xml tag snippet:
<library path="ivjejb35.jar" /> <!-- needed for access beans in oc4j -->
          <library path="wsdl4j.jar" />
          <library path="CoverZones_DataBeans.jar"/>
          <library path="CoverZones_Session_EJBClient.jar"/>
          <library path="CoverZones_Request_Processors.jar" />
     <imported-shared-libraries>
          <remove-inherited name="apache.commons.logging" />
     </imported-shared-libraries>
<principals path="principals.xml" />
The same ear file without the above changes has worked in another Ora10gAS 10.1.3.3 cluster setup and the application works successfully.
regards
Raj

Similar Messages

  • 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.

  • Unable to deploy .EAR file to PI 7.1

    /people/vijayakhanna.raman/blog/2007/06/08/cool-way-to-create-your-own-scas
    Note 696084 - EP 6.0: How to create SDA files for EPA or PAR files

    hi,
    your ejb-jar.xml should look like:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
          <description>EJB JAR description</description>
          <display-name>EJB JAR</display-name>
          <enterprise-beans>
                <session>
                      <ejb-name> MIDataTarget_PortTypeBean </ejb-name>
           <home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4</home>
                  <remote>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4</remote>
    <local-home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocalHome4</local-home>
                     <local>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4</local>
                   <ejb-class>com.wipro.javaProxy. MIDataTarget_PortTypeBean </ejb-class>
                      <session-type>Stateless</session-type>
                      <transaction-type>Container</transaction-type>
                </session>
          </enterprise-beans>
    </ejb-jar>
    check:
    http://wiki.sdn.sap.com/wiki/display/XI/JavaProxyOutbound+Implementation
    /people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
    http://wiki.sdn.sap.com/wiki/display/XI/PIBlogsby+Topics
    make sure that you are using PI 7.1 libraries:
    https://wiki.sdn.sap.com/wiki/display/XI/XIlibrariesfor+development
    for references in application-j2ee-engine.xml use:
    http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
    For deploying either you can directly deploy ear project using NWDS 7.1 or convert ear to sda using CECLT tool provided with NWDS 7.1:
    Re: How to build an adapter module in NWDS 7.1?
    Thanks,
    Mayank

  • Reg: Unable to deploy .ear file in weblogic 9.0

    Hi,
    I am a developer worked with Weblogic 6.0 and we are planning to upgrade to WLS9.0. But after installation and successful configuration of domain, we are unable to deploy the.ear file.
    Thanks in advance
    Here is the erroe message:
    Messages
    Unable to access the selected application.
    [J2EE Deployment SPI:260101]Parameter may not be null. java.lang.NullPointerException at weblogic.deploy.api.internal.utils.ConfigHelper.checkParam(ConfigHelper.java:126) at weblogic.deploy.api.tools.ModuleInfo.createModuleInfo(ModuleInfo.java:82) at weblogic.deploy.api.tools.SessionHelper.getModuleInfo(SessionHelper.java:559) at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:433) 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:585) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:812) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:751) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:434) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:245) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:316) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:48) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1948) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:184) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:590) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:840) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:607) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:135) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:130) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:927) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:571) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:122) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:149) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:108) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:223) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:169) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:290) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at

    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.

  • Unable to deploy ear file to weblogic 11g

    Unable to access the selected application.
    Exception in AppMerge flows' progression
    Exception in AppMerge flows' progression
    VALIDATION PROBLEMS WERE FOUND problem: cvc-attribute.4: The value '6' does not equal the fixed value '5' of attribute 'version':<null>
    VALIDATION PROBLEMS WERE FOUND problem: cvc-attribute.4: The value '6' does not equal the fixed value '5' of attribute 'version':<null>
    Please help.

    Hi ,
    This issue with build an application ear file.
    please follow below steps to resolve.
    1. verify your build script  having or indicated the correct value of the -Dwls-11 option if not change accordingly
    2.  ./buildear.sh -Dappserver=weblogic -Dwls-11=<true/false> -Dpackage=ear filename create-ear
    Thanks !!!
    Babu

  • Unable to deploy ear file through NWDS 7.3

    Hi,
    When I try to deploy the ear dc project in NWDS 7.3, I'm getting the below error.
    Could you please help me on this.
    Error details:
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [huskyenergy.ca_hsky~base~utils~ear] failed
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
      at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
      at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
      at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [huskyenergy.ca_hsky~base~utils~ear] failed
      at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
      at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
      at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
      at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
      at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
      at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [huskyenergy.ca_hsky~base~utils~ear] failed
      at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
      at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
      at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
      at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
      ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/WX2/J70/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/173/huskyenergy.ca~hsky~base~utils~ear.ear] failed
      at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3366)
      at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
      at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
      ... 11 more
    Caused by: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occurred during web services 630 deployment. Unable to generate deployment data for application huskyenergy.ca/hsky~base~utils~ear.
      at com.sap.engine.services.webservices.server.deploy.ws.WS630DeployProcess.generateDeployFiles(WS630DeployProcess.java:227)
      at com.sap.engine.services.webservices.server.deploy.ws.WS630DeployProcess.generateAndRegisterDeployFiles(WS630DeployProcess.java:209)
      at com.sap.engine.services.webservices.server.deploy.ws.WS630DeployProcess.execute(WS630DeployProcess.java:115)
      at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:330)
      at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWebServices630(WebServicesDeployManager.java:1029)
      at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployInternal(WebServicesDeployManager.java:266)
      at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:248)
      at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:309)
      at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
      at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
      at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
      at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
      at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
      at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1832)
      at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
      at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
      at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
      at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
      at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
      at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
      at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
      at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
      at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
      at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
      at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.webservices.server.deploy.migration.ws.exception.ConversionException: Parsing ws-deployment-descriptor, Vitrual Interfaces and WebService Definitions failed. The application will not be started.
      at com.sap.engine.services.webservices.server.deploy.migration.ws.MigrationController.saveXMLFiles(MigrationController.java:156)
      at com.sap.engine.services.webservices.server.deploy.migration.ws.MigrationController.gatherContentForApplication(MigrationController.java:138)
      at com.sap.engine.services.webservices.server.deploy.migration.ws.MigrationController.deployNW04Archives(MigrationController.java:113)
      at com.sap.engine.services.webservices.server.deploy.ws.WS630DeployProcess.generateDeployFiles(WS630DeployProcess.java:223)
      ... 27 more
    Caused by: com.sap.engine.services.webservices.server.deploy.migration.ws.exception.ConversionException: Unable to load interface mapping data in mappings.xml.
      at com.sap.engine.services.webservices.server.deploy.migration.ws.NW04ConversionTool.nw04ToParisConversion(NW04ConversionTool.java:148)
      at com.sap.engine.services.webservices.server.deploy.migration.ws.MigrationController.saveXMLFiles(MigrationController.java:153)
      ... 30 more
    Caused by: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.lib.descriptors.ws04wsdd.OperationConfigurationDescriptor.getTransportBindingConfiguration() of a null object loaded from local variable 'operationConfigDescriptor'
      at com.sap.engine.services.webservices.server.deploy.migration.ws.NW04toMapping.loadOperationParameter(NW04toMapping.java:230)
      at com.sap.engine.services.webservices.server.deploy.migration.ws.NW04toMapping.loadOperation(NW04toMapping.java:162)
      at com.sap.engine.services.webservices.server.deploy.migration.ws.NW04toMapping.loadInterface(NW04toMapping.java:91)
      at com.sap.engine.services.webservices.server.deploy.migration.ws.NW04ConversionTool.nw04ToParisConversion(NW04ConversionTool.java:145)
      ... 31 more
      at com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:60)
      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:597)
      at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1040)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1116)
      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1535)
      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1535)
      at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:422)
      at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
      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:597)
      at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1535)
      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1535)
      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:329)
      at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:139)
      at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:472)
      at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
      at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
      at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
      at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
      at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
      at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
      ... 3 more

    Hello Jun,
    I'm trying to deploying the ear in nwds 7.3 which was successfully migrated from nwds 7.0
    Please let me know if you need any details.

  • Bug or error during deploy ear file

    here is the error:
    Auto-deploying ejb.jar (No previous deployment found)... CountryLocal_EntityBea
    Wrapper0.java:2412: cannot resolve symbol
    symbol : variable dirty
    location: class CountryLocal_EntityBeanWrapper0
    if((dirty & 0xffffffff) != 0)
    ^
    CountryLocal_EntityBeanWrapper0.java:2418: cannot resolve symbol
    symbol : variable dirty
    location: class CountryLocal_EntityBeanWrapper0
    if((dirty & 1) != 0) { if(!first) buffer.append(", "); buffer.append("code = ?"
    ; first = false; }
    ^
    here is the orion-ejb-jar.xml
    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
    <orion-ejb-jar deployment-version="9.0.3.0.0" >
    <enterprise-beans>
    <entity-deployment name="Country" location="Country" table="COUNTRY" data-source="jdbc/OC4JConnectionPool">
    <primkey-mapping>
    <cmp-field-mapping name="uniqueid" persistence-name="UNIQUEID" persistence-type="VARCHAR2(255)" />
    </primkey-mapping>
    <cmp-field-mapping name="code" persistence-name="CODE" persistence-type="VARCHAR2(255)" />
    <cmp-field-mapping name="name" persistence-name="NAME" persistence-type="VARCHAR2(255)" />
    <finder-method query="">
    <!-- Generated SQL: "select COUNTRY.UNIQUEID from COUNTRY -->
    <method>
    <ejb-name>Country</ejb-name>
    <method-name>findAll</method-name>
    <method-params>
    </method-params>
    </method>
    </finder-method>
    </entity-deployment>
    </enterprise-beans>
    <assembly-descriptor>
    <default-method-access>
    <security-role-mapping name="&lt;default-ejb-caller-role&gt;" impliesAll="true" />
    </default-method-access>
    </assembly-descriptor>
    </orion-ejb-jar>

    I got answer from j2ee forum.
    the bug number is 2700883

  • Unable to deploy ear file

     

    Hi Ronak,
    Earlier posting attached had EJB in exploded format.
    use sempire_web.war instead of sempire_web
    under <web-uri>
    and this should help you to deploy the EAR
    --Vijay
    "Ronak Parekh" <[email protected]> wrote:
    >
    >
    >
    Vijay,
    What do you mean by exploded format? My ejbs are in my jar file itself.
    Ronak
    "vijay" <[email protected]> wrote:
    IS there any reason why you have EJBs in exploded format?
    Can you try Jaring up the EJBs?
    --Vijay

  • 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]

  • Error while deploying EAR file through SDM

    Hi All,
    I am deploying EAR file through SDM. Its taking too much time to deploy in the 3rd stage (its just a simple hello file for testing purpose and its still in that stage for 2 hours).
    When I see the log, I can see some fata error. Please suggest me what should I do. 
    ==
    Oct 15, 2008 4:31:44 PM  Info: SDM started successfully.
    Oct 15, 2008 4:33:21 PM  Info: Opened client connection to sapretail (IP address
    sapretail/172.20.177.203, remote port 58645)
    Oct 15, 2008 4:33:23 PM  Info: Request for Logon as admin accepted
    Oct 15, 2008 4:39:07 PM  Info: Loading archive '/usr/sap/trans/EPS/sap.comwdtu
    torial~ex1.ear'
    Oct 15, 2008 4:40:50 PM  Info: Actions per selected component:
    Oct 15, 2008 4:40:50 PM  Info: Initial deployment: Selected development componen
    t 'wd/tutorial/ex1'/'sap.com'/'LOKAL'/'0.2008.10.14.12.51.57' will be deployed.
    Oct 15, 2008 4:44:41 PM  Info: Saved current Engine state.
    Oct 15, 2008 4:44:48 PM  Fatal: State BeforeNextDeployment can't process event I
    nitiateDeployment
    The reason I am doing through SDM because while deploying through NWDS its throwing an error
    Oct 13, 2008 12:44:41 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : sapretail
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/231477/LOCALS1/Temp/temp41002sap.comwdtutorial~ex1.ear
    Deployment exception : Server sapretail did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sapretail at port 50118: sapretail
    Inner exception was :
    Server sapretail did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sapretail at port 50118: sapretail
    Please suggest a solution.
    Regards,
    Jitender

    Now, when I deploy through NWDS, I get the following error.
    Result
    => deployment aborted : file:/C:/DOCUME1/231477/LOCALS1/Temp/temp51346sap.comwdtutorial~ex1.ear
    Aborted: development component 'wd/tutorial/ex1'/'sap.com'/'LOKAL'/'0.2008.10.15.21.04.16':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: [sapretail] with user name: [J2EE_ADMIN]                     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

  • 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                                                                                                                                                                                                   

  • Error occurred while deploying ear file

    Hello experts,
    I am using NWDS (NW Version: 7.0.18). For a particular java file I am getting this error:
    ERROR: Not deployed. Deploy Service returned ERROR:
    20110728174758 Info   :                     java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/WSPiloto.ear.
    20110728174758 Info   :                     Reason: None of the available containers recognized the components of application sap.com.avn/WSPiloto; it is not possible to make deploy.  Most commonly used containers do not recognize the content of the application. Please contact the application vendor for details.
    Appreciate your help to fix the issue.
    Thanks in advance,
    Guillermo,
    dev

    Hi,
    can you please check if the following note helps?
    #1270242 -- None of the available containers recognized the components
    (http://service.sap.com/sap/support/notes/1270242)
    Best Regards,
    Ervin

  • 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

  • Deploying EAR files in PI 7.1

    Hello,
    we are currently upgrading our XI 3.0 system to PI 7.1.
    We had developed some adapter modules for XI 3.0 and we have compiled them with new libraries for using in PI 7.1.
    But how can we deploy the created EAR-files in PI 7.1 now?
    In XI 3.0 we used the Visual Administrator for Deploying. But we can't use this tool any more.
    The SAP Netweaver Administrator doesn't have such a feature (we didn't find it anyway until now).
    The only thing I found was to deploy EAR-Files using Developer Studio. But we can't deploy EAR files in test and production system this way.
    Does anybody know an easy way to deploy EAR files in PI 7.1 (like in XI 3.0)?
    Regards,
    Thorsten

    Hi Sean,
    Definitely it is possible to use JSPM to deploy ear files in PI 7.1 (at least SP06). When you open up JSPM tool you will have to select "Hot Fixes" and then next. The file will have to be copied to the following Unix directory /<transport directory>/EPS/in. Unfortunately if the file is already deployed and you want to deploy it again with the same version but changes, you will not be able to redeploy it. For that propose you can use the scripts under unix ../j2ee/deployment/scripts. please have a lock under: http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/1bd4293d034f08e10000000a114a6b/content.htm. There you will also find a script to convert an EAR file to SDA.
    Regards,
    Toni

  • 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

Maybe you are looking for

  • Question on BW data and R/3 transaction data mapping

    Hello Expert, How can we find the transactions to mapping the data in BW and R/3? For example, DS 2LIS_04_P_COMP is for extraction component of order. We can change the component requirement in R/3. After that, a delta will post on delta queue. Howev

  • Problem in LOV display length

    i am facing a problem in a LOV display, one of the columns had a length of 4 earlier from the base table used in the LOV but after changing the base table to 10, actual column length is 5 but the fifth character is not showing in the LOV. I hope, my

  • Internet Problem

    Hello, I am new to Solaris. I installed Solaris 10 8/07; Have Dell 4600 with P4, Intel pro 100 Lan+Modem 56 Cardbus II, and Intel Pro/100 VE Network connection; Have Cable Modem(using ethernet) but can't connect to internet; could it possibly be ethe

  • Set my own page number

    My book has many front covers. It takes first seven pages as a front covers (including table of content). The problem is 8th page is my first page. How can I change page number from eight to one ? Thanks for every answers.

  • Why I am not able to approve/reject my workflow notification from email?

    For R12 AP Invoice Approval Workflow, I have done Approver group set ups in AME. In HR People form, set my email id for that person. In FND USER from, used that person as the employee to have the email id populated for the user and saved the record.