8.5 Backing Up, Copying, and Restoring Configurations

Copying a Configuration from One Server to Another

Exporting a Configuration

Importing a Configuration

Exporting a Configuration File

If elements are already defined on the target server and you copy only the relationships, the relationships remain intact. If you copy the related elements, then the elements and their properties overwrite those on the target server.

As an example of exporting relationships with a server configuration, assume that you want to export a view with ACLs intact, but you do not want to copy the user credentials to the target system. The relationship is between the ACL and the user. If you do not export related elements, then the user’s password is left intact on the target system.

If the target server doesn’t have the related elements, they can be created. This can occur in the case of a relationship between an element in the Service Models hierarchy and an element in the Elements hierarchy. In this case, to construct the relationship, the target element must be defined in Configuration Storage. It does not, however, affect any potential algorithm settings, or other property data related to the target element.

To export a configuration file:

Importing a Configuration File

Before importing a configuration file, be sure the file meets the requirements for well-formed imported XML code containing necessary DTD headers, and the basic XML tags and commands for elements and views.

To import a configuration file:

Exporting Configuration Files

The following sample code exports a configuration file:

var server = formula.Root.findElement('formulaServer=Server/root=Administration')
var dname = element.dname;
formula.log.info( "Exporting the hierarchy starting at " + dname);
server.perform(session, "Config|ExportSilent", [], [ dname, 'd://OperationsCenter_install_path//cstest.xml']);

Replace the following variables:

element.dname

d://OperationsCenter_install_path//cstest.xml

Importing Configuration Files

The following sample code imports a configuration file.

var server = formula.Root.findElement('formulaServer=Server/root=Administration') 
server.perform(session, "Config|ImportSilent", [], ['d://OperationsCenter_install_path//cstest.xml']);

Replace the following variables:

d://OperationsCenter_install_path//cstest.xml

Understanding XML File Structure

Any structure in your Service Models hierarchy can be translated into an XML file using the Export command. The file can then be edited for required changes or shared with other installations.

The well-formed XML contains basic tags and commands. At the simplest level, the XML file must contain this basic structure:

<views>
  <tree>
    <element>element definition tags</element>
  </tree>
</views>

Imported XML files need to be well-formed XML files containing necessary DTD headers, as shown in the following example XML code. This code creates a hierarchy with Test Element as the top element with a native child (Child Element) and a link to an existing technology branch (Tivoli TEC+):

<!DOCTYPE views PUBLIC "-//Managed Object Solutions, Inc.//DTD views 1.0//EN" "http://www.ManagedObjects.com/dtds/views_1.0.dtd">

<views destroy="no">
    <tree start_at="root=Organizations">
      <element> 
        <name>Test Element</name>
        <class>org</class> 
        <displaySourceElements>false</displaySourceElements> 
        <contact>Jim</contact> 
        <company>Enigma Corp</company> 
        <address>394 First Street, Fairfax, VA</address> 
        <phone>703-555-1212</phone> 
        <email>test@mo.com</email> 
        <secure name="simple" related="yes" self="yes" children="no"> 
          <grant names="GroupOne,GroupTwo" permissions="view,manage,access,define"/> 
          <deny names="GroupThree" permissions="access,define"/> 
        </secure>
        <element>
          <name>Child Element</name>
          <class>org</class>
          <displaySourceElements>true</displaySourceElements>
          <contact>John</contact>
          <company>Enigma Corp</company> 
          <address>394 First Street, Fairfax, VA</address> 
          <phone>703-555-1212</phone> 
          <fax>703-555-3939</fax> 
          <pager>322-325-3565</pager> 
          <sref name="simple"/> 
          <relate kind="ORG">script=TivoliTec+/root=Elements</relate> 
        </element>
      </element>
     </tree>
</views>

Understanding XML Tags

Table 8-3 provides description of main XML tags used for the creation of Service Views.

<tree start_at="org=Northeast/root=Organizations">

Element Property Tags

The tags listed in Table 8-4 are nested within an <element> tag and specifically define the properties of the element.