Refresh or Clone OnBase Test Data

[Stephanie_Ashle]

Hello! 

Our test system was created 4-5 years ago, and we would like to have newer data available for testing as we are implementing Document Retention.  How do others refresh their test system data?  Full clone from production and change configurations?  Blow away current test and make new test?  We are on Foundations EP1 so I know there are a lot of new features/utilities than there were previously.  

Thank you for any feedback/advise.

Stephanie

[Kelby_Adams1]

I recommend using the new Test System Creation Utility with Foundation. 

If you have anything in the old Test that you would like to move to the new test, I would use the export utility to export it out and move it to the new test.

[James_Perry]

In a situation like yours if you want to test completely then it is easiest to clone Production to a Test environment then update the connections and data to point to the new Test environment in Test. This will give you the best opportunity to test against your current configuration and data. 

Be sure that you have either migrated or exported anything in your current Test environment before blowing it away with a clone of Production.

[Eric_Beavers]

If you want a clean environment with all the configuration and only a selection of documents then the recommended approach in EP1 is use Test System Creator (aka TSC). For additional configurations, you can then use the Import/Export tool from OnBase Configuration to migrate smaller parts. Documentation is available in the System Admin MRG for EP1. Look for the section titled "TEST SYSTEM CREATION UTILITY" and the section "IMPORTING AND EXPORTING CONFIGURATION ITEMS". To get your data (at least for documents), just build a custom query that would retrieve such documents and call the query's configuration ID (or name) in your TSC create command or the GUI (EP1+).

If you want a complete clone, you can go with the traditional method that involves backing up and restoring your production database/diskgroups as a Test. You can find guidance in the Building Test Systems document:

https://community.hyland.com/gallery/items/53540-creating-an-onbase-test-environment

This has risks in that you need to remember to Isolate Test. A few years ago some of us started a discussion of common things that need updated with this method.

In both of these cases, these parts only cover the creation of database and diskgroups. If you are trying to test additional functionality, for example the Web Client, you will need to install those servers and related dependencies.

Training.Hyland.com Premium Subscribers have additional learning available:

Test System Creation: Hands On Lab

Test System Creation & Configuration Import/Export

Import Export Framework

[Stephanie_Ashle]

Thank you for all the responses.  It was nice to hear all the options available.  We are going to try with the Test System Creator first.  If it does not meet our needs, we will check into a full clone and re-configuration.  Thank you again.