Enterprise ERP Post Server Transfer Information

Owned by Knowledge Assistant
Last updated: Oct 31, 2024
3 min read
Description of Issue

What information do I need to know after an EERP server transfer?

Context

  • Tyler Deploy

  • Enterprise ERP

  • On-Premise

  • Server Transfer

Cause

Post-server transfer information

Resolution

  • Several applications and services use the <domain>\tylerservice and <domain>\munisldap accounts; the password cannot be changed without impacting the system

  • Spool, Export, Import, Attachment and Report files are in the <drive>\musys folder on the application server.  Tyler recommends accessing these files via the EERP application as much as possible. Please review Using the File Transfer Program explaining how to use the File Transfer program within EERP

  • For the best application performance, users should access Tyler Hub URL’s using Google Chrome. Users will be prompted with a Tyler Identity login screen. If “remember me” is checked, users will stay logged in to Tyler Hub on the local browser for 30 days unless browser cache is cleared or if they sign out from Tyler Hub. It is also recommended that pop-up blockers be turned off 

  • The local muntrain and muntest databases can be refreshed from the most recent backup of munprod (from the dbexport folder).  Please review How to Refresh a Non Production Munis Database on how to refresh a non-production EERP database.  When refreshtest is invoked, it will automatically run through its database upgrade process, in case the destination environment is on a newer version than PROD

  • ReadyForms relies on Printer Definitions and Delivery Definitions within the EERP database. Performing a refresh of a EERP environment will replace these settings with the settings from the munprod database. If you wish to preserve these items, first export them from the target environment, run the refresh, and then re-import them into the target environment. Please review Export and Import Printer Definitions and create a backup for printer definitions and this  Copy ReadyForms Delivery Definitions From One Environment to Another for delivery definitions

  • EERP Self Service maintenance windows should be configured within Self Service Hosting for server maintenance periods. This will display a message to employees, citizens or vendors regarding the scheduled downtime. Please refer to How to Enable Self Service Maintenance Windows for further detail

  • Please review  to identify who is currently logged into EERP

  • The TCM HTML5 Twain Plugin installation packages are available on tyler community at https://tylercommunity.tylertech.com/content-manager/m/installation-files

  • During your server transfer testing period, please test in the “Production” environment on the target servers. This will ultimately become your Production environment once you are live on these servers and, as such, it is the most important environment to work any issues out of

  • During your server transfer testing period, please be aware of system changes such as Tyler Forms updates, printer definitions, roles, and user attributes. Tyler Form updates must be made on both servers. Printer definitions, role, and user attribute changes should be made on both servers, except version-dependent changes. Please inform your Deployment Engineer at the time of the cut to live where changes have been made (if any)

  • EERP Web Services (GAS) rely on the ability to communicate with the EERP database in order to start properly. Please keep this in mind when rebooting your servers. If your EERP databases and web services are on different servers, make sure the databases are available before starting the web services.

  • As of EERP version 2018.1, by default, EERP is configured to capture and share EERP production analytics with Tyler Technologies. The data we collect is uploaded to Azure and into Tyler’s Application Insights account. We are not collecting any personally identifiable information or sensitive data

  • For sites that leverage SQL Always On High Availability, rebooting of the SQL servers will cause the availability groups to fail over to a single server.  Once all the SQL servers are back online you will want to manually failover groups to split up the database traffic as you desire

Additional Information