CONNECT Windows Source Install Webinar Questions Log (04/10)
April 22, 2010, 2:00pm – 4:00pm
Q: Has this been tested on Windows7?
No, we have not tested on Windows 7. The newest OS that most of the team has used has been Vista 64-bit. If anyone in the Open Source community has successfully used Windows 7, please post to the forum and let us know!
Q: On the Java JDK install, is the Java Database option required?
We have not tried disabling it, but we do not use it for CONNECT.
Q: Is java 1.6.0_17 ok?
We do not officially support 1.6.0_17. We only officially support 1.6.0_16 and are fully tested with that version. If you get CONNECT working in a 1.6.0_17 environment, please share with the community.
Q: I missed the Webinar for the Linux Install. Is there a recording or presentation I can review for the one you did on Tuesday?
http://www.connectopensource.org/about/events/webinar-2-4-install
Q: Is a certificate necessary to pass all the validation steps? One from Entrust?
A certificate is required to pass the validation steps. However, the certificate only has to be one from Entrust if you are actually on the NHIN. For development or testing with other groups outside of the NHIN, a certificate is required but it does not have to be the NHIN Entrust Certificate.
When running Validation Self Tests found on the CONNECT Portal (http://developer.connectopensource.org/display/NHINR30/CONNECT+Validation+Tests), certificates are only needed for Outbound Tests. The self-tests are designed to run on the same gateway. Entrust certificates are needed only when communicating with the NHIN.
Q: Can you use MSSQL too?
Yes. You would need to update hibernate files in %NHINC_PROPERTIES_DIR%\nhin\hibernate. This is a topic that would be good for someone in the Open Source community to further explore.
Q: I currently have CONNECT 2.1 installed. Can I install 2.4 over 2.1 or do I first need to uninstall 2.1? If I need to uninstall, are there any instructions on how to do that?
There are currently not instructions to migrate from 2.1 to 2.4. This would be a great topic for the Code-A-Thon. There have been significant changes from 2.1 to 2.4, including tool upgrades and code changes, so it is recommended to uninstall old tools and run a new install.
Q: Does this script [database script] assume all files are located in the C drive or is it flexible regarding where the files are installed?
It is flexible. It just needs to be able to recognize where mySQL is installed and be able to access the script from wherever the source code is checked-out.
Q: If we've installed previous versions of Connect, is there anything that we need to know to upgrade to the current version, or do we just go through all of these steps again to refresh the source code and rebuild?
This depends on the previous version of CONNECT. Going from 2.2 to 2.3, the version of Netbeans/GlassFish as well as mySQL changed. Therefore, these tools would need to be updated. The change from 2.3 to 2.4 was not as significant. See next question.
Q: I upgraded from CONNECT 2.3 to CONNECT 2.4 what are necessary steps to be taken?
The tool stack from 2.3 to 2.4 remains the same. Ideally checking out the new 2.4 code and building/deploying should work, but no one here has testing simply doing that. If you can get 2.4 working by just checking out the new 2.4 code (you can run an SVN SWITCH), building and deploying, please share with the community.
Q: I just copied the new files keeping the old files of CONNECT 2.3 , will it work?
This depends on what files you copied. No one has officially tested just replacing the 2.3 source with the 2.4 source, but if you can get it working, please post to the forum and let us know.
Q: How much space required for full install from scratch?
Approximately 1GB for GlassFish + CONNECT
Q: IF we're in dev/test mode and we want to test transferring information between our gateway and a test federal server, do we need an OID?
Yes. You also need an Entrust Certificate.
Q: What's the difference between 2.4 and 2.4.1?
Release Notes here: http://developer.connectopensource.org/display/NHINR24/2.4.1
Q: If I install two instances with the copyv3 certs, can they talk to each other?
Yes. You would need to do a self-signed certificate exchange.
Q: What do you know about moving NHIN services to the cloud in the next release?
More details concerning CONNECT and the cloud in the near future.
Q: Is current version 2.4 or 2.4.1?
The latest release as of today (April 22nd, 2010) is CONNECT 2.4.1.
Q: What's the current version for the code-a-thon?
https://svn.connectopensource.org:8443/svn/Nhin_Public/Current
It can also be found here: http://developer.connectopensource.org/display/CONNECTWIKI/Source+Code+Repository
Q: Can we install Connect gateway on 2 machines and communicate those two for patient search through UniversalClientGUI?
Yes, the UniversalClientGUI can be used to query to another machine as long as the installations and configurations on each of the machines is set properly.
Q: Is there any specific doc for defining OpenSSO policies for CONNECT?
Here is the page that talks about OpenSSO and CONNECT: http://developer.connectopensource.org/display/NHINR30/OpenSSO+Policy+Engine
There are currently 2 options in regards to the implementation of the Policy Decision Point (PDP). The first is an implementation by Jericho (http://developer.connectopensource.org/display/NHINR30/Jericho+Policy+Engine), and the second is a simple reference implementation in the AdapterPDPOpenSSO Web Application. Currently our behavior is simply based on the patient opt-in status. One can customize the decision making logic in the XSPAXACMLAuthzDecisionQueryHandler which implements the RequestHandler as required by OpenSSO. In that manner a user can define how his system will make decisions on the information provided to it. Once they install that generated class into the OpenSSO instance in GF it will be used.
There are many general pages out on the web regarding philosophies of creating a PDP and on OpenSSO. Here are a few:
https://opensso.dev.java.net/public/use/docs/fampdf/techover.pdf
https://opensso.dev.java.net/public/use/docs/opensso/index.html
http://wikis.sun.com/display/OpenSSO/getstarted
Q: For problems with the validation tests, is the best way to resolve those issues before the code-a-thon to post the issue to the forum?
Yes. Feel free to seek help from the Installation Forum: http://www.connectopensource.org/developer-resources/forums
Q: Do we need an NHIN OID or can we use our existing HL7 OID?
The NHIN OID’s are generated through HL7. As long as your organization has registered the OID with HL7, there should not be a problem.
Also, for internal testing, you ca use whatever OID you want for a Home Community ID. When on the NHIN, that organization would have to obtain a real OID.
