55
Active Global Support Juni, 2012 Upgrade to SAP Solution Manager 7.1

Upgrade to SAP Solution Manager 7.1

Embed Size (px)

Citation preview

Page 1: Upgrade to SAP Solution Manager 7.1

Active Global Support

Juni, 2012

Upgrade to SAP Solution Manager 7.1

Page 2: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 2

Agenda

Upgrade versus New Installation

• Performing the Upgrade (or New Installation)

• Upgrade Impact to Existing Scenarios

Technical Upgrade of SAP Solution Manager

• Upgrade Roadmap

• Landscape

• Performing Post-Upgrade Configuration

Scenario Upgrade

• RCA

• Monitoring

• Solution Documentation

• Test Management

• Incident Management and Change Management

Lessons learned and additional information

Page 3: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 3

Upgrade versus new Installation

You should definitely upgrade if

• you are currently using SAP Solution Manager

• systems are connected and data transmitted (e.g. SAP

EarlyWatch Alert)

• business processes are documented inside SAP Solution

Manager

• any data exists which you want to preserve

You may want to consider a new installation if

• your SAP Solution Manager system is outdated and not

really used

• Main purpose is to generate keys and download Support

Packages

• none of the information contained needs to be preserved

• it is a sandbox installations used for evaluation purposes

It is generally not possible to

transfer data from any release

prior 7.01 to SAP Solution

Manager 7.1 (e.g via

transport). From 7.01 to 7.1 it

is partially possible to transfer

data (please refer to SMP).

The upgrade is the best

choice for existing SAP

Solution Manager systems.

Page 4: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 4

Why SAP recommends to adopt SAP Solution Manager 7.1

2011 2012 2013 2014 2015

Q 1 Q 2 Q 3 Q 4 Q 1 Q 2 Q 3 Q 4 Q 1 Q 2 Q 3 Q 4 Q 1 Q 2 Q 3 Q 4 Q 1 Q 2 Q 3 Q 4

Mainstream Maintenance SAP Solution Manager 7.0 EHP 1

Mainstream Maintenance Ramp Up SAP Solution Manager 7.1

Upgrade

Invest now in SAP Solution Manager 7.1 because:

You can adopt the SAP Solution Manager 7.1 innovations at your own pace and priorities, e.g. Management Dashboards, Business Process

Blueprinting, Solution Documentation, Test Automation, Central Application Monitoring.

You can do a technical upgrade to SAP Solution Manager 7.1 without additional hardware, little user impact and not significantly more effort

compared to applying a support package on SAP Solution Manager 7.0 . EXCEPTION: Charm and Service Desk!

Maintenance of SAP Solution Manager 7.0 ends by end of 2013. No functional enhancements on SAP Solution Manager 7.0

Page 5: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 5

SAP Solution Manager 7.1 What Scenarios are impacted?

Scenarios Motivations Impact

Root Cause Analysis Impacts for Business Objects managed systems, PI managed systems Medium

End User Experience Monitoring New extractors for reporting Medium

Change Request Management /

Service Desk

CRM implementation migration High

Central User Administration SAP Note 1300104: Manage non recommended changes in instance

profile parameters

Low

IT Reporting SAP Note 1178655: Compression for InfoCubes Low

SLD LMDB implications Medium

Page 6: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 6

Leverage incremental improvements by selective activation

Area Examples Effort

Solution Documentation Reverse Analysis Content Upload content

Upload Interface None

Template Management Compare and adjust None

Solution Implementation BPMN Business Blueprint Configuration (small effort)

Test Management Integration of third party test tools None

Test Scope Optimization None

System Monitoring CCMS based monitoring replaced by new

monitoring infrastructure

Optional

Maintenance Management System Recommendations None

Business Process Operations Analytics and dashboards Configuration (small effort)

Page 7: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 7

Leverage incremental improvements by selective activation

Area Examples Effort

Upgrade Management Upgrade dependency analyzer None

Custom Code Management Get full transparency of all custom code

objects across systems

Implementation project

recommended

Application Operations Technical Monitoring and Alerting Implementation project

recommended

Downtime Management Workload Management None

IT Calendar None

Page 8: Upgrade to SAP Solution Manager 7.1

Upgrade Roadmap

Page 9: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 9

Preparing for Installation/Upgrade

Installation How Upgrade

Plan implementation of missing software components, agent and

possible restarts for managed systems. Master Guide

Plan implementation of missing software components, agent and

possible restarts for managed systems.

Plan user & port availability. Security Guide Plan user & port availability, (More information see Slide 13)

Check hardware prerequisites for SAP Solution Manager 7.1 Quick Seizer/ Sizing Guide Check hardware prerequisites for SAP Solution Manager 7.1

Obtain the Installation Software DVD‟s or

service.sap.com/swdc Obtain the Upgrade Software

Install SAP Solution Manager including support package update Inst. / Upgr. Guides Upgrade to SAP Solution Manager 7.1

Update SLD Content to latest available version

Connect managed systems to SLD SWDC / SDN

Update SLD Content to latest available version

Check the connection of managed systems to SLD

Install Diagnostics agent and SAP HostAgent on all managed

systems

Inst. Guides +

SOLMAN_SETUP

Install Diagnostics Agent and SAP HostAgent on all managed

systems

Implement missing/latest software requirement on managed

systems (ST-A/PI & ST-PI) service.sap.com/swdc

Implement missing/latest software requirement on managed

systems (ST-A/PI & ST-PI), Note 1483508

Install Introscope Enterprise Manager

Install Diagnostics Agent and Host Agent on all Enterprise

Manager hosts

service.sap.com/swdc +

Guides

Upgrade Introscope Enterprise Manager

Install Diagnostics Agent and Host Agent on all Enterprise

Manager hosts

Perform configuration of SAP Solution Manager and managed

systems.

SOLMAN_SETUP

+ add. guides

Perform configuration of SAP Solution Manager and managed

systems.

Page 10: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 10

SAP Solution Manager 7.1 Installation/upgrade roadmap

Implement Pre-requisites Implement missing software on

managed systems

Install Solution

Manager

Upgrade Solution

Manager; Including

Wily IS EM

Download software from SMP

Perform Delta

Configuration with

Solman_setup

Repeat managed

Systems

configuration only

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent on

all managed hosts

Install Diagnostics

Agent for DB host

and Wily Hosts

Perform Backup

Run Self-Diagnosis

Perform Basic

Configuration with

Solman_Setup

Install Wily IS EM

Install Diagnostics

Agent for all

managed Hosts

Perform managed

Systems

configuration with

SolMan_Setup

Install Diagnostics

Agent on Wily Hosts

Restart Java

Managed systems

Page 11: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 11

SAP Solution Manager 7.1 Times Spent doing Technical Upgrade – experience so far

Pre Processing

10 to 20 hours

Import

5 to 10 hours

Post Processing

8 to 20 hours

Run Time Run Time Downtime

Basic Configuration

10 to 14 hours

1 to 2 hours 5 to 8 hours 3 to 4 hours

Run Time Downtime Run Time

Pre Processing Import Basic Configuration

Upgrade to 7.1

Support Package

implementation

Technical downtime is similar for Support Package Stack and Upgrade

Dependent on the scenario

some scenarios can be used

directly after the basic

configuration.

Page 12: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 12

New planning tool For installations and upgrades

The objective of the planner is to provide a support

for upgrade/installation projects planning.

The tool enables you to:

• Assess your current situation by describing your Solution

Manager landscape and your existing scenarios.

• Decide which of those scenario are critical -> requires

minimal downtime.

• List test cases already created for existing scenarios

• Define the scope of the new installation/upgrade.

• Propose a high-level sequence of tasks that have to be

performed during the project

• Validate the technical infrastructure of your environment

• Identify risks factors linked to your technical and functional

environment.

The outcome of the tool should be used as an input for your project planning and should be

validated by the project team.

Click on picture to download the planner!

Page 13: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 13

Hardware pre-requisites Sizing

SAP is providing a standard sizing with the help of the quick sizing tool. To get a more detailed view on the

hardware pre-requisites a second toolset, SAP Solution Manager Sizing Toolkit, provides information on

infrastructure requirements including SAPs, Memory, Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems (http://service.sap.com/sizing-solman).

Page 14: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 14

Hardware considerations

No hardware investments should be required if you

• are on SAP Solution Manager 7.0 EHP 1 and plan no

changes to the scope

• are on SAP Solution Manager 7.0 EHP 1 and plan to add

only a small number of managed systems or users

The hardware should be reviewed if you

• want to leverage areas of SAP Solution Manager currently

not in use

• plan to add a larger number of users (e.g. to manage a

complete IT Service Desk)

• want to add a large number of managed systems

• you are currently on a release smaller than SAP Solution

Manager 7.0 EHP 1

Page 15: Upgrade to SAP Solution Manager 7.1

Landscape

Page 16: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 16

Managed System Physical Host

VHost

SAP Solution Manager Host

SLD Host SAP Solution Manager Host

Wily IS EM 9.X

Solution Manager 7.01 <> 7.1 Infrastructure

SAP Solution Manager 7.1

SMSY

SLD

Local SLD

Wily Introscope

Enterprise

Manager

Managed

System Java

Diagnostics

Agent

IS BC

Agent

SAP Host Agent

Diagnostics

Agent

Diagnostics

Agent

LMDB

Install an

Diagnostics

Agent on each

Wily Host

Central or Local

SLD must be

connected to

LMDB

SMSY must be

linked to LMDB

DB Physical Host

Virtual Host

Diagnostics Agent SAP Host Agent

Install a

Diagnostics

Agent on each

DB Host

SAP Host Agent

SAP Host Agent

Managed

System

ABAP

CCMS

SAP Host Agent

(minimum version

mentioned in note

1365123) must be

installed on ALL Hosts

SAP Host Agent

configuration needed for

Diagnostics Agents

communication

Diagnostics

Agent

Diagnostics

Agent

SAP Host Agent

SAP Host Agent Diagnostics Agent

Page 17: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 17

SLD Impacts

Refer to the LMDB presentation for complete description.

3 cases can occur:

• Local SLD in SAP Solution Manager: it could be removed and replaced by LMDB

• Central SLD in SAP Solution Manager: No impact.

• Runtime SLD in SAP Solution Manager: NOT Recommended in 7.X (only valid in ABAP only

Landscape)

Page 18: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 18

SAP Solution Manager 7.1 SLD & LMDB

Solution Manager 7.1

Local SLD

(use optional)

Central SLD

SMSY LMDB

Migration

LMDB implications in 7.1:

• Flexible landscape database based on the CIM

data model

• No local SLD required anymore, but supported

• Full synchronization between Landscape SLD‟s

and LMDB

• Automatic data migration from SMSY to LMDB in

the 7.1 upgrade where needed for the respective

Solution Manager scenarios

Landscape Management Database (LMDB)

Setup Guide

Page 19: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 19

SAP Solution Manager 7.1 Outside Discovery & LMDB

Host B

Host A

DB

IIS

Virt Host A1

Virt Host B1

SolMan Host

SLD

OS Info

OS Info

SAP Host Agent

Diagnostics

Agent

Diagnostics

Agent

SAP Host Agent

SAP Solution Manager 7.1

LMDB

• Enhances available landscape information in LMDB in SAP Solution

Manager

• Support also products where no SLD data supplier is available, e.g:

• Databases & Operating Systems

• Microsoft components

• Is aware of virtualization through information from SAP Host Agent

• Works completely automatic with Diagnostics Agents

Troubleshooting Guide

Page 20: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 20

Landscape scenarios Where to install an agent?

PhyHost2 PhyHost3

LHost1 LHost2 LHost3

PhyHost1

C1 C2 C3 C4 C5 C6

cluster C7 C8

Diagnostics Agent

Managed Component SAP Solution Manager

SAP HostAgent

SAP Host Agent

Diagnostics

Agent 1

SAP Host Agent

Diagnostics

Agent 2

Diagnostics

Agent 4

Diagnostics

Agent 3

SAP Host

Agent

Diagnostics

Agent 5

H!

D1 • 1 diagnostics agent per logical „host‟

represented by a name: physical or

virtual

• 1 SAP HostAgent per physical host

• 1 agent per host supports several

managed systems running on the same

named host

Page 21: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 21

Differences of the available Diagnostics Agent Versions

7.0 / 7.01 SR1 7.11 7.20 / 7.02

7.30

Integrated in NW DVD’s Yes Yes Yes Yes

Standalone Version available No Yes Yes Yes

JVM JDK 1.4.2 SAPJVM SAPJVM SAPJVM

Default System ID SMD DAA DAA DAA

Support for SLD & direct connection

(simultaneously) No No Yes Yes

SSL Support & Certificate Handling Yes No Yes Yes

SAProuter Support No Yes Yes Yes

SAP Host Agent needed

Yes (for MAI manual

install needed)

No (RCA uses

saposcal)

Yes (manual

install) Yes (auto install)

Yes (auto. installed /

updated)

Recommended

for new installations

Dia

gn

ostics A

ge

nt N

od

e C

on

ce

pt

with

So

lMa

n 7

.1 S

P0

5

+

Page 22: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 22

Outlook: Diagnostics Agent on-the-fly (with SP05)

The following configuration is considered for a system:

• 1 Physical host

• 1 .. N Virtual Hosts running on the physical host

Definition

Agent Nodes are SMD agents running under the same SID and instance number. They are isolated into different processes controlled by the same shared instance.

The Diagnostics Agents Node installation consists of the following:

• 1 dedicated SID

• 1 dedicated Instance Number

• 1 to N Agent “Nodes”

• 1 Agent node represents the physical host

• 1 Agent node will represent exactly one Virtual Host

Page 23: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 23

Current & Additional approach

Physical Host

Virtual Host A

Virtual Host B

Virtual Host C

Jstart

Virtual Host A

sa

psta

rtsrv

Agent SID/SMDA98

Jstart

Virtual Host B

Jstart

Virtual Host C

Physical Host SAPHOSTAGENT

Jstart

Virtual Host A

sa

psta

rtse

rv Agent SID/SMDA98

Virtual Host A

Jstart

Virtual Host B

sa

psta

rtse

rv Agent SID/SMDA97

Virtual Host B

Jstart

Virtual Host C

sa

psta

rtse

rv Agent SID/SMDA96

Virtual Host C

SAPHOSTAGENT

Page 24: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 24

Managed Systems

DAA 98 IS EM Host

CA Wily Introscope - Architectural Overview

Introscope

Enterprise

Manager

Persistent store

JVM

J2EE Application

.Net CLR

.Net Application

Introscope WebView

Diagnostics Agent

Port

6001

Port

8081

For SolMan 7.1 Diagnostics agents have to be

installed on Wily IS EM hosts

Introscope workstation

IS BC

Agent

IS Host Adapter

IS BC

Agent

Port

6001

Page 25: Upgrade to SAP Solution Manager 7.1

Performing Post-Upgrade Configuration

Page 26: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 26

SAP Solution Manager Configuration Automatic Basic Configuration

• Accessible via transaction code SOLMAN_SETUP

• Allows an easy, fast and step-by-step configuration of SAP

Solution Manager

• Single, easy to use wizard for system preparation & basic

configuration

• Highly automated configuration

• Integrated documentation for each step

• Easy access to open tasks and postponed activities

• Configuration of all managed systems from one central

entry point

• Configuration of other scenarios like Technical Monitoring,

Data Volume Management,…

Supports Upgrades and new

Installations ! SolMan_Setup Wiki in SDN

Page 27: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 27

Automatic Basic Configuration Configuration Roadmap

Prepares the system for the configuration

Needs to be performed fully after a new installation

After patches and upgrades needed to update dialog and system users, and assign the

appropriate default roles and to implement the appropriate Central Correction Note (CCN)

System

Preparation

Configures the basic scenarios in SAP Solution Manager (Service Delivery, Issue Management,

Early Watch Alerts, Maintenance Optimizer, Root Cause Analysis, …)

Needs to be performed after new installations and after support packages to perform delta

configuration

Overview screen tells you which configuration needs update

Basic

Configuration

Connection and configuration of managed systems

Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP

Solution Manager

Creation of Logical Components for managed systems

Managed

Systems

Configuration

Page 28: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 28

SAP Solution Manager Configuration Overview Screen

The overview shows the status of the SAP

Solution Manager configuration

Which steps of the configuration have been

performed when and by whom

Which steps of the configuration needs an

update

Check „Update Needed

Flag“ to see which activities

need to be reperformed

after a SP update

New

Scenarios

with SP05

Page 29: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 29

SAP Solution Manager Configuration Managed Systems Configuration: New steps in 7.1

Support for all technical system

types (incl. selected 3rd party like

Websphere)

Technical Scenarios (multiple

systems like double stacks)

And standalone databases

Detailed Status overview:

- RFC working

- Configuration status

- System well defined

- ST-API & PI checks

Integration of LMDB

Technical System

maintenance

ABAP/JAVA double stack

scenario are automatically

created

Configure RFC Connection via Managed

System Configuration

Page 30: Upgrade to SAP Solution Manager 7.1

RCA

Page 31: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 31

RCA Impacts

Migration of Diagnostics Relevant Flag

• After the upgrade, the manually maintained flag needs to be migrated from SMSY to LMDB after the first successful

SLD-LMDB synchronization

• For managed systems which are registered in SLD This is the only post upgrade step

• For system which have been registered manually before the upgrade

• First the system itself needs to be migrated from SMSY to LMDB

• Then the Diagnostics relevant flag needs to be migrated

Because of changes in the system modeling, special considerations need to be taken into account for

• For BOE 3.1 systems: Minimum version SolMan 7.1 SP02

• The technical system Tomcat was modelled as a system of system type Unspecific with SolMan 7.01

• This is replaced by technical system of type Apache Tomcat (ATC)

• Therefore you have to mirgrate the BOE systems

• And the Tomcat systems have to be created newly in LMDB either manually or automatically with a SLD data supplier

automatically with SLD Data Supplier

• For PI systems

• repeat managed systems setup

1483508 - Solution Manager 7.1:

Root Cause Analysis pre-requisites

Page 32: Upgrade to SAP Solution Manager 7.1

Monitoring

Page 33: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 33

System Monitoring Impacts

The upgrade to 7.1 has no impact for CCMS based system monitoring

It will work out of the box after the upgrade

There is no migration guideline available from System Monitoring to Technical Monitoring.

Technical Monitoring is based on predefined templates that can be used out of the

box.

CCMS Monitoring is based on local settings. Unable to decide automatically on a

value which should be taken over.

Default templates contains SAP Best Practices monitoring metrics and events. So the

approach for customer implementation is:

Implement and test default templates for a subset of Technical Systems.

Decide to adapt thresholds and metrics.

Rollout adjusted templates for the complete production landscape

Page 34: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 34

Technical Monitoring and Alerting in Application Operations

New Infrastructure for Technical Monitoring and

Alerting

Introduced with SAP Solution Manager 7.1

Based on E2E Diagnostics architecture

SAP‟s new standard for central Monitoring and Alerting

New work center “Technical Monitoring” has been

introduced which contains the new applications

One open Infrastructure

• SAP„s new standard for alerting in Java

• Create alerts based on metrics from all SAP

technologies

More Information for Monitoring

Application Operations Wiki in SDN

Page 35: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 35

EEM Impacts

There is no impacts for Robots, scripts and runtime monitoring. It will work out

of the box.

The EEM reporting functionalities must be reactivated via SOLMAN_SETUP.

• Creation of Technical Scenarios containing the list of managed systems

monitored by EEM scripts.

• Activation of the corresponding extractors.

Page 36: Upgrade to SAP Solution Manager 7.1

Solution Documentation

Page 37: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 37

No Impact but additional functions!

Solution Documentation Impact

Advanced Scenario Modeling based on Business Process

Modeling Notation (BPMN) standards

No change access to Solution Documentation and

Projects while the Technical Upgrade process

Compare & Adjust

RBPD

Business Transaction Type

Page 38: Upgrade to SAP Solution Manager 7.1

Test Management

Page 39: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 39

Test Option 1

Test Option 2

Test Option 3

SAP Quality Center by HP

Test Workbench

Work Center TM

SAP Solution Manager SAP Solution Manager

Test Automation Framework integrated ISV test automation tools

Quality Manager, ReqPro, RFT, ...

Business Blueprint

BPCA SAP TAO

Business Blueprint

Test Planning

Test System Setup Test Execution

Change

Deployment

Change Impact Analysis SAP Solution

Update

New SAP

Solution

new

new

advanced advanced

advanced

SAP Test Management Options for SAP Customers based on SAP Solution Manager 7.1

Test Scope Identification Type of Change

Changed*

Changed*

* Changed based on new Transaction Types in Incident Management

More Information for

Test Management

Page 40: Upgrade to SAP Solution Manager 7.1

Change Management and ITSM

Page 41: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 41

Standard Process After the Upgrade For Incident and Change Request Management

SOLMAN_SETUP has to be completed

Copy new transaction types

to customer namespace

Re-assign text-, partner- and date-

profile

Copy new status- and action-profile

to customer namespace

Adapt status- and action-profile

customer specific

Define copy control rules for new transaction

types

Perform Web UI configuration

Customize new functions in

ITSM / ChaRM

Adapt user authorizations

and roles

ITSM and ChaRM available in SolMan 7.1

Customers beginning to use IT Service Management and ChaRM after the upgrade have to go through the standard operation

procedure recommended by SAP.

Customers who already have used the processes in 7.0 can reuse parts of existing configuration.

Page 42: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 42

Impact

Impact on incident and change request management in SAP Solution Manager 7.1

UIs are upgraded from SAP GUI to SAP CRM Web UI

New transaction types in 7.1 replace the 7.0 transaction types

New functions in 7.1 are only available in the SAP CRM Web UI with new transaction types

There is no automatic migration from 7.0 transaction types, but large parts of 7.0 customizing can be reused

To minimize the impact of these changes for customer projects, SAP offers a transition phase

• You can process existing tickets based on 7.0 transaction types within the Work Center UI or SAP GUI, until they

are closed

You create new tickets with the 7.1 object types and process them with the SAP CRM Web UI

The SAP Solution Manager Work Centers are still available for all other ALM processes.

New

Transaction

Type

Old

Transaction

Types …process old tickets until they are closed…

After upgrade to SAP Solution Manager 7.1

…ticket processing…

transition phase

Old

Transaction

Type

Old

Transaction

Type

New

Transaction

Types

New

Transaction

Type

<< create >>

<< create >>

All tickets based on

old transaction types

are closed

This presentation and SAP„s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided

without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

Page 43: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 43

Incident Management Impact

During the transition phase, you should consider the following:

• All new incidents are created with the new transaction types and processed within the SAP WebClient. You can

use PFCG roles to restrict the authorization for message creation. Please note that many authorization objects

have been changed due to the new object types.

• Existing support messages (SLFN) should be processed in the Work Center or SAP GUI, until they are

completed.

• Only in the Work Center, you are able to search and display the new and the former incident documents.

• You can use:

• the Work Center as a central access point for creating and searching incidents and problems, whereas the processing will

be in the SAP WebClient

• only the SAP WebClient to start all SAP ITSM functions.

Page 44: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 44

ITSM implementation procedure Incident & Problem and Change Request Management

Page 45: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 45

Upgrade of Existing ChaRM Process Current Effort Estimations (1)

Action Estimated Effort

Copy new transaction types to customer namespace 1 hour

Re-assign text-, partner- and date- profile 1 hour

Copy new status- and action-profile to cust. namespace 2 hour

Adapt status- and action-profile customer specific 1 - 2 days

Define copy control rules for new transaction types 1 hour

Perform Web UI configuration 4 hours

Customize new functions in AIM / ChaRM 2 hours

Adapt user authorizations and roles Depending on organization

Custom Developments (BADIs, Additional fields, etc...) Depending on customizing level and complexity

Total: ~ 3 Days + X

A Transition project has to be executed which will depend on the: • number of customized workflows and number of implemented BADIs

Page 46: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 46

Installation/Upgrade Guide for ITSM and ChARM

Installation / Upgrade How

ChaRM Configuration Upgrade Guide Ver1 Conf. + Upgrade Guide

IT Service Management SOLMAN_SETUP + Inst. Guides

Business and Authorization Roles (ITSM) Guide

Configuration Business Rule Framework Plus (ITSM) Guide

Configuration Multilevel Categorization (ITSM) Guide

Full-Text Search with TREX (ITSM) Guide

Links http://service.sap.com/changecontrol

http://help.sap.com/saphelp_sm71_sp01/helpdata/en/4c/3acb82b50843b4e10000000a42189e/frameset.htm

http://wiki.sdn.sap.com/wiki/display/SM/Change+Request+Management

http://wiki.sdn.sap.com/wiki/display/SMAUTH/Home

Page 47: Upgrade to SAP Solution Manager 7.1

Lessons learned and more information

Page 49: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 49

Expert Guided Implementation

Service.sap.com -> SolutionManager -> Services -> Expert Guided Implementation

• Technical Upgrade to SAP Solution Manager 7.1

• Basic Configuration 7.1

• Technical Preparation

• Migration Charm 7.0 to 7.1

• Authorization Concept & Roles in SAP Solution Manager 7.1

• End-User Experience Monitoring Reporting Analytics

• System Monitoring and Reporting

Planning Calendar

Page 50: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 50

Lessons learned From the Customer Validation, Beta Projects & RampUp

Start Landscape Planning early

Prepare a tracking list of managed systems

Get the users and connections opened with the customer before the project starts

Check SLD quality and SW components of the managed systems

Import the latest SLD content in SLD before starting the configuration

Ensure Diagnostics Agents and SAP Host Agent availability before starting

Check profile parameters after installation / upgrade

On Oracle DB‟S Update the DB statistics

Page 51: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 51

Tracking, Tracking, Tracking,….

Before starting:

• Scope (What should be implemented? Which systems should be connected?)

• Existing Solution Manager installation (Keep? Install New? Upgrade?)

• Reconfirm Sizing (New Scenarios require new sizing…)

• Clear Landscape Picture (How are the systems build? High Availability? Where to install agents?)

• SLD Landscape (Central SLD in place? Content Version?)

• CA Wily Introscope (Existing? Update?)

• Per managed system

• Software Prerequisites fulfilled?

• Users & authorizations in place?

• Network ports opened?

• Agents installed & configured?

• Responsibilities?

More information in the

SolMan_Setup Wiki in SDN

Page 53: Upgrade to SAP Solution Manager 7.1

Thank You!

Contact information:

Page 54: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 54

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a

purchase decision. This presentation is not subject to your license agreement or any other agreement

with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to

develop or release any functionality mentioned in this presentation. This presentation and SAP's

strategy and possible future developments are subject to change and may be changed by SAP at any

time for any reason without notice. This document is provided without a warranty of any kind, either

express or implied, including but not limited to, the implied warranties of merchantability, fitness for a

particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly negligent.

Page 55: Upgrade to SAP Solution Manager 7.1

© 2011 SAP AG. All rights reserved. 55

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.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft

Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,

z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,

PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered

trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or

registered trademarks of Adobe Systems Incorporated in the United States and/or other

countries.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are

trademarks or registered trademarks of Citrix Systems, Inc.

© 2011 SAP AG. All rights reserved.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World

Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, 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.

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.

The information in this document is proprietary to SAP. No part of this document may be

reproduced, copied, or transmitted in any form or for any purpose without the express prior

written permission of SAP AG.