Template properties

SystemID.<target SID>.

SystemHost.

<database hostname>

Contains System ID <SID> and

hostname/virtual hostname of the

database for the new target system

that will be provisioned

during template execution.

Example:

<property checksum="FD7F1E4A3812A054376E35753082606E" id="PROP-0" name="Target System ID">

      <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                        SystemID.<target SID>.SystemHost.<database hostname>

      </value>

</property>

back to top

SystemID.<target SID>.

Number.<instance number>.

InstanceHost.

<instance hostname>

Contains System ID <SID>,

instance number, and

hostname/virtual hostname of the

application server instance for the

new target system that will be

provisioned during template execution.

Example:

<property checksum="8694B5000532B173F110AE49AE729C0D"id="PROP-3" name="Target Instance ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          SystemID.<target SID>.Number.<instance number>.InstanceHost.<instance hostname>

        </value>

</property>

back to top

Physical hostname on which

the new target system will be

provisioned during template execution.

Example:

<property checksum="BAFE399DEFF538343309CBB8C55C76CA" id="PROP-2" name="Target Instance Host">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <physical hostname>

        </value>

</property>

back to top

This property is physical hostname

on which new target system

database will be provisioned

during execution of template

Example:

<property checksum="CFEF1CAFD894CA0A745A877986628595" id="PROP-12" name="Target Database Host">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:type="xs:string">

                          <database hostname>

        </value>

</property>

back to top

DatabaseName.<target SID>.

DatabaseType.<type>.

DatabaseHost.

<database hostname>

Contains System ID <SID>,

instance number, and

hostname/virtual hostname

of the application server  instance

for the target system that will

be created during template

execution.

Example:

<property checksum="9F1A6F61956403112F22241673CF4890" id="PROP-21" name="Target Database ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          DatabaseName.<target SID>.DatabaseType.<type>.DatabaseHost.<database hostname>

        </value>

</property>

back to top

Contains System ID <SID>

for the new target system that

will be provisioned during template

execution.

Example:

<property checksum="E961BBF2E1BA696EC531A96E0A017244" id="PROP-17" name="Target Service ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <SID>

        </value>

</property>

back to top

SystemID.<SID>.

Number.<instance number>.

InstanceHost.<hostname>

Contains System ID <SID>,

instance number, and

hostname/virtual hostname of the

central service instance for

the target system that will be

created during template execution.

Only relevant for Java systems

Example:

<property checksum="A28E073BA8CC34E09D76A9FD8F9F569A" id="PROP-2" name="Target Central Service ID">

            <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                              SystemID.<SID>.Number.<InstNumber>.InstanceHost.<hostname>

              </value>

</property>

back to top

Contains System ID <SID>,

instance number, and

hostname/virtual hostname

of the central service instance

for the target system that will

be created during template

execution. Only relevant for

Java systems.

Example:

<property checksum="2A0BBB37E26D2D2497B3A9D22D375D2C" id="PROP-3" name="Target Central Service Host">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                        <physical hostname>

        </value>

</property>

back to top

SystemID.<source SID>.

SystemHost.

<database hostname>

Contains System ID <SID> and

hostname/virtual hostname of

the database for the source system

that will be used during template

execution.

Example:

<property checksum="5BB4B4103242694E799A12C7589813C4" id="PROP-1" name="Source System ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          SystemID.<source SID>.SystemHost.<database hostname>

        </value>

</property>

back to top

SystemID.<source SID>.

Number.<instance number>.

InstanceHost.

<instance  hostname>

Contains System ID <SID>,

instance number, and

hostname/virtual hostname

of the application server

instance for the source system

that will be used during template

execution.

Example:

<property checksum="E1E4F335051FD2EE7B0E81137038DC75" id="PROP-18" name="Source Instance ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          SystemID.<source SID>.Number.<instance number>.InstanceHost.<instance  hostname>

        </value>

</property>

back to top

Contains hostname of the

application server instance

for the source system that

will be used during template

execution.

Example:

<property checksum="584C2AD405239707B4924899D0D624D1" id="PROP-13" name="Source Instance Host">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <physical hostname>

        </value>

</property>

back to top

SystemID.<source SID>.

Number.<instance number>.

InstanceHost.<instance hostname>

Contains hostname of the

application server instance

for the source system that

will be used during template

execution. Only relevant for

Java systems.

Example:

<property checksum="19DF6FF77E005E4028ABDFB9C720F0AE" id="PROP-16" name="Source Central Service ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          SystemID.<source SID>.Number.<instance number>.InstanceHost.<instance hostname>

        </value>

</property>

back to top

DatabaseName.<source SID>.

DatabaseType.<type>.

DatabaseHost.

<database hostname>

Contains system ID <SID>,

instance number, and

hostname/virtual hostname

of the application server

instance of the source

system that will be used during

template execution.

Example:

<property checksum="9F1A6F61956403112F22241673CF4890" id="PROP-21" name=" Source Database ID ">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:type="xs:string">

                          DatabaseName.<source SID>.DatabaseType.<type>.DatabaseHost.<database hostname>

        </value>

</property>

back to top

Contains the hostname

of the source system

database that will be

used during template

execution.

Example:

<property checksum="143930545B06FC04733FF323DD6BEF85" id="PROP-34" name="Source Database Host">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                        <physical hostname>

        </value>

</property>

back to top

/<database root folder>/<SID>/….

/sapdbctrl-config

Indicates whether profiles

of the source system will

be changed during

provisioning process

Example:

<property checksum="037F8B5D8C153B2AA56BC3636ABEA10E" id="PROP-24" name="Instance Start Profile Path">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                    /<database root folder>/<SID>/…/sapdbctrl-config

        </value>

</property>

back to top

Depending on the value of this property,

profiles of the source system will be

changed during provisioning process

Example:

<property checksum="598FEDC16474FF1BCCCC93250010B593" id="PROP-4" name="Add ChangeProfile Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                        true

        </value>

</property

back to top

Contains the physical

host that will be set or

changed in the relevant

provisioning step during

template execution.

Example:

<property checksum="6B387E54CE6ABADE77E803FAD2F0A018" id="PROP-5" name="Changed Hostname">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <physical hostname>

        </value>

</property>

back to top

/usr/sap/<target SID>/SYS/

profile/<profile name>

Contains the path to the

target system's profile

that will be changed

during template

execution.

Example:

<property checksum="FFF18FB0C18BF582D6E2E55E73F7A09F" id="PROP-6" name="ChangeProfile Path">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          /usr/sap/<target SID>/SYS/profile/<profile name>

        </value>

</property>

back to top

Represents the source

system administrator

user.

Example:

<property checksum="5C69443DA0E6DE52700C3D7D9600FC59" id="PROP-7" name="SAP User Administrator">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <SID>adm

        </value>

</property>

back to top

Indicates whether groups

will be cleared during

provisioning process.

Example:

<property checksum="05B6FC16A3129CAA57FF277D7733209B" id="PROP-11" name="Clear Groups Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether the

cache of the host will be

cleared during provisioning

process.

Example:

<property checksum="891A6E9BF73BE487904BF9A09367E5E3" id="PROP-13" name="Clear Hosts Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether users

will be cleared during

provisioning process.

Example:

<property checksum="D4929A5E1AD4843EE10746E1691F78F7" id="PROP-14" name="Clear Users Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether force

mode is activated.

Example:

<property checksum="88257A779F935CF477E2F8CD3EC336DE" id="PROP-16" name="Forced Mode Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether the

execution of user exit

commands in LVM is enabled.

For more information,

see SAP Help Portal at

http://help.sap.com/saphelp_lvment21

-> Application Help

->Landscape Configuration ->

Extended Landscape

Configuration ->

Configuring User Exits.

Example:

<property checksum="A06FA3A897E4F0C100B06AB02BC6B997" id="PROP-23" name="User Exit Script Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether the

database backup will be

performed on the

running database

Example:

<property checksum="9A0BD8CA2DE27C125EB49C9661DE0D43" id="PROP-25" name="Is Online Copy Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether the

mount points will be

deleted at the end

of the provisioning

process.

Example:

<property checksum="9BF2486FAD5A77F291DF9B9C554D85E3" id="PROP-26" name="Delete Mount Points Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether the

provisioning  process

will ignore errors on the

operation Stop for the

system and it’s instances.

Example:

<property checksum="520A409DD0C62965703E9BCEB0D30971" id="PROP-27" name="Ignore Service Stop Error Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          false

        </value>

</property>

back to top

Contains value for

timeout of operations

like Prepare and Start.

Example:

<property checksum="A6BDCAC2E10870B580CB4D35AC64DF25" id="PROP-29" name="Operation Timeout">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:int">

                          0

        </value>

</property>

back to top

Indicates whether the

instance needs to be

registered into file sapservices

on the host.

Example:

<property checksum="F8F830107A96D2FAA7A76BD731A2DF30" id="PROP-30" name="Instance Register Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether mount

points will be created

during provisioning

process.

Example:

<property checksum="7E1C5DCBAB100087536C9F0B1611E4F0" id="PROP-32" name="Create Mount Points Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Contains path to

temporary Oracle logs.

Example:

<property checksum="3504B16A266EF0CD1F91DF8EDC9B16F0" id="PROP-35" name="SAPinstWorkDir">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          Path to Oracle directory

        </value>

</property>

back to top

Indicates whether the

process makes the virtual

host active state on the

Virtualization screen.

Example:

<property checksum="56DB6DEF8F696616B296FF4C3C645529" id="PROP-39" name="WaitForResource State Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          Active

        </value>

</property>

back to top

Indicates whether the

process waits for a

response and checks

the hostname before

it continues with the

execution.

Example:

<property checksum="BC1E06F4A7768506DD6A1F5C8AB4AF98" id="PROP-40" name="WaitForResource And Check Hostname Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          false

        </value>

</property>

back to top

Indicates whether the

process waits for response

and checks the hostname

before it continues with the

execution.

Example:

<property checksum="FB41058E36594822DB47C25733C4406D" id="PROP-41" name="WaitForResource Forced Monitoring Timeout">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:int">

                        -2

        </value>

</property>

back to top

Indicates whether the

process waits for response

and checks the hostname

before it continues with the

execution.

Example:

<property checksum="5DFF28D5F50ADF798EF9E04F3434BE05" id="PROP-50" name="WaitForResource And Force Monitoring Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether the

process makes the virtual

system available on the

Virtualization screen in a

power on state.

Example:

<property checksum="502075190D819229EA070DB384AD490F" id="PROP-45" name="Virtual System PowerOn Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Indicates whether

post-copy automation

will have auto confirm

option on.

Example:

<property checksum="DACEAF25FEF1DF15DBCEF4213A062573" id="PROP-0" name="Auto Confirm Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          false

        </value>

</property>

back to top

<name of custom operation

in LVM>

Contains the name

of a custom operation

defined in LVM

Example:

<property checksum="F76CCAE19A6D53D649F9BB145E88892C" id="PROP-3" name="Custom Operation ID">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <name of custom operation in LVM>

        </value>

</property>

back to top

<name of custom hook in LVM>

Contains the name of a

custom hook operation

defined in LVM.

Example:

<property checksum="F3CF606BBFBEBBAE8AE68E4B9F47CF28" id="PROP-5" name="Hook Operation Name">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <name of custom hook in LVM>

        </value>

</property>

Indicates whether the

database needs to be

attached during template

execution.

Example:

<property checksum="EE517075C278C973257A891DD99E7789" id="PROP-27" name="No DB Attach Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

This property contains two

maps with key-value pairs.

One of the maps is secured,

while the other contains

information in plain text.

All of the parameters,

that are needed for custom

operation must be

set in one of these two maps

back to top

Contains the RFC destination

name for a client specific RFC

destination of a system.

Necessary for post-copy

automation task list execution;

The required format is

LVM_<system service ID>.

Client.<client number>

Contains the the ID of the task

list that will be executed.

Contains the ID of the

configured task list variant

in ABAP.

Contains the ID of the

internal runtime.

Contains the number of

completed tasks.

Contains the number of

done RFC connection retries.

Contains the task parameters.

One tag per task parameter.

Indicates whether the

value is cryptified.

Example:

<property checksum="69C0A71A2DB37435F54701F32A48DB39" id="PROP-2" name="CTC Request">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ctcRequest">

<targetDestinationName>

        LVM_<system service ID>.Client.<client number>

</targetDestinationName>

<scenarioId><Scenario ID></scenarioId>

<completedTasks>0</completedTasks>

<rfcConnectionRetryCounter>0</rfcConnectionRetryCounter>

</value>

</property>

back to top

Contains the service ID

of the source system

database instance.

Contains the service ID

of the source system

instance with liveCache.

Contains the backup

interval number.

Contains the maximum

times backup is done.

Contains the path to

the database log directory.

Indicates whether

consistency should

be kept; Applicable

only for liveCache.

Indicates whether to finalize

liveCache; Applicable only

for liveCache.

Indicates whether to prepare

liveCache; Applicable only

for liveCache.

Contains the service

ID of the target system

database instance.

Example:

<property checksum="B1FAA40029D9C4FEB29F3735532C8052" id="PROP-25" name="DB Backup Mode">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="dbBackupModeContext">

<databaseServiceId>[service ID]</databaseServiceId>

<interval>[interval number]</interval>

<maxBackupTime>[maximum backup time]</maxBackupTime>

<dbConfigurationDirectory>[directory path]</dbConfigurationDirectory>

<consistencyLiveCache>[true/false]</consistencyLiveCache>

<doFinalizeLiveCache>[true/false]</doFinalizeLiveCache>

<doPrepareLiveCache>[true/false]</doPrepareLiveCache>

<targetDatabaseServiceId>[service ID]</targetDatabaseServiceId>

</value>

</property>

back to top

Contains the Java Post-copy

automation label as

configured in LVM.

Contains the variant

identificators.

Contains the encrypted

master password.

Contains the source system

J2EE user name or in case of

Refresh target system

J2EE user;

encrypted.

Contains the source system

J2EE user password

or in case of system refresh,

the target system

J2EE user password;

encrypted.

port; port number equals

50000 + <target instance number> * 100

Contains the communication

hostname of the primary

application server

(system central instance (CI)

or first AS instance);

Can be identical with

the installation hostname.

Contains the path to

the CTC export directory

or in case of system

refresh, the initial import path.

Indicates whether cleanup

should be done.

Example:

<property checksum="305E320ADB36D8B2BA3819E03DC8CFF8" id="PROP-41" name="Java PCA Request">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="javaPCARequest">

<javaPCAConfig>[Java PCA label]</javaPCAConfig>

<scenarioName>[scenario name]</scenarioName>

<variantIds>[variant identifiers]</variantIds>

<masterPassword isSecured="true">[encrypted password]</masterPassword>

<j2eeUser isSecured="true">[encrypted user]</j2eeUser>

<j2eePassword isSecured="true">[encrypted password]</j2eePassword>

<protocol>[protocol]</protocol>

<port>[port]</port>

<hostname>[hostname]</hostname>

<doCleanup>[true/false]</doCleanup>

</value>

</property>

back to top

Type of the request

visible in Infrastructure

tab in LVM as

"Provisioning type"

Name of configuration

for SWPM toll in LVM

Path to a location where

SWPM will be executed

on a local host

Identifier of the product that

SWPM tool was released for

Version of release with

which SWPM working

Mount point where

installation master

will be mount on

a local host

Password for Administrator

user, value is crypt

List with instances

of SAP system

Map of key-value

pairs with parameters

needed for SWPM

Map of key-value pairs

with parameters needed

for SWPM,

values are encrypted

Example:

<property checksum="ADF19CEB0A3977A03996DEA5440F013B" id="PROP-38" name="SAPINST Parameters">

  <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sapInstUserInput">

    <requestType>SYSTEM_COPY</requestType>

    <releaseConfigId>

          <releaseConfigName>SWPM10SP06PL0</releaseConfigName>

    </releaseConfigId>

    <paramaterFileNeeded>true</paramaterFileNeeded>

    <SourceInstallationPath>/tmp/install/VCM_sapinst</SourceInstallationPath>

    <ProdID>NW_StorageBasedCopy</ProdID>

    <releaseVesion>7.40</releaseVesion>

    <isntMasterMountPoint>/tmp/install/VCM_sapinst</isntMasterMountPoint>

    <adminPwd isSecured="true" />

    <sapInstances>SystemID.<Target SID>.Number.<InstNumber>.InstanceHost.<hostname></sapInstances>

    <sapInstances>SystemID.<Taregt SID>.Number. .<InstNumber>.InstanceHost.<hostname></sapInstances>

    <sapinstParameters>

        <entry>

          <key/>

          <value/>

        </entry>

                    …

    </sapinstParameters>

    <secureParameters>

        <entry>

            <key/>

            <value/>

        </entry>

                    …

    </secureParameters>

</value>

</property>

back to top

if it is a Unicode or not,

value type is Boolean

true/false

value type is Boolean

true/false

target SID,

value type is string

target database SID,

value type is string

database hostname

of a target system,

value type is string

fully qualified domain

name of the hostname ,

value type is string

database hostname

of a source system,

value type is string

SID of source system,

value type is string

source database SID,

value type is string

database physical

hostname of a source

system,

value type is string

path to database

configuration file,

value type is string

list of sap instance

separated with ";"

one instance in a list

has format:

";"<Instance name>,

<source instance number>,

<full path to profile>,

<source hostname>,

<target instance number>,

<target hostname>

value type is string;

value type is Boolean

true/false

path to database

configuration file,

value type is string

path to global SAPMNT

share,

value type is string

type of database,

value type is string

<secureParameters>

All values are crypt

database manager

password in case

it is different from

master password

database administrator

password in case

it is different from

master password

password for  java

schema of database

password for

sqd<sid> user

password for

<sid>adm  user

password for

SapService<SID> user

password for

<sid>adm  user

One entry tag for each

storage adapter, where key

is the storage adapter.

Label and value

is the prepare clone volume

request.

Unique label for

configured storage

adapter in LVM

Prepare clone volume

request

Volumes that will be cloned

during the provisioning process;

one tag per volume to be cloned;

One tag per volume

Volume groups that will be cloned

during the provisioning process;

one tag per volume group

to be cloned;

One tag per volume group

Indicates whether the database

is in backup/suspend mode.

<property checksum="7DB2C27413BA39F8E678F49C5106640E" id="PROP-16"

name="Prepare Storage Clone Request">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:type="multiStorageOperationRequest">

<adapterIdToRequest>

<entry>

  <key>

  <label>[storage adapter label]</label>

  </key>

  <value xsi:type="prepareCloneVolumesRequest">

  <volumesToBeCloned/>

  ...

  <volumeGroupsToBeCloned/>

  ...

  <dbBackupMode>[true/false]</dbBackupMode>

  <customCloningProperties />

  </value>

</entry>

...

</adapterIdToRequest>

</value>

</property>

back to top

Unique identifier for storage

system configured in LVM

for the source system;

Not null

Unique identifier for storage

volume configured in LVM

for the source system;

Not null

Indicates whether the

sourceVolumeId is identifier

of storage volume

or snapshot

Mount configurations

for the source system;

one tag per mount

configuration

Unique identifier for storage

system configured in LVM

for the target system;

Not null

Unique identifier for storage

pool configured in LVM

for the target system;

May be null

Unique identifier for storage

volume configured in LVM

for the target system;

May be null

Type of the clone;

allowed values are

CLONE, SNAPSHOT

Mount configurations

for the target system;

one tag per mount

configuration

Masking properties

of the cloned target volume

<volumesToBeCloned>

<sourceStorageSystemId>[storage system id]</sourceStorageSystemId>

<sourceVolumeId>[storage volume id]</sourceVolumeId>

<isSourceVolumeSnapshot>[true/false]</isSourceVolumeSnapshot>

<sourceMountConfiguration/>

...

<targetStorageSystemId>[storage system id]</targetStorageSystemId>

<targetVolumeName>[storage volume name]</targetVolumeName>

<syncType>[sync type]</syncType>

<targetMountConfiguration/>

...

<maskingProperties/>

</volumesToBeCloned>

back to top

Container tag for each

mount configuration

for the source system

Identifier for service

(instance) of

source system

Storage type;

allowed values are

NAS, SAN

Mount point path

on the system

Mount options for

read/write, etc.

Mount options used for the

first prepare of the cloned

volumes only;

If null the mountOptions will

be used for the first prepare;

These options are especially

interesting if the storage library

needs to perform some special

steps during the first prepare

of the cloned volumes

(e.g. renaming/initializing

volume groups etc.)

Indicates whether the

mount is shared

<sourceMountConfiguration>

<serviceId>[service id]</serviceId>

<mountOrderNumber>[order number]</mountOrderNumber>

<storageType>[storage type]</storageType>

<mountPoint>[mount point path]</mountPoint>

<exportPath>[export path]</exportPath>

<mountOptions>[mount options]</mountOptions>

<fsType>[file system type]</fsType>

<shared>[true/false]</shared>

</sourceMountConfiguration>

back to top

Container tag for each

mount configuration

for the target system

Identifier for service

(instance) of target

system

Storage type;

allowed values are

NAS, SAN

Mount point path

on the system

Mount options for

read/write, etc.

Mount options used for

the first prepare of the

cloned volumes only;

If null the mountOptions will

be used for the first prepare;

These options are especially

interesting if the storage library

needs to perform some

special steps during the

first prepare of

the cloned volumes

(e.g. renaming/initializing

volume groups etc.)

Indicates whether

the mount is shared

<targetMountConfiguration>

<serviceId>[service id]</serviceId>

<mountOrderNumber>[order number]</mountOrderNumber>

<storageType>[storage type]</storageType>

<mountPoint[mount point path]</mountPoint>

<exportPath>[export path]</exportPath>

<mountOptions>[mount options]</mountOptions>

<fsType>[file system type]</fsType>

<shared>[true/false]</shared>

</targetMountConfiguration>

back to top

Source physical hostnames

where this volume is currently

attached;

Not null;

May be empty if not attached

to any host;

One tag per hostname

Target physical hostnames

where this volume should

be reachable;

Not null;

May be empty if not attached

to any host;

One tag per hostname

Host properties per physical

hostname;

given properties are just

with illustration purposes

and may differ from

actual required properties

One entries tag for each

hostname properties;

key – physical hostname

the properties are related to

Key-value pairs of properties

for this physical hostname;

given properties are just with

illustration purposes and may

differ from actual required properties;

One tag per property

Target virtual hostname from

where this volume shall be reachable;

Not null;

May be empty if it should not be

reachable from any virtual hostname;

One tag per virtual hostname

Target networks in CIDR notation

from where this volume shall be

reachable;

Not null;

May be empty if it should not

be reachable from any network

<maskingProperties>

<sourcePhysicalHostnames>[physical hostname]</sourcePhysicalHostnames>

<targetPhysicalHostnames>[physical hostname]</targetPhysicalHostnames>

<targetPhysicalHostnames>[physical hostname]</targetPhysicalHostnames>

<targetPhysicalHostnames>[physical hostname]</targetPhysicalHostnames>

<hostProperties>

  <entries key="[physical hostname]" />

  <entries key="[physical hostname]">

  <properties key="virtualResourceId">[virtual resource id]</properties>

  <properties key="virtualResourceProviderId">[virtual resource provider id]</properties>

  <properties key="virtualResourceIpAddress">[virtual resource IP address]</properties>

  <properties key="virtManagerUrl">[virtual manager URL]</properties>

  </entries>

  <entries key="[physical hostname]" />

  <entries key="[physical hostname]">

  <properties key="virtualResourceId">[virtual resource id]</properties>

  <properties key="virtualResourceProviderId">[virtual resource provider id]</properties>

  <properties key="virtualResourceIpAddress">[virtual resource IP address]</properties>

  <properties key="virtManagerUrl">[virtual manager URL]</properties>

  </entries>

</hostProperties>

<virtualHostnames>[virtual hostname]</virtualHostnames>

...

<networksCidrNotation>[networks CIDR notation]</networksCidrNotation>

...

</maskingProperties>

back to top

Volume groups that will be

cloned during the provisioning

process;

one tag per volume group

to be cloned;

One tag per volume group

Identifier of the source

storage volume group

to be cloned;

Not null;

Not empty

Name of the source

storage volume group

to be cloned;

May be null or empty

Identifier of the target

storage volume group

to be cloned;

Not null;

Not empty

Name of the target

storage volume group

to be cloned;

May be null or empty

Logical volumes in the

volume group;

One tag per logical volume

Identifier of the source

logical volume;

Not null;

Not empty

Name of the source

logical volume;

May be null or empty

Identifier of the target

logical volume;

Not null;

Not empty

Name of the target

logical volume;

May be null or empty

List of additional attributes.

This property has only one

key and many values.

Example:

<property checksum="ABE301A9F3229FA09915FC2E7E17AD7A" id="PROP-17" name="User Data Collection">
            <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ldapObjectCollection">
                <users>
              </users>
…
              <groups>
              </groups>
…
            </value>
</property>

back to top

Example:

key = objectClass ;  values : inetOrgPerson, organizationalPerson, posixAccount, person, top

<additionalListAttributes>
<entry>
<key xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">objectClass</key>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema xsi:type="xs:string">inetOrgPerson</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">organizationalPerson</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">posixAccount</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">person</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">top</value>
</entry>
</additionalListAttributes>

back to top

List of additional string attributes

key: sn -> value

key: cn ->value

key: dn – >value

For every group that user

belong to there is a separate

property

<memberOfGroups>

cn=dbq1bctl,dc=groups,

dc=wdf,dc=sap,dc=com

</memberOfGroups>

What shell will be used from this

user when it logs on

Original user ID

<srcUserId>

uid=sap<SID>,

dc=users,

dc=wdf,

dc=sap,

dc=corp

</srcUserId>

What user manager

will be used to create user

Value type is Boolean

true/false

Value type is Boolean

true/false

Value type is Boolean

true/false

Domain name

<dn>

uid=sapq1b,

dc=users,

dc=wdf,

dc=sap,

dc=corp

</dn>

<groups>

...

</groups>

Map wit key-value pairs

• member – value is string ;

example

uid=q1sadm,

dc=users,

dc=wdf,

dc=sap,

dc=corp

• memberuid – user id

List of additional attributes.

This property has only

one key and many values.

Example

: key = member ;

value is list of user members of this group

: key = memberuid ;

value is list of user IDs

members of this group

: key = objectclass;

value is list of groupOfNames,

posixGroup, top

back to top

List of additional

string attributes

Value type is Boolean

true/false

example:

cn=dbq1bmon,

dc=groups,

dc=wdf,

dc=sap,

dc=corp

User input data that is

needed for an operation.

ID of the virtualization entity

that is a part of the operation.

Label configured in the

Infrastructure tab for the

used virtualization manager.

For example vCenter01.

Consists of the type of

the entity and its ID.

Type of the virtualization

entity.

For example

VIRTUAL_HOST.

ID that is used by

the Virtualization Manager

Name of the operation that the

virtualization manager has

exposed to LVM using

LVM’s virtualization adapter.

Some examples for

VMWare’s Vsphere are:

START,

PROVISION,

DESTROY,

SHUTDOWN

Characteristics of a given

operation. They are different

for a different virtualization

manager.

Indicates if the operation

has phases.

Every Virtualization

Manager defines its

operations as having

phases or not. If there are

no phases the operation

has a single Virtualization

Operation Context.

Otherwise every phase

will have its own context

wrapped in a PhaseContexts.

Shows whether a target entity

is produced as a result of

a given operation.

For example for a Provisioning

type of operation there

is such an entity.

For simple operations

like Start/Stop there is no such.

The name of the newly

provisioned virtualization entity.

ID of the virtualization entity

that hosts the target entity.

Specific input that the

operation requires

Represents the set of user data

that each operation specific to

a given Virtualization Manager

might require in order to be executed.

For each virtualization manager

the dialogStepContexts may differ

as each Virtualization Manager

defines its own dialog step contexts.

Indicated if the newly provisioned

entity has an IP already reserved or

will use the DHCP to obtain one.

Example:

<property checksum="02819FD35F78FCB5C23BD22798DD2C6D" id="PROP-47" name="Virtualization Operation Context">

      <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="virtOpPrep">

<entityId>

<adapterLabel>[label of used virtualization manager] </adapterLabel>

<typedEntityId>

<elementType>[virtualization entity type] </elementType>

<elementId>[element_ID_in the_virt_manager]</elementId>

</typedEntityId>

</entityId>

<entityName>[name of virtualization entity]</entityName>

<operation>[name of the operation]</operation>

<operationCharacteristics>

<isPhasedOperation>[true/false]</isPhasedOperation>

<isSyncOperation>[true/false]</isSyncOperation>

<isRequiringRequestDialog>[true/false]</isRequiringRequestDialog>

<targetEntityRequirement>[Required, Optional, None] </targetEntityRequirement>

</operationCharacteristics>

<targetName>[target_host_name]</targetName>

<targetHostingEntityId>

                    <adapterLabel>[name_from_infrastructure]</adapterLabel>

                    <typedEntityId>

                        <elementType>[type]</elementType>

                        <elementId>[element_id_in the_virt_manager]</elementId>

                    </typedEntityId>

</targetHostingEntityId>

<opSpecificInput xsi:type="virtProvisionInput">

<defaultTargetEntityId>

<dialogContext>

<opInput>

<operation>

<entityId>[Element ID as  seen in virtualization manager]</entityId>

<entityName>[name]</entityName>

<entityType>[type]</entityType>

<operationInput xsi:type="virtProvisionInput">

</opInput>

</dialogContext>

<selectedEntityIds>

<dhcpUsed>[true/false]</dhcpUsed>

      </value>

</property>

back to top

Name of the Virtualization

Operation.

Example:

<property checksum="5A2F1981E0A934801A6799A8A953F404" id="PROP-49"            name="Virtualization Operation">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="virtOperation">

<operation>[START]</operation>

</value>

</property>

back to top

Example:

<property checksum="CB1614C8671D8FE011A2F16CFFA49B59" id="PROP-50"

  name="Virtualization Operation Dialog Context">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="dialogContext">

<dialogStepContexts\>

</value>

</property>

back to top

Virtualization entity

ID that is used as a

parent.

Example:

<property checksum="518820B5E2D864D5E1A29434E66BF57E" id="PROP-48" name="Virtualization OpTarget HostingEntity">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xmlVirtualizationId">

<adapterLabel>[label]</adapterLabel>

<typedEntityId>

<elementType>[type]</elementType>

<elementId>[element_id_in the_virt_manager]</elementId>

</typedEntityId>

</value>

</property>

back to top

Example:

<property checksum="028F416301654EF49388BA89B0511C3B" id="PROP-46" name="Virtual Database Host">

<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xmlVirtualizationId">

<adapterLabel>>[name]</adapterLabel>

<typedEntityId>

<elementType>[Type]</elementType>

<elementId>[element_id_in the_virt_manager]</elementId>

</typedEntityId>

</value>

</property>

xmlElementValue.

Represent the target system

involved in the corresponding

provisioning process

<system>

Consists of the following elements:

0..1 <dependencylist>,

0..1 <intersystemdependencies>,

0..1 <j2eeconfig>,

0..N <rfcdestination>,

0..1 <emailnotification>,

0..1 <customnotification>,

0..1 <solmansettings>,

0..1 <isolations>,

0..1 <custompropertylist>,

0..1 <mountlist>,

0..1 <additional_attributes>,

0..1 <profile_parameters>,

0..1 <characterizations>,

1..N <service>

This section represents custom

dependencies list.

Consists of 0..N <dependency>

sourceserviceid

targetserviceid

A single system

dependency element

This section represents

intersystem dependencies list.

Consists of 0..N

<intersystemdependency>

sourceservicetype

source service type

targetsystemserviceid

target SID

targetservicetype

target service type

user

passwd

Will appear in case of

Java system. This section

contains user/password

for the Java system

saprouter - SAP router string

hostname -  host name

instanceno - instance number

language - language

client – client

isPcaDestination – possible values true or false

sncEnable - True in case SNC is enabled

sncPartnerName – snc partner name in case sncEnable = true

sncQoP – only in case sncEnable = true

This section contains the

either default RFC

destination configuration

or PSCA RFC

destination configurations.

emailaddresses

completed - True or false

failed - True or false

suspended - True or false

waiting - True or false

canceled - True or false

partiallyfailed - True or false

customnotificationname – notification name

completed - True or false

failed - True or false

suspended - True or false

waiting - True or false

canceled - True or false

partiallyfailed - True or false

solManUseSsl – true or false

solManHost

solManPort

solManUser

solManPw – encrypted solution manager password

solManSapRoute – solution manager sap router string

solManSapRouterPw – encrypted solution manager sap router password

port – solution manager message server port

msgserver – solution manager message server host

issecured – True if solution manager message server uses https and false otherwise

solutionManagerRelease – solution manager release

solutionManagerSP – solution manager SP

encryptedpasswd – solution manager encrypted password

solutionmanagersystem – solution manager system

type – host

value -  port

key

value

secure - true of false

encrypted true or false

storagetype

fstype

partnerid

usage

key

value

key

value

refname

valuerefname

<service>

Represents a single instance, database or custom service within given system. Consists of the following elements

0..1 <properties>,

0..1 <entityusagetypes>,

0..1 <hostnames>,

0..1 <databaseproperties>,

0..1 <instanceagentproperties>,

0..1 < instanceagentregistration>,

0..1 <requirements>,

0..1 <consumedresourcelist>,

0..1 <custompropertylist>,

0..1 <solmansettings>

description

businessarea

servicegroup

systemid

instanceno

instanceprofilepath

user

passwd

encryptedpasswd

Consists of 0..1 <primaryhostname>,

0..N <hostname>

name

refnetworkname

name

refnetworkname

dbname

user

passwd

encryptedpasswd

dbSuperAdminUser – database super admin user

dbSuperAdminPw – database super admin password

dbJavaSchemaUsr - database java schema user

dbJavaSchemaUsrPw - database java schema user password

dbABAPSchemaUsr - database abap schema user

dbABAPSchemaUsrPw - database abap schema user

dbconfdir – database configuration directory

usehttps – possible values true or false

port

httpProxy – configured proxy label

instanceprofilepath

clientCertAlias

user

passwd

encryptedpasswd

user

passwd

encryptedpasswd

memory

saps

preferredhost

addressspace

cputype

os

osversion

type

cputype

Example:

<property checksum="…" id="…" name="Target System">

  <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xmlElementValue">

    <system description="…" installationhost="…" release="…" systemid="…" systemtype="…" />

      <rfcdestination client="…" encryptedpasswd="…" hostname="…" instanceno="…" language="…" passwd="…" saprouter="…" user="…" />

      <isolations>

<isolation type=" … " value="…”  />

…

      </isolations>

      <additional_attributes>

<attribute key=" " value=" />

…

      </additional_attributes>

      <service acenabled="… " acmanaged="…" communicationhost="…" dbInstanceName="…" dbtype="…" id="…" installationhost="…" operational="…" refpoolname="…" servicetype="…" systemid="…" type="…" >

        <properties businessarea="…" description="..." servicegroup="…" />

        <hostnames>

          <primaryhostname name="…" refnetworkname="…" />

        </hostnames>

        <databaseproperties dbconfdir="…" dbname="…" />

        <requirements memory="…" preferredhost="…" saps="…">

          <resourcetype addressspace="…" cputype="…" os="…" osversion="…" />

…

        </requirements>

        <consumedresourcelist>

          <consumedresource type="…" value="…" />

…

        </consumedresourcelist>

        <mountlist automount="…">

          <mount fstype="…" storagetype="…" usage="…">

            <mountpoint>…</mountpoint>

            <exportpath>…</exportpath>

            <options>…</options>

          </mount>

…

        </mountlist>

        <additional_attributes>

          <attribute key="…" value="…" />

…

        </additional_attributes>

      </service>

      <service …>

…

      </service>

    </system>

  </value>

</property>

back to top

id – resource id

hostname - hostname

acmanaged – True or false

refpoolname

saps

operational – true or false

This section represents a virtual machine. Consists of

0..1 <entityusagetypes>,

1..1 <hostagentproperties>,

0..1 <networkinterfaces>,

0..1 <resourcetype>,

0..1 <additional_attributes>,

0..1 <storage_properties>,

0..1 <custompropertylist>

usedefaultcredentials

user

passw

encryptedpassw – true or false

usehttps

port

httpProxy

clientCertAlias

ifid – interface id

refnetworkname – network name

addressspace

cputype

os

osversion

key

value

key

value

secure - true of false

encrypted true or false

Example:

<property checksum="..." id="..." name="ComputerSystem">

  <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xmlElementValue">

    <resources>

      <resource acmanaged="..." hostname="..." id="..." operational="..." refpoolname="..." saps="...">

        <hostagentproperties port="..." usedefaultcredentials="..." usehttps="..." />

        <networkinterfaces>

          <interface ifid="..." refnetworkname="..." />

          ...

        </networkinterfaces>

        <resourcetype addressspace="..." cputype="..." os="..." osversion="..." />

        <additional_attributes>

          <attribute key="..." value="..." />

          ...

        </additional_attributes>

      </resource>

    </resources>

  </value>

</property>

back to top

Example:

<property checksum="7C310BF7CD4B161FA9679CA8FE77AEA1" id="PROP-34" name="User Management Name">

    <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                        <User Management Handler Name>

    </value>

</property>

back to top

Example:

<property checksum="BCBFC3130F8FB7227B50AE6137899E76" id="PROP-13" name="Directory

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          /tmp/VCM_pca/....

        </value>

</property>

back to top

Example:

<property checksum="CB7E0E3CF85A93FEFA6053F6F7A7E22D" id="PROP-12" name="Directory User">

          <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                            <SID>adm

          </value>

</property>

back to top

Example:

<property checksum="CD745EEEED2F0AB6DF0AEBE4CB641A0F" id="PROP-14" name="Directory Group">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          sapsys

        </value>

</property>

back to top

RequestNewTargetVolume

NamesIfNotUnique Flag

This property is set from LVM template to true.

This means that during System Refresh

if storage volume names already

exist a new one will be created.

A naming conventions that will

be followed for new names is

"vol -<target_SID>-<instance type>-

<unique number>".

If user has it’s own naming

conventions this property must

be set to false and  volume names

need to be parameterized with placeholders.

Example:

<property checksum="1EA450A76F81AEE563C9706A5D11F53A" id="PROP-40"

    name="RequestNewTargetVolumeNamesIfNotUnique Flag">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

It will be used in step "Delete Volumes"

to ask for confirmation

before deleting volumes

Example:

<property checksum="01588F90D2E7DE7755FA1B9EEDA2B001" id="PROP-41" name="Request Confirmation">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:boolean">

                          true

        </value>

</property>

back to top

Physical hostname on which new

target system will be provisioned

during execution of template

Example:

<property checksum="BAFE399DEFF538343309CBB8C55C76CA" id="PROP-2" name=" Physical hostname ">

        <value xmlns:xs="http://www.w3.org/2001/XMLSchema"

                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">

                          <physical host name>

        </value>

</property>

back to top

List of additional attributes.

This property has only one

key and many values.

Example:

<property checksum="ABE301A9F3229FA09915FC2E7E17AD7A" id="PROP-17" name="Users">
            <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ldapUser">
                <users>
              </users>
…

…
            </value>
</property>

back to top

Example:

key = objectClass ;  values : inetOrgPerson, organizationalPerson, posixAccount, person, top

<additionalListAttributes>
<entry>
<key xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">objectClass</key>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema xsi:type="xs:string">inetOrgPerson</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">organizationalPerson</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">posixAccount</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">person</value>
<value xmlns:xs=”http://www.w3.org/2001/XMLSchema” xsi:type="xs:string">top</value>
</entry>
</additionalListAttributes>

back to top

List of additional string attributes

key: sn -> value

key: cn ->value

key: dn – >value

For every group that user

belong to there is a separate

property

<memberOfGroups>

cn=dbq1bctl,dc=groups,

dc=wdf,dc=sap,dc=com

</memberOfGroups>

What shell will be used from this

user when it logs on

What user manager

will be used to create user

Value type is Boolean

true/false

Value type is Boolean

true/false

Value type is Boolean

true/false

Domain name

<dn>

uid=sapq1b,

dc=users,

dc=wdf,

dc=sap,

dc=corp

</dn>

<groups>

...

</groups>

One entry tag for each

storage adapter, where

key is the storage adapter.

Label and value is the storage

clone request.

Example:

        <property checksum="FD0BA2418CBA580C22E6D694C77D6770" id="PROP-1" name="Storage Clone Request">

            <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="multiStorageOperationRequest">

                <adapterIdToRequest>

                    <entry>

                        <key>

                            <label>ssc</label>

                        </key>

                        <value xsi:type="deleteVolumesRequest">

                            <storageVolumes>

                                <storageSystemId>....</storageSystemId>

                                <storagePoolId>.....</storagePoolId>

                                <storageVolumeId>....</storageVolumeId>

                                <name>...</name>

                                <totalSpaceMB>0</totalSpaceMB>

                                <freeSpaceMB>0</freeSpaceMB>

                            </storageVolumes>

                            <storageVolumes>

                              .....

                            </storageVolumes>

                        </value>

                    </entry>

                </adapterIdToRequest>

            </value>

        </property>

back to top