Toolkit is controlled by several configuration files which are documented on this
page.
The WAR file contains the primary configuration file:
WEB-INF/toolkit.properties
The most important property is
External_Cache=/var/lib/tomcat_ttt/ttt/external_cache
the location of the External Cache. Note: in the future this properties file
will be scaled back and only contain the External_Cache property with the others moving
to secondary files within the External_Cache.
Looking at all the properties:
Toolkit_Host=hit-testing.nist.gov Toolkit_TLS_Port=9443 Toolkit_Port=9100
define the web location of the toolkit. These are used when addressing simulators
defined by the toolkit.
Default_Environment=EURO2012
The default environment setting. This controls the certificates used when initiating
SOAP based connections and the Affinity Domain configuration for XD profiles. The
value defines a directory name in the External Cache*:
Inside environment are directories naming the selectable environments. An environment contains
a Java keystore holding a private key for initiating a TLS connection, the password for
this keystore is kept in the password file. The codes.xml file contains the Affinity
Domain configuration to be used for validating metadata-carrying messages. This
directory structure looks like:
environment/ NA2013/ codes.xml keystore/ keystore keystore.properties
The contents of the keystore.properties file looks like
keyStorePassword=changeit
If multiple environments are defined then they are also defined below the environment
directory and are selectable from the UI.
The following properties are used only in very special situations and should not
be modified:
Enable_all_ciphers=false Use_Actors_File=true Gazelle_Config_URL=
The administrative password needed to edit the properties file from the UI. The
default value, as shown, is very easy to remember.
Admin_password=easy
The location of the External Cache as described above.
External_Cache=/var/lib/tomcat_ttt/ttt/external_cache
Since this file is delivered inside the WAR file it must be edited each time the WAR
file is updated. For this reason, all parameters other than External_Cache will
eventually move to a more stable location.