Deploying ear file / Automatic Deployment /AS Deployment

Hello All,
i was trying to deploy a ear file of 100 mb in a10.1.3 Server on a specific oc4j instance.
The error is
Error initializing site OracleAS Java Web Site: No web-app named 'lib/axis' found in application '--WorkBrain' (found web-modules are: 'workbrain', 'axis')
As we all know this error message would have been throwed by Server during the process of parsing the application.xml while trying to deploy.
The entries on META-INF/application.xml are below
<web>
<web-uri>workbrain.war</web-uri>
<context-root>/</context-root>
</web>
</module>
<module id="WebModule_1066144042228">
<web>
<web-uri>lib/axis.war</web-uri>
<context-root>axis</context-root>
</web>
The same .ear file was tested on another oc4j instance.
We tried the Automatic Deployment method (dropping the .ear file in applications dir )
and restarted the oc4j instance.
This worked perfectly.
So what happens in the above two cases..
Why the Server stops the deployment through the AS console .?
Why the Server allows the same .ear file through automatic deployment.
In case if any one needs to refer to automatic deployment .
http://otndnld.oracle.co.jp/document/products/as10g/101300/B25221_03/web.1013/b14431/autodeploy.htm.
The .ear file is not corrupted iam able to unzip the file and i verified the presence of lib/axis .
Please Clarify....
Regards
Prem

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

Similar Messages

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

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

Fail to deploy ear file to AS10g

Hi friends,
I use Jdev10g to generate ear file and dcmctl to deploy to AS10g. Something must have been wrong but I couldn't work it out. Really need your help.
--info: Project:"Master Detail page using ADF"
http://www.oracle.com/technology/sample_code/products/jdev/10g/ADF_ComplexMasterDetail.zip
--Here are my WAR and EAR file
unzip -l ../ias904/mywork/ADF_ComplexMasterDetail.ear
Archive: /raid1/oracle/ias904/mywork/ADF_ComplexMasterDetail.ear
Length Date Time Name
104 09-21-04 13:28 META-INF/MANIFEST.MF
4730626 09-21-04 13:28 ADF_ComplexMasterDetail.war
439 09-21-04 10:39 META-INF/application.xml
285 09-21-04 10:36 META-INF/orion-application.xml
4731454 4 files
unzip -l ../ias904/mywork/ADF_ComplexMasterDetail.war
Archive: /raid1/oracle/ias904/mywork/ADF_ComplexMasterDetail.war
Length Date Time Name
104 09-21-04 13:28 META-INF/MANIFEST.MF
3175 09-21-04 13:28 WEB-INF/classes/DataBindings.cpx
439 09-21-04 11:17 WEB-INF/classes/META-INF/application.xml
575 09-21-04 13:26 WEB-INF/classes/META-INF/data-sources.xml
285 09-21-04 11:17 WEB-INF/classes/META-INF/orion-application.xml
613 09-21-04 13:26 WEB-INF/classes/Model.jpx
881 09-21-04 13:28 WEB-INF/classes/connections.xml
1844 09-21-04 13:26 WEB-INF/classes/model/DepartmentManagersView.xml
4004 09-21-04 13:26 WEB-INF/classes/model/Departments.xml
3849 09-21-04 13:26 WEB-INF/classes/model/DepartmentsImpl.class
1975 09-21-04 13:26 WEB-INF/classes/model/DepartmentsView.xml
364 09-21-04 13:26 WEB-INF/classes/model/DepartmentsViewImpl.class
1329 09-21-04 13:26 WEB-INF/classes/model/DeptMgrFkAssoc.xml
1091 09-21-04 13:26 WEB-INF/classes/model/DeptMgrFkLink.xml
1336 09-21-04 13:26 WEB-INF/classes/model/EmpDeptFkAssoc.xml
1095 09-21-04 13:26 WEB-INF/classes/model/EmpDeptFkLink.xml
1332 09-21-04 13:26 WEB-INF/classes/model/EmpJobFkAssoc.xml
1343 09-21-04 13:26 WEB-INF/classes/model/EmpManagerFkAssoc.xml
1098 09-21-04 13:26 WEB-INF/classes/model/EmpManagerFkLink.xml
9312 09-21-04 13:26 WEB-INF/classes/model/Employees.xml
7121 09-21-04 13:26 WEB-INF/classes/model/EmployeesImpl.class
3836 09-21-04 13:26 WEB-INF/classes/model/EmployeesView.xml
1135 09-21-04 13:26 WEB-INF/classes/model/EmployeesViewImpl.class
2842 09-21-04 13:26 WEB-INF/classes/model/Jobs.xml
3368 09-21-04 13:26 WEB-INF/classes/model/JobsImpl.class
997 09-21-04 13:26 WEB-INF/classes/model/client/EmployeesViewClient.class
239 09-21-04 13:26 WEB-INF/classes/model/common/EmployeesView.class
1210 09-21-04 13:26 WEB-INF/classes/model/common/bc4j.xcfg
1273 09-21-04 13:26 WEB-INF/classes/model/hrService.xml
1717 09-21-04 13:26 WEB-INF/classes/model/hrServiceImpl.class
2152 09-21-04 13:26 WEB-INF/classes/model/model.xml
3591 09-21-04 11:17 WEB-INF/classes/view/BrowseAllEmployeesAction.class
1122 09-21-04 11:17 WEB-INF/classes/view/BrowseEmployeesInDeptAction.class
1179 09-21-04 11:17 WEB-INF/classes/view/QueryEmployeesAction.class
4529 09-21-04 11:17 WEB-INF/classes/view/UIModels/browseAllDepartmentsUIModel.xml
5104 09-21-04 11:17 WEB-INF/classes/view/UIModels/browseAllEmployeesUIModel.xml
6195 09-21-04 11:17 WEB-INF/classes/view/UIModels/browseEmployeesInDeptUIModel.xml
4436 09-21-04 11:17 WEB-INF/classes/view/UIModels/editEmployeeInDeptUIModel.xml
4300 09-21-04 11:17 WEB-INF/classes/view/UIModels/editEmployeeUIModel.xml
3742 09-21-04 11:17 WEB-INF/classes/view/UIModels/masterDetailUIModel.xml
3631 09-21-04 11:17 WEB-INF/classes/view/UIModels/queryAllDepartmentsUIModel.xml
6130 09-21-04 11:17 WEB-INF/classes/view/UIModels/queryEmployeesInDeptUIModel.xml
2174 09-21-04 11:17 WEB-INF/classes/view/UIModels/queryEmployeesUIModel.xml
1010 09-21-04 13:28 WEB-INF/classes/view/resources/AppSampleResources.properties
3581 09-21-04 13:28 WEB-INF/classes/view/resources/ApplicationResources.properties
1810 09-21-04 11:17 WEB-INF/classes/view/util/HelpDispatcherAction.class
49438 05-14-04 19:28 WEB-INF/lib/adf-controller.jar
163279 05-14-04 19:28 WEB-INF/lib/bc4jhtml.jar
42730 05-14-04 19:29 WEB-INF/lib/bc4juixtags.jar
118726 06-30-03 11:50 WEB-INF/lib/commons-beanutils.jar
165119 06-30-03 11:50 WEB-INF/lib/commons-collections.jar
109096 06-30-03 11:50 WEB-INF/lib/commons-digester.jar
112307 05-11-04 17:17 WEB-INF/lib/commons-el.jar
22379 06-30-03 11:50 WEB-INF/lib/commons-fileupload.jar
63980 06-30-03 11:50 WEB-INF/lib/commons-lang.jar
31605 06-30-03 11:50 WEB-INF/lib/commons-logging.jar
46865 06-30-03 11:50 WEB-INF/lib/commons-validator.jar
140889 05-14-04 19:29 WEB-INF/lib/datatags.jar
17747 05-14-04 19:29 WEB-INF/lib/graphtags.jar
65368 06-30-03 11:50 WEB-INF/lib/jakarta-oro.jar
191881 01-28-04 03:32 WEB-INF/lib/jaxen-full.jar
3086 05-11-04 17:17 WEB-INF/lib/jsp-el-api.jar
21128 01-28-04 03:32 WEB-INF/lib/jstl.jar
3503 05-11-04 17:17 WEB-INF/lib/oracle-el.jar
23563 01-28-04 03:32 WEB-INF/lib/saxpath.jar
515490 01-28-04 03:32 WEB-INF/lib/standard.jar
498051 06-30-03 11:50 WEB-INF/lib/struts.jar
1271111 01-28-04 03:32 WEB-INF/lib/xalan.jar
2529 03-01-04 04:34 appsample_files/10gwelcome.gif
37314 03-03-04 00:26 appsample_files/blaf-en-ie-6.css
62 04-04-03 06:32 appsample_files/c-ghb.gif
61 04-04-03 06:32 appsample_files/c-ghbr.gif
66 04-04-03 06:32 appsample_files/c-ghcb.gif
145 04-04-03 06:32 appsample_files/c-ghct.gif
49 04-04-03 06:32 appsample_files/c-ght.gif
68 04-04-03 06:32 appsample_files/c-ghtl.gif
68 04-04-03 06:32 appsample_files/c-ghtr.gif
5395 03-03-04 00:26 appsample_files/mod_jdeveloper.css
661 01-29-04 08:35 appsample_files/return.gif
1870 03-02-04 20:23 appsample_files/sample_footer.jsp
7957 03-02-04 08:04 appsample_files/sample_header.jsp
1544 03-02-04 20:20 appsample_files/sample_help_footer.jsp
1490 03-02-04 20:19 appsample_files/sample_help_header.jsp
747 03-26-04 17:08 appsample_files/sample_sidebar.jsp
2105 04-04-03 06:47 appsample_files/samples.gif
272 04-04-03 07:19 appsample_files/wwv_help.gif
4974 03-05-04 21:35 browseAllDepartments.jsp
5730 03-08-04 23:31 browseAllEmployees.jsp
5213 03-08-04 15:01 browseEmployeesInDept.jsp
2594 03-03-04 00:22 css/jdeveloper.css
3485 03-03-04 21:37 editDepartment.jsp
5063 03-08-04 23:27 editEmployee.jsp
2686 02-12-04 10:18 editEmployeeInDept.jsp
3279 03-08-04 14:50 help/MasterDetailJSPKey.jsp
14710 03-06-04 14:03 help/helpSection1.jsp
15223 03-08-04 23:47 help/helpSection2.jsp
16556 03-08-04 23:09 help/helpSection3.jsp
2191 03-03-04 20:37 help/helpSection4.jsp
36555 03-08-04 13:37 help/images/StrutsPageFlow.jpg
19352 03-03-04 22:13 help/images/section1_flow.gif
8532 03-08-04 13:41 help/images/section2_flow.gif
5454 03-08-04 19:08 help/images/section3_flow.gif
247 02-09-04 14:58 images/ViewObject.gif
806 02-11-04 09:33 images/sideMenuBottom.gif
833 02-11-04 09:31 images/sideMenuBottomC.gif
806 02-11-04 09:29 images/sideMenuRight.gif
806 02-11-04 09:33 images/sideMenuTop.gif
831 02-11-04 09:31 images/sideMenuTopC.gif
1739 04-05-04 16:59 index.jsp
5272 03-03-04 20:53 masterDetail.jsp
6132 03-26-04 17:06 queryAllDepartments.jsp
5104 03-08-04 23:34 queryEmployees.jsp
9543 03-08-04 23:33 queryEmployeesInDept.jsp
5468 02-18-04 10:11 sideMenu.jsp
517075 02-09-04 15:07 web-inf/lib/standard.jar
227 09-21-04 11:15 web-inf/orion-web.xml
8868 02-09-04 14:54 web-inf/struts-bean.tld
10175 09-20-04 14:42 web-inf/struts-config.xml
65029 02-12-04 10:52 web-inf/struts-html-el.tld
66192 02-10-04 12:03 web-inf/struts-html.tld
2513 02-12-04 10:53 web-inf/web.xml
4713475 121 files
--when I deployed on AS10g using:
"dcmctl
deployApplication -file ../ias904/mywork/ADF_ComplexMasterDetail.ear -a jdev9051samples/JSPMasterDetail"
I got following error:
ADMN-300158
Jar file: /var/tmp/jar64914.tmp is missing its standard xml descriptor located at WEB-INF/web.xml
oracle.ias.sysmgmt.deployment.j2ee.exception.J2eeDeploymentException: Jar file: /var/tmp/jar64914.tmp is missing its standard xml descriptor located at WEB-INF/web.xml
Resolution:
at oracle.ias.sysmgmt.deployment.j2ee.file.WarFile.<init>(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.file.EarFile.init(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.file.EarFile.<init>(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.file.EarFile.<init>(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.EarDeployerImpl.<init>(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.J2eeDeploymentImpl.getEarDeployer(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.J2eeDeploymentImpl.getEarDeployer(Unknown Source)
at oracle.ias.sysmgmt.cmdline.DcmCmdLine.deployApp(Unknown Source)
at oracle.ias.sysmgmt.cmdline.DcmCmdLine.execute(Unknown Source)
at oracle.ias.sysmgmt.cmdline.DcmCmdLine.main(Unknown Source)
Thanks in advance.

I wish there is a forum for JDev like asktom.oracle.com for DBA.
I posted several questions but receive no feedback.
future never wait :-(

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

Hi all,
We are getting an error in SDM tool while deploying EAR file.
===========================================================================
Deployment started Fri Nov 28 14:11:01 CET 2008
===========================================================================
Starting Deployment of syn_EAP
The SDM will now start SAP Web AS Java instance processes in order to perform online deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Aborted: development component 'syn_EAP'/'sap.com'/'localhost'/'2008.11.27.20.49.50'/'0':
SDM could not start the J2EE cluster on the host iwdfvm2160! The online deployment is terminated. There is no clutser control instance running on host iwdfvm2160 which is described in SecureStorage . The instances, returned by MessageServer [MS host: iwdfvm2160; MS port: 3900], are :|Name:JM_T1227866087502_0_FCP11895 |Host:rp2399 |State:5|HostAddress:10.34.38.76||Name:JM_T1227714760203_0_tx300-s3 |Host:tx300-s3 |State:5|HostAddress:null||Name:JC_tx300-s3_ERP_10 |Host:tx300-s3 |State:5|HostAddress:10.34.33.45|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment of syn_EAP finished with Error (Duration 11782 ms)
Can anyone help me regarding this issue?
Thanks,
Kalyan.

Hi Prateek,
thanks 4 reply.
I did what you said but no luck.Its giving same error.
Any other suggestions plz??
Thanks,
Kalyan.

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

Deploying ear file to multiple managed ervers

What are the steps we need to follow to deploy an ear file to multiple managed
servers.
Is there a separate method for deploying ear file to managed servers.
Do we need to setup classpath / StartupClass for the managed servers?
Anyone knows this ?

Hi Venky,
you can deploy the application from the console, r the managed servers in clustered environment?
btw what version of weblogic r u using?
thanks
Mir

Help deploying ear file in WAS

I have a few jsp, js and image files in my application that I intend deploying on the WAS. I created the ear file. When I deploy the ear file, I get the following message:
Dec 21, 2004 10:40:52 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Deploy Thread] WARNING:
vipsV4.ear -> Deployment finished with warning
DEPLOYMENT ...
==> SDM host : xxx
==> SDM port : 50018
==> URL : file:/C:/DOCUME1/smani/LOCALS1/Temp/temp11937YYY.ear
... PRECONDITION VIOLATED
com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component
found in the SDA C:\usr\sap\J2E\JC00\SDM\program\temp\temp11937YYY.ear is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Reason:
Problems during deployment !
DEPLOYMENT ...
==> SDM host : xxx
==> SDM port : 50018
==> URL : file:/C:/DOCUME1/smani/LOCALS1/Temp/temp11937YYY.ear
... PRECONDITION VIOLATED
com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component
found in the SDA C:\usr\sap\J2E\JC00\SDM\program\temp\temp11937YYY.ear is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Appreciate your help. How can I see the deployed applications in WAS. FYI, I come from a weblogic background.
Thanks

Hi Siriam,
how did you build that ear? I hope you did not just import it from weblogic and then use it from the studio. You should open new projects and import the files to the studio and thenbuild a new ear.
There is an article about prtong here at SDN: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/porting a j2ee application to sap web application server.pdf
Please check there for details.
Regards,
Benny

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

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

Invalid URL Pattern exception when deploying ear file

Hi,
I encountered some problem during deploying an ear file into SJSAS PE. This ear file has successfully been deployed into WebLogic Server and works fine.
The error message is as follows:
Deploying application in domain failed; Error loading deployment descriptors for module [wsgServerRel1_0] -- Invalid URL Pattern: [pfk/PfkMainServlet] Error loading deployment descriptors for module [wsgServerRel1_0] -- Invalid URL Pattern: [pfk/PfkMainServlet] The following is the relevant part regarding URL pattern:
     <servlet>
          <servlet-name>PfkMainServlet</servlet-name>
          <servlet-class>com.sns.pfk.servlet.PfkMainServlet</servlet-class>
          <load-on-startup>0</load-on-startup>
     </servlet>
     <servlet-mapping>
          <servlet-name>PfkMainServlet</servlet-name>
          <url-pattern>pfk/PfkMainServlet</url-pattern>
     </servlet-mapping>What else I need to do to make it work?
Regards,
Xinjun

You have an error in your url-pattern. A url-pattern must either begin with a slash ("/") for the exact match or directory match or it could begin an asteric("*") for the extension match(refer to the servlet spec).
In your case it should be something like:
<servlet-mapping>
          <servlet-name>PfkMainServlet</servlet-name>
          <url-pattern>/pfk/PfkMainServlet</url-pattern>
</servlet-mapping>
or
<servlet-mapping>
          <servlet-name>PfkMainServlet</servlet-name>
          <url-pattern>/pfk/*</url-pattern>
</servlet-mapping>

Deploying ear file / Automatic Deployment /AS Deployment

Similar Messages

Maybe you are looking for