By default, JDeveloper runs applications in the JDeveloper embedded
OC4J server to enable testing and debugging before deploying to a target
application server. JDeveloper also supports deployment to standalone OC4J instances
that are not within the Oracle Application Server. JDeveloper
establishes connection with a standalone OC4J instance via the J2EE administration
console command-line tool, admin.jar
.
To do this, you must first provide the connection information to an OC4J instance
to which you want to deploy.
Important: If you plan on deploying your applications directly to an Oracle Application Server, JDeveloper lets you can create a connection to Oracle Application Server via local or remote Distributed Configuration Management (DCM). See also About Deploying on Oracle Application Server.
To create a connection to an OC4J instance:
admin
user to authenticate
the connection. This information was specified when OC4J was installed. Default:
admin/manager
. connection.xml
file.Notes:
http://localhost:8888
principals.xml
file on Oracle Application Server. For more information, refer to the "Oracle Application Server
Containers for J2EE User's Guide" Part Number B10322-01
which is provided with the Oracle Application Server documentation library.
Creating and Deploying a J2EE EJB Module
(EJB JAR) to OC4J
Creating and Deploying a J2EE Web Module Deployment
Profile (WAR) to OC4J
BC4J Deployment Prerequisites for
OC4J Deployment
Deploying a BC4J Web Application to OC4J
Deploying BC4J as an EJB Session Bean to OC4J
About the Embedded OC4J Server