Website Properties Page
Oracle Application Server Tips by Burleson
The Website Properties Page contains
parameters found in the default-web-site.xml and the global-web-application.xml
<!DOCTYPE web-site PUBLIC
"Orion Web-site" "http://xmlns.oracle.com/ias/dtds/web-site.dtd">
Oracle9iAS Containers for J2EE Web Site">
application="default" name="defaultWebApp" root="/j2ee" />
<default-web-app application="default" name="defaultWebApp"
root="/j2ee" /> <web-app application="transtrace" name="transtrace"
root="/transtrace" /> <web-app application="default" name="dms"
This file correlates directly to the
application/url mapping in the Web Properties Page for this
Figure 8: OC4J Web Properties Page.
Here are the current URL mappings
supporting this container. If you select the application ?Name?
link you are taken to the Web Module Page for that application.
Here you will find some performance statistics and a list of the JSPs and Servlets that support the application, along with some
performance statistics. You can select one of the JSPs or Servlets
to get additional details about that particular item. At the
bottom of the page is the Administration section for configuring the
Web Module, including adding filters, environmental variables, or
editing the orion-web.xml file.
Figure 9: Application Web Module Page
JSP Configuration Page
Next, is the JSP Configuration Page.
Returning to the OC4J Home Page, select the JSP Container Properties
in the Administration Section. These parameters apply to all JSPs
executed in this container. All of these parameters are in the
global-web-application.xml file and were discussed in detail in
Figure 10: OC4J JSP Container Properties
Selecting Advanced Server Options
brings you to a page that allows direct editing of the configuration
files within EM. Once you apply the changes to the file, it will
automatically update the repository with the changes. All of the
files are actually located in the Server Root directory. They
Use this method of updating these files only
if you cannot include or modify a parameter in another part of the
Administration Section. If you directly edit the file and make an
error in format or structure, the application server may not be able
to restart after applying the changes.
Data sources are normally connections
to a database. They can be connections to any persistent storage.
Data sources are registered with the Java Naming and Directory
Interface or JNDI, locations where components can find the sources.
A data source can be defined at the application level to support a
specific application or at the container level, available to any
application running in that container. Normally, the EAR file
contains a data-source.xml file that defines the required data
sources. Data sources listed in the Data Source Page off the OC4J
Home Page are available to any application running inside the
container. If you select the application Name link, you will be
taken to the application page, where you will find another Data
Source Page relating only to that specific application.
Figure 11: OC4J Data Source Page.
Although data sources are normally
defined within an Enterprise Application Archive (EAR), you can also
define a new data source from this page by selecting the Create
button or by selecting the radio button of an already-defined data
source and selecting the ?Create Like? button. Creating a new data
source within the schema of an already-defined data source using the
?Create Like? button opens the Create Data Source Page, with many of
the data fields already filled in, including the data source class
file, jdbc driver, url, and the username and password. You must
enter a unique name for the data source. In an Oracle database, a
user has a schema, so you can skip the entry for schema and just use
the user name. The only remaining required field is the JNDI
Location field. The location must be identified so that the
container can bind the class instance to the JNDI name space. More
on JNDI later in this chapter.
The Security link takes you to the
container Security Page. OC4J defines security through Users,
Groups, and Roles. These will be discussed in greater detail in
Chapter 12 Oracle9iAS Security. Security parameters are defined in
the jazn-xml file, located in the Server Root directory along with
the jazn-data.xml file.
The JMS Provide Page allows you to
define or remove a Java Message Service provider. As discussed in
the last chapter, JMS allows for asynchronous execution of messages
by Message EJBs. Oracle uses the Advance Queuing capabilities of
the Oracle Database to support the JMS API. You can also implement
third party JMS support from this page. We will leave the
implementation of JMS to the developers, just note that this is the
page where you can define JMS providers.
Global Web Module
The last Administration link is the
Global Web Module page. Here, you define and configure parameters
that apply to all web applications. These parameters define how the
web component will handle certain types of files and are located in
the global-web-application.xml and orion-web.xml files. You can
modify or define mappings, filtering, environmental, and security
parameters from this page.
Figure 12: Global Web Module Page.
This completes the tour of the OC4J Home
Page. When using OC4J stand-alone containers, you must configure
the container using the xml files. In Oracle9iAS, you should always
configure OC4J using Enterprise Manager to insure that the
repository and the flat xml file are in synch. Many of the OC4J
parameters can be set for both the container and for individual
applications. To configure container parameters, select the
Administration Pages from the OC4J Home Page. To configure
parameters for a specific application, select the application link
from the OC4J Home Page and then select the appropriate
configuration page in the application?s Administration section.
This is an excerpt from "Oracle
10g Application Server Administration Handbook" by Don Burleson
and John Garmany.