Refreshing the OnBase Test Environment

Sometimes, despite our best efforts, settings between production and development environments drift to a point where the test environment is no longer a true representation of production. You could open Config in both environments, put the windows side by side and crawl through all of the settings, but who has that kind of time or patience? Not to mention the risk of human error. Happily, there are two other options: restoring a backup of the production database, or using the configuration migration utility. Each option has its advantages, as highlighted below.

This content is for subscribers. Please enter the password to access it.

About Jennifer Siegel

Jennifer (aka Pixie) has over 20 years of experience in the Information Technology field, which includes 13+ years of Systems Administration and 15+ years of developing and implementing technical documentation and training. She has extensive experience with OnBase, SQL, and a firm foundation in computer science. Despite this, she considers herself a well-adjusted nerd with hobbies including gardening (poorly), archery, and knitting in public.

Subscribe to our Newsletter!

We will send you a newsletter once a month with updates from our blog, resource library, and events calendar.

Newsletter Sign Up
Interested to see what ECM can do for your company?
Get in touch with us today to learn more
Contact Us

Contact Us Today

  • This field is for validation purposes and should be left unchanged.