"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Setting up your development environment

Download build and Install

VGL and Auscope portal shares the same underlying portal-core framework and the architect for both platform are similar following the same MVC design pattern.

Install portal-core into your maven repository following this guide.

Follow the same procedure as the AuScope Portal setup guide but replacing the GIT repository with https://github.com/AuScope/VEGL-Portal.git to build your VGL portal.

Because VGL uses MySql database for persistant storage, MySQL drivers( MySQL Connector J) need to be installed on your machine. There are various ways to do this and it depends on your configuration and set up but as long as the driver is found on the classpath, VGL portal will pick it up.

http://dev.mysql.com/downloads/connector/j/

Configuration

In order for VGL to connect to the underlying mySQL database and access the cloud, the following properties files must be completed to provide database and cloud credentials.

config.properties

# Replace <HOST> with your machine hostname
INDEX-KF.googlemap.key=<Google map key. You may copy the same key as the other configuration there>
INDEX-KF.jdbc.url=<An URL to points to the appropriate mysql database>
INDEX-KF.erddapservice.url=http://siss2.anu.edu.au/erddap/griddap/
INDEX-KF.smtp.server=<A valid SMTP server for VGL to use a relay>
INDEX-KF.localStageInDir=<A local directory that host data files where VGL has write access to>

env.properties

Make sure all mandatory information are filled in.
env.jdbc.user=<USER>
env.jdbc.password=<PASSWORD>
env.outputgeonetwork.user=<GEONETWORK USER>
env.outputgeonetwork.password=<GEONETWORK PASSWORD>
env.nci.ec2.accesskey=<env.nci.ec2.accesskey>
env.nci.ec2.secretkey=<env.nci.ec2.secretkey>
env.nci.storage.accesskey=<env.nci.storage.accesskey>
env.nci.storage.secretkey=<env.nci.storage.secretkey>
env.nectar.ec2.accesskey=<env.nectar.ec2.accesskey>
env.nectar.ec2.secretkey=<env.nectar.ec2.secretkey>
env.nectar.storage.accesskey=<env.nectar.storage.accesskey>
env.nectar.storage.secretkey=<env.nectar.storage.secretkey>

I will make special mention to the following fields
  • env.jdbc.user - this is the username for accessing the mysql database which is pointed to in the config.properties file
  • env.jdbc.password - this is the password for accessing the mysql database which is pointed to in the config.properties file
  • env.outputgeonetwork.user - this is the username for login into the geonetwork registry to submit completed job
  • env.outputgeonetwork.password - this is the password for login into the geonetwork registry to submit completed job
All other keys should be provided in the cloud credentials.

SVN Security Tip for passwords

Once you have edited config.properties and env.properties, these 2 files are going to appear each time you commit. You will run the risk of checking in the passwords into the repository and breach security. One tip to help with this would be to use svn changlist
svn changelist ignore-on-commit file-you-want-to-add

In tortoise, you can:

  1. right click on any folder
  2. select tortoise svn
  3. select Check for Modification
  4. Right click on the properties file
  5. Move to Changelist
You can either create your own, eg setup (as below) or use the reserved changelist called ignore-on-commit.

Topic revision: r8 - 31 Jul 2014, JoshVote
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).