Server Upgrade Guide SAP BusinessObjects Strategy Management 7.5 to 10.

0 Series
Target Audience Technology Consultants System Administrators

PUBLIC Document version: 1.3 2011-11-07

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

Copyright 2011 SAP AG. 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. 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. 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. 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, 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. 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.
Disclaimer

Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.
Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

2/38

PUBLIC

2011-11-07

Typographic Conventions

Example
<Example>

Description

Example Example Example

Example

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2011-11-07

PUBLIC

3/38

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace http://service.sap.com/ instguides. The following table provides an overview on the most important document changes:
Version Date Description

1.0 1.1 1.2 1.3

2011-06-16 2011-09-08 2011-09-15 2011-11-07

First version no changes Added SAP Solution Manager requirement for SAP NetWeaver. Updated section about deploying the FCP and POASBC components. Changed client browser support from Internet Explorer 7.x and 8 series to just 8 series.

4/38

PUBLIC

2011-11-07

Table of Contents

Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 Chapter 2 Chapter 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 Chapter 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.3 4.4 4.5 4.6

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further Useful Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from 7.5 at a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 7 7 8 8 8 8

Quick Guide for 7.5 to 10.0 series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining the Strategy Management Downloads . . . . . . . . . . . . . . . . . . . . . . . Backing Up Application Server Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up Interactive Publisher Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recording Application Definitions That Are Not Upgraded . . . . . . . . . . . . . . Exporting Performance Management Scorecard Data . . . . . . . . . . . . . . . . . . . Stopping Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling SAP BusinessObjects Strategy Management . . . . . . . . . . . . . . . . . Undeploying the Software Component Archive . . . . . . . . . . . . . . . . . . . . . . . Cleaning Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing or Upgrading to SAP NetWeaver 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . Installing Application Server and Supporting Files . . . . . . . . . . . . . . . . . . . . . . Installing Application Server on a Microsoft Windows Server . . . . . . . . . . . . . Installing Application Server on a Linux/UNIX Server . . . . . . . . . . . . . . . . . . . Installing Application Server on a Microsoft Windows Client . . . . . . . . . . . . . Copying Backed Up Files to the New Installation Location . . . . . . . . . . . . . . . Deploying the FCP and POASBC Components . . . . . . . . . . . . . . . . . . . . . . . . Deploying the Software Component Archive . . . . . . . . . . . . . . . . . . . . . . . . . Importing Bootstrap Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 15 16 16 17 17 18 18 19 21 21 21 22 23 24 25 25 26 26

2011-11-07

PUBLIC

5/38

4.7 4.8 4.9 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 Chapter A A.1

Importing Performance Management Scorecard Data and Model Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Resetting Web Service Providers to Basic Authentication . . . . . . . . . . . . . . . . . 28 Restarting SAP NetWeaver and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagram Manager Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating User Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing the Excel Add-In Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Merging Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting Month Name Abbreviations to Non-English Text . . . . . . . . . . . . . . Copying Files From the \Procs Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redefining Strategy Management Objects That Were Not Upgraded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Respecifying Encrypted Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 31 32 32 32 33 33 33 34

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 List of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6/38

PUBLIC

2011-11-07

1 1.1

Introduction About this Document

1 Introduction

1.1 About this Document

Use this guide to learn how to upgrade to the latest version in the SAP BusinessObjects Strategy Management 10.0 series. This document contains the following sections: Planning Preparation Upgrade Process Follow-up Activities
NOTE

The central starting point for the technical implementation of your SAP solution is the Master Guide, which you can find on SAP Service Marketplace at http://service.sap.com/ instguidesEPM-STM.
NOTE

You can find the most current information about the technical upgrade of the strategy management application and the latest upgrade, installation, and configuration guides on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. We strongly recommend that you use the documents available here. The guides are regularly updated.
Constraints

To learn how to upgrade the Excel Add-In client program, refer to the Client Installation Guide for SAP BusinessObjects Strategy Management Excel Add-In on SAP Service Marketplace at http://service.sap.com/ instguidesEPM-STM.

1.2 Naming Conventions

In this documentation, the following naming conventions apply:
Variables
<nw_server>:<port>

Description

Server name or IP address and port where SAP NetWeaver is installed and strategy management application components are deployed

2011-11-07

PUBLIC

7/38

1 1.3

Introduction Related Information

1.3 Related Information

Planning Information

For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace:
Content Location on SAP Service Marketplace
http://service.sap.com/instguidesEPM-STM http://service.sap.com/securityguide

Latest versions of installation and upgrade guides Network security System requirements and supported platforms

Product Availability Matrix (PAM) at http:// service.sap.com/pam. Then search on strategy management.

1.4 Further Useful Links

The following table lists further useful links on SAP Service Marketplace:
Content Location on SAP Service Marketplace
http://service.sap.com/messages http://service.sap.com/notes http://service.sap.com/swdc

Information about creating error messages SAP Notes search SAP Software Distribution Center (software download and ordering of software) SAP Online Knowledge Products (OKPs) role-specific Learning Maps

http://service.sap.com/rkt-epm

1.5 SAP Notes for the Upgrade

Make sure you read the Release Notes to learn about the new features in this release located at:
http://service.sap.com/releasenotes

Choose SAP Solutions SAP BusinessObjects Strategy Management .

SAP Note Number Title Description

1564692

Central Note for SAP BusinessObjects Strategy Management 10.0 Restrictions Note for SAP BusinessObjects Strategy Management 10.0

1573951

Describes how to get started with downloading SAP BusinessObjects Strategy Management 10.0 Describes the limitations of the release

1.6 Upgrading from 7.5 at a Glance

This table shows system changes for SAP BusinessObjects Strategy Management 7.5 to 10.0. These changes affect the upgrade process. If you are upgrading from one SAP BusinessObjects Strategy Management 10.0 version to another, you can skip this section.

8/38

PUBLIC

2011-11-07

1 1.6

Introduction Upgrading from 7.5 at a Glance

For information about all new features, see the release notes at http://service.sap.com/ releasenotes.
Component Changes Action / Further Information

Support of user management systems

The application supported the following user management systems in 7.5: SAP NetWeaver UME, SAP BusinessObjects Enterprise XI or SAP BusinessObjects User Management System. Now the application supports only SAP NetWeaver UME. Strategy The Manage Application Groups management users, section of the administration permissions, and application is removed. Users are accessibility now defined in roles in SAP NetWeaver Administrator rather than application groups in the administration application. Application groups are converted to roles in SAP NetWeaver UME during the upgrade. Upgraded roles have the prefix SSM_. For example the sample Executive application group is created as the SSM_Executiverole. Roles have actions to define the user permissions and accessibility. Administration of With many changes to user users administration, there is no longer a need to synchronize users. All functionality related to synchronizing users is removed from the application. Server System SAP NetWeaver 7.2 system Requirements requirements changed to SAP NetWeaver 7.3

The application does not support SAP BusinessObjects users and groups directly from SAP BusinessObjects. The system administrator must configure SAP BusinessObjects for Single Sign-On using SAML. For more information, see the Installation Guide for SAP BusinessObjects Strategy Management at http:// service.sap.com/instguidesEPM-STM. Then choose Adding Strategy Management Users to SAP NetWeaver UME. No action is required to upgrade application groups except those that have the Create/Edit Objectives permission. This permission is now obsolete and handled by the SSM_CreateScorecard action for a role. If an application group had this permission, you need to edit the role and make sure to add the SSM_CreateScorecard action to allow users to continue to create objectives and perspectives (as well as define all other aspects of a scorecard) For information about creating new roles, see the Installation Guide on SAP Service Marketplace at http:// service.sap.com/instguidesEPM-STM. Then choose Setting Up Users, Roles, and Application Properties.

No action is required.

User System Requirements

Users now need the following: Internet Explorer 8 series Adobe Air A program that can open a CSV file (to export views)

Upgrade your version of SAP NetWeaver to 7.3 Make sure strategy management users meet the new requirements. For more information, see SAP Library for SAP BusinessObjects Strategy Management on the Help Portal at http://help.sap.com/epm. Then choose Startup Requirements. If users do not have Internet Explorer 8 series, Adobe Air, Adobe Flash Player, or a CSV reader, they must install these programs.

2011-11-07

PUBLIC

9/38

1 1.6

Introduction Upgrading from 7.5 at a Glance Changes Action / Further Information

Component

Sun JRE 1.6 (client) changed from 1.5 or higher Users no longer need Microsoft Word or Excel when exporting views. Model connection You must re-enter passwords for passwords and any all model connections and all password that are encrypted passwords in encrypted in lsserver.ini and lsdal.ini. lsserver.ini and
lsdal.ini

Strategy management users no longer need Sun JRE. Only scorecard administrators need Sun JRE, and they must upgrade to version 1.6.

For information, see Respecifying Encrypted Passwords [page 34].

Interactive Publisher

You can only run Interactive Publisher using the Java version, called JPIP. You cannot run Interactive Publisher using the original C++ (CPIP) version.

Diagram Manager

Interactive Publisher Installation

FCP and POASBC component deployment

Transporter directory

The Diagram Manager is no longer a client installation. It is now included as part of the strategy management SCA.and is deployed on the SAP NetWeaver server. When uploading custom images for the goal diagram, the image cannot be a .BMP file. Due to usage of JPIP as the only version of Interactive Publisher, there is no longer a need for a separate Interactive Publisher installation. There are supporting files that must be installed on a Windows machine. You must now deploy FCP and After you uninstall the 7.5 version, deploy the FCP and POASBC component in 10.0. POASBC SCAs. You deploy these SCAs before you deploy the strategy management SCAs. For more information, see the Installation Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace. Previously, you could import When importing your exported data, you must put the performance management data ZIP file to be imported into the \server\temp\SSM that was exported by browsing \import directory on the SAP NetWeaver server. In a

No action is required. The pip.type Java System Property for the strategy management application in SAP NetWeaver is ignored. The JPIP version does not use the following services: PipAdmin Web Service Table Editor SAP SM Extended Listener Registry Editor Various pip parameters Log files cache When upgrading, strategy administrators should uninstall the 7.5 version of Diagram Manager to remove it from their client machines. All strategy administrators can create goal diagrams in the administration application, the same way as before, without having to install any client software. No further action is necessary. Diagram Manager users who used a .BMP file as a custom image must save it to another format and reload it. When installing Application Server on a Windows server, you can install the supporting files at the same time. When installing Application Server on a UNIX/Linux server, you must also install Application Server on a Windows client to obtain the supporting files and copy them to the appropriate location.

10/38

PUBLIC

2011-11-07

1 1.6

Introduction Upgrading from 7.5 at a Glance Changes Action / Further Information

Component

for the file from any location. default installation, the full path is \usr\sap\<SID>\J00 Now the file to be imported must \j2ee\cluster\server\temp\SSM\import. be in a particular directory.

This table shows application changes for SAP BusinessObjects Strategy Management 7.5 to 10.0. These changes may affect the upgrade process.
Component Changes Action / Further Information

Administration application

Scheduler

Operational Reviews

Reports

Dashboards

Bookmarks in the Home tab

The application is All the same functionality exists as the previous version. There are redesigned for ease of use additional features which you can learn about in the release notes and in the Application Help. For more information, see the SAP Library for SAP BusinessObjects Strategy Management at http://help.sap.com/epm Strategy Management . Then choose Application Help Administration . Scheduled tasks from 7.5 Before upgrading, the strategy management administrator must are not upgraded to the record all Scheduler tasks. 10.0 version. After the upgrade, the strategy management administrator must redefine the schedules. Operational Reviews from Before upgrading, users must save their operational reviews as 7.5 are not upgraded to local PDFs. the 10.0 version. Briefing After upgrading, users can recreate the operational reviews as Briefing Books by recapturing each view shown in the saved Books are now used instead of operational operational review. For information about Briefing Books, see SAP Library for SAP reviews. BusinessObjects Strategy Management on the Help Portal at http://help.sap.com/epm. Then choose Content Analysis Briefing Books . Reports from 7.5 are not Users have two options: upgraded to the 10.0 Before upgrading, users can record their saved reports. After version. upgrading, users can recreate the reports. The Reports tab is new You can set the EnableLegacyReports Java System Property to a reporting functionality. value of Yes. This displays a legacy Reports and Dashboards link in the Launch page. This allows you to run your 7.5 reports and dashboards using the user interface from 7.5 without any upgrade steps. Dashboards from 7.5 are Users have two options: not upgraded to the 10.0 Before upgrading, users can record their saved reports. After version upgrading, users can recreate the reports. The Dashboard tab is new You can set the EnableLegacyReports Java System Property to a dashboard value of Yes. This displays a legacy Reports and Dashboards functionality. link in the Launch page. This allows you to run your 7.5 reports and dashboards using the user interface from 7.5 without any upgrade steps. Bookmarks from 7.5 are Before upgrading, users should record their bookmarks. not upgraded to the 10.0 After upgrading, users can recreate the bookmarks. version

2011-11-07

PUBLIC

11/38

1 1.6

Introduction Upgrading from 7.5 at a Glance Changes Action / Further Information

Component

Goal Diagrams

terminology

Status indicators do not After upgrading, run the Calculate All Scorecard Objects schedule. The appear as expected status indicators will appear. For more information, see Redefining Strategy Management Objects That Were Not Upgraded [page 33]. The following terms are No action is necessary. changed: metric measure SAP NetWeaver BI SAP NetWeaver BW component tab alert notification application groups roles Index KPI indexed KPI dimensional model, cube model Cube Builder application Model Designer application

12/38

PUBLIC

2011-11-07

Quick Guide for 7.5 to 10.0 series

2 Quick Guide for 7.5 to 10.0 series

The upgrade process is the same when upgrading from any 7.5 series to the latest 10.0 series. For the sake of brevity, this Guide uses the term 7.5 to refer to the 7.5 SP series from which you are upgrading.
Preparation Section Activity

3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9

Upgrade Process Section

Obtain the latest strategy management 10.0 installation. Back up the Application Server databases and custom files. Back up Interactive Publisher files. Record application definitions for scheduled tasks, reports, dashboards, bookmarks, and operational reviews. Export performance management scorecard data and model connections from 7.5 using the Transporter utility. Stop strategy management services. Uninstall SAP BusinessObjects Strategy Management if you plan to install the new version to a non-default location. Undeploy the strategy management application. Clean up cache files and Work databases.

Activity

4.1

4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9

Confirm the current version of SAP Solution Manager is available on your system or install SAP Solution Manager on a new server. Upgrade the SAP NetWeaver server to version 7.3, or install SAP NetWeaver 7.3 on a new server. Install the latest version of SAP BusinessObjects Strategy Management 10.0. Copy backed up files to the new installation location. Deploy the FCP and POASBC components. Deploy the new Software Component Archive from the latest 10.0 series. Import the latest 10.0 series bootstrap data using the Transporter utility. Import performance management data into the latest 10.0 series using the Transporter. Reset Web Service Providers to Basic Authentication. Start strategy management services and restart SAP NetWeaver to clear all table cache.

2011-11-07

PUBLIC

13/38

Quick Guide for 7.5 to 10.0 series

Follow-Up Activities Section Activity

5.1

5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9

Diagram Manager users must uninstall the client program from their machines. Diagram Manager users who used a .BMP file as a custom image must save it to another format and reload it. Make sure strategy management users are running with the new system requirements on their machines. Distribute Excel Add-In installation file to Excel Add-In users. Merge customizations Reset month name abbreviations to non-English text Copy files from the \Procs directory Additional configurations Redefine strategy management objects in the latest version of strategy management that were not included in the upgrade. Respecify encrypted passwords.

14/38

PUBLIC

2011-11-07

3 3.1

Preparation Obtaining the Strategy Management Downloads

3 Preparation

3.1 Obtaining the Strategy Management Downloads

The Central Note for SAP BusinessObjects Strategy Management explains how to obtain the downloads for that release. Any further Support Packages for a release also include SAP Notes explaining how to obtain the download for each particular Support Package.

3.2 Backing Up Application Server Files

Procedure

1.

2.

3.

If you are running Application Server on a Microsoft Windows client or Microsoft Windows server, move the lsserver.ini file located in the Windows directory to a temporary location. By moving the file, it allows the installation to put a new version of lsserver.ini in the Windows directory. The new version contains the new path information for Application Server. If you have custom entries in the lsserver.ini, you can later incorporate the custom entries into the new version during the upgrade process. If you do not move lsserver.ini and you are installing the latest version of Application Server on the same machine as the older version, then you will need to update all directory paths in the file after the new install. Back up all your Application Server databases and custom procedure files. By default the databases that you create are located in \Program Files (x86)\SAP\SSM\ApplicationServer\home on a Microsoft Windows server. On a Linux/UNIX server they are created in the lss/workfile directory in the install location. Copy the following files from the Microsoft Windows server or Linux/UNIX server where Application server is installed to a backup location. On a Microsoft Windows server, the files are located in \Program Files (x86)\SAP\SSM\ApplicationServer\data. On a Linux/UNIX server, the files are located in the lss directory in the installation location. Make note of the location of all the files that you backup. Later in the upgrade process, you will be moving these to the corresponding directory in the new install location.
File
CGLIB MASTERDB

Description

SMREPORT

Contains User-Defined Hierarchies. Catalog of models, users, and other important system information. Contains procedures from saved reports.

2011-11-07

PUBLIC

15/38

3 3.3

Preparation Backing Up Interactive Publisher Files

4.

5.

If you customized any files that are put down by the installation, copy those files to a backup location. For example, if you created your own timesets in APLIB, copy APLIB to a backup location. If you are running on a Linux/UNIX server and you added entries to any of the shell scripts created by the install, copy these shell scripts to the backup location. If you are using the Access LSLink subsystem to retrieve data from a relational data source and you have an lsdal.ini file, copy lsdal.ini to a backup location.

3.3 Backing Up Interactive Publisher Files

Procedure

If you changed any files that were put down by the installation, you need to back up those files and then merge the changes into the new versions of those files. Copy those files located on the Microsoft Windows server to a backup location.

3.4 Recording Application Definitions That Are Not Upgraded

If you want to use existing definitions for the following items in the latest version of strategy management, you need to record the definitions. Record the definitions for any of these items that you want to use in the latest version of strategy management: Scheduled tasks in the administration application. Record the definitions of the scheduled tasks and recreate them in the latest version. Bookmarks. Record the contents of your bookmarked views. Operational Reviews. Save your operational reviews locally as PDF files. You can recreate them as Briefing Books in the latest version. Reports. Record your reports. You can create new reports in the latest version. Dashboards. You can create new dashboards in the latest version.
NOTE

If you do not want to recreate your reports or dashboards in the new version, you can continue to run the 7.5 version of reports and dashboards while also running the 10.0 version. To implement this feature, you need to implement a Legacy Reports and Dashboards link on the strategy management Launch page. For more information, see Redefining Strategy Management Objects That Were Not Upgraded. [page 33]

16/38

PUBLIC

2011-11-07

3 3.5

Preparation Exporting Performance Management Scorecard Data

3.5 Exporting Performance Management Scorecard Data

Use the Transporter tool to export your performance management scorecard data and model connections from the older version of strategy management to zip files. Later, you import the zip file after the strategy management software component archive is fully deployed.
Prerequisites

You are the strategy management administrator.

Procedure

1. 2. 3.

Access the Tools page by opening this URL in a browser window:

http://<nw_server>:<port>/strategy/tools

Click Transporter. Do one of the following depending on the version of the application you are currently running: If you are running a version from the 7.5 SP01 series to the 7.5 SP03 series, select Include Model Connections to include all model connections in the export.
NOTE

4.

If you do not include model connections in the export, you will need to re-create the model connections. If you are running version 7.5 SP04 or higher, select Export all data to export all strategy management data (including model connections). Or, to export data while excluding certain custom data, click Exclude custom data, and then select the custom data you want to exclude from the export. Click Export Database to export the strategy management application data from the SAP NetWeaver System database.
NOTE

5. 6. 7.

DO NOT apply a database filter in the export. You must export all the data. Click Download Export to download the exported database to your local system. Save the export to a .ZIP file and name it exportsm.zip. Open the downloaded .zip file and sort by size. If you see any files that have a length of 0, contact technical support and do not continue the upgrade.

3.6 Stopping Services

Procedure

1.

If you are running the original C++ (CPIP) version, on the Interactive Publisher server, go to Administrative Tools Services and stop the SAP SM Extended Listener. If you are running the default Java (JPIP) version of Interactive Publisher, you can skip this step because JPIP does not use the SAP SM Extended Listener service.

2011-11-07

PUBLIC

17/38

3 3.7

Preparation Uninstalling SAP BusinessObjects Strategy Management

2. 3.

If Application Server is installed on a Microsoft Windows server, go to Administrative Tools Services and stop the SAP SM Listener. If Application Server is installed on a UNIX/Linux server, log on as root and stop the Application Server TCP/IP Listener daemon by running the following:
tldstop

3.7 Uninstalling SAP BusinessObjects Strategy Management

You can uninstall Interactive Publisher and Application Server using Add or Remove Programs in the Control Panel or by running the xSSMSrv.exe file and deselecting the components.
Procedure
Interactive Publisher and Application Server on Microsoft Windows servers

1. 2. 3. 4.

5. 6.

On the Microsoft Windows server, make sure that you are logged in with a user and password that has administrative privileges on the server. From the installation location, run the xSSMSrv.exe file. In the first screen, click Next. In the next screen, do one of the following: Deselect SM Interactive Publisher to uninstall Interactive Publisher. Deselect SM Application Server to uninstall Application Server. Click Next. In the final screen, click Finish.

Application Server on a Linux/UNIX server

1. 2.

Assuming you backed up your database files, MASTERDB, and any other files that were customized, use the rm command to remove all files at the operating system level. If you are not reinstalling Application Server on the same system, then in the /etc/services file, delete the following line, where nnnn is a number such as 2001 or 8325. The number varies depending on the version of the strategy management software you have installed:
lsserver nnnn/tcp lsserver # Application Server Client

3.8 Undeploying the Software Component Archive

Undeploy the software component archive for strategy management using the tool you typically use to deploy and undeploy archives in SAP NetWeaver. For information about undeploying using SAP NetWeaver Developer Studio, see the topic Undeploying Archives in the SAP NetWeaver Composition Environment Library Developer's Guide on the Help Portal. To undeploy strategy management using telnet to the SAP NetWeaver Application server, do the following:

18/38

PUBLIC

2011-11-07

3 3.9

Preparation Cleaning Up Files

1. 2.

Open a DOS window and log onto the server using telnet<servername><telnet_port>. The telnet port is typically 50008. Undeploy the strategy management components:
undeploy vendor=sap.com name=xapps~cpm~sm~strategymanagement undeploy vendor=sap.com name=xapps~cpm~sm~strategymanagementaction undeploy vendor=sap.com name=xapps~cpm~sm~strategymanagementdic undeploy vendor=sap.com name=xapps~cpm~sm~client~ear undeploy vendor=sap.com name=xapps~cpm~sm~ctc NOTE

It is not necessary to restart SAP NetWeaver after an undeploy.

3.9 Cleaning Up Files

You must clean up files when upgrading from a previous version of strategy management.
Procedure

1. 2.

3.

4.

Clean your browser cache on the Microsoft Windows server and on all client machines. In the \Program Files (x86)\SAP BusinessObjects\Strategy Management \ApplicationServer directory, if you see any .GID files, delete them. These are Windows-based Application Server online Help cache files that are not deleted when upgrading strategy management. These files are created the first time you start the Windows-based Application Server online Help. If you do not see ..GID files, it means you have not access Application Server Help. In this case, you can skip this step. In the \Program Files (x86)\SAP BusinessObjects\Strategy Management \ApplicationServer\home directory, select all the Work database files, right-click, and then choose Delete from the floating menu. Work databases have the following filenames: <web_authentication_name><model>. In the \Program Files(x86)\SAP BusinessObjects\Strategy Management\ApplicationServer \home directory, select all the DB* files, right-click to display the floating menu, and then choose Delete.

2011-11-07

PUBLIC

19/38

This page is left blank for documents that are printed on both sides.

4 4.1

Upgrade Process Installing or Upgrading to SAP NetWeaver 7.3

4 Upgrade Process

This section discusses how to upgrade from SAP BusinessObjects Strategy Management 7.5 SP01 min to the latest version of SAP BusinessObjects Strategy Management 10.0.
Prerequisites

You have completed the tasks in the Preparation section of this Guide. You have upgraded your system to follow the latest strategy management system requirements. For more information, see the Product Availability Matrix (PAM) at http://service.sap.com/ pam. Then search on strategy management.

4.1 Installing or Upgrading to SAP NetWeaver 7.3

The application components must be deployed on a SAP NetWeaver 7.3 server. Before you can install strategy management, you must either upgrade your current version of SAP NetWeaver to version 7.3, or install SAP NetWeaver 7.3 on a server. This requires that you confirm the current version of SAP Solution Manager is available on your system or install SAP Solution Manager on a new server because the SAP NetWeaver AS Java installation requires an SAP Solution Manager key. For more information, see the SAP NetWeaver 7.3 Upgrade Master Guide on SAP Service Marketplace at http://service.sap.com/instguides. Then choose SAP NetWeaver SAP NetWeaver 7.3 Upgrade . In the Planning section, choose Upgrade Master Guide. For information about SAP Solution Manager, see http//service.sap.com/solutionmanager.

4.2 Installing Application Server and Supporting Files

You can install Application Server software on a Microsoft Windows server or on a Linux/UNIX server. If you are installing on a Linux/UNIX server, you must also install Application Server on a Microsoft Windows client. You must also install certain supporting files at the same time you install Application Server. For sites installing on a Windows server, you install the supporting files when you install Application Server on the Windows server. For sites installing on a Linux/UNIX server, you install the supporting files when you install Application Server on the Windows client.

2011-11-07

PUBLIC

21/38

4 4.2

Upgrade Process Installing Application Server and Supporting Files

Prerequisites

You have decided whether to install Application Server on a Microsoft Windows server or UNIX/Linux server. You have decided whether you need to install Application Server on a Microsoft Windows client. For information about whether you should install Application Server on a Windows client, see the Master Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http:// service.sap.com/instguidesEPM-STM. Then choose System Landscape.

4.2.1 Installing Application Server on a Microsoft Windows Server

You can install Application Server on a Microsoft Windows server and install the required supporting files at the same time. The supporting files required for the strategy management application are bootstrap.zip and import.zip.
Prerequisites

You are logged into the Microsoft Windows server with a user and password that has administrative privileges on the server.
Procedure

1. 2. 3. 4.

5. 6.

7.

From the installation location, run the xSSMSrv<sp>_<patch>-<smp-id>.exe file. In the first screen, click Next. In the next screen, select Strategy Management Server Components and click Next. In the path screen, click Next to accept the default path. To browse for a different location, click Browse. The default path is C:\Program Files (x86)\SAP BusinessObjects\Strategy Management. For information about supported Windows servers, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/pam. In the final screen, click Done. Move either the import.zip file or bootstrap.zip file from the \SAP BusinessObjects\Strategy Management\InternetPub\conf directory to the \server0\temp\SSM\import directory on the SAP NetWeaver server. In a default installation, the full path is \usr\sap\SID\J00\j2ee\cluster \server0\temp\SSM\import. If you installed Application Server on a Windows server 2008 R2 system, modify the security settings of the \data and \home directories to allow Users full control.
NOTE

To cancel the installation, click Cancel in any wizard screen.

22/38

PUBLIC

2011-11-07

4 4.2

Upgrade Process Installing Application Server and Supporting Files

The SAP SM Listener service is started by default. This service listens for WINSOCK TCP/IP Application Server client connections. The service validates the user's rights to log on to the server and start the data communication process.
More Information

Application Server Requirements [page 0 ]

4.2.2 Installing Application Server on a Linux/UNIX Server

You can install Application Server on a Linux/UNIX server. The client machines running Application Server use WINSOCK support for client/server communications to Linux/UNIX servers. After you install Application Server on a UNIX/Linux server, you must install Application Server and supporting files on a Windows client. For more information, see Installing Application Server and Supporting Files on a Windows Client [page 24].
Prerequisites

You are logged in as root on the Linux/UNIX server. You have downloaded the SAPCAR archive file and the <sarfilename>.SAR file from SAP Service Marketplace.
Procedure

1. 2.

Create a directory to install Application Server. From the location where you downloaded the .SAR file, use the following commands to transfer the .SAR file to the desired installation directory. Case is significant on UNIX so you need to match the exact case of the filename.
cp <sarfilename>.SAR /<installdir>

3. 4. 5. 6.

If reading the installation location from a Microsoft Windows client, use FTP to transfer the .SAR to the /<installdir> directory on your Linux/UNIX machine. Be sure to transfer the file as a binary file. Extract the file using the following command. Make sure you enter the exact case of the filename.
SAPCAR -xvf <sarfilename>.SAR

Enter the following command to perform the installation.

sh install.sh

Answer all the prompts about your Linux/UNIX environment to set up any environment variables required by Application Server. At the prompt to choose the target environment, enter the number that represents your platform of Linux or UNIX.
NOTE

At any time while you are answering the prompts, you can type Q to quit and cancel the installation.

2011-11-07

PUBLIC

23/38

4 4.2

Upgrade Process Installing Application Server and Supporting Files

The system creates a directory structure under the /<installdir> directory. For the complete directory structure, see Installed File Systems and Services [page 0 ].

4.2.3 Installing Application Server on a Microsoft Windows Client

You can install Application Server on a Windows client. If you install Application Server on a Linux/ UNIX server, you must also install Application Server and supporting files on a Windows client machine for the following reasons: You use the Windows client machine to connect to the back end. If you read in data from a relational database system, you use Application Server on the Windows client to create a Link ID and copy it to the Linux/UNIX server. (Application Server on Linux/UNIX has no interface to create a Link ID.) You need to install the supporting files that are required for the strategy management application. The bootstrap.zip and import.zip supporting files are provided in the Application Server Windows installation. For more information about the system landscape, see the Master Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM SAP BusinessObjects Strategy Management . Then choose System Landscape.
Prerequisites

You have installed Application Server on a Windows server or Linux/UNIX server.

Procedure

1. 2. 3. 4. 5.

6. 7.

Copy the file xSSMSrv<sp>_<patch>-<smp-id>.exe from the download location on the Microsoft Windows server to the Microsoft Windows client. From the installation location, run the xSSMSrv<sp>_<patch>-<smp-id>.exe file. In the first screen, click Next. In the next screen, select Strategy Management Server Components and click Next. In the path screen, click Next to accept the default path of C:\Program Files (x86)\SAP BusinessObjects\Strategy Management. Or, click Browse to browse for a location. Then click Next. In the final screen, click Done. (For Linux/UNIX installations) Move the import.zip file or bootstrap.zip file from the \SAP BusinessObjects\Strategy Management\InternetPub\conf directory on the server where you installed the supporting files to the \server0\temp\SSM\import directory on the SAP NetWeaver server. In a default installation, the full path is \usr\sap\<SID>\J00\j2ee\cluster\server0\temp \SSM\import.

24/38

PUBLIC

2011-11-07

4 4.3

Upgrade Process Copying Backed Up Files to the New Installation Location NOTE

8.

Move import.zip if you want the demo/sample data to be available. Otherwise, move bootstrap.zip instead. If you installed Application Server on a Windows server 2008 R2 system, modify the security settings of the /data and /home directories to allow Users full control.

More Information

Application Server Requirements [page 0 ]

4.3 Copying Backed Up Files to the New Installation Location

Procedure

1.

2.

3. 4.

If running Application Server on a Microsoft Windows server, compare the new versions of lsserver.ini and lsdal.ini to the backed up files and copy/edit any necessary information into the new files. Copy all the Application Server databases that you backed up to the appropriate directories in the new install location. This includes any databases you created and also MASTERDB, CGLIB, and SMREPORTS which can overwrite the version put down by the new install. If you backed up the APLIB database to preserve custom sets, you will have to copy these sets into the new version of APLIB put down by the install. If you backed up any customized files or scripts, compare the backed up version with the one put down by the install and merge any customizations into the new version.

4.4 Deploying the FCP and POASBC Components

You deploy several software component archives if there are new versions included in the latest support package. Use the Java Support Package Manager (JSPM) tool to deploy. JSPM is part of every SAP NetWeaver installation with usage types based on AS Java.
NOTE

You must deploy the FCP and POASBC components before deploying the strategy management application components. If you accidentally deploy the FCP and POASBC components after deploying the strategy management components, you get an error message when trying to access the strategy management application. For information about troubleshooting this issue, see the Strategy Management Installation Guide on SAP Service Marketplace. Then choose Troubleshooting an Incorrect Deployment.

2011-11-07

PUBLIC

25/38

4 4.5

Upgrade Process Deploying the Software Component Archive

Procedure

Deploy the following components one-by-one in this exact order. If the support package includes a subset of these components, deploy the components provided while adhering to this order: RPP-FCP-JEE: FCP Java server component. POASBC-BUIBB: Software component that contains the building blocks. POASBC-BUI: Software component that contains the Flex foundation artifacts. POASBC-BUINW: Software component that contains the NetWeaver adapter implementation and platform (integration tier, presentation, and business tier). This software component contains the default NW Java-only implementation, platform, and libraries for the platform, such as JSON, JAX-RS, CVOM. This component also contains a service to generate PDFs. To deploy the SCA using telnet to the SAP NetWeaver Application server, do the following: 1. Open a DOS window and log onto the server using telnet <servername><telnet_port>. The telnet port is typically 50008. 2. Deploy the components as follows:
deploy <drive>:\usr\sap\<SID>\SYS\EPS\in\<filename>.SCA

4.5 Deploying the Software Component Archive

Use the Java Support Package Manager (JSPM) tool to deploy the SCA. JSPM is part of every SAP NetWeaver installation with usage types based on AS Java.
Prerequisites

You have installed NW 730 SP1 Java.

Procedure

1.

Deploy the Strategy Management Software Component Archive (SCA) file, which you downloaded to the SAP NetWeaver server. 2. Restart SAP NetWeaver. To deploy the SCA using telnet to the SAP NetWeaver Application server, do the following: 1. Open a DOS window and log onto the server using telnet <servername><telnet_port>. The telnet port is typically 50008. 2. Deploy the strategy management components as follows:
deploy <drive>:\usr\sap\<SID>\SYS\EPS\in\<filename>.SCA

4.6 Importing Bootstrap Data

You must import bootstrap data when upgrading from any previous version of the strategy management components.

26/38

PUBLIC

2011-11-07

4 4.7

Upgrade Process Importing Performance Management Scorecard Data and Model Connections

Prerequisites

You are the strategy management administrator.

Procedure

1.

Depending on your implementation as noted below, move either the import.zip file or bootstrap.zip file from the \SAP BusinessObjects\Strategy Management\InternetPub\conf directory on the Application Server server to the \server0\temp\SSM\import directory on the SAP NetWeaver server. In a default installation, the full path is \usr\sap\<SID>\J00\j2ee\cluster \server0\temp\SSM\import.
NOTE

2. 3. 4. 5. 6.

Move bootstrap.zip if you do not want the sample data to be available or if it was on your system prior to upgrading and is included in your exportsm.zip file. If you did not have the sample data available previously and you want it now, move import.zip. Access the Tools utility. To do so, open this URL in a browser window:
http://<nw_server>:<port>/strategy/tools

Click Transporter. In the Choose a database transport file section, ensure that the Delete all data in database before the import? dropdown list is set to No. From the dropdown list of zip files, select the bootstrap.zip file or import.zip file you moved into the \import directory. Click the Import into Database button.
NOTE

In case the import fails, you can review the error log in the Log Viewer in SAP NetWeaver Administrator by going to SAP NetWeaver Administrator Troubleshooting Logs and Traces LogViewer . Then choose Show View Open View System Logs and Traces . The physical location is at \<server installation>\j2ee\cluster\server0\log.

4.7 Importing Performance Management Scorecard Data and Model Connections

You must import your performance management scorecard data and model connections you exported in a previous preparation section.
Prerequisites

You are the strategy management administrator. You dumped model connection and user data during the Preparation phase and the zip file is available for import.

2011-11-07

PUBLIC

27/38

4 4.8

Upgrade Process Resetting Web Service Providers to Basic Authentication

Procedure

1.

2. 3. 4. 5.

Move the exportsm.zip file to the \server0\temp\SSM\import directory on the SAP NetWeaver server. In a default installation, the full path is \usr\sap\<SID>\J00\j2ee\cluster\server0\temp \SSM\import. Access the Tools utility. To do so, open this URL in a browser window:
http://<nw_server>:<port>/strategy/tools

Click Transporter. In the Choose a database transport file section, from the dropdown list, select the exportsm.zip file that you copied to the \server0\temp\SSM\import directory. Click the Import into Database button.

Result

The previously exported performance management scorecard data and model connections are added to the strategy management application.
NOTE

In case the import fails, you can review the error log in the SAP NetWeaver Administrator by going to SAP NetWeaver Administrator Troubleshooting Logs and Traces LogViewer . Then choose Show View Open View System Logs and Traces . The physical location is at \<server installation>\j2ee\cluster\server0\log.
More Information

Restarting SAP NetWeaver and Services [page 29]

4.8 Resetting Web Service Providers to Basic Authentication

If you are using Web Services such as SMDataService, or CubeService, you must reset them to use Basic Authentication.
Prerequisites

You are the administrator of SAP NetWeaver.

Procedure

1. 2. 3. 4. 5. 6.

Start Web Services Administration in SAP NetWeaver using the following URL:
http://<nw_server>:<port>/nwa

Choose SOA Application and Scenario Communication Single Service Administration . Select the Service Definitions tab if it is not currently selected. In the Find text box, enter iSMDataService or CubeServiceInterface and click Go. In the WSDL Port Type Name list, select iSMDataService or CubeServiceInterface if it is not already selected. Select the Configuration tab.

28/38

PUBLIC

2011-11-07

4 4.9

Upgrade Process Restarting SAP NetWeaver and Services

7. 8. 9. 10.

From the Service Endpoint list, select SMDataServicePort or CubeServiceInterface. Click Edit. Select the Security tab. Do one of the following: If using SAP NetWeaver UME, in the HTTP Authentication section, select User ID/Password and then click Save. If using SAP BusinessObjects authentication, in the HTTP Authentication section, make sure User ID/ Password is not selected, and then click Save.

4.9 Restarting SAP NetWeaver and Services

Prerequisites

You have administrative permission to restart SAP NetWeaver.

Procedure

1. 2. 3. 4.

Restart SAP NetWeaver to clear the table cache. Access the Tools utility at http://<nw_server>:<port>/strategy/tools and click JPIP Session Monitor. Then click Restart JPIP. If Application Server is installed on a Microsoft Windows server, go to Administrative Tools Services and restart the SAP SM Listener. If Application Server is installed on a UNIX/Linux server, log on as root and start the Application Server TCP/IP Listener daemon. Go to the directory where Application Server is installed and run the shell script to start the Listener. For example:
cd /opt/sap/sm/lss

Run the shell script to start the Listener:

sh tldgo

When lsstld has initialized, it creates a log file called LSSTLD.LOG in the current directory, and displays the following messages:
******************************************************************** lsstld: daemon initialization started at Fri May 06 08:59:15 2011 lsstld: daemon initialization completed at Fri May 06 08:59:15 2011 ********************************************************************

2011-11-07

PUBLIC

29/38

This page is left blank for documents that are printed on both sides.

5 5.1

Follow-Up Activities Diagram Manager Upgrade Tasks

5 Follow-Up Activities

For information about ongoing administration of strategy management components, see the Administrators Guide for SAP BusinessObjects Strategy Management Application Server and the Administrators Guide for SAP BusinessObjects Strategy Management Interactive Publisher and Application Components on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM.

5.1 Diagram Manager Upgrade Tasks

Starting in the 10.0 version, the Diagram Manager is incorporated into the administration application installation. It is not installed on the client machine. Users who installed an earlier version of Diagram Manager on their client machines must uninstall the program. In addition, Diagram Manager users who previously uploaded .BMP files as custom images must now save their files as .GIF, .JPEG, .JPG or .PNG files and reload the image in the diagram editor.
Procedure
Uninstalling Diagram Manager from the 7.5 Series

1. 2. 3. 4. 5.

From the installation location, run the xSSMDgm.exe file. In the first screen, click Next. In the next screen, deselect SM Diagram Manager. Click Next. In the final screen, click Done.

Reloading .BMP files with a Different Custom Image Format

1. 2. 3. 4.

Open the .BMP file in an image editor and save it as a .GIF, .JPEG, .JPG or .PNG file. In the administration application, edit the goal diagram. Make sure Format Custom Image is selected in the diagram editor. Select Action Properties , and use the Custom Image File Name dropdown list to load the image saved in the new format.

5.2 Updating User Software Requirements

In version 7.5, strategy management administrators and users of the Reports, Dashboard, and Scorecard tabs were required to run Sun JRE 1.5.0_11 or higher.

2011-11-07

PUBLIC

31/38

5 5.3

Follow-Up Activities Distributing the Excel Add-In Installation

In version 10.0, the only users who need Sun JRE are scorecard administrators. These administrators need Sun JRE version 1.6. Strategy management users and administrators now require Adobe Flash Player.

5.3 Distributing the Excel Add-In Installation

If you have not done so already, distribute the xSSMWea.exe file to all users who use the Excel Add-In. Or, you can make it available to users for download. Users can follow the installation instructions in the Client Installation Guide for SAP BusinessObjects Strategy Management Excel Add-In and skip the upgrade steps.
NOTE

Users do not need to uninstall their previous version of Excel Add-In before installing this new version. The installation updates any files in these components that changed from the previous support package, so no uninstall is required. To allow users to install Application Server on a client machine, you must distribute the Application Server installation file. It is the same file used to install Application Server on a Windows server. For information about who should install Application Server on a client machine, see the Installing Application Server on a Microsoft Windows Client [page 24].

5.4 Merging Customizations

If you previously backed up files put down by the installation because they contained customizations, merge your changes into the new files.

5.5 Resetting Month Name Abbreviations to Non-English Text

If you are running the strategy management application in a non-English language, by default, the application displays month name abbreviations in English when displaying charts, dashboard panels, and some report headings. If you previously set these month name abbreviations to use non-English text by running the setup_cal_<lang>.pro job in Application Server, you must run this job again to reset the month name abbreviations to use non-English text. For information about running setup_cal_<lang>.pro, see the Server Configuration Guide on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Setting Month Name Abbreviations to Non-English Text.

32/38

PUBLIC

2011-11-07

5 5.6

Follow-Up Activities Copying Files From the \Procs Directory

5.6 Copying Files From the \Procs Directory

In some implementations, you must copy the files from\SAP BusinessObjects\Strategy Management \InternetPub\procs\<db>_procs directory up one level into the \procs directory, replacing the MaxDB version of the same files. As an upgrade step, you must copy the files if your implementation includes both of these items: You are using SQL Server or Oracle as the SAP NetWeaver system database. You are using one or more of these features: You want to look at the strategy management tables in the system database You are using the Entry and Approval application You are using Cube Builder (now called Model Designer) The task of copying files up one level was performed during the initial configuration, but must be done again during an upgrade. For information about copying the \procs folder, see the Installation Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Setting Up Client Access to the SAP NetWeaver System Database.

5.7 Additional Configurations

The latest version of SAP BusinessObjects Strategy Management contains some post-installation configurations that did not previously exist.
NOTE

Users currently running Internet Explorer 7.x as their browser must upgrade to the 8 series. For information about setting strategy management configuration properties on the SAP NetWeaver server, see the Installation Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Configuration Roadmap and Setting Up Users, Roles, and Application Properties.

5.8 Redefining Strategy Management Objects That Were Not Upgraded

Certain aspects of functionality are not upgraded when you install the new version of the application. You must make changes as appropriate.
Features

You must make the following changes for all that apply to your implementation:

2011-11-07

PUBLIC

33/38

5 5.9

Follow-Up Activities Respecifying Encrypted Passwords

Goal diagram status indicators may not appear in the latest version. If this is the case, you should run the Calculate All Scorecard Objects scheduled task to have the status indicators appear as appropriate. For any objects whose definitions you recorded before uninstalling strategy management, you can now create those objects in the latest version of strategy management. For more information, see Recording Application Definitions That Are Not Upgraded [page 16] If you do not want to recreate your reports and dashboard in the latest version, but you do want to run the 7.5 version of reports and dashboards while you run the 10.0 version, you can set the EnableLegacyReports Java System Property in SAP NetWeaver to a value of Yes. This displays a Legacy Reports and Dashboards link in the Launch page. This allows you to run your 7.5 reports and dashboards using the user interface from 7.5 without performing any upgrade steps. Although application groups are automatically upgraded to roles, you must add strategy management users to certain new required roles before access the application. For more information, see the Installation Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Adding Strategy Management Users to Required Roles. If an application group contained the Create/Edit Objectives permission, you must modify the upgraded roles and add the SSM_CreateScorecard action to those roles, if that action is not already there.

5.9 Respecifying Encrypted Passwords

Due to changes related to security, you need to respecify all encrypted passwords when upgrading from 7.5 to the latest version of strategy management.
System Passwords and PAS Passwords in Model Connections

In the administration application, go to Administration Manage Models . Select each model connection and respecify the system password and the PAS user password. Even if there was no PAS password in the previous version, you need to clear the entry that gets added during the upgrade and respecify the password.
Link ID passwords

For Link Ids stored in lsdal.ini files, open each Link Id in Application Server and re-type the password. This causes the latest encryption to be updated in lsdal.ini file.
Passwords in Lsserver.ini

1. 2. 3.

Open lsserver.ini in a text editor and remove the EncryptedPassword line. Log onto Application Server. Enter the password when prompted.

34/38

PUBLIC

2011-11-07

5 5.9

Follow-Up Activities Respecifying Encrypted Passwords

4. 5.

Click on the List tab in the Application Server Administrator and select Remote Servers from the left navigation panel. Double-click on the server name in the right panel to display the Properties page and enter the system password.

2011-11-07

PUBLIC

35/38

This page is left blank for documents that are printed on both sides.

A A.1

Appendix List of Documentation

A Appendix

A.1 List of Documentation

The following guides are located on SAP Service Marketplace at http://service.sap.com/ instguidesEPM-STM: Administrators Guide for SAP BusinessObjects Strategy Management Application Server Administrators Guide for SAP BusinessObjects Strategy Management Interactive Publisher and Application Components Client Installation Guide for SAP BusinessObjects Strategy Management Excel Add-In Server Configuration Help for SAP BusinessObjects Strategy Management

2011-11-07

PUBLIC

37/38

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

Copyright 2011 SAP AG. 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.