1,126
edits
Difference between revisions of "Exporting Application Groups to another Library Server"
Exporting Application Groups to another Library Server (view source)
Revision as of 10:18, 25 March 2018
, 10:18, 25 March 2018Added link to IBM CMOD arsxml.
(Exporting Content Manager OnDemand configuration) |
(Added link to IBM CMOD arsxml.) |
||
| 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 == | ||