source: main/trunk/ibisph-view/src/main/webapp/WEB-INF/config/SiteSpecific.properties @ 22683

Last change on this file since 22683 was 22683, checked in by GarthBraithwaite_STG, 2 months ago

view - Implemented normal content path and published path with updated comments. Removed report requests as not currently implemented in v3 with no signs of ever being. css tweaks.

File size: 6.1 KB
Line 
1#------------------------------------------------------------------------------
2# Site Specific String Property Overrides for the IBIS-PH View app/system. 
3# These values are Spring context configuration "string" bean definitions i.e.
4# only string type bean values can be specified here.  See the ss.xml to override
5# actual bean definitions.  The form is: beanID.propertyName = value
6#
7# IMPORTANT: For these values to be used, this string property override must be
8# referenced.  This is typically specified via the siteSpecificPropertyOverrides
9# bean which is a default core implementation that is typically contained in the
10# config/srping/SiteSpecific.xml file.  There is typically a more specific
11# property override file specified that is used for local development properties
12# to be specified.  This property file is typically in the user's home directory
13# (see the siteSpecificPropertyOverrides bean for a complete list of files refd).
14#
15# The use of this file is OPTIONAL.  These values can be specified in the ss.xml
16# file as well but require more work as a complete, whole new bean with the same
17# name will need to be defined.  This file is useful for poking string values into
18# existing bean definitions or when specifying different values to be used while
19# keeping the same war file deployable to multiple environments without mods.
20#
21# PATH CONVENTION:
22# Paths shall have a trailing "/".  Sub paths should never have a leading "/"
23# but will always have the trailing "/".  Base paths can have a leading "/" as
24# this represents the root of the file system.
25#------------------------------------------------------------------------------
26
27#--- IBISQ/QueryApplication URL address.  For local, non sas development the
28#       addresses can reference a proxy to the deployed IBIS View system which has
29#       to be configured for the proxy request and is setup for the backend server
30#       (the address to SAS Intrnet, or the actual address of the webserver/IBIS-Q
31#       SAS CGI application).
32#
33#       Proxy request made to a view app that makes the actual ibisq request.
34#
35#       HTTPS NOTE: things like https://kyibis.mc.uky.edu/ehl/query/proxy can choke
36#       because cert is not verified!
37#
38# Linux Example:        http://hlcbsas/cgi-bin/hi_iq_func
39# Windows Example:      http://localhost/cgi-bin/hi_iq_func.exe
40# Proxy Example:        http://ibis.mt.gov/query/proxy/temp.xml
41queryIBISQRequestPath.string =http://localhost/cgi-bin/hi_iq_func.exe
42
43
44#--- Content Paths.  Adopters should be splitting their content from the
45#       ibisph-view webapp.  This allows the ibis webapp to be seperate from the
46#       content which allows the content to be managed without having to touch the
47#       deployed webapp.
48#
49#       There are two types of content published XML and static content.  Published
50#       XML is the ibis-admin app's data that is published to XML files (org units,
51#       topics, measures, published indicators etc.).  Static content include images,
52#       json, pdfs, HTML_CONTENT XML files, query module XML files, SELECTION XML
53#       files and any content that is maintained by hand.  Published and static files
54#       can exist in different places although most adopters will likely keep them
55#       together.  The exception is if the static content is on a different server
56#       so that it is more easily managed while the published data is on a server
57#       that has the ibis data admin app.
58#
59#commonContentBasePath.string =../../ibisph-content/
60#commonContentBasePath.string =file:/d:/tomcat7/webapps/ibisph-content/
61#commonContentBasePath.string =http://localhost/ibisph-content/
62commonContentBasePath.string =../../ibisph-content/
63
64#--- Example of published XML on different server. 
65#       The core code defaults to the published XML path being the same as the
66#       content's XML path which in both cases is the base path with an "xml/" suffix.
67#       If the published XML is in a different location then both paths should be
68#       specified.
69#commonPublishedXMLBasePath.string =http://admin.ibis.org/ibisph-admin-published-content/xml
70
71
72#--- Base admin app preview related XML file path.  Just like the content base
73#        path above, this can be a relataive, explicit file path or request URL.
74#
75#    IMPORTANT SECURITY NOTE: It is recommended to go through the admin app
76#        (e.g. URL request based) for XML IP file requests so that the admin app can
77#        handle file privs/security.  This is needed for those adopters that have
78#        sensitive, non public IP files and is a good practice in general.
79#        Default value: "http://localhost/ibisph-admim/xml/preview/indicator/profile/"
80indicatorPreviewFilePath.string =http://localhost/ibisph-admin/view/xml/preview/indicator/profile/
81
82
83#--- Explicit base server with app context request URL prefix.  This value is
84#       the base of all view webapp page link requests.  If the value is blank then
85#       the app creates a default value that is the first HTTP request's URL for
86#       protocol, server name and context path.  For most situations this is default
87#       value is preferred (fine being left blank so that the working actual request
88#       URL is used).  However, in some deployments behind a proxy or if nervous
89#       about the first working request not being correct (i.e. mixed HTTP HTTPS
90#       deployments) then this value can be specified.  See notes in the
91#       commonWebAppBasePathModelMap
92#        (common.xml).  Default value: "".  Below is an example:
93#commonWebAppBaseRequestPath.string =http://ibis.your_agency.gov/ibisph-view/
94
95#--- For development users IF the above is set, place a local, user property
96#    override file in the  [user]/ibisph-view.properties file with an entry of:
97#commonWebAppBaseRequestPath.string =
98
99
100#--- self registered user email overrides
101#    BELOW ARE PLACEHOLDERS that adopters using MyData should specify.
102userEmailVerificationService.mailMessageFrom =ibis@your_agency.gov
103userEmailPasswordService.mailMessageFrom     =ibis@your_agency.gov
104userEmailVerificationService.mailSubject     =IBIS-PH - Self Registed MyData Account Verification
105userEmailPasswordService.mailSubject         =IBIS-PH - Your MyData Account Password
106
107#----------------------------------- END OF FILE -----------------------------
108
Note: See TracBrowser for help on using the repository browser.