Special case of scaled system

In a scaled system, data is imported to the sub-server. All sub-servers must have an identical configuration. The autoextendattributes and addmergeattributes options would change the configuration of an individual sub-server and the uniform configuration of all sub-servers would be lost. Therefore, using these two options is not possible in a scaled system.

If you still want to use the automatic extension of the attribute configuration, you need to export the possible extensions for each sub-server and manually import these on the master server, which can then distribute the extensions to all sub-servers in the system.

Procedure

Before you import data with new attributes to the sub-server, perform the following steps:

  1. Identify new system event attributes and extract them using the -extractattributes <File name> parameter in the xmlimport command line program.
  2. Import the new attributes on the master server.
  3. Identify new attributes that you want to be retained when merging process fragments and extract these using the -extractmergeattributes <File name> parameter in the xmlimport command line program.
  4. Manually extend the merge configuration on the master server, as described in the Add the merge attributes section below.
  5. Perform an XML data import to the sub-server with the automapping option.

Add the merge attributes

If you have specified automatic mapping extension for processes (<automapping nodetype="PROCESS" ...), you can extract the new attributes added that are to be retained when merging process fragments by specifying the -extractmergeattributes <File name> parameter in the command line. No XML data is imported. The file generated contains only a mergeattributes XML element with a list of all new attributes, and has the following structure:

<?xml version="1.0" encoding="ISO-8859-1"?>

<mergeattributes>

<attribute key="..." />

...

</mergeattributes>

Use the -export -merger <File name> parameter to export the merge configuration on the master server. Edit the merge configuration by adding the attributes (attribute XML elements for mergeattributes XML element) to all merge attributes from the exported master server merge configuration previously exported for each sub-server using -exctractmergeattributes <File name>.

Finally, use the -import -merger <File name> parameter to import the merge configuration from the master server.

Example

Exported master server merge configuration

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE mergerconfig SYSTEM "mergerconfig.dtd">

<mergerconfig>

<mergehandling>

<processmerge>

<mergeattributes>

<attribute key = "AT_SAPSYSTEM"/>

<attribute key = "AT_SAP_BELEGNR"/>

</mergeattributes>

</processmerge>

<eventmerge priority="1">

<mode>

<keymerge/>

</mode>

</eventmerge>

</mergehandling>

</mergerconfig>

Exported merge attributes for sub-server 1

<?xml version="1.0" encoding="ISO-8859-1"?>

<mergeattributes>

<attribute key = "AT_SAPCLIENT"/>

</mergeattributes>

Exported merge attributes for sub-server 2

<?xml version="1.0" encoding="ISO-8859-1"?>

<mergeattributes>

<attribute key="AT_SAP_BSTYP" />

<attribute key="AT_SAP_BSTYP" />

</mergeattributes>

Consolidated master server merge configuration

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE mergerconfig SYSTEM "mergerconfig.dtd">

<mergerconfig>

<mergehandling>

<processmerge>

<mergeattributes>

<attribute key = "AT_SAPSYSTEM"/>

<attribute key = "AT_SAP_BELEGNR"/>

<!-- Merge attributes sub-server 1 -->

<attribute key = "AT_SAPCLIENT"/>

<!-- Merge attributes sub-server 2 -->

<attribute key="AT_SAP_BSTYP" />

<attribute key="AT_SAP_BSTYP" />

</mergeattributes>

</processmerge>

<eventmerge priority="1">

<mode>

<keymerge/>

</mode>

</eventmerge>

</mergehandling>

</mergerconfig>