Page History

...

Q: Is there a User Guide?

A: Yes: The 3.0 Release 1 User Guide is the latest. Previous user guides can be found in a particular release's wiki space.

...

A: The demo version of the tool can be found here.

Q: Which browsers are supported by the Tool?

...

A: Check your junk mail or spam folders. Sometimes the messages are routed to these folders. Look out for messages coming from: results@demoresults@dcdt31prod.direct-testsitenv.comorg.

Q: Which tests are required to demonstrate Meaningful Use Stage 2 (MU2) capabilities?

...

Q: Where does the code live?

A: The code is in a GitHub repository, which will be the official repository. It is also in a read-only Google Code repository, which will be retired. The . The code can be built from source by following the 3.0 1 Source Build Guide.

Q: How do I submit a defect?

A: To submit a defect, please enter the issue using our JIRA issue tracker.

Q: If I choose to install the Tool locally, do I have to build it from source?

A: No, you can download the latest WAR file (here) and deploy it to your application server.

Q: How is the DCDT version 3.0 release different from previous releases?

A: The 3.0 release contains many improvements for the end user. Significant enhancements and improvements were made to: (1) Remove the dependency on the Direct Java RI, so that DCDT is now a stand-alone application with no dependency on the RI whatsoever; (2) Simplify the setup of DCDT: two fields -- domain name and IP address -- in the administration console are all that is needed to completely and automatically configure the tool and its certificates; and finally (3) Provide detailed feedback to the user at each step of every test case: detailed success and error messages provide specific, useful information to the user.

Q: How does the new DCDT release provide more detailed feedback?

A: Whenever a test is run, details of each step of every test case are displayed to the user. This makes it easy for the user to pinpoint the problem when a test fails. Whether a test passes or fails, all parameters and results are displayed to the user. Subsequent results are added to the web page as test cases are run, and previous results are minimized in accordion-like fashion.

Q: Is a full Java RI installation required for the new version 3 release?

A: No, DCDT is no longer dependent on the Direct Java RI. Previously, a full Java RI installation was required to provide underlying Direct functionality to DCDT, such as LDAP, DNS, email, and cryptography. DCDT now natively handles this functionality, so the installation process is much simpler.

Q: Why is DCDT trying to discover a sender certificate for Discovery testcases?

A: DCDT tries to discover a sender certificate for Discovery testcases by performing certificate discovery on the sender address of the Discovery testcase submission mapping and then verifies that it matches the certificate included in the mail signature. Although it is an optional requirement for sender/signer certificates to be discoverable, according to Section 1.4 of the Applicability Statement:

"The organization SHOULD publish the certificates for discovery by other implementations for the purposes of encryption and signature verification."

this is the only way that DCDT can assert the authenticity of the sender and signer certificate since DCDT does not keep any trust chains for any sender and/or signer certificates. 

...

.