CONNECT Linux Source Install Webinar Questions Log (04/10)
April 20, 2010, 2:00pm – 4:00pm
Q: Is there any way to record this webinar?
Yes, please see post-Webinar artifacts here: http://www.connectopensource.org/about/events
Q: Is there a link to the presentation?
Yes, please see here: http://www.connectopensource.org/about/events
Q: Do I have to use https for svn checkout?
Yes.
Q: How big are the source files altogether?
796MB (after checkout, before building)
Q: I have seen problems where the paths get too long because the paths start too deep. There seems to some limit to path names in some places.
We have not seen this problem on Linux. We’ve seen similar problems with zip files in the past and solved the problem by using 7Zip. If there are issues with long paths, please post to the CONNECT Forum and we will address it.
Q: Can you install copyv3 now and ENTRUST later?
Yes! No special rules to uninstall. The Entrust Certificates are found here: http://developer.connectopensource.org/display/NHINR24/Certificate+Setup
There will be instructions on that page to change <jvm-options> in domain.xml to reflect those Entrust Certificates.
Q: Does it work with older version mysql?
It may work on older versions, but we have fully tested and fully support v. 5.1.
Q: Do we need to have glassfish running while building and deploying CONNECT?
GlassFish does not need to run when you compile. It does need to run for deployment, but “ant deploy” will do this for you.
Q: Do you have any test for Document Submission?
There are tests for Async XDR request in Internal and EndToEnd self-tests. The tests on the CONNECT 2.4.1 page have these: http://developer.connectopensource.org/display/NHINR24/2.4.1
Q: There are instruction for Windows and Solaris. How about Linux?
Follow the Solaris instructions for the Linux Validation Tests. We may have documentation for Linux tests in the future. For now, the Solaris instructions work for the Linux environment.
Q: Are the Internal Self Test instructions meant to use your new OID as LocalHCID or 1.1?
If you have requested and OID, the LocalHCID is the new OID.
Q: Could you please run a few validation test live?
Sorry, we did not catch this question during the webinar. If you have problems with the Validation tests, please post to the Connect.Installation Issues forum, including the server.log file and details of the test failures, and we can reply with assistance.
Q: Does Connect support any other Application servers such as Weblogic, Websphere, JBoss than GlassFish?
Not yet. We are looking into it. CONNECT has run JBoss in the past, but we are current using GlassFish now.
Q: What all app servers other than Glassfish are supported?
Currently, just GlassFish.
Q: Do you have auto start script when machine is started?
We do not yet have an auto start script. However, this would be a great open source contribution.
Q: Off the topic perhaps, what will be happening at the code-a-thon?
Topics are listed here: http://www.connectopensource.org/about/events/code-a-thon-april-2010
New sessions can be started at the Code-a-Thon if there are enough participants interested in an issue.
Q: Any plan on MAC OSX?
There were groups at previous Code-A-Thons working on MAC OSX compliance. There are no immediate CONNECT plan to support MAC OSX, but if you get it working, please share with the community. This would be a great Code-A-Thon session.
Q: Will Connect support Oracle database?
This is currently in the works for CONNECT 3.0.
Q: Can this installation be done on Ubuntu 8?
We have not tested on Ubuntu. If someone in the community can tests it on Ubuntu 8, please let us know the results.
Q: I tried on Ubuntu. It seems working.
Great!
Q: I'm working on installing on Ubuntu 9.10, will let you know how it goes.
Thanks
Q: After the install, is there a test script to verify & validate installation?
Yes. Please run the Validation Tests. There is a link at the bottom of the Installation Page (http://developer.connectopensource.org/display/NHINR30/Source+Code+Install+(Linux) or you can access it directly here: http://developer.connectopensource.org/display/NHINR30/CONNECT+Validation+Tests)
Q: Does CONNECT use any X-window package? Reason I am asking is that I probably want to use server version of UNIX.
We leave this to the user. We have used Cygwin in the past, but we let the users choose their own X-window packages.
Q: I had trouble checking out the code at too deeply nested a subdirectory. Is it really true that you can check out the code into ANY subdirectory?
As long as the directory has enough disk space and permissions are set appropriately, there should not be a problem. Please post your problem in more detail on the forum so we can better address it.
Q: Is it [CONNECT] fully J2EE compliant?
It is our intent that is fully J2EE compliant. However, we have not analyzed every part of it to determine if there are areas of non-compliance.
Q: Can CONNECT be installed on cluster environment?
We develop CONNECT using the Glassfish developer profile. We also have occasion to create the Enterprise profile if the system is required to be FIPS compliant as we need the NSS data stores. As mentioned here the third profile is the Cluster profile. Here is a document which explains each of these profiles: http://docs.sun.com/app/docs/doc/819-3671/gelvk?a=view.
The applications that we develop will run in any profile; however, the configurations such as in the generated domain.xml may be different. While we have not had occasion to investigate the cluster profile and thus do not have documentation for it, I feel that one could configure in this manner.
Q: In relation to OpenSSO, is there any specific doc for that which defines how to set policy engine and policies?
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
