solman content transfer

SAP®

© 2011 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Title: SAP Solution Manager 7.0 & 7.0 EHP1 and above CONTENT TRANSFER Version: 1.3 Date: January 2011

of 9

Version: 1.3

Date: January 2011

Language: English

SAP Solution Manager 7.0 & 7.0 EHP1

and above

CONTENT TRANSFER

This document provides information on architectural and design questions, such as

which SAP Solution Manager content is transferable and how.

SAP®



of 9

Content

Preface............................................................................................................. 3

1. Operations and Solutions ............................................................ 4

2. Lifecycle Management and Projects ........................................ 5

2.1 Template Project .......................................................................................... 5

2.2 Transport of Projects ................................................................................... 5

2.3 Roadmap ....................................................................................................... 6

2.4 Solution Documentation Assistant ............................................................ 6

3. Incident Management ................................................................... 6

4. Change Management ..................................................................... 6

5. Test Management ........................................................................... 7

6. SAP Solution Manager Diagnostics .......................................... 7

7. Technical Dependencies ............................................................... 8

7.1 System Landscape Directory (SLD) .......................................................... 8

7.2 RFCs, CCMS, and SCOT .............................................................................. 8

7.3 SAP Business Intelligence and Wily Enterprise Manager Data ............ 8

7.4 Maintenance Optimizer and License Keys ............................................... 9

7.5 Central Performance History (CPH) .......................................................... 9

SAP®



of 9

Preface

This best practice provides information for driving decisions about changing an existing SAP

Solution Manager system or planning a new one. It aims to answer architectural questions and

to enable decision-makers to design a best-run concept on SAP Solution Manager. Common

triggers for decisions are:

A merge or split of organizational units resulting, for example, from the sale of

company branches

Mistakes made during previous design phases or missing knowledge about SAP Solution

Manager architecture

All functional scope relates to SAP Solution Manager Release 7.0 EhP1 (ST700, SP18) except

as noted otherwise.

The recommendations refer solely to content transfer from one productive SAP Solution

Manager system to another. There is no focus on managed systems.

SAP®



of 9

1. Operations and Solutions

“Operations” is one of the key function areas in SAP Solution Manager. It focuses on handling

your daily business (operations). The majority of Operations content is bundled in a virtual

container known as a “Solution”. This is the location for system and process information, data,

and documentation, including system administration work and core business process

knowledge.1

In the area of Operations, not all content is transferable.

SAP distinguishes between Solution content transfer and the transfer of infrastructure relating

to the SAP Solution Manager system, such as the CCMS or SAP Solution Manager Diagnostics.

The matrix below provides an initial overview of the potential transfer possibilities, followed by

best practices for performing the transfer in single areas and functionalities.

Scenario/Function Trans-

ferable? How Remarks

Central System

Administration

No

Early Watch Alert No

Service Level Report No

Business Process

and Interface

Monitoring

Yes

Initial transfer by

transaction

Solution_Transfer

Only customizing is transferred. Manual

generation and activation are required.

Alert history is lost.

System Monitoring Yes Only customizing is transferred.

Collaboration Yes Issues, Expertise-on-Demand requests,

and tasks are transferred. The service

plan must be synchronized.

Solution definitions Yes

Documentation Yes A transport request is created

automatically from the Knowledge

Warehouse folder.

Service Desk

messages

No

Logical Components No To be defined&maintained prior to

Solution transfer. Logical components

are then assigned automatically.

1 http://service.sap.com/~sapidb/011000358700000917052007E/SolMan_Solution_Concept.pdf

http://service.sap.com/~sapidb/011000358700000917052007E/SolMan_Solution_Concept.pdf

SAP®



of 9

2. Lifecycle Management and Projects

This chapter describes project-related aspects of transferring content into another SAP Solution

Manager system. The description is limited to the most important aspects involved in making

projects initially available in different SAP Solution Manager systems.

2.1 Template Project

Template projects can be assigned to a transportable package when the project is created. A

later assignment to a transportable package is possible, but very time-consuming (shipment of

all relevant objects from $Temp to related package).

However, the templates created within the template project can be transported separately.

Once a template has been transported to the target system, it is visible for all projects in the

scope tab in transaction SOLAR_PROJECT_ADMIN.

The following elements are transported:

Structures (scenarios) assigned to the template

All assignments (transactions, IMG objects, developments, test cases,..)

All documents, except project documentation for the template project

Structure attributes

The following elements cannot be transported:

Document history

Messages and issue assignments

End users and end-user roles

Assignments of administration (tab) data, such as team member assignments,

keywords, status

2.2 Transport of Projects

All projects can be transported via a transport request, which is created using transaction

SOLAR_PROJECT_ADMIN.

This functionality ensures that all assignments made to the project are included in the

transport. However, there are some limitations. For example, only recently released

documents – and only the latest versions thereof – are taken into account (the histories are

not transported).

After a successful transport, administration data such as the project landscape, team

members, and project standards need to be adapted to fit the new system.

1 Data migration of projects between systems is not supported as of SAP Solution Manager 7.0 (between SAP Solution Manager 2.1/2.2

and SAP Solution Manager 3.1/3.2 data migration was supported via transaction SOLAR_MIGRATION, see SAP Note 644123).

SAP®



of 9

2.3 Roadmap

Roadmaps created by the customer can be transported from within transaction RMDEF or

directly, using report RM_TRANSPORT_FUNCTION. This report packs the roadmap structure

with all the relevant languages, documents (phase and task descriptions), accelerators, entry

screen, and roadmap attributes into a transport request.

2.4 Solution Documentation Assistant

Using the Solution Documentation Assistant functionality, you can download or upload the

check rules for your Analysis Project. The Analysis Project contains the business process

structure, including transaction assignments and assigned check rules. The data exchange

between the two systems is performed using XML file transfer methodology.

3. Incident Management

The transfer of support messages (incidents) from one SAP Solution Manager system to

another is not supported.

4. Change Management

The transfer of change documents from one SAP Solution Manager system to another is not

supported.

SAP®



of 9

5. Test Management

The Test Workbench includes functionality for transporting test plans and test packages.

However, test plans and test packages are always transported in full: It is not possible to

transport only the changes that have been made to them. Test plans and test packages that

have a transportable package assigned to them can only be changed if you allow changes to

repository objects.

The transport connection within the Test Workbench does not include the assignment of test

cases and TBOMs to projects. There is no functionality for transporting assignments that have

been made to a project. However, you can transport the entire project using transaction

SOLAR_PROJECT_ADMIN.

The assignment of testers to test packages is not transported in the standard, because users

are specific to systems and clients. Due to the fact that testers are not transported, the

results, related messages, and Change Request Management test messages are not

transported at all.

6. SAP Solution Manager Diagnostics

In the SAP Solution Manager Diagnostics environment, there is no tool support for transferring

data between multiple SAP Solution Manager systems. This applies both to configuration data

and to the diagnostics data collected by the agents configured on the managed systems.

It is possible, however, to extract the diagnostics data out of the Business Intelligence system

in SAP Solution Manager (or a connected one) using standard BI tools. This data can also be

re-imported. SAP Solution Manager itself provides no tool support for this specific type of data

transfer or for enabling the other SAP Solution Manager system to work with the transferred

data.

SAP®



of 9

7. Technical Dependencies

This chapter provides an overview of the technical layer of SAP Solution Manager and the

related aspects of transferring content.

7.1 System Landscape Directory (SLD)

The System Landscape Directory (SLD) is a technical CIM (common information model)

database that contains all the information – such as server name, SID and product data like SP

Stacks or patch level – for the connected systems. The SLD is a central information provider

that can gather this information and act as single point of access for the administrator him-

/herself and tools/services that rely on this data

The local SLD of a Solution Manager system is usually connected to one or more central SLDs,

which deliver this information via the SLD bridge to the local SLD of the Solution Manager

system. An information exchange to the central SLD is not possible. A regular job in the

Solution Manager system synchronizes the data between the central and the local SLD.

Another job (LANDSCAPE FETCH) synchronizes the local SLD with the SMSY.

When merging systems, you can group SLDs and adapt the usage relationship when you

import the content of one or more SLDs to the new one. For a detailed description, please read

note 935474.

7.2 RFCs, CCMS, and SCOT

There is no functionality for transporting RFC connections. You therefore need to regenerate all

the required RFC connections – such as READ, LOGIN or TRUSTED RFC – within the new

productive SAP Solution Manager system.

CCMS configurations can be transported using a “monitoring properties variant”. Detailed

information can be found here2.

There is no tool available for transporting customizing settings in transaction SCOT. Moreover,

certain system-/client-related settings, such as the ’Default Domain’, should not transported at

all and must be reconfigured in the new system.

7.3 SAP Business Intelligence and Wily Enterprise Manager Data

All the data stored in the SAP Business Intelligence system included in SAP Solution Manager,

or connected to the SAP Solution Manager system as BI storage, can be extracted and

imported to another SAP Solution Manager BI with the help of SAP Business Intelligence tools

2 http://help.sap.com/saphelp_nw70/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htm

(http:/help.sap.com/saphelp_nw70/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htm

SAP®



of 9

(SAP Solution Manager provides no direct tool for collecting/exporting data that is relevant to

SAP Solution Manager from the SAP Solution Manager BI). If you have Wily Introscope

installed and you wish to merge the data from one or more Enterprise Managers, you can only

perform a “full copy” operation. This means that you stop the Enterprise Managers, copy the

data directories from the source Enterprise Manager to the target one, and restart it. An

import of additional data from a different IS EM is not possible.

7.4 Maintenance Optimizer and License Keys

The transfer of maintenance procedures (Maintenance Optimizer transactions) from one SAP

Solution Manager system to another is not supported.

For high-security customers, a possible option is to download the license keys with one

Solution Manager system and transfer them as xml files to a second Solution Manager system.

7.5 Central Performance History (CPH)

CPH configuration tables and the CPH transaction data table (cluster table) are also

transportable.

solman content transfer

Documents