SMD 7.01 Managed System Setup and Configuration for BPC 7.5

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

SAP Solution Manager Diagnostics

7.01 Managed System Configuration

for SAP Business Objects Planning

and Consolidation

Applies to:

SAP Business Objects Planning and Consolidation, version for Microsoft platform, as of 7.5, and version for SAP Netweaver, as of 7.5. As Managing System an SAP Solution Manager 7.01 SP23 or higher is required unless mentioned otherwise.

Summary

SAP Business Objects Planning and Consolidation (BPC) is integrated into SAP Root Cause Analysis application SAP Solution Manager Diagnostics (SMD). This document provides information of how to setup configure SMD of an SAP Solution Manager managing system with and for BPC managed systems.

Authors: Robin Haettich, Michael Ren

Company: SAP America Inc., SAP China

Created on: 01 September 2011

Authors Bio

Robin Haettich has been working for SAP America Inc. since 2008. His current focus area is SAP Application Lifecycle Management as well as Solution Operations Management concepts and SAP Solution Manager Integration. As Solution Architect, Robin leads customer engagements and projects to implement business process operations standards, procedures, and solutions to make SAP applications and systems ’run better’.

Michael Ren is working for SAP China, Active Global Support. His current focus area is the support of SAP Business Planning and Consolidation solutions. As product integrator, Michael works on SAP Solution Manager Diagnostics content for SAP and Business Objects products and applications.

SAP Solution Manager Diagnostics 7.01 Managed System Configuration for SAP Business Objects Planning and Consolidation


© 2011 SAP AG 2

Table of Contents

Solution Manager Diagnostics Integration .......................................................................................................... 3

System Landscape Setup in Solution Manager 7.01 (SP23 and higher) ........................................................... 3

Prerequisites ................................................................................................................................................... 3

SBOP PC 7.5 for SAP Netweaver .................................................................................................................. 4 Manual Creation of Technical System(s) for BPC .NET Server ................................................................................... 4

Creation of Technical System(s) for BPC ABAP Server .............................................................................................. 8

Installation of SAP Diagnostic Agent(s) ..................................................................................................................... 10

Installation of CA Wily Introscope .NET Agent(s) ....................................................................................................... 10

Configuration of SAP Solution Manager Diagnostics for BPC .NET Server ............................................................... 11

Configuration of SAP Solution Manager Diagnostics for BPC ABAP Server ............................................................. 13

SBOP PC 7.5 for Microsoft ........................................................................................................................... 14 Manual Creation of Technical Systems for SBOP PC 7.5 for Microsoft ..................................................................... 14

Manual Creation of Product Systems for SBOP PC 7.5 for Microsoft ........................................................................ 21

Installation of SAP Diagnostic Agents ........................................................................................................................ 23

Installation of CA Wily Introscope .NET Agent(s) ....................................................................................................... 26

Configuration of SAP Solution Manager Diagnostics for BPC Servers ...................................................................... 27

Configuration of Remote Database Monitoring .......................................................................................................... 32

Related Content ................................................................................................................................................ 33

Copyright........................................................................................................................................................... 34



© 2011 SAP AG 3

Solution Manager Diagnostics Integration

This document provides an overview of SAP Solution Manager Diagnostics Managed System Setup and Configuration for SAP BPC, i.e. SBOP PC 7.5. Please refer to the SAP Note 1461749 for further references.

System Landscape Setup in Solution Manager 7.01 (SP23 and higher)

Diagnostics in SAP Solution Manager depends on the definition of technical systems in SAP Solution

Manager System Landscape Directory. In the following, we describe the steps required to create or maintain

the technical systems for SAP BPC.

Prerequisites

Before starting the configuration of a technical system for SAP Solution Manager Diagnostics, ensure that

the following prerequisites are fulfilled:

1. Basic Configuration of SAP Solution Manager is performed

Perform the basic configuration of your SAP Solution Manager system. Starting with EhP1 of SAP

Solution Manager, this can be done using transaction SOLMAN_SETUP.

2. Diagnostics Agent is installed

For each system you want to connect to SAP Solution Manager a Diagnostics Agent (also known as

SMD Agent) needs to be installed on and for each virtual host of that system.

For further information refer to:

http://service.sap.com/diagnostics Installation & Configuration Diagnostics Agent Installation

Guide

3. Plug-Ins are updated on managed systems (ABAP only)

Ensure that the components ST-PI and ST-A/PI are updated in the managed system.


SAP Note 1010428 Select the note relevant for your Solution Manager Support Package level.

4. Managed System is connected to SLD infrastructure

In order to enable a central maintenance of systems in SAP Solution Manager, setup an SLD

infrastructure to which each managed system is connected to. There are several possibilities how

this infrastructure can be designed.


https://www.sdn.sap.com/irj/sdn/nw-sld Planning Guide - System Landscape Directory

5. Bridge forwarding from central SLD to SAP Solution Manager SLD is in place

If your SAP Solution Manager system does not host your central SLD system, setup a bridge

forwarding from your central SLD to your SAP Solution Manager SLD.


SAP Note 1148028

6. Landscape Fetch Job in SAP Solution Manager is scheduled

The system landscape directory in SAP Solution Manager retrieves the system landscape data

regularly from the SLD via the landscape fetch background job. This background job is normally

scheduled during basic configuration. You can reschedule this background job using transaction

SMSY_SETUP.

http://service.sap.com/sap/support/notes/1461749

http://service.sap.com/diagnostics


https://www.sdn.sap.com/irj/sdn/nw-sld




© 2011 SAP AG 4

SBOP PC 7.5 for SAP Netweaver

Prerequisite for Solution Manager Diagnostics of SBOP PC 7.5, version for SAP Netweaver is SAP Solution Manager 7.0 EHP 1 SP23 or higher.

The system landscape for this BPC product version consists out of at least one BPC .NET Server and one Business Plan. and Cons. ABAP Server.

The BPC .NET Server does not support the automatic creation of the technical system via SLD. Enter the

BPC system landscape information manually using transaction SMSY. Thereafter, perform the Managed

System Setup and Configuration for the BPC system using the “Diagnostics Setup” wizard.

Manual Creation of Technical System(s) for BPC .NET Server

1. Call transaction “SMSY”. 2. Repeat the steps 3-8 for all servers

which are not yet maintained in SMSY and which run software components of your BPC system (BPC Web Servers, BPC Application Servers).

3. Right-click on “Server”. 4. Select “Create New Server”.

5. Enter the server name on which the BPC .Net Server is installed.

6. Save your entries.

7. Maintain the fields “Fully-Qualified Host Name” and “IP-Address”.


9. Right-click on “System Components” (or “Technical Systems”).

10. Select “Create New System Component” (or “Create New Technical System”).

11. Enter the System ID of your BPC system plus suffix as System Component/Technical System name. If for example the System ID of the BPC ABAP Server is “PE2”, the System ID of the BPC .NET Server is “PE2_NET”.

12. Select System Type “MS.Net”. 13. Leave field “Installation Number”

empty. 14. Save your entries.

Please note:

The BPC .Net Servers are not installed with a native System ID. In order to identify the technical system, assume a System ID as outlined.



© 2011 SAP AG 5

15. Select tab “Header Data” 16. Select flag “Production”

17. Select tab “Instances” 18. Repeat the following steps for each

server (host) where BPC .Net Servers (i.e. BPC application and web servers) are installed.

19. Add a new line. 20. Select the server in field “Server”. 21. Maintain the “Instance” according to

the following naming convention: <Server Name>_<System ID>

22. Select tab “Software Components”. 23. Select “Copy Software Component

from Main Instance”. 24. Select Product “SAP BPC FOR

SAP NETWEAVER”. 25. Select the correct SAP BPC

Product Version. 26. Select Main Instance “BPC .NET

Server”. 27. Select “Continue (Enter)”

28. Select “Copy Software Component from Main Instance”.

29. Select Product “MS IIS”. 30. Select the correct MS IIS Product

Version. 31. Select Main Instance “MS IIS”. 32. Select “Continue (Enter)”

Please note:

If your system is running on Microsoft Windows 2003 servers, the correct MS IIS version is probably 6.0. In case of Microsoft Windows 2008 servers, it is 7.0.



© 2011 SAP AG 6


34. Select Product “MSFT.NET”. 35. Select MS.Net Framework Product

Version “MSFT.NET 1.1”

Please note:

For BPC 7.5 NW SP00 to SP04, choose .NET 1.1.

For BPC 7.5 NW SP05 or higher, choose .NET 2.0. 36. Select Main Instance “MSFT.NET

Framework” Select “Continue (Enter)”


38. Right-click on “Systems”. 39. Select “Create New System”.

40. Enter the System ID of your BPC .Net system + Suffix (e.g. _NET) to differentiate from the System ID of the BPC ABAP system.

40. Select Product “SAP BPC FOR NETWEAVER”.

41. Select the correct SAP BPC Product Version.

42. Leave the field “Installation Number” empty.




© 2011 SAP AG 7

44. Select tab “Selection of Main Instances”.

45. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “BPC.Net Server”.

46. Assign the System Component/Technical System defined above and select the Type “MS. Net”.


48. Select tab “Header Data”. 49. Select “Change Product

Assignment”. 50. Select flag “Free Product/Select

Product version”. 51. Select Product “MSFT.NET” and

Product Version “MSFT.NET 1.1” 52. Select “Copy” and confirm the pop-

ups. 53. Select Product “MS IIS” and the

version of MS IIS you use” 54. Select “Copy” and confirm the pop-

ups. 55. Ensure that flag “Active” is set for all

3 products. 56. Save your entries.

Please note:

If your system is running on Windows 2003 servers, the correct MS IIS version is probably 6.0. In case of Windows 2008 servers, it is 7.0.

57. Select flag “Production”.

58. Expand node “Systems” -> “MS IIS” and select the MS IIS system you created.


60. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “MS IIS”.

61. Assign the Technical System/System Component defined above and select the Type “MS. Net”.




© 2011 SAP AG 8

63. Expand node “Systems” -> “MSFT.NET” and select the MS .Net Framework system you created previously.


65. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “MSFT.NET”.

66. Assign the System Component/Technical System defined above and select the Type “MS. Net”.


Creation of Technical System(s) for BPC ABAP Server

The data required for the System Landscape Directory (SLD) are collected via the SLD Data Supplier available in every SAP Netweaver Application Server ABAP. Start the configuration of the System

Landscape Directory (Transaction RZ70) and send the collected data to your SLD.

1. Start the configuration of System Landscape Directory in Transaction RZ70 in the BPC ABAP system.

2. Enter the SLD connection information.



© 2011 SAP AG 9

3. Activate the settings and execute. The execution result will be returned with success or error message.

4. Start Transaction SMSY in SAP Solution Manager.

5. Expand node “Systems” -> “SAP Netweaver” and select the BPC ABAP system reported to SLD.

Please note:

If the system was reported to SLD recently, it might only appear in SMSY after the next run of the landscape fetch background job.

6. Select tab “Header Data”. 7. Select “Installed Product Versions”. 8. Select flag “Free Product/Select

Product version”. 9. Select Product “SAP BPC FOR

SAP NETWEAVER” and the correct Product Version.

10. Select “Copy” and confirm the pop-ups.

11. Select Product “SAP NETWEAVER” and the correct Product Version.


13. Ensure that flag “Active” is set for “SAP BPC FOR SAP NETWEAVER” and “SAP NETWEAVER”.



16. Flag the Main Instance “Business Intelligence” as relevant.


18. Expand node “Systems” -> “SAP BPC FOR SAP NETWEAVER” and select the BPC ABAP system reported into SLD.



© 2011 SAP AG 10


20. Flag the Main Instance “Business Plan. and Cons. ABAP” as relevant.


22. Double-click on Main Instance “Business Plan. and Cons. ABAP”.

23. Select tab “Clients” on the right screen, mark the relevant client.

24. Select button “Generate RFC Destinations”. In the wizard, unselect all options but “RFC Destination and User for Read Access”.

Installation of SAP Diagnostic Agent(s)

If not already done so, SAP Host Control and SAP Diagnostics Agent need to be installed on all servers (hosts) where BPC Application Servers, BPC Web Servers and BPC ABAP Servers are installed. Please refer to SAP Note 1368413.

Installation of CA Wily Introscope .NET Agent(s)

If not already done so, CA Wily IS .Net Agent needs to be installed on all servers (hosts) where BPC Application Servers and BPC Web Servers are installed. The collection of CA Wily Introscope performance metrics for BPC .Net Servers needs to be enabled. Please refer to SAP Note 1126554.





© 2011 SAP AG 11

Configuration of SAP Solution Manager Diagnostics for BPC .NET Server

After setup of the technical systems and installation of the Diagnostic Agents, the Managed System Setup and Configuration needs to be performed.

1. Open the Root Cause Analysis Work Center (Transaction: SOLMAN_WORKCENTER).

2. Expand section “Common Tasks”. 3. Select “Diagnostics Setup”.

4. Select “Managed Systems” -> “Setup Wizard”.

5. Select the Technical System created before.

6. Select the triangle below “Managed Products”. Unselect the checkbox “Not Diagnostics Relevant” if it is set.

7. Select (highlight) the following Products to be managed by Diagnostics: MS IIS <XX>, MSFT .Net <XX>, SBOB PC <XX> if they are not highlighted already.

8. Select “Set” if you had to change anything, otherwise select “Cancel”.



© 2011 SAP AG 12

9. Select the triangle below Main Instances.

10. Select (highlight) the following Main Instances to be managed by Diagnostics: MS IIS, MSFT .Net Framework, BPC .net Server if they are not highlighted already.

11. Select “Set” if you had to change anything, otherwise select “Cancel”.

12. Select “Setup <System ID>”

13. Specify Installation Path for BPC .Net Server.

14. Specify Software Component Paths for MS IIS, MSFT .Net Framework and BPC .Net Server.

15. Select “Set”.

16. Select “Next”.

17. Select “Setup”.



© 2011 SAP AG 13

18. After some seconds the setup should be completed.

Configuration of SAP Solution Manager Diagnostics for BPC ABAP Server

For BPC ABAP Server the procedure described in the SMD Managed System Setup Guide referred in SAP

Note 1265070 needs to be followed. Please refer to chapter 2.2. During setup, mark the managed products

“SAP EHP1 for SAP Netweaver 7.0” and “SBOP PC 7.5 FOR SAP NETWEAVER” as diagnostics relevant.

Mark the main instances “Business Intelligence” and “SBOP PC 7.5 FOR SAP NETWEAVER” as diagnostics

relevant.





© 2011 SAP AG 14

SBOP PC 7.5 for Microsoft

For SBOP PC 7.5 for Microsoft an automated creation of the technical system via the SLD is currently not supported. Therefore you have to enter the BPC system landscape information manually using transaction

SMSY. Thereafter, perform the Managed System Setup and Configuration for the BPC system using the

“Diagnostics Setup” wizard.

Manual Creation of Technical Systems for SBOP PC 7.5 for Microsoft

Hosts and Database

1. Call transaction “SMSY”.

2. Repeat the steps 3-8 for all servers which are not yet maintained in SMSY and which run software components of your BPC system (BPC Web Server, BPC Application Server, Microsoft Analysis Services, Microsoft Reporting Services, Microsoft Integration Services, Microsoft SQL Server Database).

3. Right-click on “Server”. 4. Select “Create New Server”.

5. Enter the server name on which your BPC server is installed.


7. Maintain the fields “Fully-Qualified Host Name” and “IP-Address”.


9. Right-click on Database. 10. Select “Create New Database”.

11. Enter the System ID of your BPC system as Database name.


Please note:

The BPC servers are not installed with a native System ID. In order to identify the technical system, assume a System ID as outlined.



© 2011 SAP AG 15

13. Select SQL Server in field Manufacturer.

14. Select the server where the SQL Server database is installed.


System Component for BPC .Net Server

1. Right-click on “System Components” (“Technical Systems”).

2. Select “Create New System Component” (“Create New Technical System”).

3. Enter the System ID of your BPC system as System Component/Technical System name.

4. Select type “MS.Net”. 5. Leave field “Installation Number”

empty. 6. Save your entry.

Please note:

The BPC servers are not installed with a native System ID. In order to identify the technical system, assume a System ID as outlined.

7. Select tab “Header Data” 8. Select flag “Production” 9. Enter the Database you maintained

previously.



© 2011 SAP AG 16

10. Select tab “Instances” 11. Repeat the following for each server

(host) where BPC application servers are installed.

12. Add a new line. 13. Select the server in field “Server”. 14. Maintain the Instance Name

according to the following naming convention: <Server Name>_<System ID>.

15. Select tab “Software Components” 16. Select “Copy Software Component

from Main Instance” 17. Select Product “SAP BPC FOR

MICROSOFT”. 18. Select the correct Product Version. 19. Select Main Instance “BPC Server”. 20. Select “Continue (Enter).”


22. Select Product “MS IIS”. 23. Select the correct MS IIS Product

Version. 24. Select Main Instance “MS IIS”. 25. Select “Continue (Enter)”.

Please note:




© 2011 SAP AG 17


27. Select Product “MSFT.NET”. 28. Select Product Version “MSFT.NET

2.0”. 29. Select Main Instance “MSFT.NET

Framework”. 30. Select “Continue (Enter)”.


System Component for Microsoft SQL Server Analysis Services



3. Enter <System ID>_SSAS (recommended) as System Component/Technical System name.

4. Select type “MS.Net”. 5. Leave the field “Installation

Number” empty. 6. Save your empty.



© 2011 SAP AG 18

7. Select tab “Header Data”. 8. Select Flag “Production”.

9. Select tab “Instances”. 10. Repeat the following for each server

(host) where Microsoft Analysis Services are installed.





MICROSOFT”. 17. Select the correct Product Version. 18. Select Main Instance “MS SQL

Server Analysis Service”. 19. Select “Continue (Enter)”.




© 2011 SAP AG 19

System Component for Microsoft SQL Server Reporting Services



3. Enter <System ID>_SSRS (recommended) as System Component/Technical System name.


Number” empty. 6. Save your entries.

7. Select tab “Header Data”. 8. Select flag “Production”.

9. Select tab “Instances”. 10. Repeat the following for each server

(host) where Microsoft Reporting Services are installed.






Server Reporting Service”. 19. Select “Continue (Enter)”.



© 2011 SAP AG 20


System Component for Microsoft SQL Server Integration Services



3. Enter <System ID>_SSIS (recommended) as System Component/Technical System name.



7. Select tab “Header Data”. 8. Select Flag “Production”.

9. Select tab “Instances” 10. Repeat the following for each server

(host) where Microsoft Integration Services are installed.





© 2011 SAP AG 21




Server Integration Service”. 19. Select “Continue (Enter)”.


Manual Creation of Product Systems for SBOP PC 7.5 for Microsoft

1. Right-click on “Systems” (“Product Systems”).

2. Select “Create New System” (“Create New Product System”).

3. Enter the System ID of the BPC system.

4. Select Product “SAP BPC FOR MICROSOFT”.

5. Select the correct Product Version. 6. Leave the field “Installation


Please note:

BPC systems are not installed with a native System ID. However, in order to identify the system, assume a unique system ID as outlined.



© 2011 SAP AG 22


9. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “BPC Server”.

10. Assign the System Component/Technical System defined above for the BPC Server and select Type “MS. Net”.

11. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “MS SQL Server Analysis Services”.

12. Assign the System Component/Technical System defined above for the MS SQL Server Analysis Services and select Type “MS. Net”.

13. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “MS SQL Integration Services”.

14. Assign the System Component/Technical System defined above for the MS SQL Server Integration Services and select Type “MS. Net”.

15. Select flags “Relevant” and “System Component” (“Technical System”) for the Main Instance “MS SQL Reporting Services”.

16. Assign the System Component/Technical System defined above for the MS SQL Server Reporting Services and select Type “MS. Net”.




© 2011 SAP AG 23

18. Select tab “Header Data”. 19. Select flag “Production”. 20. Save your entries. 21. Select “Change Product

Assignment”.

22. Select flag “Free Product/Select Product version”.

23. Select Product “MSFT.NET” and Product Version “MSFT.NET 1.1”.


25. Select Product “MS IIS” and Product Version of MS IIS you use.


27. Ensure that flag “Active” is set for all 3 products.


Please note:


Installation of SAP Diagnostic Agents

If not already done so, SAP Host Control and a Diagnostics Agent needs to be installed on all servers (hosts) on which BPC Application Servers, Web Servers, Microsoft Reporting Services, Microsoft Analysis Services and Microsoft Integration Services are installed. Please refer to SAP Note 1368413. The following post processing steps are required after the Diagnostics Agent installation on the servers.

Diagnostics Agent Configuration to Read Configuration and Log Data from Microsoft SQL Server Components

By default the Diagnostics Agent is not allowed to access the directories in which configuration and log data of Microsoft Reporting Services and Microsoft Analysis Services are stored. Please perform the following steps to enable the collection of configuration data and the access to log data for these software components.




© 2011 SAP AG 24

1. Start Windows Explorer and navigate to the directory where Microsoft Analysis Service is installed (e.g. D:\Program Files\ Microsoft SQL Server\ MSSQL.3\ Reporting Services).

2. Right-click on the “Reporting Services” folder and select “Properties”. The Properties Window for the folder is displayed.

3. Select tab “Security”. 4. Select “Add”.

5. Select location <localhost>. 6. Enter user SAPService<DASID>. 7. Select “OK”.

8. Verify that the user SAPService<DASID>has the following permissions: - Read & Execute - List Folder Contents - Read.



© 2011 SAP AG 25

9. Select “Advanced”. The “Advanced Security Settings for OLAP” dialogue box is displayed.

10. Select User SAPService<DASID>. 11. Flag the “Replace permission

entries on all child objects with entries shown here that apply to child objects” check box to propagate permissions to the child directories.

12. Select “OK”.

13. Navigate to the directory where Microsoft Reporting Service is installed (e.g. D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP).

14. Right-click on the OLAP folder and select “Properties”. The “Properties Window” for the folder is displayed.

15. Select tab “Security”. 16. Select “Add”.

17. Select location <localhost>. 18. Enter user SAPService<DASID>. 19. Select “OK”.

20. Verify that the user SAPService<DASID>has the following permissions: - Read & Execute - List Folder Contents - Read.



© 2011 SAP AG 26

21. Select “Advanced”. The “Advanced Security Settings for OLAP” dialogue box is displayed.

22. Select User SAPService<DASID>. 23. Flag the “Replace permission

entries on all child objects with entries shown here that apply to child objects” check box to propagate permissions to the child directories.

24. Select “OK”.

Installation of CA Wily Introscope .NET Agent(s)

If not already done so, CA Wily IS .Net Agent needs to be installed on all servers (hosts) where BPC servers are installed. The collection of CA Wily Introscope performance metrics for BPC .Net Servers needs to be enabled. Please refer to SAP Note 1126554. It is not required to install the CA Wily Introscope .NET Agent on servers on which only Microsoft Reporting Services, Microsoft Analysis Services or Microsoft Integration Services but no BPC .Net Server are installed.




© 2011 SAP AG 27

Configuration of SAP Solution Manager Diagnostics for BPC Servers

After setting up the technical system and installation of the Diagnostics Agents, the Diagnostics Setup needs to be performed.

1. Open the Root Cause Analysis Work Center (Transaction: SOLMAN_WORKCENTER).

2. Expand “Common Tasks”. 3. Select “Diagnostics Setup”.

4. Select “Managed Systems” -> “Setup Wizard”.

5. Find the technical systems you created before. You should be able to identify 4 technical systems with the same short System ID: MS SQL Server Analysis Services, MS SQL Server Integration Services, MS SQL Reporting Services and BPC Server.



© 2011 SAP AG 28

Diagnostics Configuration of MS SQL Server Analysis Services

1. Click on the triangle next to the System ID.

2. Click on the triangle below “Managed Products”. Unselect the checkbox “Not Diagnostics Relevant” if it is set.

3. Select (highlight) the following Product to be managed by Diagnostics: SBOP PC 7.5 for Microsoft.

4. Select “Set”. The Diagnostics Relevant Main Instance “MS SQL Server Analysis Services” should be set automatically.

5. Select “Setup <SID…>”.

6. Click on the triangle below “Details”. 7. Select the correct “Diagnostics

Agent” and “Wily Enterprise Manager”.

8. Enter the installation path of Microsoft SQL Server in “System Install Path” and “Software components path” (usually <Drive>: \Program Files\Microsoft SQL Server).

9. Select the Instance for Setup. 10. Select “Set”. 11. Select Next.


13. After some seconds the setup for MS SQL Server Analysis Services should be finished with green or at least yellow lights.

14. Select “Quit”.



© 2011 SAP AG 29

Diagnostics Configuration of MS SQL Server Integration Services



3. Select “Set”. The Diagnostics Relevant Main Instance “MS SQL Server Integration Services” should be set automatically.


5. Click on the triangle below “Details”. 6. Select the correct Diagnostics

Agent and Wily Enterprise Manager.

7. Enter the installation path of Microsoft SQL Server into “System Install Path” and “Software components path” (usually <Drive>: \Program Files\Microsoft SQL Server).

8. Select the Instance for Setup. 9. Select “Set”. 10. Select “Next”.


12. After some seconds the setup for MS SQL Server Integration Services should be finished with green or at least yellow lights.




© 2011 SAP AG 30

Diagnostics Configuration of MS SQL Server Reporting Services



3. Select “Set”. The Diagnostics Relevant Main Instance “MS SQL Server Reporting Services” should be set automatically.


5. Click on the triangle below “Details”. 6. Select the correct Diagnostics

Agent and Wily Enterprise Manager.

7. Enter the installation path of Microsoft SQL Server into “System Install Path” and “Software components path” (usually <Drive>: \Program Files\Microsoft SQL Server).



12. After some seconds the setup for MS SQL Server Reporting Services should be finished with green or at least yellow lights.




© 2011 SAP AG 31

Diagnostics Configuration of BPC Server


2. Select (highlight) the following Products to be managed by Diagnostics: MS IIS <XX>, MSFT .Net <XX>, SBOP PC 7.5 for Microsoft if they are not already highlighted.


4. Select the triangle below “Main Instances”.

5. Select (highlight) the following Main Instances to be managed by Diagnostics: MS IIS, MSFT .Net Framework, BPC Server.



8. Specify installation path for BPC Server.

9. Specify “Software component paths” for MS IIS, MSFT .Net Framework and BPC Server as indicated in the screenshot. For MS IIS 7.0 please enter "C:\Windows\System32\inetsrv" instead of "C:\Windows”.



14. After some seconds the setup should be finished with green or at least yellow lights.




© 2011 SAP AG 32

Configuration of Remote Database Monitoring

Please refer to SAP Note 1388700 for instructions how to setup the Database Cockpit for the Microsoft SQL Server database used by the BPC system.

Please note:

For Microsoft SQL Server database, the database shared library (DBSL) and the client software are provided exclusively for the Microsoft Windows operating system. UNIX/Linux-based SAP Solution Manager systems require a separate application server on Microsoft Windows to connect to a Microsoft SQL Server database.




© 2011 SAP AG 33

Related Content

SAP Business Objects Business Planning and Consolidation SDN Publications

SAP Business Planning and Consolidation Installation and Configuration

SAP Business Objects Planning and Consolidation Best Practices

https://www.sdn.sap.com/irj/sdn/bpx-epm

http://service.sap.com/instguidesEPM-BPC

http://help.sap.com/content/bestpractices/crossindustry/bestp_crossindustry_bpc.htm



© 2011 SAP AG 34

Copyright

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

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

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle 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, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Documents

SMD 7.01 Managed System Setup and Configuration for BPC 7.5