GENI Aggregate Manager

Source Code Compilation Guide

Download Code

Access to our SOAP-based GENI Aggregate Manager is available via our Subversion repository. Please install the subversion package for your system and download the code from our SVN repository using the commands shown below.

For Users: Compile Code in Unix Terminal

If you just want to compile and run the code under Unix terminal, you can do without NetBeans.

First of all, set up the following env variables in your system.

Compile the code in Unix terminal.

For Developers: Load and Compile as NetBeans Project

The software is intended to be maintained and developed using the NetBeans IDE. You will need to download and install NetBeans with Java Web support for your system from http://www.netbeans.org.

Launch the NetBeans IDE and open the AggregateWS project. This will be a directory located beneath the /usr/local/aggregate directory that was created when you ran the svn export command above, as shown in the example dialog box below:

In order to deploy the Aggregate Manager as an Axis2 service, you must build an .aar (Axis Archive) file. To do this, select the 'axis2-aar' build target using the same process that you used to run wsdl2java:

• Click the 'Files' tab.
• Click the triangle before 'AggregateWS' to show the files — you should now see a file called build.xml.
• Right-click on this file, select 'Run Target', then 'Other Targets', and finally 'axis2-aar'.

The screenshot below illustrates this process:

The 'Output' tab should show 'BUILD SUCCESSFUL' and give you the location of the .aar file that was just built. The code is now compiled and the .aar file can be deployed to any server which is running Apache Axis2 (we will explain how to setup the server in the next section):

Next Steps

Congratulations, you have compiled the Axis2 Web Service and are ready to proceed with setting up the server side. If you modify the source or WSDL file, you can use the procedure above to create a new .aar file. You can also modify the build targets so that you can deploy the .aar file directly to your server instead of having to deploy it manually.

Please see the Server Deployment Guide for information on how to proceed.