SAP Solution Manager - Content Transfer This document provides information on architectural and design questions, such as which SAP Solution Manager

SAP Solution Manager - Content Transfer This document provides information on architectural and design questions, such as which SAP Solution Manager content is transferable and how.

TABLE OF CONTENTS PREFACE... 3 1. OPERATIONS AND SOLUTIONS... 4 2. PROJECT MANAGEMENT... 6 2.1 Projects... 6 2.1.1 Documents... 7 2.1.2 Templates... 7 2.2 Roadmap... 9 2.3 Solution Documentation Assistant... 9 3. INCIDENT MANAGEMENT... 9 4. CHANGE MANAGEMENT... 9 5. TEST MANAGEMENT... 9 6. ROOT CAUSE ANALYSIS... 9 7. TECHNICAL DEPENDENCIES... 10 7.1 System Landscape Directory (SLD)... 10 7.2 RFCs, CCMS, and SCOT... 10 7.3 SAP Business Intelligence and Wily Enterprise Manager Data... 10 7.4 Maintenance Optimizer and License Keys... 10 7.5 Central Performance History (CPH)... 10 8. HOW TO... 11 8.1.1 Solution Transfer... 11 8.1.2 Project Transfer... 13 8.1.3 Template Transfer... 16 8.1.4 Roadmap Transfer... 20 8.1.5 Solution Documentation Assistant... 20 8.1.6 Test plan Transfer... 22 SAP Solution Manager 7.0 & 7.0 EHP1 CONTENT TRANSFER Version: 1.8 Date: April, 2014 2

PREFACE This document provides information to drive decisions about changing an existing SAP Solution Manager system, planning a new one, or upgrade an existing SAP Solution Manager 7.01 to a higher release. It answers architectural questions to enable decision-makers to design a best-run SAP Solution Manager concept. Common decisions to be made are: New SAP Solution Manager installation or upgrade. Merge or split organizational units resulting, for example, from the sale of company branches. Correct mistakes made during previous design phases or add missing knowledge about SAP Solution Manager architecture. The recommendations refer only to content transfer from one productive SAP Solution Manager system to another. There are no recommendations for managed systems. 3

1. OPERATIONS AND SOLUTIONS Operations is one of the key functions in SAP Solution Manager. It handles 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 data and core business process knowledge. 1 Not all Operations content is transferable. SAP distinguishes between Solution content transfer, and the transfer of SAP Solution Manager system infrastructure, such as the CCMS or SAP Solution Manager Diagnostics. The matrix below provides an initial overview of transfer possibilities, followed by best practices for performing the transfer in each area and function. Scenario/Function Transferable? How Remarks Central System Administration No Early Watch Alert No Existing EWA reports can be archived in an optical archive (see SAP note 546685) Service Level Report No Existing SLR reports can be archived in an optical archive Business Process and Interface Monitoring Only the customizing (setup session) is transferred. After the migration, manual generation and activation are required in the new system. Alert history will be lost. System Monitoring Yes Initial transfer by transaction Solution_Transfer Only the customizing (setup session) is transferred. After the migration, manual generation and activation are required in the new system. Alert history will be lost. In an upgrade it has to be decided whether a transport is appropriate, or the new Monitoring and Alerting Infrastructure is to be used (see http://wiki.sdn.sap.com/wiki/display/techops/home) Collaboration Issues, Expertise-on-Demand requests, and tasks are transferred. The service plan must be synchronized with SAP Backend Solution definitions Documentation Service Plan 1 http://service.sap.com/~sapidb/011000358700000558132009e 4

Issue Management Service Desk messages No Logical Components Change history No No To be defined & maintained prior to Solution transfer. Logical components must be created and assigned to the transferred solution again, in the new system. Change documents cannot be transferred from one system in another. Show how this procedure is executed in SAP Solution Manager. 5

2. PROJECT MANAGEMENT This chapter describes project-related aspects of transferring content into another SAP Solution Manager system. It is limited to the most important aspects of making projects initially available in different SAP Solution Manager systems. Scenario/Function Transferable? How Remarks Projects Templates Transaction SOLAR_PROJECT_ADMIN See details in chapter 2.1 Projects See details in chapter 2.1.2 Templates Roadmaps Yes Transaction RMDEF or report RM_TRANSPORT_FUNCTION See details in chapter 2.2 Roadmap Solution Documentation Assistant Transaction SOLMAN_WORKCENTER or SM_ WORKCENTER See details in chapter 2.3 Solution Documentation Assistant 2.1 Projects 2 All projects can be transported in 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. Note that Logical Components and RFC (remote function calls) destinations will not be transfered into the target system. Before you transport the project, make sure that Logical Component and RFC destinations are created and maintained in the target system. 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. The following elements are transported: Project structure (e.g. scenarios, processes, process steps) with all assignments (transactions, configuration objects, development objects, test cases,...) All documents Structure attributes Assigned test cases (manual test cases and ecatts) which are stored centrally in the Solution Manager system Assigned TBOMs (as of SAP Solution Manager 7.1) Status values in roadmaps directly assigned to a project, and project-related documents assigned to this roadmap. The following elements cannot be transported: Change history of changes on the tabs Assigned service messages and issues 2 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). 6

Assigned end users and end user roles Assignments of administration (tab) data, such as team member assignments, keywords, status Document settings in the Knowledge Warehouse (definitions of document attributes and status schemes) Logical Components (must be created and assigned again to the transferred project, in the new system) Assigned TBOMs (valid up to SAP Solution Manager 7.01) Issues and Service Desk messages are not collected while the project transport is created 2.1.1 Documents Documents usually consist of the most recent version (the version displayed in a project) and change versions, which are created automatically whenever a document is changed. The transport function in SOLAR_PROJECT_ADMIN transfers documents with all change versions only if the following prerequisites are fulfilled in the Solution Manager system: 1. For systems with support package ST 400 SP18 SP26, and support package ST 710 SP1 SP3, SAP Note 1624346 must be installed. 2. Table IWPROPVAL must not contain the following entry: AREA: IWBSOLAR CLASS: (= space) NAME: IWBSOLAR_TRANSPORT_STATUS VALUE: RELEASED If table IWPROPVAL contains such an entry, remove it, if you want to transfer all change versions of the assigned documents. Show how this procedure is executed in SAP Solution Manager. Please note that documents stored on a third-party supplier's content server and not on an SAP Content Server will not be transported directly. Please pay attention to SAP Note 865561 describing a workaround for this situation. 2.1.2 Templates Templates are created and maintained in template projects, which can be transferred in the same way as other projects, e.g. implementation projects. To be able to transfer templates or complete template projects, both the templates and the template project must be assigned to a transportable package. The package is assigned when the template project and a template are created. A transportable package can be assigned later, but it is very time-consuming (moving all relevant objects from a local package, e.g. $TMP to a transportable package). As well as transporting the whole template project (including all templates), single templates, created within the template project, can be transported separately, using the template transport function in SOLAR_PROJECT_ADMIN. Once a template has been transported to the target system, it is visible there to all projects, in the Scope tab in transaction SOLAR_PROJECT_ADMIN. Note: the following restrictions apply to transporting a template, compared to transporting projects: The template transport transfers only the most recent version of a document. Change versions of documents cannot be transferred with this function. Documentation on the Project Documentation tab is not included in the transport of a single template. Remark with respect to template project transport: 7

1) In case the template project was not assigned to a transportable package but e.g. to $TMP, all of objects created for the project have to be collected and finally assigned to a transportable package. For this please follow the described procedure: a. Create a Z* package and assign it to a workbench request b. Replace the currently assigned package (e.g. $TMP) by the new created Z* package using transaction SOLAR_PROJECT_ADMIN (tab: Transport Request => Package for Objects) c. Execute the report RSOLAR_PROJSTRUCT_UPDATE_DEVC for the template project using transaction SE38. d. Release the workbench request which has been assigned to your package Z* e. Now capture the template project into a transport request of the type Transport of Copies in SOLAR_PROJECT_ADMIN by selecting the function Project Transport f. Release this Transport of Copies from the source system. 2) If the template project is to be transported finally into a target SAP Solution Manager system, the originality of this project has to be switched to the target SAP Solution Manager system, too. This requires additional activities by using a relocation transport request. Afterwards the template project can be further processed in the new target system. SAP note 1304462 describes in the chapter Solution how to proceed, in order to switch the originality system from the old to the new origin system. Show how this procedure is executed in SAP Solution Manager. 8

2.2 Roadmap Roadmaps created by the customer can be transported in transaction RMDEF 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 (Flavors, Roles, Subject Areas) into a transport request. Only the most recent version of assigned documents is transferred. Change versions of documents are not transferred with the roadmap transport. Show how this procedure is executed in SAP Solution Manager. 2.3 Solution Documentation Assistant You can download or upload the check rules for your Analysis Project using the Solution Documentation Assistant functionality. The Analysis Project contains the business process structure, including transaction assignments and assigned check rules. The data is exchanged between the two systems using XML file transfer methodology. Show how this procedure is executed in SAP Solution Manager. 3. INCIDENT MANAGEMENT The transfer of support messages (incidents) from one SAP Solution Manager system to another is not supported. For solution-specific service desk messages (and issues), see chapter 0 1. Operations and Solutions, and for project-specific service desk messages (and issues), see chapter Error! Reference source not found. Error! Reference source not found.. 4. CHANGE MANAGEMENT The transfer of change documents from one SAP Solution Manager system to another is not supported. 5. TEST MANAGEMENT The Test Workbench includes functionality for transporting test plans and test packages. Test plans and test packages are always transported completely: you cannot transport only the changes that have been made to them. Test plans and test packages with a transportable package assigned to them can only be changed if you allow changes to repository objects. The transport connection in the Test Workbench does not include the assignment of test cases and TBOMs to projects. There is no functionality for transporting assignments made to a project. Use the transport function in transaction SOLAR_PROJECT_ADMIN to transport the corresponding project separately. The tester assignment, the test status and test-related messages of a test plan are not transported in the standard, because these entities are specific to systems and clients. Show how this procedure is executed in SAP Solution Manager. 6. ROOT CAUSE ANALYSIS There is no tool support for transferring data between SAP Solution Manager systems in the SAP Solution Manager Diagnostics environment. 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 9

Solution Manager (or a connected one) using standard BI tools. This data can also be re-imported. SAP Solution Manager provides no tool support for this type of data transfer, or to enable the other SAP Solution Manager system to use the transferred data. 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, and tools/services that use 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. Information exchange with 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, see note 935474. 7.2 RFCs, CCMS, and SCOT You cannot transport RFC connections, so you need to regenerate all the required RFC connections such as READ, LOGIN or TRUSTED RFC in the new productive SAP Solution Manager system. CCMS configurations can be transported using a monitoring properties variant. Detailed information can be found here 3. There is no tool for transporting customizing settings in transaction SCOT, and certain system/client-related settings, such as the Default Domain, should not be transported, 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 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 SAP Business Intelligence tools (SAP Solution Manager provides no tool for collecting/exporting data that is relevant to SAP Solution Manager from the SAP Solution Manager BI directly). If you have Wily Introscope, you can only merge the data from one or more Enterprise Managers, by full copy. You stop the Enterprise Managers, copy the data directories from the source Enterprise Manager to the target, and restart them. You cannot import additional data from a different IS EM. 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. 3 http://help.sap.com/saphelp_nw73/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htm 10

8. HOW TO 8.1.1 Solution Transfer What to do Screen Display Select the solution to transport, in transaction SOLUTION_TRANSFER in SAP Solution Manager, and mark the items to be transported, in the Scope area. Choose the transport target. Click Next, to start the export. Once the export is completed, you will be prompted to store the file solution.zip. Save it to the designated destination. The transport request ID will be shown in the status line. Put the previously-created transport request in the transport directory of your SAP Solution Manager, and import it in transaction STMS. Execute transaction SOLUTION_TRANSFER. A browser windows opens. Choose the location of the solution.zip file, and upload it to the SAP Solution Manager. 11

Once, the solution.zip is uploaded, choose the Target Solution. This is a previously-created new solution, or an existing one. Choose the target logical components, the import option and the scope. Click Import. If the transport request has not yet been imported, the system tells you which transport request now has to be imported. Return to topic content 12

8.1.2 Project Transfer What to do Screen Display Select the project to transport, in transaction SOLAR_PROJECT_ADMIN in SAP Solution Manager. Mark the project Select Transport from the top menu or click on the transport icon 13

If you choose All Languages please refer to SAP note 1742533 Enter a transport request (NOT a local request). Download the data file of this transport request, and upload it into the transport folders of the SAP Solution Manager. The transport is visible in the import queue in transaction STMS. Select transport request and start the import. 14

The import can be performed immediately, or scheduled. On the Option tab, mark Ignore Invalid Component Version (in an upgrade from SAP Solution Manager 7.01 to 7.1). Return to topic content 15

8.1.3 Template Transfer What to do Screen Display Select the template project in which you have stored the template to transport, in transaction SOLAR_PROJECT_ADMIN in SAP Solution Manager. Open the template project 16

Choose the Template tab, and select the template from the list. Click on Transport Click on Continue 17

Select an option, and click Continue. Follow the instruction on the screen, to select a role of the project system landscape, and click Continue. Choose a transport request/ task, and the languages, and click Continue. If you mark the checkbox here, unreleased documents will also be collected. 18

If there are local objects, reassign them to a transportable package. Finished. Return to topic content 19

8.1.4 Roadmap Transfer What to do Screen Display Select the roadmap to transport, in transaction RMDEF in SAP Solution Manager. The context menu contains Transport Select a transport request and the content options. Return to topic content 8.1.5 Solution Documentation Assistant What to do Screen Display Execute transaction SOLMAN_WORKCENTER in SAP Solution Manager, and choose the work center Solution Documentation Assistant. Navigate to the Content Interface and choose either Download Check Rules or Download Analysis Project, depending what you are going to export. 20

a.) Select Download Check Rules, click Search, select the Check Steps and click Download, to store the zip file on your PC. b.) Select Download Analysis Project, select the Analysis Project, and click Download, to store the zip file on your PC. To upload the previously stored zip files (from SAP Solution Manager 7.01 or 7.1) execute transaction SOLMAN_WORKCENTER, select the Solution Documentation Assistant work center, navigate to the Content Interface, and click Upload Content. Select the previously stored zip files, and click Start, to import the content. Return to topic content 21

8.1.6 Test plan Transfer What to do Screen Display Select the test plan to transport, in transaction SOLMAN_WORKCENTER, in SAP Solution Manager. In the menu Test Plan, choose Transport Test Plan. Select the objects to be transported, and click on Transport. Fill in a transport request (or create a new one). Return to topic content 22

www.sap.com 2012 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.