Elements Web Application
Overview
The Elements web application is a J2EE web application. The application provides user session management,
the Elements web user interface, and supports the Elements user applications.
Database Connectivity
The application communicates with the database using JDBC drivers. This application uses only the OCI JDBC driver
and requires the Oracle client software to be installed on the web server.
Directory Structure
The following subdirectories always appear under the ee application directory, and are required
components of the application.
- css
- Contains the cascading stylesheets. The look and feel of the html user interfaces is mainly controlled
through the use of cascading stylesheets.
- downloads
- Contains additional client installation programs such as the Java runtime, and SVG plugin. Any
third party software that is a prerequisite to running the web application should be placed here.
- images
- Contains images and icons for the applications.
- script
- Contains JavaScript files for the application.
- tmp
- Contains temporary files generated by the application.
- WEB-INF
- Protected directory containing license files, configuration files, and application executable files.
See web.xml section below for addtional information.
- xslt
- Contains xslt stylesheets used by the application. These stylehseets may be edited through the html user
interface.
The following application specilization subdirectories may appear under the ee application directory.
- bea
- cadm
- cpic
- dars
- DCGS
- dod5000
- dodaf
- elements
- FCS
- feaf
- MethodologyA
- MethodologyM
- Zachman
You may extend the Elements web application by adding specific content. The general pattern for this is to add
a subdirectory to contain any static content, and then provide a link into this content through the Desktop Sections of the home page.
URL Conventions
The webapplication uses a URL structure which resembles the nature of the information requested.
For example
http://localhost:8080/ee/request/filter?id=1
Where...
- http://localhost:8080
- The protocol (http), the server (localhost) and the port the server is using for the protocol (8080).
- /ee
- The name, and top level, of the web application, this is a part of all requests, and is normally ee.
- request
- This maps the request to a special processing area of the web application. Common request handlers are:
- filter
- folder
- page
- chart
- elementForm
These handlers are followed by the query string portion of the url. The id parameter is almost always included,
and allows a request for a uniquely identified object in the system.
For example
- http://localhost/ee/request/elementForm?id=225
- Displays a detail report for the element which
has an element id of 225.
- http://localhost/ee/request/filter?id=2
- Displays the result of executing a filter with a named text id of 2.
Note that for some request handler types (folder, and filter) the display results can
be significantly altered by adding an "xform=" parameter. When "xform=" is not present
a default transform is used.
- http://localhost/ee/request/filter?id=2&xform=itemized
- Displays the result of executing a filter with a named text id of 2, and
outputting the result through an xslt stylesheet named "itemized".
Additional Configuration
There are addtional configuration options in the web.xml file located under the WEB-INF directory. These items are not adjustable
through the configuration utility. Most of the items
in this file should not be adjusted but the following items may be changed as needed.
Session timeout.
<!-- Session configuration -->
<session-config>
<session-timeout>30</session-timeout>
</session-config>
- The session timeout value is specified in minutes. The default value is 30 minutes. After a user has been inactive
for at least the amount of time specified by the session-timeout, the users session will be terminated, and they
will automatically be logged out.