Changeset 22687 in main


Ignore:
Timestamp:
03/11/21 21:31:28 (5 weeks ago)
Author:
GarthBraithwaite_STG
Message:

nm and epht - updated ss prop for latest core code.

Location:
adopters
Files:
1 deleted
2 edited

Legend:

Unmodified
Added
Removed
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/WEB-INF/config/SiteSpecific.properties

    r22684 r22687  
    6060#commonContentBasePath.string =file:/d:/tomcat7/webapps/ibisph-content/
    6161#commonContentBasePath.string =http://localhost/ibisph-content/
    62 # THIS VALUE NEEDS TO BE THE URL TO THE PRODUCTION CONTENT SERVER
    63 # FOR LOCAL DEV THE FOLLOWING VALUE SHOULD BE PLACED IN A USER PROPERTIES FILE AND HAVE A PATH LIKE:
    64 commonContentBasePath.string =../nmepht-content/
     62###### FOR PRODUCTION, THIS VALUE NEEDS TO BE THE URL TO THE PRODUCTION CONTENT SERVER
     63commonContentBasePath.string   =http://10.135.2.255/test/nmepht-content/
     64
     65###### FOR LOCAL DEV THE FOLLOWING VALUE SHOULD BE PLACED IN A USER PROPERTIES FILE AND HAVE A PATH LIKE:
     66#commonContentBasePath.string =../nmepht-content/
    6567
    6668communityRequestPathPrefixToRemove.string =/dataportal/community/
     
    7375#       If the published XML is in a different location then both paths should be
    7476#       specified.
     77###### PRODUCTION SHOULD POINT TO THE CONTENT SERVER's IBIS XML base path.
     78commonPublishedXMLBasePath.string =http://10.135.2.255/test/nmibis-content/xml/
    7579
    76 # THIS VALUE SHOULD BE THE PRODUCTION NM IBIS VIEW APP.
    77 #commonPublishedXMLBasePath.string =https://ibis.health.state.nm.us/nmibis-view/view/xml/
    78 # FOR LOCAL DEV THE LOCAL USER FILE SHOULD CONTAIN VALUE TO POINT TO TEST  or LEAVE IT POINTING TO PROD!
    79 commonPublishedXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-view/view/xml/
     80#### FOR LOCAL DEV THE LOCAL USER FILE SHOULD CONTAIN VALUE TO POINT TO TEST
     81#### or LEAVE IT POINTING TO PROD (if access)  or  the production view webapp's "view/xml" requset.
     82#### The VALUE BELOW IS SAFE AND SHOULD WORK EVERY WHERE - EXCEPT POINTED TO PROD.
     83# commonPublishedXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-view/view/xml/
     84
    8085
    8186
  • adopters/nm/trunk/src/main/webapps/nmibis-view/WEB-INF/config/SiteSpecific.properties

    r22611 r22687  
    11#------------------------------------------------------------------------------
    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
     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
    56#
    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. 
     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).
    1014#
    1115# The use of this file is OPTIONAL.  These values can be specified in the ss.xml
     
    1620#
    1721# PATH CONVENTION:
    18 # All paths shall have a trailing "/".  Sub paths should never have a leading "/"
     22# Paths shall have a trailing "/".  Sub paths should never have a leading "/"
    1923# but will always have the trailing "/".  Base paths can have a leading "/" as
    2024# this represents the root of the file system.
    2125#------------------------------------------------------------------------------
    2226
    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.
     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.
    2734#
    2835#       HTTPS NOTE: things like https://kyibis.mc.uky.edu/ehl/query/proxy can choke
    2936#       because cert is not verified!
    3037#
    31 # Linux   Example: http://hlcbsas/cgi-bin/hi_iq_func
    32 # Windows Example: http://localhost/cgi-bin/hi_iq_func.exe
    33 # Proxy   Example: http://ibis.mt.gov/query/proxy (request to another view app that makes the actual ibisq request)
    34 #queryIBISQRequestPath.string =http://10.135.2.255/cgi-bin/hi_iq_func3.exe
    35 #queryIBISQRequestPath.string =https://ibistest.health.state.nm.us/nmibis-view/query/proxy/1.xml
    36 queryIBISQRequestPath.string =http://127.0.0.1:8888/cgi-bin/hi_iq_func3.exe
     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
     41# THIS WAS THE VALUE IN THE v3 SS?????:  queryIBISQRequestPath.string =http://127.0.0.1:8888/cgi-bin/hi_iq_func3.exe
     42queryIBISQRequestPath.string =http://10.135.2.255/cgi-bin/hi_iq_func3.exe
    3743
    38 #--- Most adopters should be splitting their XML and JSON content out from the
    39 #        ibisph-view webapp.  This has several advantages like shared data and not
    40 #        having to put any content files in the deployment package.  The main content
    41 #        path is specified below.  The xml and json paths by default are subdirs
    42 #        below the main content path.  Below are examples of how to specify the base
    43 #        content file path used by all "Path" type bean configurations. 
    44 #    Again this simply provides a mechanism to easily locate files to a
    45 #    directory outside of the webapp.  The default location is the relative
    46 #    "" path within the webapp.   
     44
     45#--- Content Paths.  Adopters should be splitting their content from the
     46#       ibisph-view webapp.  This allows the ibis webapp to be seperate from the
     47#       content which allows the content to be managed without having to touch the
     48#       deployed webapp.
     49#
     50#       There are two types of content published XML and static content.  Published
     51#       XML is the ibis-admin app's data that is published to XML files (org units,
     52#       topics, measures, published indicators etc.).  Static content include images,
     53#       json, pdfs, HTML_CONTENT XML files, query module XML files, SELECTION XML
     54#       files and any content that is maintained by hand.  Published and static files
     55#       can exist in different places although most adopters will likely keep them
     56#       together.  The exception is if the static content is on a different server
     57#       so that it is more easily managed while the published data is on a server
     58#       that has the ibis data admin app.
     59#
    4760#commonContentBasePath.string =../../ibisph-content/
    4861#commonContentBasePath.string =file:/d:/tomcat7/webapps/ibisph-content/
    49 #commonContentBasePath.string =https://ibistest.health.state.nm.us/nmibis-content/
    50 commonContentBasePath.string =../nmibis-content/
     62#commonContentBasePath.string =http://localhost/ibisph-content/
     63###### FOR PRODUCTION, THIS VALUE NEEDS TO BE THE URL TO THE PRODUCTION CONTENT SERVER
     64commonContentBasePath.string =http://10.135.2.255/test/nmibis-content/
    5165
    52 #--- Special Content Path Uses
    53 #    For development users to access QA or production IP XMLs place a local, user
    54 #    property override file in the [user]/nmibis-view.properties file with an
    55 #    entry like:
    56 #indicatorXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-content/xml/indicator/
    57 #    This same can be applied to any other directory values like commonContentBasePath.string
    58 #    and ephtContentBasePath.string etc.
     66##### FOR LOCAL DEV THE FOLLOWING VALUE SHOULD BE PLACED IN A USER PROPERTIES FILE AND HAVE A PATH LIKE:
     67#commonContentBasePath.string =../nmibis-content/
     68
     69
     70#--- Example of published XML on different server. 
     71#       The core code defaults to the published XML path being the same as the
     72#       content's XML path which in both cases is the base path with an "xml/" suffix.
     73#       If the published XML is in a different location then both paths should be
     74#       specified.
     75#commonPublishedXMLBasePath.string =http://admin.ibis.org/ibisph-admin-published-content/xml
     76
     77###### PRODUCTION SHOULD POINT TO THE CONTENT SERVER's IBIS XML base path.
     78commonPublishedXMLBasePath.string =http://10.135.2.255/test/nmibis-content/xml/
     79
     80#### FOR LOCAL DEV THE LOCAL USER FILE SHOULD CONTAIN VALUE TO POINT TO TEST
     81#### or LEAVE IT POINTING TO PROD (if access)  or  the production view webapp's "view/xml" requset.
     82#### The VALUE BELOW IS SAFE AND SHOULD WORK EVERY WHERE - EXCEPT POINTED TO PROD.
     83# commonPublishedXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-view/view/xml/
    5984
    6085
     
    6691#        handle file privs/security.  This is needed for those adopters that have
    6792#        sensitive, non public IP files and is a good practice in general.
     93#        Default value: "http://localhost/ibisph-admim/xml/preview/indicator/profile/"
    6894indicatorPreviewFilePath.string =http://localhost:8080/nmibis-admin/view/xml/preview/indicator/profile/
    6995
    7096
    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 =https://ibis.health.state.nm.us
     97#--- Explicit base server with app context request URL prefix.  This value is
     98#       the base of all view webapp page link requests.  If the value is blank then
     99#       the app creates a default value that is the first HTTP request's URL for
     100#       protocol, server name and context path.  For most situations this is default
     101#       value is preferred (fine being left blank so that the working actual request
     102#       URL is used).  However, in some deployments behind a proxy or if nervous
     103#       about the first working request not being correct (i.e. mixed HTTP HTTPS
     104#       deployments) then this value can be specified.  See notes in the
     105#       commonWebAppBasePathModelMap
     106#        (common.xml).  Default value: "".  Below is an example:
    86107
    87108#--- For development users IF the above is set, place a local, user property
    88 #    override file in the  [user]/nmibis-view.properties file with an entry of:
    89 commonWebAppBaseRequestPath.string =http://127.0.0.1:8080/nmibis-view/
     109#    override file in the  [user]/ibisph-view.properties file with an entry of:
     110commonWebAppBaseRequestPath.string =
     111# WAS v3 SS.XML VALUE???: commonWebAppBaseRequestPath.string =http://127.0.0.1:8080/nmibis-view/
    90112
    91113
    92114#--- self registered user email overrides
     115#    BELOW ARE PLACEHOLDERS that adopters using MyData should specify.
    93116userEmailVerificationService.mailMessageFrom =nm-ibis.user.verification@state.nm.us
    94117userEmailVerificationService.mailSubject     =NM IBIS - Self Registed MyData Account Verification
Note: See TracChangeset for help on using the changeset viewer.