Java EE Deployment
To deploy a Java EE application or module:
- Make sure that the Java EE application or module does not require additional resources such as named JDBC data sources or JMS queues. If the application requires external resources, you must configure them in the target Oracle WebLogic Server domain before deploying the application.
- Copy the archive file or exploded archive directory for the Java EE application or module into the
/autodeploy directory
of the examples server domain directory. By default, this is located in
ORACLE_HOME/user_projects/domains/wl_server/autodeploy .
(Where ORACLE_HOME represents the directory you specified as the Oracle Home when you installed WebLogic Server; for example, C:\Oracle\Middleware\Oracle_Home .)
- Start the Examples WebLogic Server instance.
- Access the application using either a Java client or the configured URI for the application.
What's Going On?
When running in development mode, Oracle WebLogic Server automatically deploys applications copied into the the /autodeploy subdirectory of the domain directory. Auto-deployment is a simple and quick method of deploying
an application for testing or evaluation. See Auto-Deploying Applications in Development Domains.
Additional Resources
|
JSP/HTML Deployment

To deploy a simple JSP or HTML file:
- Make sure your JSP file does not reference a tag library or other
external resources -- such resources require additional deployment steps
that are beyond the scope of these Fast Track procedures. HTML files
do not have this restriction.
- Copy your JSP or HTML file into the
EXAMPLES_HOME/
examples/build/mainWebApp
directory.
(Where EXAMPLES_HOME is the directory in which the WebLogic Server code examples are configured. For example,
ORACLE_HOME/wlserver/samples/server .)
- Start the Examples WebLogic
Server instance.
- In a Web browser, request the JSP or HTML file using the following URL:
http://localhost:port/myFile
where:
localhost
is the host name of the machine running Oracle WebLogic Server
port
is the port number where Oracle WebLogic Server is listening for requests (7001 by default)
myF
ile is the full name, including the .jsp or .html extension, of the JSP or HTML file you copied in step 2
What's Going On?
The JSP or HTML file has been automatically deployed from a directory preconfigured to target
the Examples Server. mainWebApp is deployed by default and you can place your own JSP and HTML files into the mainWebApp exploded directory in order to quickly view or test them.
Additional Resources
|
System Administrator Tools

System Administrators can use the following tools to get started:
- Administration Console
The Administration Console is a browser-based Web application
that allows you to configure and monitor your Oracle WebLogic Server
domain, server instances, and running applications and their associated
resources. You can also use the Administration Console to create new
server instances and clusters and tune application descriptors. The
default administrator username is weblogic, and the password
is set when the WebLogic Server Examples domain is configured post-installation.
More information.
Click here to start the Administration
Console. After you log into the Administration Console using the credentials
you provided during installation, click the
Help button or "How do I ...?" links for additional information.
- Configuration Wizard
Use the Oracle WebLogic Server Configuration Wizard to create
new domains and to create templates for automating domain configuration.
More information.
|