SEALS Platform

The Runtime Evaluation Service version released addresses the following topics:

1. Supporting fine-grained tool execution time measurement
2. Supporting the measurement of memory consumption for a given tool execution
3. Supporting simple custom tools

To do so, this release includes the following new features:

• Feature 743: Support fine-grained tool execution time measurement
• Feature 744: Support measuring memory consumption for a given tool execution
• Feature 810: Support custom tools

The release also includes the following bug fixes to the previous version:

• Bug 473: RES Bootstrap utility tests fail in *nix OSs
• Bug 474: RES Monitor utility tests fail in *nix OSs

Additionally, several improvements have been made to the previous version:

• Improvement 741: Automatic generation of IDs for stored results
• Improvement 746: Clean up integration test evaluation description
• Improvement 747: Improve the way in which Core Tool Services faults are handled
• Improvement 805: Modify SoapUI integratation test to deal with all possible termination events
• Improvement 826: Clean up dependencies in the SEALS Core modules
• Improvement 836: Refactor utilities for logging configuration properties
• Improvement 840: Standardize configuration of the Runtime Evaluation Service

The documentation for this release is available here

Finally, this release depends on the following SEALS Platform modules:

• Test Data Repository Service 1.1

• Results Repository Service 1.1

Additional build information for this release can be directly obtained from the continuous integration server (here).

If you want to download the binary distribution, you can do it from here

The SEALS Service Manager represents the core component of the SEALS Platform. This component is responsible for providing access to the computational and data resources of the SEALS Platform and for the internal coordination of the modules of the SEALS Platform. SEALS Service Manager version 1.1, and is fully integrated with the Runtime Evaluation Service 1.2.

The SEALS Service Manager 1.1 version includes the following subsystems:

• Execution Subsystem 1.1
• Infrastructure Management Subsystem 1.1

In addition, this release includes four utilty modules:

• SEALS Commons 1.2
• Core Commons 1.2
• SSM Resources 1.1
• SSM Service API 1.1

This release includes the following features:

• Feature 808: Tool metadata processing in SSM-ES
• Feature 831: Physical Computer Resource Wrapper for a RES Worker hosted in a physical computer
• Feature 832: SSM-IMS source & binary distribution
• Feature 833: SSM-ES source & binary distribution
• Feature 849: Integration tests in SSM-ES

Additionally, the following improvement have been made to the previous version:

• Improvement 571: Externalize the configuration of the ERM Timer
• Improvement 639: Update the services in SOAPUI Tests in SSM-IMS
• Improvement 809: Incorporate ES routes with RES Worker 1.1 changes
• Improvement 829: Normalize the service uris in SSM-ES
• Improvement 830: Normalize the service uris in SSM-IMS
• Improvement 834: Externalize the configuration of the CRM Timer
• Improvement 835: Improve the logs in SSM-IMS
• Improvement 847: Logging configuration properties in SSM-ES startup
• Improvement 848: Logging configuration properties in SSM-IMS startup

If you want to download the binary/source distributions of SEALS Service Manager, they are available from the following links:

• Execution Subsystem 1.1
• Infrastructure Management Subsystem 1.1

For more information please check the following resources:

• SEALS project homepage

• SEALS community site

• Bug tracking & change management
  *SSM-ES
  *SSM-IMS

• Continuous integration and delivery

• Software configuration management
  *SSM-ES
  *SSM-IMS

Many thanks for your interest in SEALS Platform.

The SEALS Team
http://about.seals-project.eu/people

This version integrates the following modules:

• Runtime Evaluation Service 1.1
• SEALS Service Manager 1.0
• Test Data Repository Service 1.1
• Results Repository Service 1.1

The release includes the following new features:

• Feature 81: Retrieve the execution status of an execution request
• Feature 82: Retrieve the list of tools used in an execution request
• Feature 83: Retrieve the list of test data sets used in an execution request
• Feature 84: Retrieve the list of results generated by an execution request
• Feature 320: Execution request life-cycle control operations (cancel, abort)
• Feature 342: Provide java clients for accessing Tools Repository Service
• Feature 354: Transfer the output of one tool to another tool
• Feature 355: Integration of custom services in the platform
• Feature 435: Provide example of how to deploy custom services for evaluation descriptions
• Feature 535: Execute multiple predeployed evaluation descriptions
• Feature 573: Add persistence layer for internal RES artifacts
• Feature 622: Retrieval of suite item metadata
• Feature 656: Simplify build & deployment process of the Runtime Evaluation Service
• Feature 657: Allow using faults in custom services
• Feature 658: Migrate to Apache ODE 1.3.5
• Feature 688: Enable sharing files among services regardless their location
• Feature 729: Allow cancelling the processing of a pending exectution request
• Feature 730: Allow aborting the execution of an executing execution request
• Feature 731: Enable managing the priority of execution request
• Feature 733: Support long-lived invocations

In addition, the release solves the following bug:

• Bug 632: The Runtime Evaluation Service fails to invoke SWS tools from BPEL

The following improvements have been also included in the release:

• Improvement 386: Execution request queue refactoring
• Improvement 497: Remove the necessity of filtering and deploying RES Resources appart
• Improvement 554: Provide an standard logging mechanism for using accross the RES modules
• Improvement 555: Provide an standard XML management mechanism for using accross the RES modules
• Improvement 596: Retrieve multiple objects from suite metadata
• Improvement 617: Enhance Clover & Sonar integration for the Runtime Evaluation Service
• Improvement 664: Clean up RES Service API module
• Improvement 672: Migrate from RRS version 1.1-b to version 1.1
• Improvement 673: Migrate from TDRS version 1.1-b to version 1.1
• Improvement 681: Update res-itest-ed project to reflect new features and improvements

For further information, please have a look at the following news:

• Runtime Evaluation Service 1.1 released
• SEALS Service Manager 1.0 released

This release is the first stable version of the SEALS Service Manager, and is fully integrated with the Runtime Evaluation Service 1.1

The SEALS Service Manager 1.0 version includes the following subsystems:

• Execution Subsystem 1.0
• Infrastructure Management Subsystem 1.0

In addition, this release includes four utilty modules:

• SEALS Commons 1.1
• Core Commons 1.1
• SSM Resources 1.0
• SSM Service API 1.0

What's new in SEALS Service Manager 1.0:

• Externalized Configuration
  • Database configuration
  • Public service locations
  • VMware Server configuration
• Better integration with Runtime Evaluation Service (RES)
• Improved information extraction functionalities
  • Execution request state
  • Execution results
  • Consumed test data
  • Evaluated tools
  • Associated evaluation description
• Ability to search execution requests
• Improved execution request management functionalities
  • Cancel execution requests
  • Abort execution requests
  • Prioritise execution requests

This release includes the following features:

• Feature 81: Retrieve the execution status of an execution request
• Feature 82: Retrieve the list of tools used in an execution request
• Feature 83: Retrieve the list of test data sets used in an execution request
• Feature 84: Retrieve the list of results generated by an execution request
• Feature 320: Execution request life-cycle control operations (cancel, abort)
• Feature 729: Allow cancelling the processing of a pending exectution request
• Feature 730: Allow aborting the execution of an executing execution request
• Feature 731: Enable managing the priority of execution request

Additionally, the following improvement have been made to the previous version:

• Improvement 386: Execution request queue refactoring

The documentation for this release is available here

If you want to download the deployable artifacts, they are available from the following links:

• Execution Subsystem
• Infrastructure Management Subsystem

Additional build information for SEALS Service Manager can be directly obtained from the continuous integration server (here).

The Runtime Evaluation Service version released addresses the following topics:

1. Supporting multiple predeployed evaluation descriptions
2. Allowing the integration of custom services
3. Supporting long-lived invokations
4. Sharing files among services (tools and custom services)

To do so, this release includes the following new features:

• Feature 354: Transfer the output of one tool to another tool
• Feature 355: Integration of custom services in the platform
• Feature 435: Provide example of how to deploy custom services for evaluation descriptions
• Feature 535: Execute multiple predeployed evaluation descriptions
• Feature 573: Add persistence layer for internal RES artifacts
• Feature 656: Simplify build & deployment process of the Runtime Evaluation Service
• Feature 657: Allow using faults in custom services
• Feature 658: Migrate to Apache ODE 1.3.5
• Feature 688: Enable sharing files among services regardless their location
• Feature 733: Support long-lived invocations

The release also includes the following bug fixes to the previous version:

• Bug 632: The Runtime Evaluation Service fails to invoke SWS tools from BPEL

Additionally, several improvements have been made to the previous version:

• Improvement 497: Remove the necessity of filtering and deploying RES Resources appart
• Improvement 554: Provide an standard logging mechanism for using accross the RES modules
• Improvement 555: Provide an standard XML management mechanism for using accross the RES modules
• Improvement 617: Enhance Clover & Sonar integration for the Runtime Evaluation Service
• Improvement 664: Clean up RES Service API module
• Improvement 672: Migrate from RRS version 1.1-b to version 1.1
• Improvement 673: Migrate from TDRS version 1.1-b to version 1.1
• Improvement 681: Update res-itest-ed project to reflect new features and improvements

The documentation for this release is available here

Finally, this release depends on the following SEALS Platform modules:

• Test Data Repository Service 1.1

• Results Repository Service 1.1

Additional build information for this release can be directly obtained from the continuous integration server (here).

If you want to download the binary distribution, you can do it from here

The Runtime Evaluation Service version released includes the following new features:

• Feature 353: Transparent management of zip files
• Feature 357: Execute tool packages (Store in the tool metadata the Java class name / service for dynamically running the tool plugin)
• Feature 359: Run the BPEL workflows using execution requests
• Feature 360: Need to manage exceptions from the used libraries / services
• Feature 418: Instructions about how to integrate an evaluation description in the SEALS Runtime Evaluation Service

The release also includes the following bug fixes to the previous version:

• Bug 417: Several problems while creating a new tool

Additionally, several improvements have been made to the previous version:

• Improvement 377: Migrate RES common services to CXF
• Improvement 462: Remove external and unused dependencies of RES
• Improvement 463: Enhance internal module dependency version specification
• Improvement 466: Improve usability of Tool Package Plugin
• Improvement 476: Improve usability of Tool Wrapper Maven Archetype
• Improvement 478: Include RES-wide integration testing mechanisms in the RES component

The documentation for this release is available here

It is also worth mentioning that starting with this release a well defined versioning strategy for SOAP Web Services will be put in place for managing the different services offered by the SEALS platform (see specification). This includes those offered by the Runtime Evaluation Service to Evaluation Description developers (see issue 436).

Finally, this release depends on the following SEALS Platform modules:

• Test Data Repository Service 1.1b

• Results Repository Service 1.1b

Additional build information for this release can be directly obtained from the continuous integration server (here).

If you want to download the artifacts, you can do it from here

The SEALS Platform 1.0-alpha version released include the following modules:

• SEALS Service Manager 1.0-alpha
• Runtime Evaluation Service 1.0-alpha
• Test Data Repository Service 1.1-alpha
• Results Repository Service 1.1-alpha

You can download the artifacts that make up the release from the SEALS Artifact Repository:

• SEALS Service Manager - Execution Subsystem (JBI Service Assembly file)

• SEALS Service Manager - Infrastructure Management Subsystem (JBI Service Assembly file)

• Test Data Repository Service (WAR file)

• Results Repository Service (WAR file)

• Ontology Engineering Tool - Sample Conformance Evaluation (JBI Service Assembly file)

• ProtegeOWL tool (Zip file)