The instructions below are temporary instructions to allow early adaptersadopters/testers to be able to build, deploy, and demonstrate the OpenRegistry project in its current state. The instructions below are not a reflection on how the final project may be built, packaged and deployed. The final project may look entirely different.
Info | ||
---|---|---|
| ||
This checklist can be used in conjunction with the instructions below. It was created as part of a test deployment in August 2012.
Also see: https://github.com/UniconLabs/openregistry-springbatch-poc |
Retrieve the Source from Source Control
Step 1 is to retrieve the current source code from source control. Information about source control can be found here. Currently, you'll want to check out trunk.
Warning |
---|
Future steps will refer to the following: |
Modify the Source Files for Your Institution
Step 2 is to locate the openregistry-webapp web app (most likely under $OPEN_REGISTRY_PROJECT/openregistry-webapp). Find the WEB-INF/applicationContext.xml and open it with your favorite text editor. Locate the property "hibernate.dialect" and replace the value with the value for your local database. Example Hibernate dialects can be found on the Hibernate web site.
Build the WAR File
Step 3, assuming you have Maven2 installed, is to cd to $OPEN_REGISTRY_PROJECT and type "mvn clean package install". This will generate a WAR file called $OPEN_REGISTRY_PROJECT/openregistry-webapp/target/openregistry.war. If you don't have Maven2 installed, please install it first.
Set Up Tomcat
Step 4 assumes you have a Tomcat instance set up. OpenRegistry will deploy to other containers, but they have not been tested. Place the openregistry.war in $TOMCAT_HOME/webapps
Step 5 is to set up your database access. You'll need to create an openregistry.xml similar to the one below and place it in $TOMCAT_HOME/conf/Catalina/localhost
Code Block | ||||
---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?> <Context path="/openregistry"> <!-- Turn off tomcat session persistance --> <Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"> <Store className="org.apache.catalina.session.FileStore"/> </Manager> <Resource name="jdbc/MyDataSource" auth="Container" type="com.mchange.v2.c3p0.ComboPooledDataSource" description="OpenRegistry Database" factory="org.apache.naming.factory.BeanFactory" acquireIncrement="5" minPoolSize="5" maxPoolSize="256" maxIdleTimeExcessConnections="900" driverClass="oracle.jdbc.driver.OracleDriver" jdbcUrl="jdbc:oracle:thin:@databaseserver.com:dbalias" user="@@<at:var at:name="username" />@@"@@@username@@@" password="@@<at:var at:name="password@@@password@@@" />@@" maxStatementsPerConnection="37" numHelperThreads="5" testConnectionOnCheckin="true" idleConnectionTestPeriod="300" preferredTestQuery="SELECT SYSDATE FROM DUAL"/> </Context> |
...
Warning |
---|
Assuming your user has the appropriate permissions, the database structure will be created for you. You'll need to populate it with some basic data though (Phone Types, People, etc.) before you can really use it. See Sample Reference Data and Sample Rutgers Specific Reference Data, in that order. As of this writing, only the "Add Person" and "Add Role" use case is complete, thus it assumes information already existscases are mostly complete. The Sample Database Inserts examples can now be added directly via the "Add Person" use case and those examples will probably get out of date compared to any changes to the data model. |
Start Tomcat & Test
Assuming you have Tomcat running on port 8080, start up Tomcat ($TOMCAT_HOME/bin/startup.sh or $TOMCAT_HOME/bin/startup.bat) and point your web browser to:
Code Block |
---|
http://localhost:8080/openregistry/addPerson.htm
|
or
Code Block |
---|
http://localhost:8080/openregistry/addRole.htm?personKeysorPersonKey=52&roleInfoKey=21 |
(personKey sorPersonKey and roleInfoKey are dependent on what's in your database)
Run the Demonstration War from within Intellij IDEA
If you use Intellij IDEA for Java development, you can run the demonstration code from within the IDE, making it easier to debug and explore the code. See Running from Intellij IDEA for setup instructions.