phgrid wiki

GIPSE Service Installer

 

GIPSE Service Installer Instruction Set

Prerequisites:
 
Java: Jdk 1.5 or greater

Ant: apache 1.7 or greater

Globus: ws-core 4.0.5 or greater

Tomcat:  5.5.27 or 6.0

Additional prerequisites for building:

svn:  subversion 1.4 or greater


Configuring, Building, Deploying Source:

1. Download service package (source)

Create a temporary directory and use the subversion command

svn co http://phgrid.googlecode.com/svn/GIPSEServiceInstaller/trunk

2. Configure gipseinstaller.properties

Rename the gipseinstaller.properties.example file to gipse.properties. Using your preferred text editor, modify the following properties with the values appropriate for your environment:

properties.list=gipseservice.properties
prop.dir=props
gipseservicesource.dir=serviceSrc
svnServiceURL=SVN URL OF GIPSE SERVICE

Update the names of the properties files that will be needed to build the given gipse service (example, the GIPSE Biosense service needs gipse.properties and the GIPSE Poison service needs gipsepoison.properties and npds-ws-client.properties) if there is more than one properties file, use a comma (,) to separate the file names.  Also, update the svn url of the service you wish to build and deploy.

3. Place necessary properties files (as defined by properties.list) in the "props" directory

4. Compress folder up for deployment (optional)

5. Build and Deploy service

You can build deploy the service using:

"ant all"

This will download the service from the specified url, place the specified properties files into the appropriate location, build the service, and deploy it to globus and tomcat.

If you need to modify the deployment, the targets can be modified in the build file.


Recent site activity

Disclaimer

Please note that as part of the collaborative nature of this initiative, the content in this site may include submissions from employees or contractors of the Centers for Disease Control and Prevention/the Agency for Toxic Substances and Disease Registry. The opinions / findings are those of the submitter(s), and do not necessarily represent the official position of the Centers for Disease Control and Prevention/the Agency for Toxic Substances and Disease Registry.

All submitters must agree and adhere to the Code of Conduct posted on this site. All submissions are examined in a timely fashion to assure compliance with the stated code of conduct. Those not found to be in compliance are promptly removed.