Versions Compared

Old Version 2

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version Current

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section includes the following topics:

Anchor
AboutexportingandimportingAdminPointsettings
AboutexportingandimportingAdminPointsettings
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.

Anchor
ExportSettingscommand
ExportSettingscommand
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

  • 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 7-1    Elements 1 Elements of the Dialog argument

Element

...

Description
dialog settings_dialog_

...

name

The type of dialog to be exported. The possible values are:

...

  • locations

...

  • grouping

...

  • sla
settingsfile path_name_of_output_

...

fileThe name of the XML file to export the setting dialogs data to.

Anchor
ImportSettingscommand
ImportSettingscommand
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

  • 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 on page 102.

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 7-2    Elements 2 Elements of the Import-related argumentsElement    Description

ElementDescription
dialog settings_dialog_

...

name

The type of dialog to be exported. The possible values are:

...

  • locations

...

  • locations-full

...

  • grouping

...

  • sla
settingsfile path_name_of_output_

...

fileThe name of an XML file to export the dialog settings data to.

Anchor
Preparingthesettingsimportfiles
Preparingthesettingsimportfiles
Preparing the settings import files

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

  • 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 on page 100.

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.

Info

...

Using this setting will replace all previous locations definitions.

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 7-3    Elements 3 Elements of the location settings import fileElement    Description

ElementDescription
Location

...

nameThe name of the location. May not exceed 20 characters.
IP

...

fromThe lowest IP within the range. The address should suit the IP mask 253.255.255.255.
IP

...

toThe highest IP within the range. The address should suit the IP mask 253.255.255.255.
Location proxy_

...

aliasThe alias name of the warehouse system the Location is assigned to. '*' indicates all warehouse systems.

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 7-4    Elements 4 Elements of the grouping settings import file

Element

...

Description
Group

...

nameThe name of the group. May not exceed 20 characters.
Group

...

technologyThe technology code of the group. To find a valid code, see Table

...

5

...

.
Group

...

entityThe entity code of the corresponding technology. To find a valid code,

...

 see Table

...

5

...

.
Identifier

...

nameThe identifier text associated with the group. Full string and % wildcard characters allowed.
Group proxy_

...

aliasThe alias name of the warehouse system the Group is assigned to. '*' indicates all warehouse systems.

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

Anchor
Table5
Table5
Table 5 Mapping Table 7-5    Mapping grouping technologies to entities

Technology nameTechnology

...

SAP    SP    Transactions    A

SAP    SP    Application Servers    P

SAP    SP    Servers    S

Web    WW    URLs    A

Web    WW    Transactions    P_T

Web    WW    SAP Titles    P_ST

Web    WW    Siebel Titles    P_ST

Web    WW    PeopleSoft Panels    P_PG

Web    WW    Servers    S

Web    WW    Instances    I

Web    WW    Pages    BT

Web    WW    URL File Extensions    UE

Web    WW    Domains    SI

...

codeEntity nameEntity code
SAPSPTransactionsA
SAPSPApplication ServersP
SAPSPServersS
WebWWURLsA
WebWWTransactionsP_T
WebWWSAP TitlesP_ST
WebWWPeopleSoft PanelsP_PG
WebWWServersS
WebWWInstancesI
WebWWPagesBT
WebWWURL File ExtentionsUE
WebWWDomainsSI

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 7-6    Elements 6 Elements of the SLA settings import file

Element

...

Description
SLA

...

nameThe name of the SLA. May not exceed 20 characters.
SLA

...

technology

The technology code of the SLA.

To find a valid code, see Table

...

7

...

.

SLA

...

entityThe entity code of the corresponding technology. To find a valid code,

...

 see Table

...

7

...

.
SLA

...

Type

Either service time (S) or response time (R).

To find the corresponding type for each technology,

...

 see Table

...

7

...

.

SLA proxy_

...

aliasThe alias name of the warehouse system the SLA is assigned to. '*' indicates all warehouse systems.

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

Anchor
Table7
Table7
Table 7-7    Mapping Mapping SLA technologies to entities

SLA

...

typeTechnology nameTechnology codeEntity nameEntity code
Service timeMicrosoft .NETDNServersS
Service timeJ2EEJEServersA
Service timeOracleORProgramP
Service timeOracle ApplicationsOAFormsA
Service timeOtherOTTiersA
Service timeSQL ServerSQProgramsP
Service timeTuxedoTUServicesA
Service timeWebSphere MQMQReader ApplicationsGA
Service timeWeb (server)WWURLsA
Response timeSAPSPTransactionsA
Response timeWeb (client)WWPagesA1
Scroll Ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 | 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/precise/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 |  
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
  | 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse

Service time    Microsoft .NET    DN    Servers    S

Service time    J2EE    JE    Servers    A

Service time    Oracle    OR    Program    P

Service time    Oracle Applications    OA    Forms    A

Service time    Other    OT    Tiers    A

Service time    SQL Server    SQ    Programs    P

Service time    Tuxedo    TU    Services    A

Service time    WebSphere MQ    MQ    Reader Applications    GA

Service time    Web (server)    WW    URLs    A

Response time    SAP    SP    Transactions    A

Response time    Web (client)    WW    Pages    A1

 

 

Precise. Performance intelligence from click to storage. Learn more > >

...