Test Case TC_318

This page describes one of the test cases of the EODiSP. The test case described in this page instantiates a nominal scenario of the use case UC_318.

This test case uses the EarthCARE Simulator as a test platform. The simulator is operated in its default configuration.

Contents

Overview

Identifier TC_318
Name Deploy an HLA federate.
Primary Actor ETH_2 Model Owner
Description

Describes the step to deploy an HLA federate. This steps apply to each federate for the EarthCARE simulator.

A federate can be deployed in two physical formats

  • One single jar file
  • A directory containing the code

In both cases, a Manifest file with the correct information must be present.
Pre-Condition (1) The HLA federate has been developed. (2) A Java Programming Environment (IDE) such as Eclipse is available.
Post-Condition One single jar file containing the federate.
top ^

Steps

  1. Actor creates a MANIFEST.MF file for the federate he has developed. Such a file includes meta information about a bundle (i.e. a project). The following information should be included in the file:
    • Manifest-Version: Version of the MANIFEST.MF file.
    • Bundle-ManifestVersion: Version of the MANIFEST.MF file in the bundle.
    • Bundle-Name: Name of the bundle
    • Bundle-Description: Description of the bundle
    • Bundle-SymbolicName: Identification of the bundle
    • Bundle-Version: Version of the bundle
    • Som-Id: Identification of the SOM to which this federate complies to.
    • Som-Version: Version of the SOM to which this federate complies to.
    • Main-Class: The main class which is used to start the federate
  2. Actor exports the whole project as .jar file by using the mechanism provided by the IDE. Alternatively, the actor may choose to deploy the whole directory.

top ^