The command line deployment tool (admin.jar) requires an EAR file as it's deployment archive. To deploy a WAR file using this, you must package the WAR file within a EAR file. You can manually deploy a WAR file to OC4J However following are the steps involved in deploying a WAR file in OC4J. Open the default-web-site.

Assuming your OC4J home is $J2EE_HOME, the resource adapter is packaged in standalone_ra.rar, and you'd like to name the resource adapter "standalone". Then you need to create a directory named "standalone" in $J2EE_HOME/connectors, copy standalone_ra.rar to $J2EE_HOME/connectors/standalone, add the following to J2EE_HOME/config/oc4j-connectors.xml: <connector name="standalone" path="standalone_ra.

OC4J standalone is the Oracle9iAS Containers for J2EE distribution which can be run outside of the complete Oracle9iAS environment. OC4J standalone is typically used for development and testing purposes, and could be used for simple small scale Web solutions.

Delete existing deployment. If you have previously deployed "foo.war" in TOMCAT_HOME/webapps, then it has been unpacked into webapps/foo/... You must delete this directory and all its contents. On Unix, this can be done with rm -r $TOMCAT_HOME/webapps/foo This process may become easier in the future. A "deploy tool" is on the Tomcat "to-do" list. Note that if you deploy a WAR file in this manner, you do not need to make any changes to server.

OC4J standalone comes with a command line utility, admin.jar. This enables you to perform a set of administrative functions from the command line. Also, you may directly modify the XML configuration files in the OC4J standalone environment.

To instal OC4J standalone, unzip the oc4j_extended.zip file using the archive utility of your choice. The jar utility in your J2SE installation can also be used. To complete the installation of OC4J change to the <install-dir>j2ee/home directory, and issue the following command: > cd <install-dir>/j2ee/home The installation prompts you to enter and verify an administration password, which is used for the administration console command-line tool.

a) To start OC4J using the default configuration files (recommended), which are located in the j2ee/home/config directory. > cd <J2EE_HOME> The server outputs an initialization string with the version number when it is ready to accept requests, for example: Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) initialized

You can stop OC4J by pressing ^c (Ctrl+c) in the window where the process was started, or by using the shutdown command in the admin.jar command-line utility, or by using the process termination command (for example "kill" on UNIX/Linux) for your operating system.

For deploying a Web application like the default-web-app, please read the "Deploying With Exploded Directory Format" section of Getting Started Guide that comes with OC4J. For OC4J 1022, you can set the attribute development to "true" for the orion-web-app in your orion-web.xml file and that will save your generated code in the persistence directory. <orion-web-app deployment-version="9.0.2.0.0" development="true" jsp-cache-directory=".

Yes, create a war file and name it file.war and place in the root directory of your web space (mainwebsite_html or /var/www/html/ ) The contents will automatically be deployed when the JVM is restarted.

Yes. If you wish to deploy only a Web module then you can utilize the default application OC4J is configured with. This is a two step task: First, tell the container about the WAR file to be deployed. Open the <J2EE_HOME>/config/application.xml file in an editor. Add a new <web-module> tag and specify the attributes for your WAR file. Secondly, tell the OC4J HTTP server about the new WAR file and provide a URL to access it. Open the <J2EE_HOME>/config/http-web-site.

In Oracle9iAS Release 2, OC4J is started as a managed process by Oracle Process Management Notification (OPMN). This provides automatic startup, shutdown and death detection functionalities for OC4J processes. For environments which require the use of OC4J as a service, Oracle9iAS should be used. Create a service for the this command file using NT/Win2k Resource Kit. You can use the following Microsoft article how to create a service: http://support.microsoft.com/support/kb/articles/q137/8/90.

Not in this release. All configuration and deployment operations with OC4J standalone are performed by directly modifying it's configuration files. We will be providing a Web based management console that makes use of the latest JMX specifications to perform both configuration and deployment tasks in a forthcoming release.

Assuming your OC4J home is $J2EE_HOME, the resource adapter is packaged in embedded_ra.rar. You need to assemble the resource adapter (embedded_ra.rar) into an application module (EAR file) along with other application components, add the following to the application deployment descriptor of your application module (/META-INF/applicatoin.xml): ... <application> ... <module> <connector>embedded_ra.rar</connector> </module> ..

We can deploy a WAR for the customer upon request. It should be uploaded to /home/username in that case send us an email. Auto-deployment is available by uploading to /home/username/public_html. But keep the following in mind: After deployment, the expanded files will be owned by the user Tomcat runs under, so the client will not be able to edit those files. They can only update them by uploading an updated WAR. Very few WAR's run correctly as uploaded.

This command provides a graceful shutdown of the container. If it does not shut down the container, you can force a rapid shutdown by passing the -force argument, as follows:

Type mvn war:war at the command line. Maven will build the war package for you and place it in the ./target directory. After you have the war installed and expanded, you might want to modify the /WEB-INF/longwell.properties file to match your system settings.

WAR (or "web archive") file is simply a packaged webapp directory. It is created using the standard Java jar tool. You can use <jsp:forward page="/relativepath/YourServlet" /> or response.sendRedirect("http://path/YourServlet").