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

Last change on this file since 25299 was 25299, checked in by Paul Leo, 2 months ago

Commenting out a setting that is not being used for Hawaii Dev or Production. If someone is running a local version of admin, they may set this property in there user property file

File size: 5.7 KB
2# Site Specific Property Overrides for the IBIS-PH View app/system.  These values
3# are applied to the Spring context configuration bean definitions.  The form is:
4# beanID.propertyName = value
6# IMPORTANT: For these values to be used, they must be referenced.  This is
7# typically specified via the siteSpecificPropertyOverrides bean which is a
8# default core implementation that is contained in the config/srping/SiteSpecific.xml
9# file. 
11# The use of this file is OPTIONAL.  These values can be specified in the ss.xml
12# file as well but require more work as a complete, whole new bean with the same
13# name will need to be defined.  This file is useful for poking string values into
14# existing bean definitions or when specifying different values to be used while
15# keeping the same war file deployable to multiple environments without mods.
18# All paths shall have a trailing "/".  Sub paths should never have a leading "/"
19# but will always have the trailing "/".  Base paths can have a leading "/" as
20# this represents the root of the file system.
23#--- IBISQ/QueryApplication URL address.  The addresses can include a proxy to
24#       the deployed IBIS View system which is allowed to communicate to the backend
25#       server, the address to SAS Intrnet, or the actual address of the webserver/
26#       IBIS-Q SAS CGI application.
28#       HTTPS NOTE: things like can choke
29#       because cert is not verified!
31# Linux   Example: http://hlcbsas/cgi-bin/hi_iq_func
32# Windows Example: http://localhost/cgi-bin/hi_iq_func.exe
33# Proxy   Example: (request to another view app that makes the actual ibisq request)
34queryIBISQRequestPath.string =
37#--- Most adopters should be splitting their XML and JSON content out from the
38#        ibisph-view webapp.  This has several advantages like shared data and not
39#        having to put any content files in the deployment package.  The main content
40#        path is specified below.  The xml and json paths by default are subdirs
41#        below the main content path.  Below are examples of how to specify the base
42#        content file path used by all "Path" type bean configurations. 
43#    Again this simply provides a mechanism to easily locate files to a
44#    directory outside of the webapp.  The default location is the relative
45#    "" path within the webapp.   
46#commonContentBasePath.string =../../ibisph-content/
47#commonContentBasePath.string =file:/d:/tomcat7/webapps/ibisph-content/
48#commonContentBasePath.string =
49commonContentBasePath.string =../hhdw-content/
51#--- Special Content Path Uses
52#    For development users to access QA or production IP XMLs place a local, user
53#    property override file in the [user]/ file with an
54#    entry like:
55#indicatorXMLBasePath.string =
56#    This same can be applied to any other directory values like commonContentBasePath.string
57#    and ephtContentBasePath.string etc.
60#--- Base admin app preview related XML file path.  Just like the content base
61#        path above, this can be a relataive, explicit file path or request URL.
63#    IMPORTANT SECURITY NOTE: It is recommended to go through the admin app
64#        (e.g. URL request based) for XML IP file requests so that the admin app can
65#        handle file privs/security.  This is needed for those adopters that have
66#        sensitive, non public IP files and is a good practice in general.
67##### Not using for Hawaii.  If someone wants to run a local admin, add to user properties file
71#--- Base server with app context request URL to be used by the app when creating
72#    outside links back to the app.  This value needs to be the server name AND
73#    application context.  An example of where this value is used is for google
74#    search requests and the user self registration verification process email
75#    link.  The user is sent a verification email that has a URL that the user
76#    clicks to verify and activate their account.  This is needed because the
77#    server only knows its IP address - it has no idea what DNS entry is needed
78#    to get to itself.  For the same reason the outside application context path
79#    is also needed (upstream proxy can be one value while the app knows its
80#    context path differently).  This value is then used internally by the code
81#    to build the actual request URL.  This value defaults to:
82#    http://localhost/ibisph-view/ which is only used for local development.
83#    This value will never be the webapp's address and context the outside
84#    request and WILL fail (ie set this to the approp value).
85#commonWebAppBaseRequestPath.string =
87#--- For development users IF the above is set, place a local, user property
88#    override file in the  [user]/ file with an entry of:
89commonWebAppBaseRequestPath.string =
92#--- self registered user email overrides
94userEmailVerificationService.mailSubject     =HHDW IBIS - Self Registed MyData Account Verification
96userEmailPasswordService.mailSubject     =Your HHDW-IBIS MyData Account Password
98#----------------------------------- END OF FILE -----------------------------
Note: See TracBrowser for help on using the repository browser.