Deploying ear file to glassfish server

Hello Frnds,
I am trying to deploy my ear file to glassfish server and i am gettin the following error.
Can any one tell me having any idea on this.?
Message ID Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException
+Complete Message Fatal Error from EJB Compiler -- Caught java.lang.RuntimeException while processing CMP beans for application [abcd.4.0.0]; module [abcd.jar]: Cannot find accessor getPictureBody for CMP field pictureBody. See log for details. at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:315) at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:648) at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:593) at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:290) at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:226) at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:319) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:240) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:788) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)+
helping on this is really appreciated :)
Cheers,

At first glance, your CMP metadata doesn't match what the actual bean has. You've told CMP that there's a pictureBody property on some bean, but there actually isn't

Similar Messages

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]

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

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.

How to deploy an Ear File into Weblogic Server

Hello,
i have created an ADF application successfully and make it as an EAR file.
How can we deploy that EAR file into weblogic server..?
Let me know step-by-step procedure.
Regards.

Hi,
Steps to deploy EAR file on Weblogic server:
1) login to http://<hostname>:<port>/console
2) Go to deployments and then install your ear on weblogic server.
Also you will need to create a data source with same name as given in your Application Module.
Following link contains steps for data source creation - http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.html ( section - "Configure a JDBC Data Source")
Thanks,
Randhir

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?

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 in deploying EAR file

hi experts,
iam trying to deploy EAR file created using NWDS, when i am trying to deploy in XI server i am getting the following error,
can any one solve my problem.
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/ldaptofileear..
Reason: Errors while compiling:
E:/usr/sap/BWS/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/ldaptofileear/EJBContainer/temp/temp1209360116023/com/sap/aii/proxy/xiruntime/core/_AbstractProxyInboundRemote4ObjectImpl0_0_Tie.java:98: illegal escape character
if (method.equals("U0024messageSpecifier")) {
regards,
Madhav Poosarla.

hi prateek,
i have not used this below code in my java proxy code
if (method.equals("U0024messageSpecifier")) {
but while i am deploying the java proxy, it is showing
the following path
E:/usr/sap/BWS/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/ldaptofileear/EJBContainer/temp/temp1209360116023/com/sap/aii/proxy/xiruntime/core/_AbstractProxyInboundRemote4ObjectImpl0_0_Tie.java:98: illegal escape character
and giving this error
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/ldaptofileear..
Reason: Errors while compiling:
plz check this error
regards,
Madhav

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

What to do after deploy ear file

hi all,
i have deployed ear file successfully but i don't know what is the url i can use ta access my application
the steps:
1) i have deployed my application to ear file in my machine
2) i took this ear file and install it in weblogic server admin console successfully
3)what can i do to run my application ( i installed my application on weblogic without changing any configurations)
4)ear file i create it from application properties no viewcontroller properties
thank you

You normally specify the web root as part of the deployment process. If you cant remebmer, open the WLS admin console, select the deployments, open the tree for your application (or just click it), in the modules and components section look for the web application under modules nad click the link, in the next page select configuration. The last entry on this side holds the context root for your app.
To call the app you use an URL like 'http://wlsserver:port/contextroot/faces/startpage'
wlsserver and port you should know, contextroot you just found in the last page the missign information is the startpage which you should know when you test the app in jdev.
Timo

Deploy war file to JBOSS server

I have a simple project called "Test" which just has a "System.out.println" statement. After I build it, I Exported the war file to "{install dir}\JBOSS\jboss-4.0.0\server\default\deploy". when I ran the project at "//localhost:8080/Test". I got the following errors in the JBOSS server window:
2005-01-29 15:21:21,131 ERROR [org.jboss.web.localhost.Engine] StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception
java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:44)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:169)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:595)
2005-01-29 15:21:21,242 INFO [STDOUT] Connected to server
2005-01-29 15:21:21,242 INFO [STDOUT] socket closed
do you know how to fix it? Thanks.

The project I'm working on has two part:
- Web application (a war file)
- Enterprise application (an ear file)
I tried to merge them to one part and make the web application a web module of the enterprise application. I deployed the war into the ear file and the web application can be accessed successfully on my local testing machine. However, when I deploy the ear file on the server, I couldn't access to the web application anymore. Any explanation/solution would be appreciated.
Thanks,
Chuottui.

Deploy .EAR file on localhost

We are trying to deploy our .EAR file on the J2EE engine in our dev environment. The dev environment consists of the SAP discovery server - all components are locally installed on this machine.
We started the sap system from the sap mmc console correctly - it shows the processes jstart.exe, enqueueserver.exe and message_server.exe running. However, when we try to deploy to the J2EE engine on local and when we see in the window>preferences>SAP J2EE engine, it does not show any J2EE engines running on localhost.
We tried to do it using sdm but could not find the sdm components on the local machine.
How can we find out the exact name and port number of the J2EE engine on the local host or find the SDM deployment

Hi.
WLS version and service pack level? Please post the entire weblogic.deploy command along
with the exception that follows.
Thanks,
Michael
Harjeet Singh wrote:
I try to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
on 7001. When I try to run it gives me following error:
[java] JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
as: system: password
system password is correct. I have tried http://localhost:7001 to but doesen't seem
to work.
Any ideas.
HS--
Michael Young
Developer Relations Engineer
BEA Support

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

Deploying ear file to glassfish server

Similar Messages

Maybe you are looking for