Exporting Application Groups to another Library Server

From CMOD.wiki
Jump to: navigation, search

Why export configuration data?

The most common reason for exporting configuration data in Content Manager OnDemand is to 'promote' an Application Group, Application, and Folders from a development or test system to production. However, you may be migrating a server to new hardware, or a new version of CMOD.

How do I export configurations from CMOD?

Using the Administrative Client, log into both of the systems that you want to export the configuration to and from. Inside the OnDemand Admin Client, select the item you want to export to the opposite server (say, an Application Group) and right-click on it. Choose 'Export' from the pop-up menu, and you'll be presented with an 'Export' window. From the 'Server' pop-up menu at the top of that window, choose the server to send the configuration data to. Then click the 'Export' button on the right, to send the data over.

If you have command-shell access to the OnDemand server, you can use the IBM CMOD arsxml utility to export configuration data into XML format, then distribute the file to systems, and import it there. This is particularly good for distributing specific changes (users) across multiple servers (Test, Production, and Disaster Recovery).

Order of Operations

When exporting configuration data from one Content Manager OnDemand Server to another, there is a specific order in which to export the data:

  • Printers
  • Users
  • Groups
  • Storage Sets
  • Application Groups
  • Folders
  • Cabinets
  • Holds
  • Report distribution items (Reports, Banners, Bundles, Schedules, and Distributions)
  • OnDemand distribution facility items (Recipients, Recipient lists, E-mail templates, Report IDs, Bundles, and Distributions)