Page History

...

1. Download the most recent version of the XDS toolkit from NIST: http://ihexds.nist.gov/downloads.html
2. As an example, the file will be called xdstools.178a.war. In this example, "178a" is a version number. Rename the file to xdstools2.war and drop the war in the web apps folder of your tomcat server.
3. Start your tomcat server.
4. Wait until the Tomcat server has started completely, and then stop it. We want Tomcat to expand the xdstools2.war file.
5. You need a cache folder for the xdstools2 software. There is a zip of that folder with contents here:  xds_external_cache.zip
6. Unzip the cache folder in a location where the Tomcat server will have ready access.
   1. You could place this directly under the tomcat home folder. If you update Tomcat, you will have to remember to retrieve this.

   2. You can place it another another folder altogether (some as your home directory). 

7. Edit the file ..tomcat/webapps/xdstools2/WEB-INF/toolkit.properties. Make these changes
   1. Toolkit_TLS_Port: no change; we are not yet doing TLS
   2. Toolkit_Port: change to match the port for your Tomcat server; by default, this would be 8080
   3. Default_Environment: ERL  This matches a folder that was created when you unzipped the XDS external cache
   4. Admin_password: up to you to change or keep it; if you are behind a firewall and testing internally, you can use the default
   5. Use_Actors_File: true
   6. Gazelle_Config_URL: leave this empty
   7. External_Cache: Give it the absolute path to the ads_external_cache folder created when you unzipped the cache above
   8. Toolkit_Host: remains localhost
8. Start the Tomcat server (again).
9. Browse to http://localhost:8080/xdstools2 (substitute the port number if you are not using the standard Tomcat port)
10. You need to create one Registry/Repository simulator that will receive and store XDS documents. On the xdstools2 home page
    1. Select "Simulator Control" under the Simulators heading. This opens a new tab in the xdstools2 page, not a new tab in your browser.
    2. Environment should be set to "ERL" based on your prior configuration
    3. Set the value for TestSession to "null"
    4. Under Simulator Control, select the actor type "Document Repository/Registry" and activate the "Create Actor Simulator" button.
    5. That creates a Repository/Registry with an identifier generated by the software.
    6. Look in the cache folder you created previously. Look in the folder: xds_external_cache/simdb. You should see a folder with the same name as the id that was generated. If you look in that folder, you should see a folder named rr and a file named simctl.ser.
11. Shutdown the Tomcat server.
12. Make a copy of the xds_external_cache folder (e.g., make a zip). This will give you the XDS Repository/Registry in an empty state that you can easily use to restore your system.
13. Start the Tomcat server and browse to the homepage of the xdstools: http://localhost:8080/xdstools2
14. You are now going to test your Repository/Registry.
    1. Select "Repository Test Data" under "Send Test Data"
    2. For Patient ID, use the value:  IHERED-1644^^^&1.3.6.1.4.1.21367.13.20.1000&ISO
    3. Select Test Data Set: SingleDocument
    4. SAML: should be off
    5. TLS: Uncheck, we are not using TLS yet
    6. Document Repository: Check the Private rr you created (you might have saved it with a different name).
    7. Click the Run button
    8. The tool (self test) should report a success. If there are any errors or red text, you will need to review the reasons for failure. You might need to check with Steve.