Professional Documents
Culture Documents
BPC 10.0 EPM Admin
BPC 10.0 EPM Admin
0
version for the Microsoft platform
Target Audience 'n# Technical Consultants 'n# System Administrators 'n# Solution Consultants 'n# Business Process Owners 'n# Support Specialists
PUBLIC '4KFug*no<ThtTXJ.*?@>GQ8
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
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
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.
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
This page is left blank for documents that are printed on both sides.
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
Description
<drive>
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
This page is left blank for documents that are printed on both sides.
3 3.1
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.
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
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
14/102
PUBLIC
2011-05-10
3 3.2
Monitoring of Planning and Consolidation Monitoring with the Management Console Category Task
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.
The following information is available in the Management Console: V The status of Planning and Consolidation processes V Performance metrics of the Windows Server Operating System, the SQL Server, and Analysis Services V A list of which Planning and Consolidation users are active on the system
2011-05-10
PUBLIC
15/102
3 3.2
*e Details about what function each user is executing *e 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: *e Activate and deactivate Planning and Consolidation logging *e End resource-intensive processes *e 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
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://<PC_server:port>/sapmc/ sapmc.html, where <PC_server:port> 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
M-~ Ensure that you have Java Virtual Machine installed on your client and on your browser M-~ Configure your browser to allow Java M-~ Enable the Java plug-in
Procedure
1. 2. 3.
4.
Start the Management Console http://<PC_server:port>/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: M-~ Start M-~ Stop M-~ Manage DB M-~ Connect to server M-~ 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
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
Center pane Center pane Center pane Center pane Center pane Center pane Hits by User
Home
Status Breakdown
Home
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
Home
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.
SPID ECID Status Login Name Host Name BLK DBName Command Request ID OLE DB Calls
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.
Summary
SQL
Database Server Summary Server Statistics Database Server Summary Performance (Database Server)
SQL System
System
System
20/102
PUBLIC
2011-05-10
3 3.2 Field
Monitoring of Planning and Consolidation Monitoring with the Management Console Description Path
Current Locks
Current Connections
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
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 Statistics
CAUTION
SQL Server
Who
SQL SQL
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
Monitoring of Planning and Consolidation Monitoring with the Management Console Description Path
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
SQL
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
Monitoring of Planning and Consolidation Monitoring with the Management Console Description Path
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
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.
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
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.8 Management Console Event Logs 3.2.8.1 Managing Event Log Records
The 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: 1C Activate or deactivate debugging logs 1C Set the amount of time that elapses before logs are deleted or moved to a history table in the database
Function Navigation What You Should Know
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.
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
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: uD-]
Information (contains descriptive information about the event) uD-]
Warning (this event may warrant further investigation) uD-]
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
Output of the SAP Planning and Consolidation Server Diagnostics program IIS HTTP error log files General IIS log files
26/102
PUBLIC
2011-05-10
3 3.5
2011-05-10
PUBLIC
27/102
3 3.6
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 <Drive>\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: p`; w3wp.exe (Microsoft Internet Information Services application pool process) p`; dllhost.exe (DLL application process) p`; 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.
The Change and Transport System requires the following prerequisite applications: p`; SAPJco3 The SAP Java Connector (SAP Jco) is a toolkit that allows a Java application to communicate with any SAP system. p`; di_cmd_tools This is part of the SAPJco toolkit. p`; Java JDK The Java Development Kit.
28/102
PUBLIC
2011-05-10
3 3.7
Jv 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: Jv Selecting the content to include in the transport Jv Attach additional objects to a transport request Jv View the objects in a transport request Jv Export the selected content to the transport package Jv 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.
As of Planning and Consolidation 10.0, to improve performance, only the following COM+ applications are used: Jv For Planning and Consolidation: J Data Manager, which has components that handle some Data Manager tasks J x86, which has components for the services control wrapper and transfer members
2011-05-10
PUBLIC
29/102
3 3.7
9W For the BUI: 98 .NET Data Helper 98 x86, which has application printing components
Features
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 <FileFullPath>. 2. Use the regsvcs <FileFullPath> .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 <SAP BPC system> 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
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.
2011-05-10
PUBLIC
31/102
4 4.1
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
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]
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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
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 y Instance name y Port number y Provider OLAP Server Name y Instance name y Port number File Share Server Name y Local data path Application Server Name y External server name Virtual server name y Website y HTTP compression y Protocol y Port number y Authentication type
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, <Drive> \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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
The SLD Data Supplier requires the following components to work with Planning and Consolidation: $N Application server Java $N The most recent Component Repository (CR) Content $N 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: $N Enable If the check box is selected, the Planning and Consolidation system transfers system data to the SLD server periodically. $N Server host
34/102
PUBLIC
2011-05-10
4 4.1
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
d$$ d$$
d$$
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.
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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
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://<CMS name>: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: 1NY Windows 1NY 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: 1NY Define System User Groups Here you can define groups of Windows users that have similar system responsibilities. 1NY 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
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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
From the Server Manager Options menu, you have the following entries that are specific to the CMS authentication mode: y9@ 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. y9@ 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: y9/ 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. y9/ 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. y9/ Click 2. Migrate, and then click OK to migrate the validated Windows user information to CMS. y9/ 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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
If required, you can save a copy of the result log. q 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
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 q The wizard displays a list of environments that can be migrated to CMS q Select one or more of these environments q The wizard displays list of the Windows user IDs assigned to these environments q 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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
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
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
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: 8F 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. 8F 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
OU=Marketing OU=Sales;OU=Marketing
OU=Sales;OU=Marketing;CN=Users
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.
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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
Prerequisites
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.
+ 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]: +l Application Server External Server name This is the external IP address or fully qualified domain name where the application server resides. +l 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
Management of Planning and Consolidation Managing Your Planning and Consolidation Servers
W[o Define external IP addresses in the Server Options [page 33] window. W[o Open the TCP/IP ports from your firewall software.
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
42/102
PUBLIC
2011-05-10
4 4.2
Management of Planning and Consolidation Asynchronous Interfaces and Data Transfers Navigation Path
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
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 execution
Data 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].
2011-05-10
PUBLIC
43/102
4 4.4
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
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].
2011-05-10
PUBLIC
45/102
4 4.4
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: tp 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. tp 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: tp If it is a single server configuration, you can leave the fields blank. The current server is assumed. Click Next. tp 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 <DB Server name>\<non-default instance name>. 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
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.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
Optimization Type
Lite Optimization
Incremental 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: FG Select additional or different models to optimize FG Choose the type of optimization to apply FG 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. FG 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.
48/102
PUBLIC
2011-05-10
4 4.5
Significant portions of the following information have been copied in fair use from Microsoft Web sites.
4.5.2.1.1
Partitioning Overview
Partitioning is perhaps the single most significant thing you can do to improve performance in a large model. Dividing a model into multiple partitions reduces total processing time for the following reasons: re Multiple partitions can be processed in parallel. You can decrease the total time required to process a model by processing multiple partitions in parallel (provided you have sufficient processor and memory resources). By default, Analysis Services processes each partition in a model serially. For large models, parallel processing results in dramatic performance benefits in the following cases: re During the initial load of the data warehouse re During full model processing re During model refreshes
NOTE
If the Analysis Services server has insufficient memory to store the aggregations for each partition being processed, Analysis Services uses temporary files, which negates the performance benefit you are trying to achieve through the use of parallel processing. To process partitions in parallel, you must use a tool that calls the Analysis Management Object (AMO) interface. For an example, see the Parallel Processing sample application in the SQL Server Resource Kit. re Only some partitions need to be processed. You can process only the partitions that have been updated with new data. This decreases the overall time required to update a model with new data. Analysis Services can process one or several small partitions more quickly than it can process a single large partition containing all of the data for the model.
2011-05-10
PUBLIC
49/102
4 4.5
If you partition your model by time, you merely need to process the partitions containing data from the most recent period, rather than processing the entire model. )i Different partitions can have different aggregation designs. You can design additional aggregations on heavily queried partitions and design fewer aggregations on less heavily queried partitions. If you keep the number of the partitions with a large number of aggregations small, and design fewer aggregations for those partitions that are queried less frequently, you can reduce overall processing time. However, if you plan to merge partitions at a later date, you must ensure that the merged partitions have the same aggregation design at the time of the merger. )i Different partitions can have different storage modes. You can use different storage modes for particular purposes.
EXAMPLE
You can create a small partition using ROLAP to enable you to implement real-time OLAP, and then use MOLAP for all other partitions to maximize query responsiveness. )i Partitions can be refreshed individually. You can refresh a partition more quickly than an entire model, consuming fewer resources, and affecting fewer users. When a partition is incrementally updated, a temporary partition is created and then merged into the existing partition. This can result in data fragmentation, which is similar to disk or index fragmentation. As a result, you should schedule a regular refresh of a partition to enable Analysis Services to resort the data for faster multidimensional access, create better multidimensional mapping files, and make smaller aggregations. The division of a model into multiple partitions is transparent to the user. When a query requests data that spans multiple partitions, Analysis Services uses aggregations or scans data in each partition and then combines this information to resolve the query and return the results to the user. You can significantly increase query responsiveness and processing performance by horizontally segmenting the data by one or more keys, such as date or department, and dividing the model into multiple partitions. From an operational perspective, you can improve Analysis Services performance by keeping partition sizes reasonable and setting partition data slices. For more information about each of these configuration issues, see the Microsoft Analysis Services Performance Guide on www.microsoft.com/technet. Each partition file has an extension of fact.data. When a partition file exceeds 5 GB or more than 20 million records, you should consider dividing the partition into multiple partitions. While the above parameters are useful as guidelines, these are not the only considerations. However: )i Smaller partitions can be processed faster than larger partitions.
50/102
PUBLIC
2011-05-10
4 4.5
xT5Z When data changes, you do not need to process all of the partitions in the model. xT5Z Queries can be executed faster on smaller partitions if the data slice is set properly. In this scenario, Analysis Services does not need to scan as much data to resolve multiple queries. Performance degradation typically occurs when the cache is repeatedly refreshed from the disk. This becomes especially problematic when there are large numbers of alternate hierarchies, since the time needed to reprocess each partition varies directly with the number of hierarchies.
4.5.2.1.2
Consider the aspects described in this topic when determining a partitioning scheme.
Features
Data Usage
The primary factor that you should use to determine your partitioning scheme is your data usage. Partitions can be sliced by any number of dimensions.
EXAMPLE
Performance
In addition to the data size considerations, partition so that the data slices created allow a single partition to be accessed for logic, reports, and so on. In many cases, this makes the Time dimension a natural choice for partitioning and slices. However, this is not necessarily always the case. You can create partitions across multiple dimensions; TIME and ACCOUNT, for example. Since it may be necessary to access multiple partitions for certain tasks, this approach may improve performance in some cases and degrade it in others. In many cases, partitioning just by TIME (without partitioning by any other dimensions) is the most effective strategy. Be sure to measure the results of your strategy. In one real-world case, a partitioning scheme that used CATEGORY and CURRENCY did not improve performance over the default. There is some evidence to indicate that multidimension partitioning does not seem to improve performance by as great a margin as the implementation of an initial, single-dimension scheme (in other words, it is common to experience diminishing returns).
2011-05-10
PUBLIC
51/102
4 4.5
Administrative Implications
In addition to performance, you need to consider the administrative implications of your partitioning scheme: zU3 Balance ease of administration with scheme complexity: If the Planning and Consolidation administrator needs to spend hours every week repartitioning, it may not be the optimal solution. zU3 Period modifications necessitate partition recreation: When you create a partition according to time slices, if you want to modify, shift or roll-up periods, you must recreate the partitions accordingly.
CAUTION
Allow for the complete processing of dimensions before processing any partitions based on that dimension. zU3 Ensure completion of dependent partition processing: When processing partitions, you must ensure that a dimension is completely processed prior to processing any partitions based on it. You may experience negative consequences if you process a partition while one of its dimensions is also being processed.
4.5.2.1.3
Before you can partition, you must define in detail the data slice for each partition.
Features
If the data slice value for a partition is set properly, Analysis Services can quickly eliminate irrelevant partitions from the query processing and significantly reduce the amount of physical I/O and processor time needed. To enable Analysis Services to take full advantage of partitions, you must define the data slice for each partition in the Partition Wizard of Analysis Manager. The data slice identifies the actual subset of data contained in each partition. The Partition Wizard does not require you to set this data slice when you create a partition. As a result, it is possible to create a partition without setting the data slice.
CAUTION
Always set the data slice when creating the partition. Failure to do so can result in the addition of considerable system overhead (artificially increasing response times). Without the data slice, Analysis Services cannot limit a query to the appropriate partitions and must scan each partition even if zero cells are returned. To draw an analogy with SQL Server, creating a partition without a data slice is like creating a partitioned view without the CHECK clause. While you can do it, you force the query optimizer to scan all of the partitions in the view because you have not
52/102
PUBLIC
2011-05-10
4 4.5
given it enough metadata to figure out what partition to access when a query is issued. While the Analysis Services runtime engine does not use a relational query optimizer (it has its own component that accomplishes a similar operation), it uses the data slice in roughly the same way: as metadata to tell it which partitions to scan if an aggregate cannot be used or is not available. If you partition a model by month, and have 36 months worth of data (in 36 partitions), and if you do not specify the data slice, then the runtime engine must scan all 36 partitions to answer a query. If you specify the data slice, it could potentially only have to scan 1/36th the data, with an obvious improvement in performance. To maximize querying performance with partitions, construct partitions with data slices that mirror the data slices required by your users. For example, suppose you are deploying a model that typically tracks data as a time series (such as a financial model), and most queries retrieve data based on period. You should partition the model by period to provide the greatest performance benefit. With very large models, partitioning along multiple dimensions (such as time and department) can yield substantial query responsiveness benefits. Remember that each partition can have a different aggregation design.
RECOMMENDATION
If you are creating rolling monthly partitions as each month closes, you should ensure that the data slice is set for each new partition after it is created.
Data Slices Result in the Creation of JOIN and WHERE Clauses
Setting a data slice also causes Analysis Services to add a JOIN and a WHERE clause to the SQL statement used for retrieving data from the source database during processing. The WHERE clause limits the data retrieved by the SQL statement to the data that belongs in the data slice.
EXAMPLE
If you say that a partition's data slice is June 2008, Analysis Services adds a join to the time dimension and adds the WHERE clause:
WHERE <month field> = June AND <year field> = 2008
or whatever the appropriate member and level names are. If you do not define a data slice and you have multiple partitions, Analysis Services does not restrict the data that is retrieved from the source database. Without the data slice, if you just happen to have July 2008 data in the June partition, Analysis Services does not complain, it just double-counts the July 2008 data. For more information, see Maintaining Partitions in SQL Server Books Online. By specifying the data slice, the system can add these JOIN and WHERE clauses that assist in maintaining the integrity of the data.
2011-05-10
PUBLIC
53/102
4 4.5
4.5.2.1.4
Partition Planning
Partition planning ensures that you can reproduce and verify the partitioning scheme.
Prerequisites
You have chosen your basic scheme and determined the manner in which you would like to slice your data.
Features
Ensure that the Fact prefix is part of every partition name. It is important to prepend Fact to each partition name, as Save Model follows the naming convention:
Fact<ModelName>#####
The following tables contain examples of the planning that you should complete prior to creating your partitions for various fact tables. Preparing this information in this format greatly decreases the amount of time that you need to create the partitions. The following table contains planning details for the dbo.tblFactFINANCE table:
Partition Name Slice Filter (The Where Clause) Storage Mode
FACTFINANCE2002
2002.TOTAL
FACTFINANCE2003
2003.TOTAL
FACTFINANCE2004
2004.TOTAL
FACTFINANCE2005JAN FACTFINANCE2005FEB
(dbo.tblFactFINANCE.TIMEID >= '20020100') AND (dbo.tblFactFINANCE.TIMEID <= '20021200') (dbo.tblFactFINANCE.TIMEID >= '20030100') AND (dbo.tblFactFINANCE.TIMEID <= '20031200') (dbo.tblFactFINANCE.TIMEID >= '20040100') AND (dbo.tblFactFINANCE.TIMEID <= '20041200') dbo.tblFactFINANCE.TIMEID = '20050100' dbo.tblFactFINANCE.TIMEID = '20050200'
MOLAP
MOLAP
MOLAP
MOLAP MOLAP
54/102
PUBLIC
2011-05-10
4 4.5
Management of Planning and Consolidation Periodic Tasks Slice Filter (The Where Clause) Storage Mode
Partition Name
FACTFINANCE2005MAR FACTFINANCE2005Q2
FACTFINANCE2005Q3
2005.TOTAL. 2005.Q3
FACTFINANCE2005Q4
2005.TOTAL. 2005.Q4
dbo.tblFactFINANCE.TIMEID = '20050300' (dbo.tblFactFINANCE.TIMEID >= '20050400') AND (dbo.tblFactFINANCE.TIMEID <= '20050600') (dbo.tblFactFINANCE.TIMEID >= '20050700') AND (dbo.tblFactFINANCE.TIMEID <= '20050900') (dbo.tblFactFINANCE.TIMEID >= '20051000') AND (dbo.tblFactFINANCE.TIMEID <= '20051200')
MOLAP MOLAP
MOLAP
MOLAP
The following table contains planning details for the dbo.tblFAC2FINANCE table:
Partition Name Slice Filter (The Where Clause) Storage Mode
FAC2FINANCE
All
[no filter]
MOLAP
The following table contains planning details for the dbo.tblFACTWBFINANCE table:
Partition Name Slice Filter (The Where Clause) Storage Mode
FACTWBFINANCE
All
[no filter]
ROLAP
4.5.2.1.5
In Planning and Consolidation, you can create an OLAP custom partition function and scheme. This setting is kept even during manipulation (add, modify, copy, or restore) environments or models. The FINANCE model has a number of partitions as part of the default installation. Of those, the FINANCE partition is the only one you need to address by deleting that partition and replacing it with partitions that divide the data into smaller segments.
Procedure
1. 2. 3.
Start SQL Server Business Intelligence Development Studio, which is part of the Microsoft SQL Server suite. Choose File Open Analysis Services Database . In the Connect to Database dialog box: :Ow Choose Connect to existing database.
2011-05-10
PUBLIC
55/102
4 4.6
Management of Planning and Consolidation Optimizing the Flow of Data in the Database
,.V9 Enter the server name. ,.V9 Choose the database. 4. Choose OK. The Microsoft Visual Studio screen appears. 5. In the context menu of the FINANCE model, which is located in the CUBES section of the Solution Explorer pane, choose Open to open a tab displaying the default FINANCE model partitions. 6. Delete the FINANCE partition. 7. Choose New Partition. The Partition Wizard dialog box appears. 8. In the Specify Source Information dialog box: ,.V9 Choose Finance as the Measure group. ,.V9 Choose Data Source View.AppDef as the Look in. ,.V9 Select dbo.tblFactFinance as the table to use. 9. Choose Next. In the Restrict Rows dialog box: ,.V9 Choose Specify a query to restrict rows. ,.V9 Enter a query. For more information, see Partition Planning [page 54]. ,.V9 Choose Check to verify the validity of the query. ,.V9 Choose Next. In the Completing the Wizard dialog box, choose Design aggregations later. ,.V9 Choose Finish. 10. Repeat steps 7 through 9 for each partition you need to create.
NOTE
,.V9 When you have created partitions, remember to schedule a regular reset of the partitions. For example, if you have created a partition for 2009, you must reset the partition to use it for 2010. ,.V9 If you create an OLAP custom partition function and scheme, you must adhere to the following naming rule: ,.VV Partition function name: <dim>RangePF ,.VV Partition scheme name: <dim>RangePS
56/102
PUBLIC
2011-05-10
4 4.6
Management of Planning and Consolidation Optimizing the Flow of Data in the Database
Planning and Consolidation uses this table is a staging area before writing the data to the database. k Global Cache Global cache is an area of memory or a disk on the server that holds query results. That is, if you run a query, the results are stored in the global OLAP cache for potential reuse.
Send Governor environment parameters can be modified as a means of tuning performance. When tuning performance, consider the following: k For situations in which you have a larger user base (with a large number of concurrent users) you may wish to use fewer threads with a bigger interval. k Increasing the value of MAXCELLS_THREAD_SG would improve performance for a single send, while degrading the systems ability to process concurrent users. k Increasing the value of UNITPER_SP would improve performance for a single send, while degrading the systems ability to process concurrent users.
2011-05-10
PUBLIC
57/102
4 4.6
Management of Planning and Consolidation Optimizing the Flow of Data in the Database
bs When you change the SEND_SGTABLE_COUNT parameter, you should also choose Modify Model from the action pane to save your changes
Global cache parameters are defined during system implementation. However, it may emerge from the evaluation of data that the global cache parameters need to be adjusted to fit system demands. In this case, you are able to change these settings later. The following is a brief overview of the global cache parameters. For a more detailed description, refer to the SAP application help at http://help.sap.com and search for Global Cache.
Cache Inactive
Setting this parameter means that the global cache is centrally deactivated.
Local Cache Size in MB
This parameter determines the memory size of the local OLAP processor cache.
Global Cache Size in MB
This parameter determines the maximum memory use for all objects in the global cache. Memory use means the amount of memory used by the objects in the shared memory. Shared memory refers to the swapping of data if the memory reaches its maximum size. The actual memory use in the shared memory is generally higher because administrative data is also written there.
Persistence Mode
The persistence mode allows you to determine whether and in what form cache data is to be stored: bs Main Memory Cache with or Without Swapping
58/102
PUBLIC
2011-05-10
4 4.7
This persistence mode parameter determines what happens to the data in the cache if the memory reaches its maximum size. A proportion of the data must either be removed or swapped. A process using the Least Recently Used (LRU) algorithm determines which data is affected by this. O7 Persistent Cache for each Application Server or Cross-Application Server This persistence mode parameter determines whether the data is to be stored in a file (flat file) or in a database table. The following table is an overview of how the persistence modes can be used:
Persistent Cache for each Application Server or CrossApplication Server
Persistence Mode
The cached data is stored as a file in a directory on the application server or cross-application server in the network. Database Table: Main Memory Cache with Swapping: The cached data is When the cache memory is exhausted, data is stored in stored in the database O7 Cluster table O7 Transparent table (BLOB) the database in a non-transparent cluster table or in a as a non-transparent transparent table with Binary Large Object (BLOB). cluster table or as a transparent table with BLOB (Binary Logical Object). Cluster tables differ in whether they have the application server in the key. This depends on the cache mode.
When the cache memory has been exhausted, data is removed. IMain Memory with Swapping: When the cache memory has been exhausted, data is stored in a file
4.7 Best Practices for Performance Management 4.7.1 Tuning Planning and Consolidation
This section provides guidance and techniques for developing high-performance models by explaining what can be done to tune each layer, from the hardware up through the system software to the model and the reports.
2011-05-10
PUBLIC
59/102
4 4.7
Features
The practices in this section help to provide you with a solid understanding of your model and a foundation for a high performance solution. Its overall organization is as a checklist. By working through this section from beginning to end, you can determine which best practices have been applied and which have not.
NOTE
Not all techniques are necessary, or even appropriate, for all situations. Also, the concepts in this section have not been tested in all scenarios and your results may vary.
The Tuning Layers
The layers addressed are: ? p Hardware ? p Operating System ? p SQL Server ? p Analysis Services ? p Environment database ? p Data load processes ? p Reports and Input Forms ? p Model Maintenance
Tuning Minimum Consideration
If nothing else, you should focus on the following: ? p Use large servers ? p Eliminate HTTP connections ? p Use report templates
More Information
Hardware Configuration [page 61] Operating System Configuration [page 62] System Software Configuration [page 62] tblDefaults Parameters [page 64] Model Customizations [page 65] Model Design [page 66] Model Maintenance [page 70] Identifying Performance Bottlenecks [page 71] FACT, FAC2, and WB Tables [page 73]
60/102
PUBLIC
2011-05-10
4 4.7
Hardware configuration can be complex, and its relationship to performance might not be readily apparent. We recommend that you engage technical consulting to ensure all details are in order.
Features
While your performance profile may vary, for large models we recommend at least an application server and a database server. You might consider load balancing. If possible, an additional server is recommended; splitting the OLAP and SQL components on different servers provides the most scalable solution. The appropriate most configuration can only be determined when the application design is known. Working with SAP resources provides the experience to assist you.
Server Performance
Faster hardware typically provides the biggest performance boost. In particular: 2m?F Lots of fast CPUs, either dual core or hyperthreaded 2m?F Enough RAM to hold the entire database and all processes 2m?F High speed, properly configured I/O devices Consider no less than: 2m?F Four dual core 3GHz, or faster, CPUs 2m?F 8 GB RAM Minimum (16 or 32 is better) 2m?F Three or four separate RAID drives and controllers for operating system and files, and data, temp and log files
Clients
Since Planning and Consolidation is a client application, client workstations should have as much RAM as possible. Informal testing has shown that upgrading a client machine's RAM reduces complex expansion and report times by more than 50%.
RECOMMENDATION
If the clients are using Citrix on shared hardware, contact technical consulting.
2011-05-10
PUBLIC
61/102
4 4.7
Put data, logs, tempdb, and the operating system on separate physical drives.
Virus Scanning Software
Make sure virus scanning is limited to the files that are absolutely needed (avoid scanning the transaction log or the read/write actions performed by SQL and Analysis Services).
Setting Connection Timeouts
Connection timeouts help reduce the loss of processing resources consumed by idle connections. When you enable connection timeouts, IIS enforces the time-outs at the connection level. See the procedures below.
Procedure
To Set an HTTP Keep-alive
1. 2. 3. 4.
In IIS Manager, expand the local computer and click the Web Sites or FTP Sites folder. On the right pane, double-click HTTP Response Headers. In the list that appears, right-click to show the context menu. In that menu, choose Set Common Headers. In the Set Common Headers window, choose Enable HTTP Keep-alive. Click OK.
1. 2. 3. 4.
In IIS Manager, expand the local computer and click the Web Sites or FTP Sites folder. Right-click on the site where you want to set a connection time-out value. On the context menu, choose Manage Web Site Advance Settings . In the pop-up window, scroll down to Behavior and expand Connection Limits. Type the maximum number of seconds that IIS should maintain an idle connection before resetting the connection in the value of Connection Time-out (seconds).
62/102
PUBLIC
2011-05-10
4 4.7
Features
SQL Server Configuration
Make sure you are running the SAP supported SQL server version for both SQL and OLAP (see the SAP Planning and Consolidation 10.0 Master Guide. Make sure AWE is configured for the large amount of memory you have installed in the hardware. If disk I/O is an issue, look into using file separation techniques.
Analysis Services Configuration for SQL 2008
We have found the majority of the settings for SQL should follow the Microsoft documented guidance. We have also found that the Query/MaxThread value should be 10 (default value) plus the total number of Planning and Consolidation databases (environments) plus twice the number of CPUs. Without making the appropriate setting, processing time is significantly slower. For more details, contact the SAP support team.
Operating System Services
Turning off services that are not required saves memory and CPU. The following is a list of services that you do not need on the Planning and Consolidation server. 3p! Alert 3p! Application Management Transfer service 3p! ClipBook 3p! Computer Browser 3p! Distributed Link Tracking client 3p! Distributed Transaction Coordinator 3p! Fax Service 3p! Indexing Service 3p! Internet Connection Sharing 3p! Logical Disk Manager Administrative Service 3p! Messenger 3p! Microsoft NetMeeting Remote Desktop Sharing 3p! Network DDE 3p! Performance logs and alerts 3p! Protected Storage 3p! QoS RSVP 3p! Remote Access Auto Connection Manager 3p! Remote Access Connection Manager 3p! Remote Procedure Call (RPC) locator
2011-05-10
PUBLIC
63/102
4 4.7