Exporting and importing AdminPoint settings

This section includes the following topics:

• About exporting and importing AdminPoint settings
• Export Settings command
• Import Settings command
• Preparing the settings import files

About exporting and importing AdminPoint settings

The CLI utility lets you import or export location, grouping, and SLA settings from AdminPoint. This can be useful if you want to copy specific settings from one Precise installation to another, or if you prefer to add or edit settings without using the AdminPoint user interface.

Export Settings command

The Export Settings command exports the settings defined in the following AdminPoint dialog boxes to an output file in XML format:

• Location Settings
• Grouping Settings
• SLA Settings

This command uses the following format:

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password>
                    | -i3-clear-password <clear_password>}
                    -action export-settings
                    -dialog <settings_dialog_type>
                    -settingsfile <path_&_name_of_output_file>
UNIX             ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password>
                    | -i3-clear-password <clear_password>}
                    -action export-settings
                    -dialog <settings_dialog_type>
                    -settingsfile <path_&_name_of_output_file>

Dialog argument

The following table describes the syntax of the dialog argument.

Table 1 Elements of the Dialog argument

Import Settings command

The Import Settings command imports the settings defined in the following AdminPoint dialog boxes from an input file in XML format:

• Location Settings
• Grouping Settings
• SLA Settings

Before the import process, all definitions are backed up and saved to the folder that contains the import file. See Preparing the settings import files.

The import settings command uses the following format:

Windows    infra\bin\psin_cli.bat
                  -i3-user <user_name>
                  {-i3-encrypted-password <encrypted_password>
                  | -i3-clear-password <clear_password>}
                  -action import-settings
                  -dialog <settings_dialog_type>
                  -settingsfile <path_&_name_of_output_file>
UNIX          ./infra/bin/psin_cli.sh
                  -i3-user <user_name>
                  {-i3-encrypted-password <encrypted_password>
                  | -i3-clear-password <clear_password>}
                  -action import-settings
                  -dialog <settings_dialog_type>
                  -settingsfile <path_&_name_of_output_file>

Dialog argument

The following table describes the syntax of the dialog argument.

Table 2 Elements of the Import-related arguments

Preparing the settings import files

The settings import file assembles the settings that are defined in the following AdminPoint dialog boxes:

• Location Settings
• Grouping Settings
• SLA Settings

Each dialog box requires its own import file. You can create this file either manually or by running the export settings command. See Export Settings command.

About the locations/locations-full settings import file

Below are details regarding the various locations settings import file.

Locations

Use the locations option when you want to append locations to your previous locations definitions.

Locations-full

Use the locations-full setting if the location settings file represents the entire locations definitions that should be defined in the system.

Import file structure

The locations/locations-full settings import file is structured as follows:

<locations>
     <location name="<name>" proxy_alias="<Framework node alias>" >
          <ip from="<ip address>" to="<ip address>" />
          1...n
     </location>
     1...n
</locations>

The following is an example of a location settings import file:

<locations>
     <location name="USA Sales" proxy_alias="win-1">
          <ip from="10.1.1.100" to="10.1.2.100" />
          <ip from="10.3.1.100" to="10.3.1.100" />
     </location>
     <location name="France Support" proxy_alias="*">
          <ip from="80.1.2.150" to="80.1.2.200" />
     </location>
</locations>

The following table describes the elements of the location settings import file.

Table 3 Elements of the location settings import file

About the grouping settings import file

The grouping settings import file is structured as follows:

<grouping>
     <group name="<name>" technology="<technology code>" entity="<entity code>" proxy_alias="<Framework node alias>">
          <identifier name="<identifier string>" />
          1...N
     </group>
     1...N
</grouping>

The following is an example of a grouping settings import file:

<grouping>
     <group name="OA Users" technology="OA" entity="U" proxy_alias="win-1">
          <identifier name="admin" />
          <identifier name="visitor" />
          <identifier name="operations" />
     </group>
</grouping>

The following table describes the elements of the grouping settings import file.

Table 4 Elements of the grouping settings import file

The following table shows how the different grouping technologies can be mapped to entities.

Table 5 Mapping grouping technologies to entities

About the SLA settings import file

The SLA settings import file is structured as follows:

<slas>
     <sla name="<sla name>" entity="<entity code>" technology="<technology code>"
     sla-type="<sla type>" activity-type="<activity type>" application="<application name>" red="<breach threshold>"
     yellow="< breach threshold >" proxy_alias="<Framework node alias>">
          <identifier name="<identifier string>" />
          <identifier name="<identifier string>" />
     </sla>
</slas>

The following is an example of an SLA settings import file:

<slas>
     <sla name="Tuxedo default SLA" entity="A" technology="TU" sla-type="S" activity-type="" application="" red="5000" yellow="2000" proxy_alias="win-1">
          <identifier name="%PAP" />
          <identifier name="APP%" />
     </sla>
</slas>

The following table describes the elements of the SLA settings import file.

Table 6 Elements of the SLA settings import file

The following table shows how the different SLA technologies can be mapped to entities.

Table 7 Mapping SLA technologies to entities

IDERA |  Products | Purchase | Support |  Community |  Resources |  About Us  | Legal