ALMA Science Archive IVOA web services.

The ALMA IVOA services require a properties file to configure the various service URIs that the services will use to locate each other. This is done via a Registry service that will map the service URIs to actual URLs.

The properties file, org.opencadc.alma.properties, is required to be in the ~/config/ folder. This file contains the Service URIs (identifiers) that will be looked up in the Registry to obtain an actual URL.

org.opencadc.alma.properties

  almaDataLinkServiceURI=ivo://almascience.org/datalink
  almaRequestHandlerServiceURI=ivo://almascience.org/requesthandler
  almaFileSodaServicePort=8080
  almaSODAServiceURI=ivo://almascience.org/soda
  almaDataPortalServiceURI=ivo://almascience.org/dataportal
  almaLoggingServiceURL=https://example.org/logging/entry

The Registry service to distribute URLs for running services, namely the SIAv2 and ObsCore services.

This service will have two files; reg-applications.properties, and reg-resource-caps.properties.

Once deployed, the reg service will make their contents available via the /reg/applications and /reg/resource-caps endpoints.

Is expected to have two entries:

ivo://almascience.org/requesthandler=https://almasciencedl.eso.org/rh
ivo://almascience.org/dataportal=https://almascience.org/dataPortal

The URI keys will conform to the provided ones in the org.opencadc.alma.properties, and provide the services with an endpoint to use it. The reg-applications.properties differs in that it provides access to non-IVOA services, but still necessary ones.

Five IVOA services will need to be listed here, as well as the endpoints to use them. These URI keys will also match the configured ones in the org.opencadc.alma.properties. The data service will be located by the Request Handler location service due to the complexity of have the service run on multiple nodes.

# The registry service
ivo://almascience.org/reg = https://almascience.org/reg/capabilities

## ALMA services

# The IVAO SIA compatible service
ivo://almascience.org/sia = https://almascience.org/sia2/capabilities

# The IVOA DataLink service
ivo://almascience.org/datalink = https://almascience.org/datalink/capabilities

# The IVOA SODA service
ivo://almascience.org/soda = https://almascience.org/soda/capabilities

# The IVOA TAP service
ivo://almascience.org/tap = https://almascience.org/tap/capabilities

SIA v2 service. This uses the ObsCore (TAP) service as described by the registry. See the SiaRunner.properties file to specify the TAP URI to use.

ObsCore (TAP) service to query the ALMA ObsCore database. An existing Oracle instance is required.

DataLink service to expand an MOUS ID into download URLs

Internal service to run on a storage (NGAS) node and execute the cutout code directly against files. It is mostly SODA compliant.

IVOA SODA service. This will use the reg service to locate the Request Handler service, and the back-end SODA service.

The ALMA IVOA services are released on a quarterly (every three months) basis, namely to obtain the current underlying image (Tomcat 9 with JDK 21) and ensure current CVE fixes. These images are automatically built and pushed to Docker Hub under the opencadc organization.