Changeset 22740 in main


Ignore:
Timestamp:
03/23/21 20:52:11 (3 weeks ago)
Author:
GarthBraithwaite_STG
Message:

nm and epht - updated ss props with new local path.

Location:
adopters
Files:
3 edited

Legend:

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

    r22687 r22740  
    4747#       deployed webapp.
    4848#
    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.
     49#       There are three types of content published XML, static content (xml, pdf,
     50#       images, etc), and saved XML content (saved query, self registered users). 
     51#       - Published XML is the ibisph-admin app's published content data (org units,
     52#       topics, measures, published indicators etc.).  These files should always be
     53#       referenced and never versionsed as they are dynamic content.  These files
     54#       will live on the same server (or fileserver) as the ibisph-admin app. 
     55#       - Static content include images, json, pdfs, HTML_CONTENT XML files, query
     56#       module XML files, SELECTION XML files and any content that is maintained by
     57#       hand.  This content is read only and can live anywhere as long as the file
     58#       is accessible via a URL (shared fileserver or web server etc.).  These types
     59#       of files are likely versioned and maintained by hand.
     60#       - Saved XML (saved query, self registered users, and possibly cached data)
     61#       are view webapp dynamically created files.  As such just like the admin app,
     62#       theese produced files will live on the same webapp server (or fileserver). 
     63#       IMPORTANT NOTE: These file should never be saved within the view webapp
     64#       because future webapp deployment conflicts (could overwrite the user saved
     65#       files) or for those adopters who deploy as an .ear or .war and choose to keep
     66#       the file zipped instead of expanding it. 
     67#
     68#       It is possible for all three published, static, and saved files to live on
     69#       the same app server and in the same directory structure.  It is also very
     70#       likely that all live on their own server.
    5871#
    5972#commonContentBasePath.string =../../ibisph-content/
     
    6376commonContentBasePath.string   =http://10.135.2.255/test/nmepht-content/
    6477
    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/
     78#--- Example of published XML on different server. 
     79#       The core code defaults to the published XML path being the same as the
     80#       content's XML path which in both cases is the base path with an "xml/" suffix.
     81#       If the published XML is in a different location then both paths should be
     82#       specified.
     83#commonPublishedXMLBasePath.string =http://admin.ibis.org/ibisph-admin-published-content/xml
     84
     85#--- Example of saved/local XML on same webapp server but within a different dir.
     86#       If not defined, the app config defaults to the commonContentBasePath.
     87#       IMPORTANT: If the commonContentBasePath is a URL and points to a different
     88#       server this value MUST be specified and MUST be locally accessible file path.
     89#commonLocalBasePath.string =../ibisph-user-content
     90#commonLocalBasePath.string =file:/s:/ibisph-view-saved-content
     91
    6792
    6893communityRequestPathPrefixToRemove.string =/dataportal/community/
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/xslt/html/SiteSpecific.xslt

    r22659 r22740  
    203203                                                <ul>
    204204                                                        <li><a href="{$ibis.baseRequestPath}about/AboutEPHT.html" title="What is Environmental Public Health Tracking?">About Tracking</a></li>
    205                                                         <li><a href="{$ibis.baseRequestPath}about/Introduction.html" title="Background of NM Tracking">Background</a></li>
     205                                                        <li><a href="{$ibis.baseRequestPath}about/OurStory.html" title="Background of NM Tracking">Our Story</a></li>
    206206                                                        <li><a href="{$ibis.baseRequestPath}about/ContactInformation.html" title="Contact Information">Contact Us</a></li>
    207207                                                </ul>
  • adopters/nm/trunk/src/main/webapps/nmibis-view/WEB-INF/config/SiteSpecific.properties

    r22687 r22740  
    4848#       deployed webapp.
    4949#
    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.
     50#       There are three types of content published XML, static content (xml, pdf,
     51#       images, etc), and saved XML content (saved query, self registered users). 
     52#       - Published XML is the ibisph-admin app's published content data (org units,
     53#       topics, measures, published indicators etc.).  These files should always be
     54#       referenced and never versionsed as they are dynamic content.  These files
     55#       will live on the same server (or fileserver) as the ibisph-admin app. 
     56#       - Static content include images, json, pdfs, HTML_CONTENT XML files, query
     57#       module XML files, SELECTION XML files and any content that is maintained by
     58#       hand.  This content is read only and can live anywhere as long as the file
     59#       is accessible via a URL (shared fileserver or web server etc.).  These types
     60#       of files are likely versioned and maintained by hand.
     61#       - Saved XML (saved query, self registered users, and possibly cached data)
     62#       are view webapp dynamically created files.  As such just like the admin app,
     63#       theese produced files will live on the same webapp server (or fileserver). 
     64#       IMPORTANT NOTE: These file should never be saved within the view webapp
     65#       because future webapp deployment conflicts (could overwrite the user saved
     66#       files) or for those adopters who deploy as an .ear or .war and choose to keep
     67#       the file zipped instead of expanding it. 
     68#
     69#       It is possible for all three published, static, and saved files to live on
     70#       the same app server and in the same directory structure.  It is also very
     71#       likely that all live on their own server.
    5972#
    6073#commonContentBasePath.string =../../ibisph-content/
     
    8295#### The VALUE BELOW IS SAFE AND SHOULD WORK EVERY WHERE - EXCEPT POINTED TO PROD.
    8396# commonPublishedXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-view/view/xml/
     97
     98
     99#--- Example of saved/local XML on same webapp server but within a different dir.
     100#       If not defined, the app config defaults to the commonContentBasePath.
     101#       IMPORTANT: If the commonContentBasePath is a URL and points to a different
     102#       server this value MUST be specified and MUST be locally accessible file path.
     103#commonLocalBasePath.string =../ibisph-user-content
     104#commonLocalBasePath.string =file:/s:/ibisph-view-saved-content
     105
    84106
    85107
Note: See TracChangeset for help on using the changeset viewer.