## Action
= Action Deliver Start+Stop Scripts + Documentation =

Part of [[Iteration8| iteration 8]].

## Detailed description of wanted output from the work to be carried out.
## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written.

This action consists of two parts.
 1. Making start and stop scripts for deploying and taking down the miniDOMS.
 2. Writing documentation for deploying and taking down the miniDOMS.

== Making start and stop scripts ==
Write and deliver the needed scripts for miniDOMS to the IT maintenance department. The IT maintenance will probably prefer to be responsible for the Tomcat (see [[ActionSystemSetupAgreement|Action agree on system setup]]), which means that we probably need deploy scripts.

The installation will be performed in two major steps.
First Maintenance will run the basis script(s) to setup the basis (tomcat, ...).
Then they will run the miniDOMS scripts(s) to setup the main DOMS.

 * The basis scripts will be made by Maintenance, possibly based on guidelines from the DOMS Team.
 * The miniDOMS scripts will be made by the DOMS Team.

Go through the description of release test 7 to get an overview of the whole process of installation.
 * (1 md) Identify the knowledge from the beginning of the release test that will be needed by Maintenance for making the basis scripts.
 * (3 md) From the steps in the release test, build the miniDOMS script(s).

(2-4 md) Build a script for taking down the miniDOMS.


== Writing documentation ==
The system maintenance documentation should describe the scripts and Tomcat settings and how to act upon different scenarios; also depends heavily [[ActionSystemSetupAgreement|Action agree on system setup]].

(1 md) The documentation takes the form of a user manual for the scripts provided in the first part of this action.


## Targeted WBS Tasks and Assigned Developers can be found on the iteration page for this action.