SBOP_PC_10_M_Admin

Administrator's Guide SAP BusinessObjects Planning and Consolidation 10.0version for the Microsoft platformTarget Audience Technical Consultants System Administrators Solution Consultants Business Process Owners Support Specialists

PUBLIC Document version: 1.0 2011-05-10

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. 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 is a registered trademark of Oracle Corporation. 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. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. 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.

2/102

PUBLIC

2011-05-10

Document History

The following table provides an overview of the most important document changes.Version Date Description

1.0

2011-05-10

This is the first release.

2011-05-10

PUBLIC

3/102

Table of Contents

Chapter 1 Chapter 2 Chapter 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.4.1 3.2.4.2 3.2.5 3.2.6 3.2.7 3.2.8 3.2.8.1 3.2.8.2 3.3 3.4 3.4.1 3.4.2 3.4.3 3.5 3.5.1 3.6 3.7

Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Monitoring of Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . Setting up a Minimal-Access User for Support . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring with the Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . Information and Actions in the Management Console . . . . . . . . . . . . . . . . . . Management Console Installation and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping Planning and Consolidation Remotely . . . . . . . . . . . . . Monitoring the Application and the Database . . . . . . . . . . . . . . . . . . . . . . . . . Management Console Home Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Console Database Server Fields . . . . . . . . . . . . . . . . . . . . . . . . . . Alert Monitoring with the Management Console . . . . . . . . . . . . . . . . . . . . . . Identifying and Stopping a Resource-Intensive Process . . . . . . . . . . . . . . . . . . Performing a Detailed Server Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Console Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Event Log Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Console Logging Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log and Trace Files List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Planning and Consolidation Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace File for Debugging Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Manager Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Computing Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring with the Central Computing Management System . . . . . . . . . . . Change and Transport System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking COM+ Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 15 15 16 17 18 18 20 23 24 24 24 24 25 26 26 26 26 27 27 27 28 29

4/102

PUBLIC

2011-05-10

Chapter 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 4.1.10 4.1.11 4.2 4.3 4.4 4.4.1 4.4.2 4.5 4.5.1 4.5.1.1 4.5.1.1.1 4.5.2 4.5.2.1 4.5.2.1.1 4.5.2.1.2 4.5.2.1.3 4.5.2.1.4 4.5.2.1.5 4.6 4.6.1 4.6.2 4.7 4.7.1

Management of Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . Managing Your Planning and Consolidation Servers . . . . . . . . . . . . . . . . . . . . Viewing Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SLD Data Supplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the Connection to the Central Management System . . . . . . . . . . . Migrating Users to the Central Management System . . . . . . . . . . . . . . . . . . . . Domain User Group Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Credentials for Component Services . . . . . . . . . . . . . . . . . . . . . Setting up Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kerberos Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous Interfaces and Data Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . Stored Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up and Restoring Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimizing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partitioning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considerations when Determining a Partitioning Scheme . . . . . . . . . . . . . . . . Data Slice Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partition Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OLAP Custom Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimizing the Flow of Data in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . Send Governor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Best Practices for Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . Tuning Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31 31 32 32 33 34 35 38 39 40 41 42 42 43 43 44 44 45 47 47 47 47 48 49 49 51 52 54 55 56 57 58 59 59

2011-05-10

PUBLIC

5/102

4.7.2 4.7.3 4.7.4 4.7.5 4.7.6 4.7.7 4.7.8 4.7.9 4.7.10 4.7.10.1 4.7.10.2 Chapter 5 5.1 Chapter 6 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.1.6 6.1.7 6.1.8 6.1.9 6.1.10 6.1.11 6.2 Chapter 7 7.1 7.2 7.3 7.4

Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tblDefaults Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Model Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Model Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Model Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Performance Bottlenecks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FACT, FAC2, and WB Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FACT, FAC2, and WB Table Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . FACT Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

61 62 62 64 65 66 70 71 73 74 75

High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 High Availability Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Environment Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimension Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Profile Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logic File Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data and Data File Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transformation and Conversion File Migration . . . . . . . . . . . . . . . . . . . . . . . . Data Manager Package Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving Microsoft SQL Server-Based Data Manager Packages . . . . . . . . . . . . . . Moving File-based Data Manager Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report, Input Form, and Book Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documents View Republication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support Packages and SAP Notes Implementation . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning and Consolidation Version Information . . . . . . . . . . . . . . . . . . . . . . Analyzing Problems Using Solution Manager Diagnostics . . . . . . . . . . . . . . . . Installing Appsight Black Box Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting and Analyzing System Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 80 80 81 82 82 83 84 84 85 85 86 86 86 87 87 87 87 88

6/102

PUBLIC

2011-05-10

7.5 7.6 7.7 7.8 7.9 Chapter 8 8.1 8.2 8.3

Generating and Analyzing Trace Files Using E2E Trace . . . . . . . . . . . . . . . . . . Logging and Tracing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Client and Server Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting in Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CA Wily Introscope Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

89 92 93 93 94 97 97 97 98

2011-05-10

PUBLIC

7/102

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

1

Important SAP Notes

1 Important SAP Notes

CAUTION

Check regularly to see which SAP Notes are available for this Administrator's Guide.Important SAP Notes SAP Note Number Title Comments

1573539

SAP Planning and Consolidation 10.0 This is the Central Note for Planning and SP00, version for the Microsoft Consolidation 10.0. platform This note contains important information about the installation of SAP Planning and Consolidation 10.0, version for the Microsoft platform.

2011-05-10

PUBLIC

9/102


2

Getting Started

2 Getting Started

CAUTION

This guide does not replace the daily operations handbook that we recommend customers create for their specific production operations.About this Guide

Designing, implementing, and running Planning and Consolidation at peak performance 24 hours a day has never been more vital for your business success than now. This guide provides a starting point for managing Planning and Consolidation solutions and maintaining and running them optimally. It contains specific information for various tasks and lists the tools that you can use to implement them. This guide also provides references to the documentation required for these tasks, so you sometimes also need other Guides such as the Master Guide and SAP Library.Naming Conventions

In this document, the following naming conventions apply:Variable

Description

Server name or IP address and port number of SAP Planning and Consolidation application location. The drive where SAP Planning and Consolidation is installed. The default for this is C:/PC_MS.

2011-05-10

PUBLIC

11/102


3 3.1

Monitoring of Planning and Consolidation Setting up a Minimal-Access User for Support

3 Monitoring of Planning and Consolidation

There are a number of methods that are available to you for monitoring your Planning and Consolidation system. Not all of the application described in the following sections may be available to you and you may also have alternative monitoring tools that you use. The following sections describe some of the SAP-recommended monitoring applications and also how to setup a user, with minimal access to Planning and Consolidation, who can provide support without impacting the Planning and Consolidation data.

3.1 Setting up a Minimal-Access User for SupportA user, who performs monitoring and diagnostic services, requires only minimal access to Planning and Consolidation data. Therefore, it may be advisable to create a user with minimal access rights particularly for remote monitoring and diagnosis. This user can send and retrieve Planning and Consolidation data but cannot modify system settings in the Administration Client, such as managing environments or models. This level of access is sufficient for purpose of remote support and monitoring using functions such as End-to-End (E2E) trace. The following procedure describes the creation and configuration of such a user.Procedure

1. 2. 3. 4.

Log on to the EnvironmentShell environment through the Administration Client. Create a Task Profile for the new user. Choose Security Task Profiles , and then select Add New Task Profile from the Manage Task Profiles action pane. In the Add New Task Profile assistant, enter a suitable task profile name and description. Choose Next and select tasks as listed in the following table:Category Task

Comments Web reporting

Administer Comments Edit Comments Administer Documents Edit Crystal Dashboards Edit Documents

2011-05-10

PUBLIC

13/102

3 3.1

Monitoring of Planning and Consolidation Setting up a Minimal-Access User for Support Category Task

Edit Reports Data Manager Edit Workspaces Cancel Any User Packages Download Data Edit Packages Edit Transformation Files Edit Conversion Files Edit Package Schedules for Any User Run Administration Packages Run Packages Edit Book and Distribution templates Publish Books Run Documents from EPM add-in Edit content of Public Folder Edit Journals Lock/Unlock Journals Post Journals Reopen Journals Unpost Journals View Journals Edit Ownership Manager View Ownership Manager Edit Templates Run Drill Throughs Use Input Forms and Save Manage Audit Manage KPIs Use Automated Variance Analysis Run Audit Reports Run Business Process Flow Reports Run Comment Reports Run Security Reports Run Work Status Reports Use Business Process Flows Use Offline Collection Use Offline Distribution Use System When Offline

Publish

Folder Access Journal

Consolidations Analysis and Collection

Data Audit Automated Variance Analysis System Report

Business Process Flows Collaboration System Security

14/102

PUBLIC

2011-05-10

3 3.2

Monitoring of Planning and Consolidation Monitoring with the Management Console Category Task

Work Status Console

Use Work Status Management View System Logs

5. 6.

Choose Security Users and then select Add new user from the Manage Users action pane. In the Add New Users wizard, enter a suitable user name or use the Search function to find an available user name.NOTE

7. 8.

When you are assigning a user name it may only comprise alphanumeric characters and the underscore (_). That is the characters \ / : * ? < > | ; , & % are not permitted. Choose Next at the next two steps, and then assign the task profile that you created to the user. Check that the user has no teams assigned and only the minimal task profiles assigned and click Apply.

Result

You have created a user with minimal access to the Planning and Consolidation system. Anybody, who needs access for remote support and monitoring can use this user.NOTE

You may need to configure the individual functions and tools to accept this user. For more information, see the documentation for the individual function and tools.

3.2 Monitoring with the Management ConsoleThe Management Console monitors a Planning and Consolidation and Microsoft Platform installation at the hardware, server software, and Planning and Consolidation level to provide system baselines, to allow proactive system performance optimization, and to assist in platform support and troubleshooting.

3.2.1 Information and Actions in the Management ConsoleInformation in the Management Console

The following information is available in the Management Console: The status of Planning and Consolidation processes Performance metrics of the Windows Server Operating System, the SQL Server, and Analysis Services A list of which Planning and Consolidation users are active on the system

2011-05-10

PUBLIC

15/102

3 3.2

Monitoring of Planning and Consolidation Monitoring with the Management Console

Details about what function each user is executing A list of resource-intensive processes The Management Console also has access to a detailed server diagnosis utility.Actions in the Management Console

The following actions can be performed in the Management Console: Activate and deactivate Planning and Consolidation logging End resource-intensive processes Manage logging schedules (archiving and deletion parameters)NOTE

There is no means of changing logging severity levels in the Management Console; system logs are either enabled or disabled. By default, logging is disabled. For more information about enabling or disabling logs, see Managing Event Log Records [page 24]. For information about the severity levels recorded in the logs, see the Status field description in Management Console Logging Fields [page 25].NOTE

Only an authorized system administrator can perform these actions.

3.2.2 Management Console Installation and UseManagement Console Installation

For information about setting up the Management Console, see http://service.sap.com/ instguidescpm-bpc Planning and Consolidation 10.0, version for the Microsoft platform SBOP Plan & Consol 10.0 M Installation Guide . To access the Management Console, open a browser and enter http:///sapmc/ sapmc.html, where describes your Planning and Consolidation application server.Centralized Monitoring in a Server Farm

In an environment where multiple application servers are implemented (for the purposes of providing high availability and network load balancing), each server has its own Management Console. You can use each console to monitor the server on which it is installed. You can also monitor any other server in the server farm environment by selecting the link to any other application servers Management Console from the dropdown list at the top of the Management Console. To provide a centralized view of the application servers, you can use SAP Solution Manager diagnostics to link to the various consoles. Additional monitoring capabilities are provided by CA Wily Introscope. See CA Wily Introscope Integration [page 97].

16/102

PUBLIC

2011-05-10

3 3.2


Prerequisites

The Management Console requires Microsoft SQL Server 2008.

3.2.3 Starting and Stopping Planning and Consolidation RemotelyFor maintenance and support purposes, it is often useful to be able to start and stop Planning and Consolidation remotely. You can do this from the Management Console.Prerequisites

Ensure that you have Java Virtual Machine installed on your client and on your browser Configure your browser to allow Java Enable the Java plug-inProcedure

1. 2. 3.

4.

Start the Management Console http:///sapmc/sapmc.html. When the Management Console opens, choose New. In the New System dialog, enter the Hostname of the Planning and Consolidation system that you wand to address and the Managed Object (the name of the Planning and Consolidation System). After you have entered the Hostname, you can also choose Discover to locate all SAP instances on the server. Choose Finish. Enter your username and password. The Planning and Consolidation instance appears in the in the tree view at the left of the Management Console. You can expand the tree to view the Planning and Consolidation components; selecting a component displays information about the component on the right of the Management Console. Right-clicking on any component in the Planning and Consolidation tree, including the main entry, shows a context menu with the following options: Start Stop Manage DB Connect to server Export Thes options are self-explanatory. If the component is running, Start is grayed out. Similarly Stop is grayed out if the component is not running.

2011-05-10

PUBLIC

17/102

3 3.2


3.2.4 Monitoring the Application and the DatabaseThe Management Console provides performance metrics for the Windows Server Operating System, the SQL Server, and Analysis Services. In addition, many of these metrics are summarized on the Management Console Home page. The information provided for each of these system tiers is detailed in the tables in the following topics.

3.2.4.1 Management Console Home Screen FieldsThe following table lists fields in the Management Console Home screen.Field Description Path

Process ID Image Name Mem Usage

Task ID App ID Name Description Service Name Shutdown After Hits By User

Status Breakdown

CPU Utilization

A numerical identifier that uniquely identifies a process while it runs. The process name The amount of the physical memory used by the process. By default, this column is sorted in descending order, so that the most resource-intensive process appears at the top. The process ID of the currently selected task The model ID of the currently selected task The name of the currently selected task The description of the currently selected task The service name of the currently selected task The value that appears after system shutdown The number of times that each user has accessed Planning and Consolidation Displays a graphical representation of the HTTP status codes in the systems, by percentage. Indicates the current processor load, as a percentage. This number is an average across all of the available

Home Home Home

Task Manager Task Manager Task Manager

Home Home Home Home Home Home Home

Center pane Center pane Center pane Center pane Center pane Center pane Hits by User

Home

Status Breakdown

Home

System Performance (App Server)

18/102

PUBLIC

2011-05-10

3 3.2 Field

Monitoring of Planning and Consolidation Monitoring with the Management Console Description Path

processors or cores available on the machine. Memory: Pages Writes/sec This indicates the number of physical memory pages per second being used by the system. The value is a sum of all physical memory banks in the machine. Available Bytes The physical memory, in available bytes, that can be used by the system without the need to use virtual memory or the page file. The value is a sum of all physical memory banks in the machine. Avg Disk Bytes per Read The average number of bytes per read from the physical disk(s) in the machine Avg Disk Write Queue Length The average number of write requests that were queued for the selected disk during the sample interval Current Disk Queue Length The average number of bytes per read from the physical disk(s) in the machine. This value is an aggregate of all drives on the machine . Current Locks Indicates the number of locks on tables or modedls currently in the database. This number is an aggregate of the locks on all of the databases on the machine. Current Lock Waits Indicates the number of clients waiting for a lock to be released. This is an aggregate of all of the clients waiting for lock releases for all of the databases on the machine. Current Connections The number of current, active server connections Cache Evictions per Second This number indicates the frequency with which the cache is returning information to the disk. If this number consistently ranges from 50 to 100, evaluate your hardware resources.

Home


Home


Home

Server Disk IO

Home

Server Disk IO

Home

Server Disk IO

Home

Analysis Services Connections and Locks

Home

Analysis Services Connections and Locks

Home Home

Analysis Services Connections and Locks Analysis Services Connections and Locks

2011-05-10

PUBLIC

19/102

3 3.2

Monitoring of Planning and Consolidation Monitoring with the Management Console NOTE

The App ID, Name, Description, Service Name, and Shutdown After fields contain a value only when a DLL host is selected. You can use that value determine the identity of the COM object.

3.2.4.2 Management Console Database Server FieldsThe following table describes the management console database server fields:Field Description Path

SPID ECID Status Login Name Host Name BLK DBName Command Request ID OLE DB Calls

Refer to Microsoft SQL Server documentation.

Database Server Database Server Who

Summary Who SQL Server

The number of OLE database calls.CAUTION

Database Server Server Statistics

Summary

SQL

Ensure that this value is never greater than the number of user connections. Active Temp Tables The database server utilizes temp tables to handle data-intensive queries. A lack of temp tables under these conditions can indicate low disk space. Processes Blocked Indicates the number of processes that are blocked because of a query. CPU Utilization Indicates the current processor load, as a percentage. This number is an average across all of the available processors/cores available on the machine. Memory: Pages Writes/sec This indicates the number of physical memory pages per second being used by the system. The value is a sum of all physical memory banks in the machine. Available Bytes The physical memory in available bytes that can be used by the system without the need to use virtual memory or the page file. The value is a sum of all physical memory banks in the machine.

Database Server Server Statistics

Summary

SQL

Database Server Summary Server Statistics Database Server Summary Performance (Database Server)

SQL System

Database Server Summary Performance (Database Server)

System

Database Server Summary Performance (Database Server)

System

20/102

PUBLIC

2011-05-10

3 3.2 Field


Current Locks

Current Lock Waits

Current Connections

Cache Evictions per Second

Database Server Summary Indicates the number of locks on tables or Analysis Services Connections & models currently in the database. This number is an aggregate of the locks on all of Locks the databases on the machine. Database Server Summary Indicates the number of clients waiting for a Analysis Services Connections & lock to be released. This is an aggregate of all of the clients waiting for lock releases for all of Locks the databases on the machine. Database Server Summary The number of current, active server Analysis Services Connections & connections. Locks Database Server Summary This number indicates the frequency with Analysis Services Connections & which the cache is returning information to Locks the disk.RECOMMENDATION

Avg Disk Bytes per Read Avg Disk Write Queue Length Current Disk Queue Length

User Connections OLE DB Calls

If this number consistently ranges from 50 to 100, we recommend that you evaluate your hardware resources. Database Server The average number of bytes per read from Who the physical disks in the machine Database Server The average number of write requests that Database Disk IO were queued for the physical disks in the machine Database Server The current number of queued disk operations. If this number spikes during poor Database Disk IO processing performance, especially during the base or aggregating phases, then the current disk storage solution may not be adequate to support the needs of Analysis Services. Ideally, the value of this performance counter should be as low as possible at any given time. Database Server The number of users with a current, open Server Statistics connection to the database server. Database Server The number of OLE database calls. Server StatisticsCAUTION

SQL Server SQL Server Who

SQL Server

Who

SQL Server SQL Server

SQL SQL

Active Temp Tables

Ensure that this value is never greater than the number of user connections. Database Server The database server utilizes temp tables to handle data-intensive queries. A lack of temp Server Statistics tables under these conditions can indicate low disk space.

SQL Server

SQL

2011-05-10

PUBLIC

21/102

3 3.2 Field


Processes Blocked Operations by Database SPID Status Login Name Host Name BLK By DB Name Command CPU Time Disk IO Last Batch Program SPID 1 Request ID Instance SqlMessage Message Step ID Step Name SqlSeverity JobID JobName RunStatus RunDate RunDuration Operator Emailed OperatorNetsent OperatorPaged RetriesAttempted Server Current Locks

Indicates the number of processes that are blocked because of a query. A graphical display of the current, active processes, categorized by database. Refer to Microsoft SQL Server documentation.

Database Server SQL Server Server Statistics Database Server SQL Server Operations by Database Database Server SQL Server Who2

SQL Who

Refer to Microsoft SQL Server documentation.

Database Server SQL Server Server Agent Statistics

SQL

Current Lock Waits

Current Connections

Database Server Analysis Services Indicates the number of locks on tables or Analysis Services Connections & models currently in the database. This number is an aggregate of the locks on all of Locks the databases on the machine. Database Server Analysis Services Indicates the number of clients waiting for a Analysis Services Connections & lock to be released. This is an aggregate of all of the clients waiting for lock releases for all of Locks the databases on the machine. Database Server Analysis Services The number of current, active server Analysis Services Connections & connections. Locks

22/102

PUBLIC

2011-05-10

3 3.2 Field


Cache Evictions per Second

Database Server Analysis Services This number indicates the frequency with Analysis Services Connections & which the cache is returning information to Locks the disk.RECOMMENDATION

Avg Disk Bytes per Read Avg Disk Write Queue Length Current Disk Queue Length

If this number consistently ranges from 50 to 100, we recommend that you evaluate your hardware resources. The average number of bytes per read from the physical disks in the machine. The average number of write requests that were queued for the physical disks in the machine This counter represents the current number of queued disk operations. If this number spikes during poor processing performance, especially during the base or aggregating phases, then the current disk storage solution may not be adequate to support the needs of Analysis Services. Ideally, the value of this performance counter should be as low as possible at any given time.

Database Server Analysis Services Analysis Services Disk IO Database Server Analysis Services Analysis Services Disk IO Database Server Analysis Services Analysis Services Disk IO

3.2.5 Alert Monitoring with the Management ConsoleYou can set alerts in the Management Console, to provide a visual cue when designated server thresholds are exceeded. For example, you can set an alert when CPU Utilization exceeds a certain percentage.Function Navigation What You Need to Know

Home System Performance (App Server) Setting alerts on the application server Choose Set Thresholds.

Database Server Summary Setting alerts on the database server Choose Set Thresholds.

System Performance (Database Server)

The System Performance panel is highlighted by a red border while the threshold is exceeded. The System Performance panel is highlighted by a red border while the threshold is exceeded.

2011-05-10

PUBLIC

23/102

3 3.2


3.2.6 Identifying and Stopping a Resource-Intensive ProcessTo identify a resource-intensive process, examine the Task Manager on the Home screen. By default, the processes in this table are sorted by descending order, in terms of memory usage. The most resourceintensive process appears at the top. To stop a process, select it in the Task Manager on the Home screen, and choose Stop Process. For more information, see Management Console Home Screen Fields [page 18].NOTE

You can set the recovery options for a process to determine whether or not it restarts automatically after you end it using Management Console. To examine and modify these settings in Microsoft Windows, choose Start Administrative Tools Services . In the context menu of the service, choose Properties. On the Recovery tab, select the conditions under which the service should restart.

3.2.7 Performing a Detailed Server DiagnosisIn the Management Console, you can run a diagnostic utility to create a detailed report that includes information about: The status of the various component services Database connectivity Microsoft Internet Information Services (IIS) configuration To run a detailed server diagnostic, choose Planning and Consolidation Logging Server Diagnostic .

3.2.8 Management Console Event Logs 3.2.8.1 Managing Event Log RecordsThe debug logs in Planning and Consolidation are optional, and (by default) not active. However, the logging section does display all of the status and error messages that Planning and Consolidation issues during normal operation. In the logging area of the Management Console, you can: Activate or deactivate debugging logs Set the amount of time that elapses before logs are deleted or moved to a history table in the databaseFunction Navigation What You Should Know

Activate or deactivate optional

Planning and Consolidation Logging Options Manage Debug Logs

Admin

For performance reasons, do not enable debugging logs on an open-ended basis in a production environment. Enable debugging

24/102

PUBLIC

2011-05-10

3 3.2

Monitoring of Planning and Consolidation Monitoring with the Management Console Navigation What You Should Know

Function

component logging Planning and Consolidation Logging Admin Archive current history Options Manage System Logs Move current logs to history logs

Delete all history logs Archive dated history logs Delete dated history logs

Planning and Consolidation Logging Admin Options Manage System Logs Delete history logs Planning and Consolidation Logging Admin Options Schedule Move current logs if Planning and Consolidation Logging Admin Options Schedule Purge history logs if

logs for just the minimum time needed to complete your analysis. This function moves all of the logging messages currently being displayed on the screen to the database. Current logs are saved in tblLogs, while archived logs are saved in tblLogHist. This function deletes all history logs in the system. These logs are moved to the tblLogHist database table. This function deletes history logs, based on conditions that you in the system.

3.2.8.2 Management Console Logging FieldsThe fields listed in the table below can be found in the logging section. To access these fields, choose Planning and Consolidation Logging Planning and Consolidation Logging .Features

You can search for records by any of the fields listed below. However, because of a Management Console limitation, we recommend that you avoid the use of time parameters in a search.Field Description

ID

The job or process ID.NOTE

System Job Status

Date

This field can be double-clicked to open the Planning and Consolidation Logging dialog box, which contains message metadata, including detailed information or error messages (where applicable). This field displays the source Planning and Consolidation component. The job or process name The severity level of the logging message: Information (contains descriptive information about the event) Warning (this event may warrant further investigation) Error (this log entry notifies you of an unexpected or adverse outcome) The date on which the process executed.

2011-05-10

PUBLIC

25/102

3 3.3

Monitoring of Planning and Consolidation Log and Trace Files List

3.3 Log and Trace Files ListThis release of Planning and Consolidation creates the following set of model-specific log and trace files independent from those of the Management Console, which are in the logging directory of each Planning and Consolidation host: Trace files Bpctrace.x.log located in /logging/trace, where x is a number between 0 and 9, such as bpctrace. 5.log. The default severity of traces is Error. Log files Bpclog.x.log located in /logging/log, where x is a number between 0 and 9, such as Bpclog.5.log. The default severity of logs is Info.

3.4 Other Planning and Consolidation Log FilesThis section details log files, from an operations perspective.

3.4.1 Miscellaneous Log FilesThe following table contains a list of miscellaneous Planning and Consolidation log files:Log File Notation Location Description

osoftdiagnostic.txt HTTPERR *.log

serverpath/server management/ systemroot/LogFiles/ systemroot/LogFiles/W3SVC1/

Output of the SAP Planning and Consolidation Server Diagnostics program IIS HTTP error log files General IIS log files

3.4.2 Trace File for Debugging LogicYou can turn on tracing for script logic and business rules when you need to troubleshoot a particular script or rule. We recommend that this is only used by experienced Planning and Consolidation consultants and support. We also recommend that these files are removed periodically since they take up a considerable amount of space. The activity is recorded in a file called debuglogic.log and stored in \webfolders \\\privatepublication\\.

26/102

PUBLIC

2011-05-10

3 3.5

Monitoring of Planning and Consolidation Central Computing Management System

3.4.3 Data Manager Log FilesWhenever you use a Data Manager package to move Planning and Consolidation data, the system creates a log file. This file can be useful in troubleshooting the execution of packages. We recommend that these files are removed once the packages have completed since they take up a considerable amount of space. These logs are stored in \webfolders\\\privatepublication \\tempfiles. The name of the log file contains the following details: The name of the package A timestamp The extension .LOGEXAMPLE Validatetransformation20090915211503.log

3.5 Central Computing Management SystemYou can set up Central Computing Management System (CCMS) within SAP Solution Manager for monitoring your SAP Planning and Consolidation system

3.5.1 Monitoring with the Central Computing Management SystemYou can set up Central Computing Management System (CCMS) within SAP Solution Manager for monitoring .NET application servers within your SAP Planning and Consolidation system. You can set up log file and process monitoring to monitor managed hosts, which are the SAP Planning and Consolidation application servers. Monitoring in the central monitoring system is based on SAP CCMS agent functionality, which you must install on the monitored hosts. For information about setting up CCMS for use with Planning and Consolidation, see SAP Note 1379213. After setting up and configuring monitoring for SAP Planning and Consolidation, log on to SAP Solution Manager, then access CCMS. In the SAP Menu, select Tools CCMS Control/Monitoring CCMS Monitor Sets (transaction code RZ20) . The following monitor sets are available in CCMS within SAP Solution Manager for Planning and Consolidation:

2011-05-10

PUBLIC

27/102

3 3.6

Monitoring of Planning and Consolidation Change and Transport System

Availability Monitoring

A simple Generic Request and Message Generator (GRMG) scenario for SAP Planning and Consolidation is available. This checks the availability of the SAP Planning and Consolidation application server, and presents the status of its current availability.Error Monitoring

The log file for SAP Planning and Consolidation is monitored for error patterns. The monitor present its status and alerts according to the presence of error messages in the SAP Planning and Consolidation log, which is located in \logging\log. If errors occur in this log, you can display them in transaction CCMS by selecting Open Alerts.Operating System Monitoring

The servers hosting the SAP Planning and Consolidation application are monitored for resource consumption. Operating system metrics such as overall CPU and memory consumption are reported. In addition, the following operating system processes are monitored: w3wp.exe (Microsoft Internet Information Services application pool process) dllhost.exe (DLL application process) BPCSendGovernor.exe (SAP Planning and Consolidation Send Governor process) You can customize the thresholds for alert triggering to suit your business needs. You can access technical configuration details at http://server_name:port/osoft/app/ SMDWebService/BPCSMDService.asmx.

3.6 Change and Transport SystemThe Change and Transport System (CTS+) supports the movement of transportable content between Planning and Consolidation servers.Prerequisites

The Change and Transport System requires the following prerequisite applications: SAPJco3 The SAP Java Connector (SAP Jco) is a toolkit that allows a Java application to communicate with any SAP system. di_cmd_tools This is part of the SAPJco toolkit. Java JDK The Java Development Kit.

28/102

PUBLIC

2011-05-10

3 3.7

Monitoring of Planning and Consolidation Checking COM+ Objects

Vcredist_x86.exe Microsoft Visual C++ redistributable version. For information about downloading and installing these applications together with information about environmental variable settings and configuring CTS+, see the Application Help.Features

The purpose of transporting content with CTS is to ensure that you have two or more Planning and Consolidation servers with the same content, and look and feel by transporting configurations and content from one system into another. This means that, for example, that you can duplicate the look and feel of your development environment in the quality and production environments. CTS is an export tool. You need to select the configurations and content for transport, and CTS creates a transport package. You can download this transport package and import it on the target server. You can use the CTS tool for the following activities: Selecting the content to include in the transport Attach additional objects to a transport request View the objects in a transport request Export the selected content to the transport package Organize the transport CTS does not provide any means of tracking or monitoring between the source and target systems. You must ensure that you always use the correct transport packages or existing content on the target system may be overwritten.More Information

For more information about CTS+, and how to transport content, see the Application Help.

3.7 Checking COM+ ObjectsYou can check the state of your COM+ components using the OS command BPCCOMPlusCheck. You can access and use this command in the SAP Solution Manager Diagnostics OS Command Console.NOTE

As of Planning and Consolidation 10.0, to improve performance, only the following COM+ applications are used: For Planning and Consolidation: Data Manager, which has components that handle some Data Manager tasks x86, which has components for the services control wrapper and transfer members

2011-05-10

PUBLIC

29/102

3 3.7

Monitoring of Planning and Consolidation Checking COM+ Objects

For the BUI: .NET Data Helper x86, which has application printing componentsFeatures

This tool checks the existence of all Planning and Consolidation COM+ applications and classes. If the classes exist, the tool tries to create an instance for each class. To resolve an error for a particular COM+ component, do the following: 1. Check that the component exists in the Global Assembly Cache (GAC) and, if it does not exist, register using gacutil/i . 2. Use the regsvcs .NET command to register COM+. 3. Verify that the COM+ application exists using Component Services. If it does not exist, do the following: 1. Create a new empty COM+ application manually. 2. Drag and drop the VB assembly into the empty application 4. Change Account for the registered COM+ object that is in the Identity tab of the properties. 5. Change COM+ Security (Connect / Impersonate). To execute the COM+ check tool and display its results in SAP Solution Manager Diagnostics, access SAP Solution Manager then choose Workcenter Root Cause Analysis (Transaction SOLMAN_WORKCENTER) Host Analysis OS Command Console . In the OS Command Console application, select the host, OS Command Group SAP BPC and execute the command BPCComplusCheck with Send Command.

30/102

PUBLIC

2011-05-10

4 4.1

Management of Planning and Consolidation Managing Your Planning and Consolidation Servers

4 Management of Planning and Consolidation

SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively manage all SAP components and complete all tasks related to technical administration and operation.

4.1 Managing Your Planning and Consolidation ServersYou use the Server Manager to manage a Planning and Consolidation server. The Server Manager is accessible on the .NET application server. With the Server Manager, you can do the following: View server information. See Viewing Server Information [page 32]. Change client and server options. See Client Options [page 32] and Server Options [page 33], respectively. Configure the System Landscape Directory (SLD). See Configure System Landscape Directory [page 34]. Configure the Central Management System (CMS). See Configure Central Management System [page 35]. Change the credentials for component services. See Changing the Credentials for Component Services [page 40]. Define user groups within Active Directory domains. See Domain User Group Setup [page 39]. Back up and restore environments. See Backing up and Restoring Environments [page 44]. Change the Server Manager language by selecting Options Language . System administrators can change environment parameters and model parameters within the Administration Client (see Environment Parameters and Model Parameters within the application help in the SAP Library at http://help.sap.com.) For information on the tasks that system administrators and nonsystem administrators can perform in Server Manager, see Server Manager Security [page 42].

2011-05-10

PUBLIC

31/102

4 4.1


4.1.1 Viewing Server InformationYou can use the Server Manager to view information about your Planning and Consolidation server components.Features

The System Information window shows information about the server, including its version, the operating system version and available memory. You can access the System Information window by doing the following: Start Server Manager by selecting (All) Programs SAP Server Manager from the Windows Start menu on your .NET application server. The System Information window opens by default. You can click the Refresh button to refresh the information on the screen.More Information

Performing a Detailed Server Diagnosis [page 24] Managing Your Planning and Consolidation Servers [page 31] Monitoring with the Management Console [page 15]

4.1.2 Client OptionsThis function allows you to set or change options related to Planning and Consolidation clients.Features

You can access the Client Options screen from the Server Manager by selecting Options Client Options. Click Update to save your changes. You can set the following option: Client Auto Update You can use the Client Auto Update program to set up the server so that it determines if a connecting client upgrade is necessary. If the system finds a newer version, it prompts you to perform the upgrade. If turned off, clients must be installed manually.NOTE

If users without administrator rights use the auto update, enter an administrator ID and password in the Admin ID and Admin password fields, respectively. The administrator ID should be a member of the local administrators group on all the computers running the auto update. This setting is not needed if all users have administrator rights.

32/102

PUBLIC

2011-05-10

4 4.1


4.1.3 Server OptionsThis function allows you to change options related to Planning and Consolidation servers. Many of the server options are set during the installation process.Features

You can access the Client Options screen from the Server Manager by selecting Options Server Options. After modifying the options, click Update to save your changes.Server Option Value Description

SQL Server Name Instance name Port number Provider OLAP Server Name Instance name Port number File Share Server Name Local data path Application Server Name External server name Virtual server name Website HTTP compression Protocol Port number Authentication type

Scheduler Server Name

The name of the SQL DB server. Defaults to the local server. The SQL instance name. If left blank, the default instance is used. The port number. The default for the SQL Server is 1443. The only available value is SQL. The name of the OLAP server. The OLAP instance name. The instance name can be changed. The default value is 2383. The default value is the name of the File Share server that should be the computer name (NetBIOS name). Where the data files are saved on File Share server. By default, \Data. The name of the application server. TCP/IP address for accessing the server from outside a firewall. The server name for load balancing if it is installed. The IIS Web site name, if it differs from the default Web site. The default value is No. (Yes provides better performance in some situations.) The available values are http or https. The default value is http. The port number to which the application server connects. 80 is the default for http, 443 is the default for https. Note: If you have chosen SAP BusinessObjects User Management System in the installation screen, Authentication type does not appear (as that IIS authentication type is Anonymous in CMS mode). Windows or Kerberos. The default is Windows. If you change this value from Windows to Kerberos, you must make some additional Server Option changes. See Kerberos Authentication Settings [page 42]. The name of the server used for scheduling, usually the application server, for example, GMPV50072862B. If you have multiple application servers, select the appropriate one.

2011-05-10

PUBLIC

33/102

4 4.1


4.1.4 Configuring the SLD Data SupplierThe System Landscape Directory (SLD) Data Supplier is the central directory of all of your system landscape information. It contains a repository of all SAP software and a representation of the technical systems, that is, the hosts on which software is installed as well as the software products and components, versions, support packages and patches that are currently installed. The software components of a product version are installed on hosts and form systems that are visible to the administrator. An administrator must have knowledge about all the systems that are in the landscape and about the versions, support packages, and patches of the software components that are installed on these systems. This kind of information is stored in the SLD and is called the Landscape Description (LD). The SLD is also a repository of software components that can theoretically be installed in the landscape. This kind of information is stored in the SLD as a Component Repository (CR). SLD data suppliers automatically register the systems on the SLD server and keep the system information up-to-date. They collect and send data about the systems to the SLD. For every newly discovered system or component, the SLD creates an association to the corresponding entry in the Component Repository. Thus, the SLD provides reliable and up-to-date system landscape information.Prerequisites

The SLD Data Supplier requires the following components to work with Planning and Consolidation: Application server Java The most recent Component Repository (CR) Content a recent version of the Common Information Model (CIM) For a definitive list of version requirements for these components, see the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam. Search on Planning and Consolidation.NOTE

For more information about installing the CR Content and CIM, see SAP Note 669669.Features

You can access the Configure SLD screen from the Server Manager by selecting Options Configure SLD . Enter data as follows: Enable If the check box is selected, the Planning and Consolidation system transfers system data to the SLD server periodically. Server host

34/102

PUBLIC

2011-05-10

4 4.1


The host on which the SLD server is deployed and running. Port The HTTP or HTTPS port at which the SLD server is listening. User name The user name associated with the SLD credentials. Password The user password associated with the SLD credentials. Transfer interval (hours) The interval (in hours) when the Planning and Consolidation system periodically transfers currently active data to the SLD server. This is only relevant if the Enable check box is selected. Use HTTPS This indicates whether the data is transferred via secure connection or not. System ID This is automatically completed by the system and is read-only in this view. The System ID (SID) is a three digit string starting with a Capital letter followed by a combination of numbers or letters. This concept is used by all SAP systems. Customers maintain SIDs in the SAP Service Marketplace (SMP) for Planning and Consolidation systems so that they can log error messages under the relevant SID of their Planning and Consolidation system. Since customers can choose a SID in the Service Marketplace, customers should also enter the same SID during the Planning and Consolidation Installation so that the system in Solution Manager can be identified based on the same SID as in SMP Update Click Update to update the information in SLD. This sends your system information (such as product version, components, and hardware information of the host, for example, number of CPUs and memory size) to SLD. This is done by an HTTP (or HTTPS) post request to the SLD server.

4.1.5 Configure the Connection to the Central Management SystemThis function allows you to set or change configuration options related to the Planning and Consolidation server authentication mode.Prerequisites

The Central Management System (CMS) is installed and the Planning and Consolidation system has an administrator-level ID and password to the CMS.

2011-05-10

PUBLIC

35/102

4 4.1


To log on to CMS as an administrator, you need the following information:Field Description

System name Trusted CMS name

Authentication type Administrator ID Administrator password Group name

Web service URL

CMS system name (server name:port number), for example, CMSServer:6400 CMS system name If a CMS cluster name exists, use the cluster name (multiple names should be separated by a comma ,). Select the appropriate value from the list The user identifier of the dedicated administrator account Password for the administrator account Group name of the SAP BusinessObjects Enterprise users, who have access to the system This group name is filtered as the default when adding a user in Planning and Consolidation Administration. (Multiple names should be separated by a comma ,.) The default is http://:8080/dewbobje/ If your system is configures with an SSL protocol and a specific port, amend this protocol accordingly.

Features

The following authentication modes are possible: Windows CMS The Server Manager Options menu has different entries according to the authentication mode selected.Windows Authentication Mode

From the Server Manager Options menu, you have the following entries that are specific to the Windows authentication mode: Define System User Groups Here you can define groups of Windows users that have similar system responsibilities. Enable CMS Authentication mode Switch from Windows authentication to CMS authentication.NOTE

If you have more than one server, you need to change the authentication mode on all servers.CAUTION

Once CMS authentication is enabled, it is not possible to revert to Windows authentication.CMS Authentication Mode

We recommend CMS authentication mode. On installation of Planning and Consolidation, CMS authentication mode is selected by default.

36/102

PUBLIC

2011-05-10

4 4.1


From the Server Manager Options menu, you have the following entries that are specific to the CMS authentication mode: Configure CMS The following parameters can be defined in the SAP BusinessObjects User Management System view:Field Description

The name of the system CMS system name If a CMS cluster name exists, use the cluster name (multiple names should be separated by a comma ,). Authentication type Select the appropriate value from the list Administrator ID The user identifier of the dedicated administrator account Administrator password Password for the administrator account Group name Group name of the SAP BusinessObjects Enterprise users, who have access to the system This group name is filtered as the default when adding a user in Planning and Consolidation Administration. (Multiple names should be separated by a comma ,.) Cache expiration duration The time (in minutes) after which the cache is cleared Heartbeat interval After a period of inactivity, the CMS session may expire at the server, after which the Planning and consolidation system cannot communicate with the server The Heartbeat function periodically simulates activity to keep the session active. Set the Heartbeat interval (in minutes) to a suitable level for the CMS session. System name Trusted CMS name

Click Update to update the user management system with these new values. CMS Migration Select this option to migrate all current Windows user authentication information to CMS user authentication information. To use this menu option, you should be logged on to CMS as an administrator. If you are not already logged on, enter the correct logon information when prompted. You are guided through the following actions: Select one or more Windows environments to migrate to CMS from the list that is displayed. The system displays a list of Windows user IDs for the selected environments. Click 1. Validate user to enable the system to align Windows and BusinessObjects user IDs. A green tick indicates that a corresponding BusinessObjects user exists while a red cross means that there is no BusinessObjects user corresponding to the Windows user ID. Click 2. Migrate, and then click OK to migrate the validated Windows user information to CMS. When the migration is complete, click 3. View result to view a detailed result log of the migration process.

2011-05-10

PUBLIC

37/102

4 4.1


If required, you can save a copy of the result log. Set complete Click 4 Set complete. The migrated environments are set as CMS mode environments. These environments are no longer visible in the migration wizard.More Information

Migrating Users to the Central Management System [page 38]

4.1.6 Migrating Users to the Central Management SystemThe Central Management System (CMS) migration wizard validates existing Windows users against corresponding CMS users. Then the wizard can migrate all existing user information to CMS user information. Existing Windows users that do not already exist in a CMS database should be set up individually in advance.Prerequisites

CMS is installed and the Planning and Consolidation system has an administrator-level ID and password to the CMS.Procedure

You access the CMS migration wizard from the Server Manager. Choose Options CMS Migration Wizard . If you are not already logged on, you are required to log on to CMS as an administrator. 1. Validate user The wizard displays a list of environments that can be migrated to CMS Select one or more of these environments The wizard displays list of the Windows user IDs assigned to these environments Click 1. Validate user 2. Migrate The wizard validates the existing Windows users against corresponding CMS users. A green tick indicates that a corresponding BusinessObjects user exists. A red cross means that a corresponding BusinessObjects user does not exist at the CMS server. In this case, click Cancel to exit the wizard and set up each user in CMS before returning to the wizard. When all the required users are validated, click 2. Migrate.

38/102

PUBLIC

2011-05-10

4 4.1


3.

4.

View result All validated Planning and Consolidation user information (those users marked with the green tick) in database table or file system are changed to CMS user information. Click 3. View result to obtain a detailed result log. You can save the result log if required. Set complete Click 4 Set complete. The migrated environments are set as CMS mode environments. These environments are no longer visible in the migration wizard.

Result

Users can log on to Planning and Consolidation through CMS authentication.NOTE

If you have owner and reviewer properties defined in your dimension worksheets, you must update them manually if they contain any Windows user information.More Information

Configure Central Management System [page 35]

4.1.7 Domain User Group SetupRather than allowing all users within Active Directory (AD) to access Planning and Consolidation, you can limit the pool of users by adding them to a particular domain and then giving access to only those users. This is important because if you try to add a user from the entire AD, the system may time out while searching.Features

You can define user groups from the Server Manager by selecting Options Define system user groups. You use the following features for defining a user group: Choosing user group names The default group name is Domain users if a domain user installs the Planning and Consolidation server. The default group name is Local users if a local user installs the Planning and Consolidation server. The group name is displayed in the Add New Users assistant in the Administration Client. You can modify the settings for an existing group by selecting the name of the group from the list. Defining Filters You use filters to define user groups. The following table includes examples of filters you can define:

2011-05-10

PUBLIC

39/102

4 4.1

Management of Planning and Consolidation Managing Your Planning and Consolidation Servers Scenario Example Description

Single organizational unit (OU) Multiple OUs

OU=Marketing OU=Sales;OU=Marketing

Multiple OUs from a single container

OU=Sales;OU=Marketing;CN=Users

A group (or user) in an OU

CN=DM,OU=Sales

Multiple groups (or CN=DM,OU=Sales;CN=DM,OU=Sales2 users) in an OU (when multiple groups are in a single or different groups)

Mixed condition

CN=DM,OU=Sales;CN=FR,OU=Sales2; CN=HR,CN=Users

Finds users of the Marketing OU. Finds users of the Sales and Marketing organizational units. Finds users of the Sales and Marketing organizational units and the Users container. Finds users of the DM group in the Sales organizational unit. Finds the users of the DM group in the Sales2 organizational unit and the users in the DM group in the Sales organizational unit. Finds users of the DM group in the Sales organizational unit, users of FR group in Sales2 organizational unit, and users of HR group in the Users container.

4.1.8 Changing the Credentials for Component ServicesWhen the Planning and Consolidation server is installed, the installing user provides service IDs and passwords. The system uses the IDs and passwords to register services on the server. We recommend that you do not change the password. However, if required, for example, if one of the Windows passwords is changed, you must change the password for the applicable Planning and Consolidation service. If the passwords do not match, the system may not work correctly. This procedure describes how to reset the credentials for your Planning and Consolidation component services.NOTE

If you only need to change the password for a service user account, do the following: from the Server Manager, select Server Reset Logon Credentials . Enter the COM+ ID and password, then click Update.

40/102

PUBLIC

2011-05-10

4 4.1


Prerequisites

The password has been changed in Microsoft Windows.Procedure

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

Select Start Programs Administrative Tools Component Services. Navigate to COM+ Applications. Select Component Services Computers My Computer COM+ Applications. Select a service, for example, OSoftUserManage, right-click, and select Properties. Select the Identity tab, enter the new password in the Password and Confirm Password fields, then click OK. Repeat the last two steps for each of the remaining services.

4.1.9 Setting up FirewallsIf your Planning and Consolidation server is behind a firewall, you must make a few changes to your setup. You must define external IP addresses and open a firewall port.Features

Defining external IP addresses You must define external IP addresses for Planning and Consolidation components for each environment you want users to be able to access across the firewall. You change the following Server Options [page 33]: Application Server External Server name This is the external IP address or fully qualified domain name where the application server resides. Reporting Services Server External server name This is the external IP address or fully qualified domain name where the Reporting Services server resides. Opening Firewall Ports You must open the HTTP default port (80), and optionally, port 443 if you want users to access the system through a secure sockets layer (SSL). If you are authenticating through a firewall with Active Directory authentication, you must have a secured channel open and port 445 open for inbound and outbound traffic if you have NetBT (NetBIOS over TCP/IP) disabled. If NetBT is enabled, you must have port 139 open for inbound and outbound traffic. You need to:

2011-05-10

PUBLIC

41/102

4 4.1


Define external IP addresses in the Server Options [page 33] window. Open the TCP/IP ports from your firewall software.

4.1.10 Kerberos Authentication SettingsIf, during the server installation, you select Kerberos as the authentication type (as opposed to the default Microsoft Windows authentication), the system automatically makes some default settings for IIS and Web.config. After the installation, if you want to change the authentication type from Microsoft Windows to Kerberos, you must change the settings for IIS and Web.config manually. In addition, settings for some third-party applications, such as Windows Server Active Directory and Microsoft Internet Explorer, are not supported by the installation and should be set manually, as described below.Features

The following table lists the setting for third-party applications required for Kerberos authentication:3rd Party Description

IIS

Only Integrated Windows Authentication for osoft and fp_client virtual directory is selected in directory security on the application server. Do not select Basic authentication. (There is no fp_client virtual directory on the application server.) Active Directory settings for Select the Trusted computer for delegation option for the application server in delegation the computer properties of Active Directory. Select the Account is trusted for delegation option in the user properties of Active Directory. Local intranet settings of Internet The URL for the application server is added to the local intranet settings Explorer (IE) in IEr. Select the Automatic logon only in Intranet Zone option in the security settings of the local intranet. The URL for the application server is added to the intranet settings in IE of the client. Select the Automatic logon only in Intranet Zone option in the security setting of the local intranet. Integrated Windows authentication option Enable the Integrated windows authentication option in IE on the client. in IE

4.1.11 Server Manager SecurityThis topic lists the tasks that a system administrator (the SYSADMIN user specified during the installation) can perform in the Server Manager.

42/102

PUBLIC

2011-05-10

4 4.2

Management of Planning and Consolidation Asynchronous Interfaces and Data Transfers Navigation Path

Server Manager Task

Launch the Server Manager View the server information Run server diagnostics Reset logon credentials Set up and maintain debug users Choose the server language Define system user groups

Not applicable Server Information Server Diagnostic Server Reset Login Credentials Server Maintain Debug Users Options Language Options Define System User Groups

4.2 Asynchronous Interfaces and Data TransfersAsynchronous Interfaces

There are the following asynchronous data exchange interfaces in Planning and Consolidation: EPM add-in for Microsoft Office data transfers (specifically, the EPMSaveData and reporting functions) Data Manager package executionData Consistency in the Event of an Interruption in Data Transfer

Data consistency is automatically managed by the system in the event of an interruption in the transfer of data between a client and the server. For instance, an interruption can occur due a workstation crash or restart. Upon resumption of the data transfer, Planning and Consolidation checks for differences between data that has already been transferred and the data that remains to be transferred. Planning and Consolidation only transfers data that was not previously transferred. Given that data consistency is preserved by the system in this way, there is no separate interface for managing interrupted data transfers.NOTE

If a Data Manager package fails to finish executing, you may experience an issue in which you cannot clear the status of the package. This does not affect the integrity of the data. For information about clearing the package status, see Troubleshooting in Data Manager [page 94].

4.3 Stored Configuration ValuesFor information about the variables that are set during the installation process, see http:// service.sap.com/instguidescpm-bpc Planning and Consolidation 10.0 version for the Microsoft platform SBOP Plan & Consol 10.0 M Installation Guide .

2011-05-10

PUBLIC

43/102

4 4.4

Management of Planning and Consolidation Backing up and Restoring Environments

4.4 Backing up and Restoring EnvironmentsSAP Planning and Consolidation Server Manager provides a facility for backing up and restoring environments. This can be useful during implementation, system recovery, and infrastructure maintenance. The following are important considerations when using Backup and Restore: Backup and Restore are comprehensive and complete. There is no incremental update, there is no partial restore. All data, master data, and metadata is included. Backup and Restore also transfers all security profiles. The backup copies all files in the \webfolders and the SQL database. Your OLAP data is recreated upon restoring an environment. The backup file does NOT include audit or logfile information. Restoring an environment over an old one deletes everything from the old one, except its audit information. When restoring an environment, Planning and Consolidation creates the storage model of the write-back OLAP partition to be MOLAP. You should reset the storage model to be a write-back OLAP partition.

4.4.1 Backing up EnvironmentsYou can back up an environment when you want to archive it or you want to move it from one Planning and Consolidation server to another. For example, you would back up an environment before moving it from a development to production server, or if you are installing a new version Planning and Consolidation on a new server. After you back up an environment, you can move it to another server using the Restore task in the Server Manager. See Restoring Environments [page 45]. You can back up environments located on a single server or in a multiserver configuration. The backup process creates three folders. The following table describes the folders and what is contained in each.Folder Description

FileDB SQL Webfolder

Contains the .zip file that contains the files in the backed up FileDB folder. Contains a .bak file that contains the backed up SQL database. Contains the .zip file that contains the files in the backed up Webfolder folder.

NOTE

The OLAP databases are not backed up. They are re-created during the restore procedure.

44/102

PUBLIC

2011-05-10

4 4.4

Management of Planning and Consolidation Backing up and Restoring Environments CAUTION

Use this procedure only if you want to back up an environment. Contact your support representative for information about backing up an environment manually.NOTE

The normal backup process backs up any Planning and Consolidation configuration files that reside on the file share. All application configuration information is stored in the Planning and Consolidation database, and is backed up and restored with the database. Files and directories that are used for logging and configuration that reside on your local machine are not automatically backed up. You should include these files and directories in your regular file back up procedure.Procedure

To back up an environment: 1. From your application server, select Windows Start (All) Programs SAP Server Manager . 2. Select Environment Backup Environment . 3. Select the checkbox next to one or more environments that you want to back up.NOTE

4. 5.

Select the Select All Environments checkbox to select all the environments in the list. In the Destination field, enter the path that describes where you want to save the backed up files, or click the browse button to search for the target backup folder. If the SQL database is on a separate server, select the Use backup files path on a remote SQL server checkbox, and enter the name of the path to the remote SQL database, for example, \\ServerName \O5Backups. This folder must be shared and writeable.NOTE

6. 7. 8.

The Use backup files path on a remote SQL server option is also used when a DMZ configuration exists between the SQL server and the application server. Click Next. Click OK, then click Close. To move the backed up environments to one or more servers, see Restoring Environments [page 45].

4.4.2 Restoring EnvironmentsYou restore environments when you want to take an environment that has been backed up, and load it on to a different Planning and Consolidation server. The destination server must have access to the directory that contains the backed up files. You can restore an environment on a single server or multiserver configuration.

2011-05-10

PUBLIC

45/102

4 4.4

Management of Planning and Consolidation Backing up and Restoring Environments

Procedure

To restore an environment: 1. From your application server, select the Windows Start (All) Programs SAP Server Manager . 2. Select Environment Restore Environment . 3. In the Step 1 dialog box, do one of the following: If it is a single server configuration, enter the path to the folder that contains the backed up environment in the Envrironment Folder field, or click the browse button to search for the folder. Click Next. If it is a multiserver configuration, do the following: 1. You can leave the Environment Folder field blank. 2. In the Webfolder field, enter the path and name of the zip file that contains the backed up Webfolder folder, or click the browse button to search for the file. 3. In the FileDB field, enter the path and name of the zip file that contains the backed up FileDB folder, or click the browse button to search for the file. 4. In the SQL database field, enter the path and name of the SQL server .bak file, or click the browse button to search for the file. If the SQL database is on a separate server, select the Use backup files path on a remote SQL server check box and enter the name of the path to the remote SQL database, for example, \\ServerName\O5Backups. This folder must be shared and write-able.NOTE

4.

5. 6.

The Use backup files path on a remote SQL server option is also used when a DMZ configuration exists between the SQL server and the application server. 5. Click Next. In the Step 2 dialog box, do one of the following: If it is a single server configuration, you can leave the fields blank. The current server is assumed. Click Next. If it is a multiserver configuration, enter the server names for each component. If the database server is installed as a non-default instance, enter \. Click Next. In the Step 3 dialog box, wait until the restore process is complete, then click Close. The restore procedure resets the connection strings on the application server to the internal server name. So if you require users to access the environment from an external IP address, you must modify those settings.

46/102

PUBLIC

2011-05-10

4 4.5

Management of Planning and Consolidation Periodic Tasks

7.

8.

When restoring an environment, the restore procedure creates the storage model of the writeback OLAP partition to be MOLAP. You should reset the storage model to be a write-back OLAP partition. For more information, see Installing SQL Server in the Installation Guide. Save each model in the environment by doing the following: 1. From the Administration Client, select a model node under Model. 2. Select Modify Model from the Manage Models action pane. 3. Select Modify Model without making any changes. 4. Repeat for each model.

4.5 Periodic Tasks 4.5.1 Scheduled Periodic TasksThe application optimization task can be scheduled periodically but can also be carried out as required.

4.5.1.1 Optimizing ModelsTo maintain good performance, models need to be optimized. There are no universal guidelines for the frequency with which you should optimize models. Optimization frequency depends on the characteristics of your hardware environment and your model. However, you can set the system to remind you to optimize the model when the system database grows to a certain size. You can use either the Administration Client or the Data Manager to optimize applications. In the Data Manager, optimization tasks can be added to administrative packages. The optimization process is included in the AdminTask_Optimize sample package. For more information about modifying, running, and scheduling packages, and using the Administration Client to manually optimize models, see the application help on SAP Library: http://www.help.sap.com.

4.5.1.1.1

Optimization Options

The optimization options interact with the three types of data storage in different ways. For more information, see Data Storage Types and the Optimization Process [external document]. The following table lists the optimization options available in Planning and Consolidation, and the effect of each on the various storage types:

2011-05-10

PUBLIC

47/102

4 4.5

Management of Planning and Consolidation Periodic Tasks Description

Optimization Type

Lite Optimization

Incremental Optimization

Full Process Optimization

Clears real-time data storage and moves it to short-term data storage. This option does not take the system offline, so you can schedule it to run during normal business activity. We recommend a Lite Optimization when the write-back table exceeds 200 KB. Clears both real-time and short-term data storage and moves both to long-term data storage. This option takes the system offline, so it is best run at off-peak periods of activity. Clears both real-time and short-term data storage and processes the partition. This option takes the system offline and takes longer to run than the Incremental Optimization. It is best scheduled at downtime periods. You can schedule Full Process Optimization to be weekly or less frequently depending upon your requirements.

Features

You can manually initiate optimization from the Administration Client. From the Model node, you can select a model and then choose Optimize Model from the Manage Models action pane. In the Optimize Models assistant, you have the following options: Select additional or different models to optimize Choose the type of optimization to apply Choose whether to compress the database.NOTE

If you run a Full Process Optimization with the Compress Database option, the model is processed, not each partition. If you have custom partitions and run Full Process Optimization, only the partition that had data moved from FAC2 and the WB table is processed. For example, you have three custom partitions (FACT2008, FACT2009, and FACT2010), and the FAC2 and the WB table have only 2009 data, in this case, if you run a Full Process Optimization, only FACT2009 is processed. Choose whether to defragment the index Optimizing the database can cause the database index to become fragmented. Selecting this option forces a reindex of the database. You can also reindex your database directly from SQL.

4.5.2 Manual Periodic TasksPartitioning is a manual task that is required perio