Context entries

The AstroGrid Community WebService uses JNDI entries to lookup the following resources.

  • The service identifier
  • The database configuration

Community identifier

The Community WebService needs to know the IVO identifier for the Community service. This identifier forms the base for the IVO identifiers used to access objects within this Community service.

For example, if the CommunityIdentifier is set to

  • org.astrogrid.test.xyz
then the IVO identifier for the service would be
  • ivo://org.astrogrid.test.xyz
and the IVO identifier for an Account abc in the Community service would be
  • ivo://org.astrogrid.test.xyz/abc

In order to make it available to the WebService, the Community identifier needs to be configured in a JNDI Environment property in the server configuration or WebApp context.

<Environment
    name="org.astrogrid.community.ident"
    type="java.lang.String"
    value="org.astrogrid.test.xyz"/>

When the WebService is installed, the install toolkit reads the Community identifier from the install.properties file and automatically configures the JNDI Environment property in the Tomcat configuration.

# Local community name.
# Change this property to set the service identifier.
org.astrogrid.community.ident=org.astrogrid.test.xyz

The install toolkit contains test data files for the following communities :

  • Cambridge (ivo://org.astrogrid.test.cam)
  • Leicester (ivo://org.astrogrid.test.le)
  • Edinburgh (ivo://org.astrogrid.test.roe)

Database resource

The Community WebService needs access to a local database to store the Community data.

In order to make it available to the WebService, the database needs to be configured in a JNDI Resource entry in the server configuration or WebApp context.

<Resource
    name="jdbc/org.astrogrid.community.database"
    type="javax.sql.DataSource"
    auth="Container"/>

When the WebService is installed, the install toolkit automatically configures the JNDI Resource property in the Tomcat configuration.

Database properties

In addition to the database Resource entry, the database properties need to be configured in a ResourceParams entry in the server configuration or WebApp context.

<ResourceParams
    name="jdbc/org.astrogrid.community.database">
    <parameter>
        <name>url</name>
        <value>jdbc:hsqldb:/var/astrogrid/org.astrogrid.community</value>
    </parameter>
    <parameter>
        <name>driverName</name>
        <value>jdbc:hsqldb:/var/astrogrid/org.astrogrid.community</value>
    </parameter>
    <parameter>
        <name>driverClassName</name>
        <value>org.hsqldb.jdbcDriver</value>
    </parameter>
    <parameter>
        <name>username</name>
        <value>sa</value>
    </parameter>
    <parameter>
        <name>password</name>
        <value/>
    </parameter>
</ResourceParams>

When the WebService is installed, the install toolkit reads the database location from the install.properties file and automatically configures the ResourceParams entries in the Tomcat configuration.

# Database files location.
# Change this property if you want to relocate the database files.
database.home=/var/astrogrid/community

The WebService needs to have read/write access to the database files. Make sure that the system account that Tomcat runs as can read and write files in this directory.