Best Practices for Implementing New Aeon Web Pages from Testweb to Production (v5.0)

Print Friendly and PDF Follow

Here are the recommended steps for moving edited Aeon web pages from testweb to production.  Please be sure that you've thoroughly tested the web pages in testweb before going live with your edited pages. 

If you need assistance identifying your production directory, finding your testweb, or completing any of the steps in this article, please contact your Aeon support representative.

If you have issues after loading your new files, locate your backup and contact your Aeon support representative to discuss the best options for troubleshooting or reverting to your backup.

Implementation Process for Sites in the PCI Environment

If your institution is using a credit card payment provider gateway and in the Atlas hosted PCI environment, your web pages will need to undergo a secure code review before implementation into production in order to adhere to PCI security requirements. After the code review, Atlas Staff will put the new pages into production for you. If you have any questions or would like to schedule a code review, please contact Atlas Support at

Implementation Process for Sites using Remote Authentication

If your institution is using remote authentication, you will have to perform the process below for both your unprotected and protected web directories and also make sure to test your dual authentication landing page (index.cshtml), if applicable. Please note that the dual authentication landing page does not have a testweb. Any edits must be made on the live page and should be tested as soon as it is published. 

Implementation Steps

Prepare Production folder (usually C:\Program Files (x86)\Aeon\Web)

  • Copy and save current production folder contents (including subfolders) and store locally as backup. Do not save backups on the production Aeon server. If Atlas support staff are implementing pages for you, they'll send you a zip file of your current production directory via SendSafely.
  • Delete css, js folders
    • This assumes you are using only css and js located in your testweb folder. If you are relying on css or js from the production folder linked to testweb, you will need to retain those files in the production directory.
  • Delete all .html files
  • Delete all .replaced files
  • Delete any old Aeon web backup folders to reduce confusion and prevent errors referencing the wrong web files.

Leave in place and do not modify or delete:

  • .dll files
  • .txt files
  • .props files
  • .config files
  • .xslt files
  • Folders including
    • Testweb
    • PDF

Install new web pages:

Copy into production folder from testweb folder:

  • Folders (with contents including any subfolders)
    • css
    • js
    • templates
    • RIS
  • All html files

DO NOT copy over webpath.txt or .props files from testweb to production.

Thoroughly test logging in and navigating the new pages.  


If this article didn’t resolve your issue, please contact Atlas Support for assistance:

Contact Support