iSharkFly-Open
/
VistA-EDIS
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

added information about configuring VistALink and SSL to README

This commit is contained in:
sblaz 2011-09-19 01:16:39 +00:00
parent adbffb9a7c
commit 33169bafb6
1 changed files with 26 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
java/README
View File

@ -29,4 +29,29 @@ Optional artifacts include:
tracking-server-bigboard/target/bigboard.war EDIS big board designed for use with no logged in user (requires configuration) tracking-server-bigboard/target/bigboard.war EDIS big board designed for use with no logged in user (requires configuration)
tracking-server-ear/target/edis.ear main.war, help.war, bigboard.war packaged as an .ear tracking-server-ear/target/edis.ear main.war, help.war, bigboard.war packaged as an .ear
Pick and choose which are appropriate depending on your deployment platform and configuration. Pick and choose which are appropriate depending on your deployment platform and configuration.
## Configuring VistALink
Currently, VistALink connection settings are "baked in" to the web application in the following file:
tracking-server-main/src/main/web-app/WEB-INF/config/vistalink-config.xml
You can either edit this before performing a build so that main.war contains your connection settings, or do it after deploying main.war to your servlet container in "exploded" mode.
Possible future development could store this connection information with some alternative implementation, like in a relational database, for example. One could potentially write a VistALink connection info administration UI as well.
## Configuring SSL
Currently, EDIS is not configured to enforce channel security over SSL, though it should be able to run over SSL if you have configured your servlet container to serve it over SSL, which you most certainly should do. If you'd like it to serve user-friendly welcome pages over port 80 and still require SSL for other bits, you will need to tweak the spring-security configuration located at:
tracking-server-main/src/main/web-app/WEB-INF/config/security-config.xml
The main web application uses the spring security framework (version 2.0.7) to implement its security layer. You can read more about it here:
http://static.springsource.org/spring-security/site/docs/2.0.x/reference/springsecurity.html
## EDIS Big Board Automatic Login with No User
Currently the EDIS Big Board web application (bigboard.war) has no authentication mechanism configured at all. VA's implementation was a WebLogic specific 2-way SSL authentication mechanism. If you want automatically authenticating big boards you will need to implement the equivalent yourself.
The main EDIS application (main.war) contains a copy of the Big Board that runs as a signed-in user, which should work as a starting point.