Strust129DemoApp

Struts 1.2.9, Spring 2.5.6 Jharks Workflow Survey Engine Demo Application

1 Download the .war file jharks-demo-webapp.war located under the jharks-workflow-survey-engine folder.

2 The jharks-demo-webapp has currently been tested for compatibility on the following application servers. We will continue to test and expand to other platforms:

• JBOSS v5.1.0

3 The jharks-demo-webapp has currently been tested for compatibility on the following database engines. We will continue to test and expand to other relational DB engines:

• Oracle 11G

Installing jharks-demo-webapp on JBOSS 5.1.0

1 Create a datasource file within JBOSS. __JBOSS does a pretty good job of providing reference examples for datasource configuration files across database engines. These files are located in <install-location>:\jboss-5.1.0.GA\docs\examples\jca. Check out the oracle-ds.xml example file.

You want to create a datasource file that matches the root context of the application you are going to deploy to JBOSS. For this example the datasource file names should be jharks-demo-webapp-ds.xml.

The content of the file should be similar to:

<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
   <jndi-name>jdbc/jharks-demo-webapp</jndi-name>
   <connection-url>jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=host1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=DEVORA11)))</connection-url>
   <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
   <user-name>appowner</user-name>
   <password>dev</password>
   <use-java-context>false</use-java-context>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
</local-tx-datasource>
</datasources>

Notes:

• Make sure your connection String is appropriate. The example above is for a clustered Oracle environment. If you have a single Oracle node your connection string would be simpler and only refer to one node.
• Make sure you Oracle Account (username) and password exist and the values in the jharks-demo-webapp-ds.xml are * Also note that jharks supports this concept of specifying a different schema owner for the user that actually owns the database objects the supplied DB scripts create.

2 Run the Oracle database scripts to create the supporting DB tables and populate with example and reference data to support the example application.

Notes:

• Also note that jharks supports this concept of specifying a different schema owner for the user that actually owns the database objects the supplied DB scripts create. There are some organizations that require a database account pair to be created (one account is the schema owner, while the other account is used for access). This forces the owning user's schema to be included in SQL scripts or a requirement to create public synonyms. Jharks handles the structure of the JDBC queries appropriately based off the setting database.schema in the ApplicationResources.properties file. This supplied demo app assumes a database account for access that owns the database objects, therefore the value is set to an empty string "". If you need to account for the previous scenario, you would need to access the jharks-demo-app source and recompile with the appropriate database.schema value. The current maven build by jharks uses filters to set the value appropriately across domains. You could change filter value appropriately or replace the filter placeholder with the actual value directly in the .properties file.

3 Copy the jharks-demo-webapp.war to the <install_location>jboss-5.1.0.GA\server\default\deploy directory and restart the JBOSS application server.

4 Try hitting the url http://<your_serer_name>:<jboss port="">/jharks-demo-webapp/home.do.