-
Notifications
You must be signed in to change notification settings - Fork 5
Updates 27th September 2014
Databases are periodically updated by developers to enable more functionality to work with ROMS and to add new dummy content.
When databases are updated they need to be updated on your local environment. to do this you need to locate the files on your hard drive. You can do this in NetBeans by going to FILES > ROMS > Database and right-clicking, then Properties.
In the Properties panel you'll see a path to the database. Click on the button with three dots (...) to copy the path, which looks something like /Users/you/NetBeansProjects/ROMS/database/000.sql.
Then, open a Terminal or Command Prompt window and type Source and paste the path. Do this for each database. The databases need to be updated in a specific order as below:
- 001
- 001-dummy
- 002
- 003
- 003-dummy
- 003-cleanup
- 004
- 004-dummy
Certain properties need to be defined using JNDI that the application server can use to lookup. These properties are defined below.
To set-up the JNDI Custom Resource, using the GlassFish administration console:
Navigate to JNDI -> Custom Resource page. Click on the new button and define the following:
JNDI Name: jndi/_edifice_property Resource Type: java.util.Properties Status: Enabled Click on the "Add Property" to add the properties described below. The following Properties are used in the application:
edifice.url
Description: This is the URL used to access the server. The reason for this is that the GlassFish server only listens on localhost. Using HTTP Request object to retrieve the URL will result in "http://localhost:8080" or whatever the GlassFish server listens on. On local, i.e. your, development server, you can leave it out. On external dev/production servers, it needs to be set to "https://edifice.rbc-lhc.org.uk:9443" for development server and "https://edifice.rbc-lhc.org.uk" for production server.
Example: http://localhost:8080
security.salt
Description: This is the initial security salt used to create security tokens/hash. If this is left out, a default security salt is used. However, this should be set on both development and production server, and should be different, random and changed on a regular interval.
Example: sdlkfjitu8bndlkjdfs901 but please do not use this on any development or production servers.