Table of Contents

Installation

Dependencies

Hardware Requirements

For basic installations with limited users and data, the entire EDAS2 application may be run on a single, modern, desktop-class computer

Database Server Requirements (Dedicated)

Minimum Requirements:

Recommended Requirements:

Software Requirements

Note: Seam is theoretically supported by the Apache Tomcat Java Server, and J2EE servers other than Jboss. However, only Jboss is supported by this project at this time. You are encouraged to review the Seam documentation for getting Seam applications to run on other application servers. Also note that Jboss 4.2.X and Java 5 are the supported versions at this time. Later versions of Jboss and Java have known issues.

Database Deployment Procedure

The following instructions are intended to support a small, testing instance of EDAS2. Database administrators will want to adjust these instructions for larger installations.

This guide assumes that you have an instance of Oracle database running. Installation of Oracle is outside the scope of these documents, but here are some links that may be helpful for getting Oracle XE running.

Note that for XE installations you will probably want to run the APEX interface on a port other than 8080 as it will conflict with any Java application servers that you may run on the same machine.

Debian-based Linux (Ubuntu)

You may download version 0.5 of the database creation scripts here: http://www.edas2.com/filemgmt/index.php?id=2

Setting up the EDAS2 Database:

1. Unzip edas2-db.zip into a custom folder, open a command prompt window and change the current path to that folder.

2. Connect with DBA privileges to the Oracle instance by issuing the following command:

sqlplus <dba_user>/<password>@<instance>

where:

3. Create data tablespace:

EDAS2_DATA 256MB AUTOEXTEND ON

Issue the following command and the SQL> prompt to create the tablespace: 

CREATE TABLESPACE EDAS2_DATA DATAFILE ‘<data_file_path>/edas2_data.dbf’ 
SIZE 256M AUTOEXTEND ON NEXT 10240K MAXSIZE 32767M 
LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

where:

4. (Optional) Create indexes tablespace:

EDAS2_INDEXES 256MB AUTOEXTEND ON (optional)

Issue the following command and the SQL> prompt to create the tablespace: 

CREATE TABLESPACE EDAS2_INDEXES DATAFILE ‘<data_file_path>/edas2_indexes.dbf’ 
SIZE 256M AUTOEXTEND ON NEXT 10240K MAXSIZE 32767M 
LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

where:

It is recommended that the indexes tablespace data file to be stored on a different mounting point than the data tablespace data file for performance reasons.

5. Create EDAS2 database user with default tablespace EDAS2_DATA by issuing the following scripts at the SQL> prompt:

CREATE USER EDAS2 IDENTIFIED BY <edas2_password>
DEFAULT TABLESPACE EDAS2_DATA TEMPORARY TABLESPACE <temp>
ACCOUNT UNLOCK;
 
GRANT QUERY REWRITE TO EDAS2;
 
GRANT UNLIMITED TABLESPACE TO EDAS2;
 
GRANT CONNECT TO EDAS2;
 
GRANT RESOURCE TO EDAS2;

where:

6. Close the current SQLPlus session.

7. Connect with EDAS2 account to the Oracle instance by issuing the following comand:

sqlplus EDAS2/<edas2_password>@<instance>

where:

8. Run the scripts in the proper order, by issuing the following commands at the SQL> prompt:

@SCHEMA/SCHEMA.SQL
 
@SEQUENCE/SEQUENCE.SQL
 
@seed/seed_org.SQL
 
@seed/seed_a.SQL
 
@seed/seed_b.SQL
 
@seed/seed_c.SQL
 
@seed/seed_d.SQL
 
@seed/seed_e.SQL
 
@seed/seed_f.SQL

9. (Optional) Move the created indexes in EDAS2 schema to the EDAS2_INDEXES tablespace, in case the tablespace was created in step 4, by issuing the following command at the SQL> prompt:

@scripts/move_indexes.SQL

10. Close the current SQLPlus session.

Server Deployment Procedure

Setting up the JBoss and Java:

Note: This guide assumes that you know how to install JBoss and Java successfully on your Windows or Linux operating system without further assistance.

Please refer to the following table and confirm that you have installed the correct version of JBoss and Java.

JBoss Version Java Version
4.2.2 Standard Edition (SE) 5 or 6
4.2.3 Standard Edition (SE) 5 or 6

1. Set ** JAVA_HOME **

After you have successfully installed the correct version of Java and JBoss, you need to set the JAVA_HOME environment variable to point to the directory where you installed Java. In Windows, this can be accomplished by going to the control panel and clicking on the System icon. Once you are on the System Properties, you can go to the Advanced tab and click on the Environmental Variables button to add a new system variable for JAVA_HOME (see Figure 1).

In Linux, you can set JAVA_HOME for a single user by modifying the .bash_profile file for the user or set it globally for all users by modifying the /etc/profile or /etc/bash.bashrc file. It is important to note that you must set JAVA_HOME to point to the directory that you installed Java. For instance, JAVA_HOME =C:\Program Files\Java\jdk1.5.0_12.

Figure 1 – Setting JAVA_HOME in Windows

2. Set the Java heap size for JBoss.

You can configure the JBoss Java heap size by modifying the existing JAVA_OPTS variable in run.bat (see Figure 2) (Windows) or run.conf (Linux). For instance, the following line JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m would configure the JVM to allocate a minimum of 128MB of RAM and a maximum of 512MB of RAM for JBoss usage. Please refer to the hardware requirements for setting this value to the minimum or recommended requirements and change it accordingly.

Note: If your machine has only 1 GB of RAM, set Xmx (maximum memory size) to 512m. If your machine has 2+ GB of RAM, set Xmx (maximum memory size) to 1024m .

Figure 2 – Configuring JVM heap size in JBoss for Windows (run.bat)

3. Unzip the distribution

After you have properly configured your environment for JBoss, you need to unzip the edas_v_0_5_java?_win.zip or edas_v_0_5_java?_linux.zip file into a custom directory.

4. Move the files to the deployment directory

Copy the edas2.war directory into the following directory under JBoss: {directory of JBoss installation}\server\default\deploy

5. Copy the deployment XML file

Copy the edas2-prod-ds.xml file into the following directory under JBoss: {directory of JBoss installation}\server\default\deploy

6. Edit the deployment XML file

Open the edas2-prod-ds.xml and modify the connection URL, username, and password parameters according to the settings of the database that you configured in the section Database Deployment Procedure. See Figure 3 for a sample.

Figure 3 – edas2-prod-ds.xml sample file

7. Copy the JDBC jar file

Copy the ojdbc14.jar file into the following directory under JBoss: {directory of JBoss installation}\server\default\lib . This step is optional if your existing installation of JBoss already contains this file.

8. Create the report directories

Create a directory on your file system to write reports into. Inside this directory create an input and output folder. Give full read-write permissions to the main folder and sub-folders. Open the file components.xml located at {directory of JBoss installation}\server\default\deploy\edas2.war\WEB-INF . Update the tmpFolder and reportFolder properties under the component report with the path of sub-folders that you just created (see Figure 4).

Figure 4 - Sample components.xml in the folder edas2.war\WEB-INF

9. Test deployment

After you have completed all the previous steps, you are done with the basic configuration of the Oracle database and JBoss application server. You can test this configuration by starting JBoss in Windows as a service or running the run.bat file from the command line. Alternatively, you if you have installed JBoss in Linux, you can start Jboss by running the run.sh script from the command line. If your JBoss starts successfully and you can copy the following URL http://localhost:8080/edas2 on a web browser and you should be able to see the login screen for EDAS2 (see Figure 4). If do not see the login screen for EDAS2, please go through all the steps again to make sure that you have completed them correctly.

Figure 5 – EDAS2 login screen

EDAS2 Administration

1. Set up Google Maps

If you are planning to access EDAS2 from a different URL than http://localhost:8080/edas2 and creating a new custom URL for multiple users, you need to go to http://code.google.com/apis/maps/signup.html and generate a key for EDAS2. Save this key and open the components.xml file located at {directory of JBoss installation}\server\default\deploy\edas2.war\WEB-INF (see Figure 5). Change the key property under the gmap component to equal the key you generated from Google.

Figure 6 - Sample components.xml in the folder edas2.war\WEB-INF

Note: If you don’t want to replace the existing Google Map Key, you will have to install the Apache Server, configure it to do http forwarding to JBoss, and allow users to access EDAS2 from Apache rather than JBoss.

2. Login

To login into EDAS2, you must use ‘admin’ for the username and ‘Admin2008’ for the password. Currently, EDAS2 does not support multiple users. The username and password of the default user cannot be changed.

3. Edit Organization Information

After you have logged in, you need to configure your own organization settings. You may do so by choosing the Administration tab on the menu and clicking on the Organization menu item. Once you have clicked on the Organization menu item, you should see a management screen for the default Organization (see Figure 6). Click on the ‘Edit’ button and change the values to match your organization’s values.

Figure 7 – Organization Management Screen

Download this page in Open Office format

Export page to Open Document format