Vous êtes sur la page 1sur 7

PRINT FROM SAP HELP PORTAL

Document: Software Life-Cycle Management URL: http://help.sap.com/saphelp_nw70ehp3/helpdata/en/90/08ff2a608441d3b082d33031b3c02c/content.htm Date created: July 13, 2013

2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. 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. SAP 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. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 7

Software Life-Cycle Management


Software Life-Cycle Management (SLM) by SAP comprises the management of SAP products and solutions in real, customer-specific system landscapes. Organizations can manage SAP software in their system landscapes by performing implementation tasks such as implementing new systems, copying existing systems, or enabling the creation and propagation of changes in the landscape. Organizations can also maintain their software by importing Support Packages and corrections or by upgrading to new software versions. Due to the complexity of todays landscapes and the interdependencies between individual software components, tool support for monitoring, maintenance, implementation, and upgrade tasks is a must. System Landscape Directory of SAP NetWeaver (from now on abbreviated as SLD to improve readability) offers both a directory of installable components that are available from SAP, and data automatically updated about systems, components, and business scenarios implemented in your system landscape. Software Life-Cycle Management helps you to set up a distributed landscape for your custom development project. In addition, it provides scenario-based implementation support for predefined business content, such as Enterprise Portal (EP) and Business Intelligence (BI) content. Software Life-Cycle Management is aligned both with SAP Solution Manager scenarios and the de facto standard ITIL (IT Infrastructure Library by OGC the Office of Government Commerce, UK).

Integration with Other IT Scenarios


SLM provides you with the services you need to implement, copy, maintain, and upgrade every SAP NetWeaver IT scenario. Every IT scenario that deals with Java development relies on SAP NetWeaver Development Infrastructure, whose setup is part of Software Life-Cycle Management.

Scenario Variants
SLM comprises the following scenario variants: Scenario Variant Implementation Support Description Addresses the requirements for: Implementing new functionality Implementing and configuring business content Copying or migrating systems Supporting the creation and propagation of customer-specific changes in an existing landscape Software Maintenance Addresses the requirements for: Updating your system landscape to keep it running smoothly Upgrading the scenarios implemented in your landscape to new releases

Related Information
The following role-specific guidelines can help you in applying this scenario: User Roles and Tasks Planning the installation of your IT scenario Planning the upgrade to your new IT scenario Installation and Upgrade Configuration Administration Security Development Guideline For more information, see the document Master Guide SAP NetWeaver available on SAP Service Marketplace at service.sap.com/instguidesnw70 Installation. For more information, see the document Upgrade Master Guide SAP NetWeaver available on SAP Service Marketplace at service.sap.com/instguidesnw70 Upgrade. Technology Consultants Guide SAP Solution Manager or the The Software Life-Cycle Management section in the Technology Consultants Guide

Software Life-Cycle Management section in the Technical Operations Manual

Security Guide Administration of SAP NetWeaver Development Infrastructure

Implementation Support
At regular intervals, you need to realize new functions in your system landscape by adding new systems to an existing landscape or even building a totally new landscape either by implementing new systems or copying existing ones. Implementation Support offers a process- and tool-oriented approach for implementing and enhancing your system landscape. In addition, Software Life-Cycle Management (SLM) provides scenario-based implementation support for predefined business content, such as Enterprise Portal (EP) and Business Intelligence (BI) content. Implementation Support provides you with the necessary infrastructure to create and propagate software changes in your landscape.

Required Usage Types of SAP NetWeaver


For the Software Change Management IT process of this IT scenario variant, the usage type Development Infrastructure (DI) is required. For other IT processes of this IT scenario variant, no special usage type is required, since they provide functions for implementing systems or copying existing

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 2 of 7

For other IT processes of this IT scenario variant, no special usage type is required, since they provide functions for implementing systems or copying existing systems with any usage type.

IT Processes of the Scenario Variant


This scenario variant comprises the following IT processes: Process Implementation Implementation and Configuration of Business Content Copy and Migration You can copy the SAP systems both ABAP and Java a scenario is based on to create consistent duplicates for test or development purposes or to build up your landscape. You can also migrate an SAP system to another operating system or database. Software Change Management You can manage the consistent and synchronous flow of object changes in a distributed system environment between different software stages, such as development, consolidation, and production. What You Need to Know Implements a new landscape or adds a scenario to your system landscape while reusing existing systems and components Business configuration is eased by tools that simplify the implementation and configuration of pre-defined business content.

Implementation
Purpose
You use the Implementation IT process to add a new system, representing an SAP NetWeaver usage type (such as Enterprise Portal, Process Integration, or Business Intelligence), to your system landscape. For faster and easier installations, Software Life-Cycle Management also offers SAP NetWeaver Rapid Installer, an installation and configuration wizard that supports a simple and rapid initial setup of an SAP NetWeaver system landscape. SAP NetWeaver Rapid Installer is available for certain usage types and a reduced set of platforms.

Use of the Process


This process is part of the following IT scenarios: IT Scenario Software Life-Cycle Management Scenario Variant Implementation Support

Prerequisites
You know which scenarios you want to implement and you have an idea of your performance requirements (such as the expected number of users or data throughput).

Process Flow
1. Using the Master Guide, you get an idea of your required building blocks (such as systems with usage types or standalone engines) and plan the mapping of these building blocks to your system landscape. 2. You use the Master Guide, installation guides, and your hardware partner to plan the technical design of each system. 3. Your hardware partner helps you to allocate correctly sized hardware. 4. You use the installation guides and the installation tool SAPinst to prepare the installation hosts. 5. You use the installation guides and SAPinst or SAP NetWeaver Rapid Installer to install the systems with your required usage types. During the installation, the installation tool starts the initial configuration template for your usage type or types. 6. You perform post-installation activities. 7. If required, you install additional software components.

For example, you install add-ons using transaction SAINT. 8. If required, you start the template-based configuration in SAP NetWeaver Administrator. Here, you can choose a template to configure a usage type. 9. If required, you adapt the technical configuration to your needs. 10. You use SAP Solution Manager to customize your system.

Result
You have implemented a landscape that runs your required scenarios.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 3 of 7

Implementation and Configuration of Business Content


Purpose
The Implementation and Configuration of Business Content IT process provides scenario-based implementation support for predefined business content such as Enterprise Portal (EP) and Business Intelligence (BI) content. Installed business content is registered in the System Landscape Directory of SAP NetWeaver. Based on this information, task lists are generated for SAP Solution Manager to guide the configuration and activation of all required content objects.

If you use only the ABAP components of an SAPNetWeaver stack, you should use the standard process to implement, configure, and activate BI content. For more information, see the documentation on Business Content.

Use of the Process


This process is part of the following IT scenarios: IT Scenario Software Life-Cycle Management Scenario Variant Implementation Support

Prerequisites
You have installed SAP Solution Manager, a business application (such as mySAP ERP), and systems with usage types BI and/or EP.

Process Flow
1. You download and update SAP Solution Manager content. 2. In SAP Solution Manager, you select your business scenario. 3. In SAP Solution Manager, you adapt your business scenario. 4. In the software lifecycle manager (part of usage type AS Java), you check your IT landscape for required products. 5. In the software lifecycle manager, you check your IT landscape for required content software components. 6. In the Administrator Workbench (part of usage type BI) or Portal Content Studio (part of usage type EP), you install any missing business content shipment units. 7. In SAP Solution Manager, you generate a configuration task list. 8. In the Administrator Workbench or Portal Content Studio, you configure content objects. 9. In the Administrator Workbench or Portal Content Studio, you activate selected content objects. 10. You test and transport your changes.

Result
Your business process is ready to run.

Copy and Migration


Purpose
You use the Copy and Migration IT process to create copies of existing systems in a flexible system copy procedure. If you want to move an existing system to a new platform (that is, a new operating system or database), you can use the migration functions provided by this IT process.

Use of the Process


This process is part of the following IT scenarios: IT Scenario Software Life-Cycle Management Scenario Variant Implementation Support

Prerequisites
You have a system that you want to copy or migrate.

Process Flow
1. You use the document System Copy for SAP Systems Based on SAP NetWeaver <Release> and SAP Notes to plan your system copy. 2. If you want to migrate your system and need to make major hardware changes, you consult your hardware partner. 3. If you want to migrate an SAP NetWeaver system with usage type AS ABAP, you apply for a migration key on SAP Service Marketplace. 4. You use the system copy guide to order the required CDs/DVDs for your source system and your target system on SAP Service Marketplace. 5. You use the document System Copy for SAP Systems Based on SAP NetWeaver <Release> to help you perform a test run of the system copy.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 4 of 7

6. You use the document System Copy for SAP Systems Based on SAP NetWeaver <Release> to help you prepare your source system and your target system. 7. You use the document System Copy for SAP Systems Based on SAP NetWeaver <Release> and our tools to help you export the source database. 8. You use the document System Copy for SAP Systems Based on SAP NetWeaver <Release> and our tools to help you set up your target system with the database load from the source system. 9. You use the document System Copy for SAP Systems Based on SAP NetWeaver <Release> to help you perform follow-up actions in the source and the target system.

Result
You have created a copy of your system. If you have migrated your system, this copy will run on a different platform from the source system.

Software Change Management


Purpose
You use the Software Change Management IT process to manage the consistent and synchronized flow of object changes between different software stages, such as development, consolidation, and production in a distributed system environment. To enable this, SAP NetWeaver Development Infrastructure helps you to set up a distributed landscape for your custom development project.

Use of the Process


This process is part of the following IT scenarios: IT Scenario Software Life-Cycle Management Scenario Variant Implementation Support

Prerequisites
You have installed a system with usage type Development Infrastructure (DI).

Process Flow
1. Your system administrator designs your software architecture, for example with Microsoft Visio. 2. In the System Landscape Directory of SAP NetWeaver (part of usage type AS Java), your system administrator defines your software components. 3. In Change Management Service (CMS) of DI, your system administrator creates one or more development tracks. 4. In CMS, your system administrator defines software layers by connecting development tracks. 5. In the authoring environment of DI, your developers perform the following actions: They create a project and define development components and usage dependencies. They create new development objects and change them, if necessary. They check out existing development objects and change them, if necessary. They check in any changed development objects. They perform a central build (activation) and deployment. They release the changes. 6. In CMS, your system administrator or quality manager transports the changes. 7. Your quality manager tests and validates the changes centrally. 8. In CMS, your system administrator or quality manager assembles the changed software components. 9. Your quality manager approves the package. 10. In CMS, your system administrator or quality manager propagates the changed software components to the next track or to delivery.

Result
Your Development Infrastructure is configured so that it provides the infrastructure for your development work, and you have handled the production of one software component release.

Software Maintenance
To keep your system landscape up-to-date and running smoothly, you need to apply updates regularly. Sometimes, the need for new functionality makes it necessary to upgrade complete scenarios realized in your system landscape to a new release. Due to the complexity of todays landscapes and the interdependencies between single software components, tool support for landscape-relevant patch and upgrade tasks is a must and provided by the Software Maintenance IT scenario variant.

Required Usage Types of SAP NetWeaver


For this IT scenario variant, no actual usage type is required. This IT scenario variant provides functionality for the maintenance of systems with any usage type,

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 5 of 7

or for the upgrade of existing systems to systems with any usage type.

IT Processes of the Scenario Variant


This scenario variant comprises the following IT processes: Process Maintenance Release Upgrade What You Need to Know Keeps your installed systems up and running and solves application problems by importing the latest Support Packages and corrections Upgrades the relevant SAP systems to update your scenario to a new release

Maintenance
Purpose
The Maintenance IT process enables you to import Support Packages and SAP Note corrections into your system landscape.

Use of the Process


This process is part of the following IT scenarios: IT Scenario Software Life-Cycle Management Scenario Variant Software Maintenance

Prerequisites
You have installed your system landscape.

Process Flow

You implement Support Packages with the information from the document Support Package Stack Guide. You implement SAP Notes using the Note Assistant (part of usage type AS ABAP). You can access the SAP Note System from SAP Support Portal. For more information, see the Note Assistant online documentation. 1. You plan and schedule changes to your system landscape. 2. You download the required Support Packages / patches from SAP Service Marketplace using Maintenance Optimizer of SAP Solution Manager and download the corrections contained in SAP Notes from SAP Support Portal. 3. If you are implementing SAP Notes, you use Note Assistant to check whether an SAP Note is applicable (that is, you check the validity, impact, and the possible side-effects). 4. You prepare the implementation as described in the relevant documentation.

For example, you can test the implementation of the Support Package / patch or SAP Note correction in a test system and perform any prerequisite actions. 5. You implement the Support Package / patch or the SAP Note correction. 6. If you are implementing SAP Notes, you perform any manual actions required after the SAP Note installation. 7. You use defined test cases to test and validate your updated system.

Result
Your system landscape is updated.

Release Upgrade
Purpose
The Release Upgrade IT scenario offers a scenario-based upgrade of both ABAP and Java components. A comprehensive guideline for the upgrade is included in the Upgrade Roadmap of SAP Solution Manager; this complements the upgrade with test and e-learning capabilities.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 6 of 7

Use of the Process


This process is part of the following IT scenarios: IT Scenario Software Life-Cycle Management Scenario Variant Software Maintenance

Prerequisites
You have a system landscape that you want to upgrade.

Process Flow
1. You use the Upgrade Master Guide to plan the system landscape of your target release. 2. If required, you upgrade the operating system and database releases with the appropriate tools. 3. With the help of the Upgrade Master Guide, Upgrade Guides, and SAP Notes you ensure that the upgrade preconditions are met for all system landscape components that need to be upgraded or installed. If required, this includes an upgrade of the operating system and database releases with the appropriate tools. 4. You perform the following steps for each of the landscape components mentioned in the Upgrade Master Guide: a. You perform the technical upgrade or the new installation. b. You use the information in the Upgrade Master Guide, Upgrade or Installation Guide, SAP Notes, and various system transactions to perform any postupgrade or post-installation actions required by the applications.

Result
You have upgraded your system landscape to the required target release.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 7 of 7