No description, website, or topics provided.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Welcome to the Test Specification Bank (TSB) Component

The Test Specification Bank (TSB) component is responsible for test (assessment) specification storage, searching, and initiation of packaging. The authenticated and authorized user can search for test specifications that were published from Test Authoring, view the actual specification XML, and initiate a packaging of that specification which will bundle the XML with all related Test Item data to be compressed and stored in a remote Secure FTP host location.

Usage note: Side-Loading External Packages

To load externally authored test packages into the TSB, you may use the “” script available in the tsb folder of the Administrative repository. Test packages will then be browsable in ART’s Select Assessment function. Refer to the script’s usage instructions for more details on script usage.


This project is licensed under the AIR Open Source License v1.0.

Getting Involved

We would be happy to receive feedback on its capabilities, problems, or future enhancements:

  • For general questions or discussions, please use the Forum.
  • Feel free to Fork this project and develop your changes!


Rest Module

The REST module is a deployable WAR file ( that provides REST endpoints that can be used to access and modify Test Spec Bank data.

In order to run and use the REST WAR application, several supporting applications must be running and accessible: sb11-program-management, sb11-monitoring-alerting (mna).

In addition, the following opentestsytem applications are also required at run time: opentestsystem Permissions and Single Sign-On (SSO).

The REST layer setup must be performed before deploying the WAR to a Tomcat-compatible application server. Specifically, virtually all of the start up and run time parameters that the REST module needs are stored in sb11-program-management using its profile property configuration feature.

To execute the REST module and connect to sb11-program-management, run time parameters are passed to the Tomcat server running the sb11-test-spec-bank REST module:"progman.client.impl.integration,mna.client.integration"

This run time parameter specifies which spring profile to use for the program management and monitoring & alerting client interfaces.


This run time parameter specifies the REST endpoint of a running sb11-program-management instance that will be accessed during REST module start up.


Note that the progman config variables required are found here:

This run time parameter specifies the property configuration set stored in the running sb11-program-management instance which contains all of the needed properties to get this instance of sb11-test-spec-bank running. The third optional value example 'dev_tsb_overrides' is a useful feature that allows for overrides: in this case, all properties contained in the property group 'tsb' for level 'dev' are used by default, except where property group 'dev_tsb_overrides' has an overriding property value.

Note: the progman config variables required are found at external_release_docs/installation/tsb-progman-config.txt. Descriptions of these values follow:

  • - URL of SSO IDP's metadata export file
  • permission.uri=http://name.of.permissions.server/rest - URI to Permissions REST interface
  • - Must match the name in Permissions and Program Management applications
  • tsb.mna.description=The Test Spec Bank Component - TSB description for MNA logs
  • mna.mnaUrl=http://name.of.mna.server/rest - URL to MNA's REST interface
  • mna.logger.level=[OFF | ERROR | WARN | INFO | DEBUG | TRACE | ALL] (default:ERROR) - Error log items of this level or higher are to be sent to the MNA application.
  • mna.clean.days=30 (default) - Clear our MNA logs after this many days
  • mna.clean.cron=0 0 0 * * ? (default) - Cron job entry for MNA log cleaning schedule
  • mna.oauth.batch.account - Username (email address) of MNA client user used for authenticating into MNA and logging metrics information
  • mna.oauth.batch.password= - Password of MNA client user
  • tsb.mongo.hostname= - TSB Mongo DB hostname
  • tsb.mongo.port=27017 - Mongo DB port
  • tsb.mongo.username= - Mongo DB username
  • tsb.mongo.password= - Mongo DB password
  • tsb.mongo.dbname=tsb-dev - Mongo DB database name
  • tsb.dtd.url=http://name.of.test.authoring.server/rest/resources/dtd/testpackage_v_9_19_2013.dtd - Test package DTD location
  • - Root context of the TSB REST service
  • tsb.minJs=true - Whether to use minimized JavaScript in the browser, true to minify
  • tib.tibUrl= - URL to TIB server
  • - TSB SFTP host
  • tsb.sftp.port=22 - TSB SFTP port
  • tsb.sftp.user= - TSB SFTP account username
  • tsb.sftp.pass= - TSB SFTP account password
  • tsb.sftp.dir= - TSB SFTP account directory
  • - TSB's TIB SFTP hostname
  • tsb.tib.sftp.port=22 - TSB's TIB SFTP server port
  • tsb.tib.sftp.user= - TSB's TIB SFTP account
  • tsb.tib.sftp.pass= - TSB's TIB SFTP account password
  • - TSB's SFTP download directory
  • tsb.export.cron.trigger=0,30 * * * * ? - Cron to configure export frequency of test specifications

Clustered Environment properties

These are optional properties which are used when configuring a clustered environment behind a load balancer (LB). To activate clustered environment support, simply change the active profile setenv as follows: change from server.singleinstance to server.loadbalanced. Furthermore, you will need to set these key/value pairs appropriately:

  • tsb.loadbalanced.url.scheme - {this should be http or https}
  • - {the loadbalancer’s name}
  • tsb.loadbalanced.server.port - {if your server requires a port, include it here, otherwise put 80 in as the default}
  • tsb.loadbalanced.includeServerPortInRequestURL - {boolean true/false value which indicates if the port should be included to resolve the server}
  • - {REST context name. e.g.: "/"}
  • tsb.loadbalanced.server.webapp.contextpath - {webapp context name. e.g.: "/tsb.webapp". Leave this blank if you are using ROOT as webapp context name}

Domain Module

The Domain module contains all of the domain beans used to model the Test Spec Bank data as well as code used as search beans to create MongoDB queries.

Persistence Module

The Persistence module is responsible for persistence of application data. This includes all business rules, validation, XML configuration, and publishing.

Upon receiving a new XML test specification to be stored, validation of that XML using the related DTD is not performed as it is a very costly operation in both time and memory usage. However, if needed it can be activated during application start up by saving a property into Program Management within the TSB profile property configuration, with a key of "tsb.dtd.validation" and value of "true".

Webapp Module

The Webapp module is a deployable WAR file (test-spec-bank.webapp-VERSION.war) that provides the UI for Test Spec Bank functionality. As with several other sb11 applications, this is a single-page application (SPA) built using AngularJS for a robust, reactive user interface. The Webapp module uses the REST module for all data access, but this is a run time dependency through a REST endpoint and not a direct code dependency.

Client Modules

There are two modules that make up the client:

  • The Client Interfaces module contains the interface classes for the client, AOP advice and point cuts, and bootstrap initialization.
  • The Integrated Client sends all messages to the advertised REST endpoints from the REST module.

In order to use one of the client implementations:

  1. Add the Maven dependencies to the POM of the project that is using Test Spec Bank.

<dependency> <groupId>org.opentestsystem.authoring</groupId> <artifactId>test-spec-bank-client<artifactId> <version>${tsb-client.version}<version> </dependency>

  1. Add a context initializer class name to the web.xml

<context-param> <param-name>contextInitializerClasses</param-name> <param-value>org.opentestsystem.authoring.testspecbank.client.init.TestSpecBankClientContextInitializer</param-value> </context-param>


These are the steps that should be taken in order to build all of the Test Spec Bank artifacts.


  • Mongo 2.0 or higher
  • Tomcat 6 or higher
  • Maven (mvn) version 3.X or higher installed
  • Java 7
  • Access to sb11-shared-build repository
  • Access to sb11-shared-code repository
  • Access to shared security repository
  • Access to sb11-rest-api-generator repository
  • Access to sb11-program-management repository
  • Access to sb11-monitoring-alerting repository

Build Order

See the Build Sequence Diagram at designPics/build%20sequence.png


The Test Spec Bank has a number of direct dependencies that are necessary for it to function. These dependencies are already built into the Maven POM files.

Compile Time Dependencies

  • Apache Commons IO
  • Apache Commons Beanutils
  • Jackson Datatype Joda
  • Google Guava
  • Hibernate Validator
  • Apache Commons File Upload
  • Jasypt
  • SB11 Shared Code
  • SB11 Shared Security
  • Logback
  • SLF4J
  • JCL over SLF4J
  • Spring Core
  • Spring Beans
  • Spring Data MongoDb
  • Mongo Data Driver
  • Spring Context
  • Spring WebMVC
  • Spring Web
  • Spring Aspects
  • AspectJ RT
  • AspectJ Weaver
  • Javax Inject
  • Apache HttpClient
  • Apache Commons Lang
  • Joda Time
  • Jackson Core
  • Jackson Annotations
  • Jackson Databind
  • SB11 REST API Generator
  • JSTL

Test Dependencies

  • Spring Test
  • Hamcrest
  • JUnit 4
  • Mockito
  • Flapdoodle
  • Podam
  • Log4J over SLF4J

Runtime Dependencies

  • Servlet API
  • Persistence API