Test to Production Migration documentation - Onbase 16

[Alvin_Gipson]

Migrating Test to Prod. Is there any documentation on how to migrate from Test to a Production server?

[Bryan_Green1]

I'm looking for the same thing. 🙂

[Kevin_Boettler]

If the test system was created with the Configuration Migration utility, the documentation for migrating back to production is available in the Configuration Migration Module Reference Guide, under the section 'Migrating a Test Environment to Production'.

The Configuration Migration Module Reference Guide for OnBase 16 is available here,
https://www.onbase.com/community/onbase/m/ob16mrg/18918

Alternatively, moving specific configuration can be accomplished in one of two ways using OnBase 16. The first is available through the configuration client and has documentation available in the System Administration Module Reference Guide, under the section 'Importing and Exporting Configuration Items'. 

The System Administration MRG for OnBase 16 is available here,
https://www.onbase.com/community/onbase/m/ob16mrg/18831

The second method is available through OnBase Studio and provides additional support for Workflow and WorkView. Documentation for this is available in the Studio MRG, under the section 'Exporting and Importing Configurations'.

The Studio MRG for OnBase 16 is available here,
https://www.onbase.com/community/onbase/m/ob16mrg/18992

[Sherri_Henderso]

I have reviewed both of these options and I have a question. Using the 'Importing and Exporting Configuration Items' I notice that the help text comes up and says that if you select 'Map' that the item is not imported, but the references are. What if the items are different, say a new field is added to a COLD process. Does that come over?

[Kevin_Boettler]

The 'map' action is used during import by other, dependent items in order to update their relationship. When 'map' is applied, it means the affected item will not be imported, and any items which rely on it will instead rely on the item you target with the 'map' action.

For example, if an item relies on a diskgroup, but no action is set on that diskgroup, analysis will warn that the diskgroup requires an action. Since diskgroups cannot be created by import, you must map to a diskgroup which exists in the destination. This tells the dependent item to instead use the diskgroup we targeted, once it has been imported. This only affects the item which relies on the diskgroup; the one targeted by 'map' is unchanged.

In general, if you want the destination to reflect the source system, you will need to use the 'create' or 'replace' actions. Using the 'map' action will usually not directly affect the targeted item.

Does that help?