Deploy EAR file through command line

Hello Gurus,
We have external consultants helping us with Java development of a certain application on our CRM system. Usually I would deploy this file through SDM (RemoteGUI). Is there a way to do this on a command line?
Thanks much.
Arvind.

Hello Community,
the sdm utility allow this, but it can be executed only if SDM server is stopped and it is in standalone mode... a bit too complicated, but it works
StopServer.sh
sdm.sh jstartup mode="standalone"
sdm.sh deploy file=<full path to file to be deployed>
sdm.sh jstartup mode="integrated"
StartServer.sh
You can find the sdm utility in <sdm_home>/program and the documentation in <sdm_home>/program/doc
Regards,
Valerio

Similar Messages

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

Undeploy an sda file through command-line

Hi All,
I want to undeploy an .sda file through command-line,what is the procedure to undeploy an sda file through command-line and send me the procedure for this
Thanks & Regards,
guru

Hi
Please find below the steps to undeploy thro command line :
Shut down the sdm server
1)SDM shutdown "sdmhome=D:\usr\sap\J2E\JCO1\SDM\program" "sdmguiport=50018" "sdmhostname=<hostname>" password="<password>" "shutdownmode=abort"
2)sdm jstartup "mode=standalone" "sdmhome=c:\usr\sap\J2E\DVEBMGS00\SDM\program"
3) sdm undeploy "sdmhome=D:\usr\sap\J2E\DVEBMGS00\SDM\program" "compname=c:\test.sda"
4)sdm jstartup "mode=integrated" "sdmhome=c:\usr\sap\J2E\DVEBMGS00\SDM\program"
5)start the sdm server again
SDM server "sdmhome=D:\usr\sap\J2E\JCO1\SDM\program"
Hope this helps. do not forget to reward points
regards
rajeshkr

How to undeploy an .sda file through command line

Hi,
How to undeploy an .sda file through command line.send me the related command to do it.and related information and links.

Hi
Please find below the steps to undeploy thro command line :
Shut down the sdm server
1)SDM shutdown "sdmhome=D:\usr\sap\J2E\JCO1\SDM\program" "sdmguiport=50018" "sdmhostname=<hostname>" password="<password>" "shutdownmode=abort"
2)sdm jstartup "mode=standalone" "sdmhome=c:\usr\sap\J2E\DVEBMGS00\SDM\program"
3) sdm undeploy "sdmhome=D:\usr\sap\J2E\DVEBMGS00\SDM\program" "compname=c:\test.sda"
4)sdm jstartup "mode=integrated" "sdmhome=c:\usr\sap\J2E\DVEBMGS00\SDM\program"
5)start the sdm server again
SDM server "sdmhome=D:\usr\sap\J2E\JCO1\SDM\program"
Hope this helps. do not forget to reward points
regards
rajeshkr

Deploy an EAR file thru command line?

I have been able to deploy the Petstore.ear file from
the 10G AS Deploy EAR file option in the Server admin console.
Now how do I to run this ear via the command line ?
Any suggestions please?

In ias9041 enterprise, I do
$IAS_HOME/dcm/bin/dcmctl deployapplication -a myapp -f /root/myapp.ear -co home
$IAS_HOME/dcm/bin/dcmctl redeployapplication -a myapp -f /root/myapp.ear -co home
$IAS_HOME/dcm/bin/dcmctl undeployapplication -a myapp -co home
I don't use the OEM at all. I do everything in command line with dcmctl and opmnctl. Read oracle's doc for more info.
Ken

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.

Deploy EAR file into WAS using command line

hi,
I have an EAR file and i want to deploy it into WAS using command line interface.
I have seen the SDM_commandline.doc file in SDM directory ..it talks about deploying SDA's and SCA's :-
> sdm deploy file=<...>
however it is not working for EAR files...is there any way to deploy EAR files directly or should I convert the EAR to SDA and then deploy using this command.
thanks

For NW Java releases prior to 7.1, an EAR file needs to be transformed into a SDA file, then it can be deployed. For later releases, an EAR file can be directly deployed.

Compare two pdf files using adobe acrobat through command line

Does anyone know how to compare two pdf files using adobe acrobat through command line. I want to do this via command line because we want to compare hundreds of file every day through some automated windows tasks.
If command line option is not available in acrobat, then is it feasible to make use of acrobat javascript API to do this task?
Any kind of help will be greatly.

Command-line: Not possible.
JavaScript: Possible, but very limited. Basically the only thing you can do is simulate clicking the Compare Documents button. The rest has to be done manually.
However, it *might* be possible to automate this process a bit more using a plugin. Ask over at the Acrobat SDK forum for more information...

Can we deploy a mapping through Command Prompt

Can we deploy a mapping through Command Prompt. If so pls tell me how
Thanks in Advance

Hi,
when deploying mappings from the coomand line or when i try to run some other script in OMBPlus i usually do the following:
* Create a .bat file that will call your tcl script it will look something like this:
rem @echo off
cd <owb_install_dir>\owb\bin\win32\
rem your script file
call OMBplus "<path to your script>\scripts\DeployMapping.tcl"
cd <path to your script>\scripts\
* Create a .tcl file that will do the following:
OMBCONNECT <user>/<passowrd>@<server name>:<port>:<Service Name>;
OMBCC 'MY_PROJECT';
#Deploy Mapping
OMBCONNECT CONTROL_CENTER <control_center_username/control_center_password>@<server name>:<port>:<service name> USE REPOS '<design repository user>';
set om "<sub_location>";
OMBCC '$om';
set m "Mapping Name";
puts " Deploying Mapping: $m";
puts "";
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$m' ADD ACTION 'MAPPING_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE MAPPING '/MY_PROJECT/$om/$m';
catch { OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$m' } ex;
puts " $ex";
OMBDROP DEPLOYMENT_ACTION_PLAN '$m' ;
OMBDISCONNECT CONTROL_CENTER;
OMBCOMMIT;
For more information refer to the OMBPlus reference documentation
Hope this helps
Regards,
Ricardo Ferreira

How to install adobe flash player through command line with some script

Hi Guys,
Do you know how to install adobe flash player through command line with some script?
Thanks,
Galina

Windows. I tried silent install with "install_flash_player.exe /install" but it works only with one file that I downloaded from adobe.com - "install_flashplayer10_mssd_aih.exe". But it is possible to download this last file only one time, every next time it redirects me to download install_flash_player.exe file.

How to deploy EAR file in Tomcat?

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

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

Deploying ear file / 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

Run App Engine through command line but have it show up in Process Monitor

We are trying to run Application Engine through command line and have it show up in the Process Monitor.
We have successfully ran the Application Engine through command line. We also can successfully run the Application Engine through PIA.
Only when you run the AppEng through PIA it goes through the Process Scheduler and shows up in the Process Monitor.
We would like to be able to do this through command line as well. Has anyone done this before?

I'm not sure if it is (easily) doable.
=> Fire a process through the front end appl is nothing but insert few rows in process scheduler tables settings (PSPRCSRQST, PSPRCSQUE), then the process scheduler is taking information from there every x seconds and eventually run the command (on the process scheduler server) keeping an eye on the process result in the tables to post the result.
=> Fire psae through command line (or pssqr) bypass the process scheduler, you can run it from any client... so even without any clue about Process Scheduler server or even without Process Scheduler at all (cf. the very first AE running during an installation is VERSION without anything else than the client).
So finally, your AE program has no clue where it should run outside the client you are fired the command from (i.e. on the batch server as it is running when you are fired the same AE through the front end application), nothing more about the process scheduler configuration file, and where the output files should be posted.
Maybe not by running the AE from the command line, but by simulating the actions as it would be from the front end application, for instance by inserting in the tables whatever you want to run... but it sounds odd. Probably some developer might have done this before... but this should be reconsidered by Peopletools version/patch level (or through CI ?)
Nicolas.
added the last paragraph
Edited by: N Gasparotto on May 21, 2010 2:46 PM

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

Help packaging an android apk through command line

Hello everyone. I've recently developed an app that is near the release deadline and I've ran into the problem of low resolutions icons. All of the troubleshooting I've done has claimed I'll need to manually package the app through the command line to do this. I have never done this before so I'm having some trouble.
I've downloaded all of the required files I believe and have reached the correct bin folder, I'm completely clueless as to what syntax I need to type in from this point though. I've gotten as far as "adt -package" which then outputs that I'm missing additional information, but as I said, I haven't used command promt much and I have no idea how to format the rest of the information I need to put in or how to attach my current app.xml file to it.
Any help would be appreciated.
Edit: Nevermind everyone. After a lot more time spent researching I've managed to piece together how to do it and actually understand it as well.

Hi,
Here is the command to package android apk through command line;
<adt-path> -package -target <target-option e.g. apk, apk-debug etc> -storetype pkcs12 -keystore <your certificate> -storepass <password> name.apk app.xml name.swf assets
Please run adt -help on terminal or cmd if you need any help regarding targets or packaging command. adt is available at you sdk/bin/adt folder.
Also, you can see the page http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac1e63e3d128cdca935b-8000.html for more details.
Hope this will help.
Regards,
Nimit

Deploy EAR file through command line

Similar Messages

Maybe you are looking for