Release ALPHA


Release ALPHA is the first of a series of three releases planned for the lifecycle of the DILIGENT project. All components included in each of these releases have to go through a strict and well-established Release Procedure.

Components List

All components included in release ALPHA are defined in Savane. Each component is represented by a Savane task where the task Context is equal to Release. Savane tasks also show the current status of each component with respect to the defined Release Procedure.

The same information, plus a number of graphs reporitng the status of the release ALPHA, is available in an Excel file:

Special Cases

The following topics present the exceptions that make impossible some services to complete the established Release Procedure. This procedure expects that each DILIGENT service can be automatically deployed in any DILIGENT Hosting Node (DHN).

  1. Some services originally planned as part of DILIGENT Release ALPHA were not made available on time for integration. These services are CANCELLED from the Release ALPHA. The following services are in this situation:
    • org.diligentproject.metadatamanager.catalog
    • org.diligentproject.personalization.userprofilemanager
    • org.diligentproject.annotation.annotationservice
  2. Some services need manual configuration to be properly set up and executed - either because they are not mature enough or because of technical limitations. For these services authomatic deployment will not be possible.These services follow the Release Procedure with the note that manual configuration is needed. Eligibility for inclusion in the ALPHA relese needs to be clarified in the Certification step. The following services are in this situation:
    • org.diligentproject.contentmanagement.collectionmanagementservice
    • org.diligentproject.contentmanagement.contentmanagementservice
    • org.diligentproject.contentmanagement.storagemanagementservice
    • org.diligentproject.dvos.credential-renewal-service
    • org.diligentproject.informationservice.disrgmaclient.SERVICE
  3. The GT4 version selected for Release ALPHA is Java WS Core 4.0.2. Due to external dependencies requirements some services need version 4.1.0 version of Java WS Core. These services cannot run in the current version of DHN because they are incompatible with the version of the software adopted in Release ALPHA.These services are CANCELLED from the Release ALPHA. The following services are in this situation:
    • org.diligentproject.contentsecurity.service

Open Issues

Which VOMap to use

The HNM is currently using a VOMap file that points to the development startup services (DIS-IC and DIS-Broker). Which VOMap should be used: development (CNR), testing (4DSOFT), pre-prod (CNR - used by portals) ?


  • For release ALPHA:
    • startup services of the development cannot be used because they run the latest version of the software (not the integration version)
    • startup services of the testing cannot be used because they are is still not available
    • startup services of the pre-prod can be used since they run the integration version of the software and are already available
    • CNR: HNM has to be changed to reflect this decision
  • For release BETA:
    • automatically deploy new startup services and then execute service deployment testing and system deployment testing (not covered for release ALPHA)

Service specific manual configuration

For some DILIGENT services, there's the need for manual configuration (either before or during execution). The deployment testing tool is an automatic process and does not support service specific configurations. Currently this situation occurs with the following services:

  • dvos.credential-renewal.service
  • cms.contentmanagement.service
  • cms.collectionmanagement.service
  • cms.storagemanagement.service


  • For release ALPHA:
    • post-deployment script: In the ServiceProfile there is a parameter called InstallScript. This parameter points to a script (packaged inside the build artifact) that must be executed after the deployment of the service and before starting the container. The deployment testing script must run this script (if existing) before starting the container. CERN: implement this change.
    • JNDI file: Information needed at service runtime can be passed using the JNDI file. CERN: investigate which service actually need this.


  • The above solutions however do not solve the issue of passwords. For dvos.credential-renewal.service the solution is to implement an "activation" mechanism based on MyProxy credentials-renew manually triggered through a portlet in the DILIGENT portal.

Service Profiles update/naming

Starting from integration build 0.3.0 the deployment testing tool has been configured to take most of its input parameters from the Service Profile xml file. Problems may occur if the Service Profile is not the latest version or if the Service Profile filename is not as described in DIS.


  • For release ALPHA:
    • use Service Profile stored in DIS-IC and update the version used in integration manually
    • CNR: send a notification to integration mailing list whenever a Service Profile is updated
  • For release BETA:
    • change the DHN startup behavior making sure that Service Profiles are retrieved from the DIS. Example for a given service:
      1. start the service
      2. from the EPR retrieve the EntryPoint
      3. query DIS for the Service Profile
      4. build from the Service Profile the correct RI Profile
      5. publish the RI Profile

-- PedroAndrade - 06 Dec 2006

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2007-03-08 - PedroAndrade
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    DILIGENT All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback