Filling in SyMBA variables within the top-level pom.xml

While the database holds all experimental metadata, it does not hold the raw experimental data. Instead we chose to keep the raw data separate to reduce the size of the relational database. Create a directory on the computer where you plan to store the data, and then put the details of the machine - and the user that will be the owner of the data - into the fields below, which are present within your-checkout/trunk/pom.xml . These elements will be read by the web interface and stored.

Also included in the variables below are a variety of other items that are required within the web interface. Each variable has a comment stating what the variable is used for. The variable set below are represented once per profile within the pom, and therefore you will need to set the variables specifically for each profile you wish to use.

        <!-- The help email address for your group -->
        <net.sourceforge.symba.webapp.helpEmail>helpdesk@cisban.ac.uk</net.sourceforge.symba.webapp.helpEmail>
        <!-- The name and verison of this software: there are already reasonable defaults, so you don't need to
        change this unless you want to -->
        <net.sourceforge.symba.webapp.softwareName>${pom.artifactId}</net.sourceforge.symba.webapp.softwareName>
        <net.sourceforge.symba.webapp.softwareVersion>${pom.version}</net.sourceforge.symba.webapp.softwareVersion>

        <!-- The class name for the jdbc driver for the SyMBA security database. Should be the same
         as jdbc.driver variable above, unless you are using a completely different database for the
         security database. -->
        <net.sourceforge.symba.webapp.security.driver>org.postgresql.Driver
        </net.sourceforge.symba.webapp.security.driver>

        <!-- jdbc connection details for the SyMBA security database -->
        <net.sourceforge.symba.webapp.security.url>jdbc:postgresql://localhost:5432/symba_security
        </net.sourceforge.symba.webapp.security.url>

        <!-- The username and password for the SyMBA security database. -->
        <net.sourceforge.symba.webapp.security.username>user</net.sourceforge.symba.webapp.security.username>
        <net.sourceforge.symba.webapp.security.password>pass</net.sourceforge.symba.webapp.security.password>

        <!-- The machine name of the remote machine where the data files will be stored -->
        <net.sourceforge.symba.webapp.scp.hostname>localhost</net.sourceforge.symba.webapp.scp.hostname>

        <!-- The full path to the actual directory where the files should reside. The data files will be put directly
          into this directory. -->
        <net.sourceforge.symba.webapp.scp.directory>/your/directory/for/data/</net.sourceforge.symba.webapp.scp.directory>

        <!-- The username and password to use to connect to the remote machine where the data files are stored -->
        <net.sourceforge.symba.webapp.scp.username>user</net.sourceforge.symba.webapp.scp.username>
        <net.sourceforge.symba.webapp.scp.password>pass</net.sourceforge.symba.webapp.scp.password>

        <!-- net.sourceforge.symba.webapp.global.remote.data.store.os MUST be either "unix" or "dos" -->
        <net.sourceforge.symba.webapp.scp.remote.data.store.os>unix
        </net.sourceforge.symba.webapp.scp.remote.data.store.os>
        <!-- In DOS, you need to replace all of the colons in an LSID. Tell SyMBA want to replace
         them with using this variable. This variable is ignored when the scp.remote.data.store.os is set to "unix"
         If you don't provide anything at all and are using "dos", the default will be a double underscore, "__" -->
        <net.sourceforge.symba.webapp.scp.lsid.colon.replacement></net.sourceforge.symba.webapp.scp.lsid.colon.replacement>