Exporting Application Groups to another Library Server - Revision history

Jderrick: Added Note for CMOD Application Group export

2020-01-22T14:10:01Z

Added Note for CMOD Application Group export

← Older revision		Revision as of 14:10, 22 January 2020
Line 17:		Line 17:
	* Groups		* Groups
	* Storage Sets		* Storage Sets
	* Application Groups		* Application Groups (Note: Applications are exported along with Application Groups)
	* Folders		* Folders
	* Cabinets		* Cabinets

Jderrick: Added link to IBM CMOD arsxml.

2018-03-25T10:18:11Z

Added link to IBM CMOD arsxml.

← Older revision		Revision as of 10:18, 25 March 2018
Line 6:		Line 6:

	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.		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 ==		== Order of Operations ==

Jderrick: Exporting Content Manager OnDemand configuration

2016-11-03T00:41:36Z

Exporting Content Manager OnDemand configuration

New page

== 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.

== 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)