source: main/adopters/hi/trunk/src/main/webapps/hhdw-view/WEB-INF/config/SiteSpecific.properties @ 25299

#------------------------------------------------------------------------------
# Site Specific Property Overrides for the IBIS-PH View app/system.  These values 
# are applied to the Spring context configuration bean definitions.  The form is: 
# beanID.propertyName = value
#
# IMPORTANT: For these values to be used, they must be referenced.  This is 
# typically specified via the siteSpecificPropertyOverrides bean which is a 
# default core implementation that is contained in the config/srping/SiteSpecific.xml 
# file.  
#
# The use of this file is OPTIONAL.  These values can be specified in the ss.xml
# file as well but require more work as a complete, whole new bean with the same
# name will need to be defined.  This file is useful for poking string values into
# existing bean definitions or when specifying different values to be used while 
# keeping the same war file deployable to multiple environments without mods.
#
# PATH CONVENTION:
# All paths shall have a trailing "/".  Sub paths should never have a leading "/"
# but will always have the trailing "/".  Base paths can have a leading "/" as 
# this represents the root of the file system.
#------------------------------------------------------------------------------

#--- IBISQ/QueryApplication URL address.  The addresses can include a proxy to 
#       the deployed IBIS View system which is allowed to communicate to the backend 
#       server, the address to SAS Intrnet, or the actual address of the webserver/
#       IBIS-Q SAS CGI application.
#
#       HTTPS NOTE: things like https://kyibis.mc.uky.edu/ehl/query/proxy can choke 
#       because cert is not verified!
#
# Linux   Example: http://hlcbsas/cgi-bin/hi_iq_func
# Windows Example: http://localhost/cgi-bin/hi_iq_func.exe
# Proxy   Example: http://ibis.mt.gov/query/proxy (request to another view app that makes the actual ibisq request)
queryIBISQRequestPath.string =http://10.0.1.141:8081/cgi-bin/hi_iq_func.exe


#--- Most adopters should be splitting their XML and JSON content out from the 
#        ibisph-view webapp.  This has several advantages like shared data and not 
#        having to put any content files in the deployment package.  The main content
#        path is specified below.  The xml and json paths by default are subdirs 
#        below the main content path.  Below are examples of how to specify the base 
#        content file path used by all "Path" type bean configurations.  
#    Again this simply provides a mechanism to easily locate files to a 
#    directory outside of the webapp.  The default location is the relative 
#    "" path within the webapp.   
#commonContentBasePath.string =../../ibisph-content/
#commonContentBasePath.string =file:/d:/tomcat7/webapps/ibisph-content/
#commonContentBasePath.string =https://ibistest.health.state.nm.us/nmibis-content/
commonContentBasePath.string =../hhdw-content/

#--- Special Content Path Uses
#    For development users to access QA or production IP XMLs place a local, user 
#    property override file in the [user]/nmibis-view.properties file with an 
#    entry like:
#indicatorXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-content/xml/indicator/
#    This same can be applied to any other directory values like commonContentBasePath.string
#    and ephtContentBasePath.string etc.


#--- Base admin app preview related XML file path.  Just like the content base
#        path above, this can be a relataive, explicit file path or request URL.
#
#    IMPORTANT SECURITY NOTE: It is recommended to go through the admin app 
#        (e.g. URL request based) for XML IP file requests so that the admin app can 
#        handle file privs/security.  This is needed for those adopters that have
#        sensitive, non public IP files and is a good practice in general.
##### Not using for Hawaii.  If someone wants to run a local admin, add to user properties file
#####indicatorPreviewXMLBasePath.string=../ibisph-admin/xml/indicator/profile/preview/


#--- Base server with app context request URL to be used by the app when creating 
#    outside links back to the app.  This value needs to be the server name AND
#    application context.  An example of where this value is used is for google 
#    search requests and the user self registration verification process email 
#    link.  The user is sent a verification email that has a URL that the user 
#    clicks to verify and activate their account.  This is needed because the 
#    server only knows its IP address - it has no idea what DNS entry is needed 
#    to get to itself.  For the same reason the outside application context path 
#    is also needed (upstream proxy can be one value while the app knows its 
#    context path differently).  This value is then used internally by the code 
#    to build the actual request URL.  This value defaults to:
#    http://localhost/ibisph-view/ which is only used for local development.
#    This value will never be the webapp's address and context the outside 
#    request and WILL fail (ie set this to the approp value).
#commonWebAppBaseRequestPath.string =http://ibis.hhdw.org/hhdw-view

#--- For development users IF the above is set, place a local, user property
#    override file in the  [user]/nmibis-view.properties file with an entry of:
commonWebAppBaseRequestPath.string =


#--- self registered user email overrides
userEmailVerificationService.mailMessageFrom =profiles@hhdw.org
userEmailVerificationService.mailSubject     =HHDW IBIS - Self Registed MyData Account Verification
userEmailPasswordService.mailMessageFrom =profiles@hhdw.org
userEmailPasswordService.mailSubject     =Your HHDW-IBIS MyData Account Password

#----------------------------------- END OF FILE -----------------------------