-
Notifications
You must be signed in to change notification settings - Fork 26
Default Environment
There is one special Environment in Toolkit named default.
This environment must always exist for Toolkit to function. When Toolkit is stared in Tomcat the External Cache is scanned. If the default environment does not exist it is created from content in the WAR file. This default Environemnt is stored in the WAR file at
toolkitx/environment/default
which is copied to
EC/environment/default
if EC/environment/default does not exist.
As of this writing, this default Environment contains:
What | Explanation |
---|---|
codes.xml |
Affinity Domain configuration including acceptable codes |
pids.txt |
Default Patient Table |
keystore/keystore |
keystore used when Toolkit initiates TLS connection |
keystore.properties |
See below |
keystore.properties is a Java properties file containing:
# keyStorePassword=changeit
which is the password for the keystore.
Toolkit
Downloads
Installing Toolkit
Configuring Toolkit for Imaging Tests
Reporting Toolkit Installation Problems
Environment
Test Session
Conformance Test Tool
Writing Conformance Tests
Overview of Imaging Tests
Test Context Definition
Launching Conformance Tool from Gazelle
Inspector
External Cache
Support Tools
Test Organization
Configuring Test Kits
Managing Multiple Test Kits
SAML Validation against Gazelle
Renaming Toolkit
Toolkit API
Managing system configurations
Configuring Toolkit for Connectathon
Developer's blog