cancel
Showing results for 
Search instead for 
Did you mean: 

Config Migration with DDS

John_Anderson4
Star Collaborator
Star Collaborator

Are there any special instructions for using Configuration Migration to create a test system when both your production and test systems will use DDS? The utility just asks for a disk group path - can you put a DDS path in there or do you have to first put the disk groups on a local drive and then go into Config and point them to the DDS server? This will be for version 12.

Thanks.

2 REPLIES 2

Shawn_Starkey
Champ in-the-making
Champ in-the-making

Hi, John, we're looking into this just now ourselves. Did you find an answer you wouldn't mind sharing?  Thanks!

Nathan_Jones3
Star Collaborator
Star Collaborator

When we used the Migration utility, we provided the Disk Group path that we were using in Production.  Of course, we changed it for our intended Test environment.  (So, instead of \\Production\DiskGroups, we used \\Test\DiskGroups.)  Then, after the migration, we had to go into Configuration and provide the DDS server address for Test.

In case it's helpful, below is a list of things that may need to be configured or updated after you create your Test environment.  I can't say that it's exhaustive.  We started with a list from our reseller and have been adding to it. 

We also found that it seemed best to run the migration from the application server, logged in as MANAGER.  This might not be necessary, but for us it ensured we had all the rights we needed.  In particular, our system bitmaps and icons weren't getting copied over.

In no particular order, look at the following:

- E-form resource paths to CSS files, images
- Workflow e-mail notifications (Recipients don't get transfered in the migration)
- Any timer/schedule differences between Test and Production?
- Update Disk Group paths (the migration does some odd naming things, we found)
- OnBase Application Server Path (this will be used for Core-based Modules) [Config | Utilities > Application Server]
- User Form paths
- Custom Query HTML form paths
- E-Forms scripts that query web services, do database queries, etc
- Register licenses [Client | Admin > User Management > Workstation Registration]
- XML Style Sheet paths
- Update DIP/TIP paths (May need to add pre-processor location) (D:\Program
- May need to update Windows services (DIP, Workflow, etc.)
- Schedulers will point to prod server
- Reassign Timers to server
- OnBase API Scripts (VBScripts, Unity Scripts, etc. that call OnBase API)
- Splash screen path [Config | Users > Global Client Settings > Misc]
- Workflow actions to execute a program, call a web service, SYS DLL Exit Call
- External auto-fill keyword sets
- Verity server paths
- Verity collections need to be copied
- Workview paths for stylesheets, resources, and backup files
- Active Directory Domain Config. (AD integration is new in OnBase 12; see also Network Security MRG) [Config -ROMANZO | Utils > Network Security]
Configure DDS [Disk Mgmt > Distributed Disk Services] (need to update/provide the server path)
- Update user passwords, particularly system accounts like MANAGER