A standalone OC4J application server is an alternative to the embedded OC4J test environment. Deploy applications to a standalone OC4J application server through a connection, as you would to deploy to Oracle Application Server or some other production application server.
JDeveloper uses the OC4J administration console command-line tool,
admin.jar
, to deploy to the standalone OC4J.
If you are deploying your applications to a standalone OC4J server, you'll need to start it, and pass it any options, from the command line by entering:
java -jar oc4j.jar
When you deploy an application directly to standalone OC4J, the settings
you specify in the deployment profile are used to update the OC4J server
configuration files listed below. The WAR and EAR named in the
deployment profile become the web module directory name and application
directory name, respectively, in <oc4j_install>
/j2ee/home/applications
.
These OC4J configuration files are updated by deployments to standalone OC4J:
server.xml
An OC4J configuration file. This file names all the installed J2EE
applications, including the application for the shared ADF UIX
installable resources. It also defines any *-web-site.xml
files that are used for the web modules. There is only one server.xml
for a running OC4J instance. The locations of the UIX runtime dependent JAR
files are also specified in this file.
http-web-site.xml
An OC4J configuration file. This file declares the port number that
OC4J is using and maps URLs to the web modules, including the
dedicated UIX installable resources web module. A URL directed to
this port number is routed to the appropriate web site for the web
module. Oracle recommends using a single *-web-site.xml
file named http-web-site.xml
, which contains many web
module definitions. The location of http-web-site.xml
is determined by server.xml
, but it is typically in the
same directory as server.xml
. The file
http-web-site.xml
changes frequently as web modules are added
or reconfigured.
About J2EE Deployment
About OC4J
About OC4J Data Sources
About the Oracle Application Server
About
the OC4J Application Directory Structure
Working with the OC4J Application Servers
Deploying to the Oracle Application Server or Standalone OC4J
Packaging and Deploying J2EE Applications
Working with the Standalone OC4J Application Server
Creating a Connection to Standalone OC4J
Copyright © 1997, 2004, Oracle. All rights reserved.