Configuration of SAP Solution Manager 7.

1
Active Global Support 2011

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

© 2011 SAP AG. All rights reserved.

2

SAP Solution Manager Landscape Overview

Solution Manager Landscape Components Managed System 1 ERP SAP Solution Manager 7. All rights reserved.1 Managed System 2 Enterprise Portal © 2011 SAP AG. 4 .

All rights reserved. 5 .…)  SAPGui  NetWeaver Business Client For the different applications. some plugin components are needed  Microsoft Silverlight (for Introscope WebView)  Adobe Flash  Java Runtime Environment  BMC Appsight BlackBox / Console © 2011 SAP AG.SAP Solution Manager Components on the Client PC Client PC Components Access to the Solution Manager with  Browser (Internet Explorer.

SAP Solution Manager Components on the Managing System Managing system components SAP Solution Manager 7.1 Workcenter Applications Service Desk Tech Mon … Repositories Possible sizing options  Installation of SAP BW on separate host  Installation of Wily Introscope Enterprise Manager on separate host  Sizing of Wily Introscope with Manager of Manager Concept LMDB SMSY Solar Directory Data Stores SAP Business Warehouse CA Wily Introscope © 2011 SAP AG. 6 .1  Is a dual stack system (ABAP & J2EE)  Includes SAP Business Warehouse  Includes CRM 7. All rights reserved.0  Includes a license for CA Wily Introscope (Right to View)  Uses SLD & LMDB for landscape data maintenance Engines EFWK CTS+ … RCA SAP Solution Manager 7.

depending on the managed system product (ST-PI and ST-A/PI) Diagnostics Agent Wily Host Agent J2EE Command Console OS Command Console .Net systems.  For J2EE / Java and .SAP Solution Manager Components On Managed System Managed system components Managed System  Can be any kind of SAP / non-SAP system  Can include a local SLD (e... the CA Wily Introscope Byte Code Agent needs to be deployed (can be done from SAP Solution Manager) © 2011 SAP AG.g. Process Integration)  Depending on system type (ABAP/Java/…) different agents and plugins are needed ABAP ST-PI ST-A/PI (Extractors) J2EE Local SLD IS BC Agent Central SLD Managed System Agents & Plugins  One Diagnostics Agent per virtual host  Agent applications are managed centrally from Sap Solution Manager system SAP Host Agent  One SAP Host Agent per physical host  For ABAP systems the plugins need to be installed. 7 . All rights reserved.

Logical Landscape View SAP Solution Manager 7.1 Workcenter Applications RCA Service Desk ChaRM … Diagnostics Agent SLD Managed System Engines EFWK CTS+ … Managed System Repositories Solar Directory Diagnostics Agent SMSY LMDB Data Stores SAP Business Warehouse CA Wily Introscope Managed System Diagnostics Agent © 2011 SAP AG. All rights reserved. 8 .

Solution Manager Architecture SLD Data Distribution in a Typical Landscape Front Ends SAP NetWeaver Developer Studio Browser Access Systems Managing Systems SAP Solution Manager LMDB SLD client access Self registration of Technical Systems Forwarding of data on Technical Systems Manual export/ import SLD Sync (unidirectional) Non-Production Environment SLD (design-time) SLD (runtime) PI (prod. All rights reserved.) Systems (non-prod.) Production Environment © 2011 SAP AG. 9 .) Other systems (prod.) NWDI PI (non-prod.

10 .1 SLD & LMDB LMDB implications in 7.1: SLD1 (PI) SLD2 (Data Supplier) SLD3 (NWDI)  Flexible landscape database based on the CIM data model No local SLD required anymore. but supported Full synchronization between Landscape SLD‟s and LMDB   Solution Manager 7.1  Automatic data migration from SMSY to LMDB in the 7.SAP Solution Manager 7.1 upgrade where needed for the respective Solution Manager scenarios Local SLD (Not required) SMSY LMDB © 2011 SAP AG. All rights reserved.

e. 11 .1 Diagnostics Agent LMDB SLD DB Virt Host A1  Host B SAP Host Agent Enhances available landscape information in LMDB in SAP Solution Manager Support also products where no SLD data supplier is available. All rights reserved.g:  OS Info  Databases & Operating Systems Microsoft components Diagnostics Agent   IIS Virt Host B1 Is aware of virtualization through information from SAP Host Agent Works completely automatic with Diagnostics Agents  © 2011 SAP AG.SAP Solution Manager 7.1 Outside Discovery & LMDB Host A SAP Host Agent SolMan Host OS Info SAP Solution Manager 7.

12 . All rights reserved.Landscape scenarios Where to install an agent? PhyHost2 VHost3 C7 C8 PhyHost3 VHost1 VHost2 cluster C1 C2 C3 C4 C5 C6 Diagnostics Agent 1 Diagnostics Agent 2 Diagnostics Agent 3 Diagnostics Agent 4 SAP Host Agent SAP Host Agent    1 diagnostics agent per managed „host‟ represented by a name: PhyHost1 physical or virtual 1 SAP HostAgent per physical host 1 agent per host supports several SAP Solution Manager managed systems running on the same named host D1 Diagnostics Agent Diagnostics Agent 1 H! SAP HostAgent Managed Component SAP Host Agent © 2011 SAP AG.

but also enable the registration in SLD to be able to use the extended connection features (available with Diagnostics Agent 7. even when not connected to the Solution Manager system  Standard when agent is installed together with SAP NetWeaver based product  Connecting the agent to the Solution Manager system can take up to 30 minutes  No additional configuration steps necessary  Is primarily targeted for manual rollout in small landscapes  Agent can be installed and connection is available instantaneous Recommendation: Connect the agent during the installation directly to the Solution Manager.Connecting Agents to the Solution Manager Available connection options Using a direct connection to the message server Using the SLD connection (Agent Candidate Management)  Agent can be installed without having access or credentials to the Solution Manager system  Agent can be provided with new connection data.20) © 2011 SAP AG. All rights reserved. 13 .

1 Agents for managed systems SAP Host Agent • You need to install at least patch level 55 of the SAP Host Agent 7.sap. © 2011 SAP AG.20 • This is installation procedure is described in SAP Note 1031096 It is recommended to enable the automatic update feature of the SAP Host Agent.com/swdc  Browse Download Catalog  SAP Technology Components  SAP SOLUTION MANAGER  SAP SOLUTION MANAGER 7. All rights reserved. so that you can update the Host Agent centrally. 14 .com/swdc  Support Packages and Patches  Browse Download Catalog  SAP Technology Components  SAP HOST AGENT  SAP HOST AGENT 7.Required Agent Versions Diagnostic Agent • You can use any version of the Diagnostics Agent (already installed agents do not need to be updated) • The agent applications are updated automatically from the Solution Manager • For new installations use the latest available version of the diagnostics agent from http://service.20. This is described in SAP Note 1473974. • The installation files are available from http://service.sap.

0 / 7.01 SR1 Integrated in NW DVD’s Standalone Version available JVM Default System ID / Instance Support for SLD & direct connection (simultaneously) SSL Support SAProuter Support SAP Host Agent needed Yes No JDK 1.20 / 7.11 Yes Yes SAPJVM DAA / SMDA97 7. 15 .Differences of the available Diagnostics Agent Versions 7. installed / updated) Recommended for new installations © 2011 SAP AG.4.2 SMD / J98 7. All rights reserved.02 Yes Yes SAPJVM DAA / SMDA97 7.30 Yes Yes SAPJVM DAA / SMDA97 No No No RCA  No Monitoring  Yes No No No Yes (manual install) Yes Yes Yes Yes (auto install) Yes Yes Yes Yes (auto.

1 J2EE ABAP VHost1 Wily Introscope Enterprise Manager VHost2 ERP Enterprise Portal IS BC Agent DAA 95 IS Host Adapter DAB 96 IS Host Adapter SLD Host SLD © 2011 SAP AG.Typical Agent Layout SAP Solution Manager Host DAA 98 SAP Host Agent Managed System Phyiscal Host 1 SAP Host Agent SAP Solution Manager 7. All rights reserved. 16 .

1 Plan user & port availability. Check hardware prerequisites for SAP Solution Manager 7. 17 . Guides SWDC / SDN Inst Guides service.sap. All rights reserved. Plan user & port availability. agent and possible restarts for managed systems.sap. guides Upgrade Plan implementation of missing software components. agent and possible restarts for managed systems.sap.1 Obtain the Installation Software Obtain the Upgrade Software Install SAP Solution Manager including support package update Update SLD Content to latest available version Connect managed systems to SLD Install Diagnostics agent and SAP HostAgent on all managed systems Implement missing/latest software requirement on managed systems (ST-A/PI & ST-PI) Install Introscope Enterprise Manager Install Diagnostics Agent and Host Agent on all Enterprise Manager hosts Perform configuration of SAP Solution Manager and managed systems.Preparing for Installation/Upgrade Installation Plan implementation of missing software components.com/s wdc Inst / Upgr.com/s wdc + Guides SOLMAN_SETU P + add. © 2011 SAP AG. Upgrade to SAP Solution Manager 7.1 Update SLD Content to latest available version Check the connection of managed systems to SLD Install Diagnostics Agent and SAP HostAgent on all managed systems Implement missing/latest software requirement on managed systems (ST-A/PI & ST-PI) Upgrade Introscope Enterprise Manager Install Diagnostics Agent and Host Agent on all Enterprise Manager hosts Perform configuration of SAP Solution Manager and managed systems. How Master Guide Security Guide Sizing Guide DVD‟s or service. Check hardware prerequisites for SAP Solution Manager 7.com/s wdc service.

18 . Databases and Disk Spaces needed to implement selected ALM scenarios for a set of Managed Systems © 2011 SAP AG. Memory. All rights reserved.Hardware pre-requisites Sizing Tool kit SAP Solution Manager sizing Toolkit provides information on infrastructure requirements including SAPs.

19 .16.6. All rights reserved. open SLD http://sldhost:sldport/sld Go to Administration  Details  Data Check Note 669669 for further information on CR Content & Model © 2011 SAP AG. better latest available To check.Check Prerequesites Update SLD CR Content & Model LMDB requires some minimun version of the CR Content and the model installed in at least one connected SLD: • CR Content: latest available • Model Version: minimum 1.

0 – System Landscape Directory: SAP NetWeaver 7.Check Prerequesites Minimum SLD Versions In order to be able to connect a SLD to the LMDB the SLD needs to have a minimum version.0 – System Landscape Directory: EHP2 for SAP NetWeaver 7. All rights reserved.0 – System Landscape Directory: EHP1 for SAP NetWeaver 7. (You can also use the SLD on your SAP Solution Manager 7. you have to forward the data supplier information from your central SLD to a SLD which fulfills the requirements. Patch 5 SP9 all SPs all SPs all SPs If your central SLD is not on one of the required support package levels.1 – System Landscape Directory: EHP1 for SAP NetWeaver 7. • • • • • • • • SAP NetWeaver 6.1 system for this forwarding) © 2011 SAP AG.1 – System Landscape Directory: SAP NetWeaver 7. 20 . Then connect this SLD to the LMDB.3 – System Landscape Directory: not supported not supported not supported SP6.2 – System Landscape Directory: SAP NetWeaver 7.40 – System Landscape Directory: SAP NetWeaver 7.

no. of exporting/importing objects Recommended value 500000 100 30000 60000 15000 60000 10000 100000000 10000 20000000 10000 50000 20000 © 2011 SAP AG. 21 . All rights reserved.Check Prerequisites SAP Solution Manager Profile Parameters Parameters abap/buffersize abap/shared_objects_size_MB rsdb/ntab/entrycount rsdb/ntab/ftabsize rsdb/ntab/irbdsize rtbb/buffer_length rsdb/cua/buffersize zcsa/table_buffer_area zcsa/db_max_buftab zcsa/presentation_buffer_area sap/bufdir_entries rsdb/obj/buffersize rsdb/obj/max_objects Description Program buffer size Size of Shared Objects Memory in MB Number of nametab entries administrated Data area size for field description buffer Data area size for initial records buffer Size of single record table buffers CUA Buffer Size Size of generic table buffer Directory entries in generic table buffer Size of the buffer allocated for screens Maximum number of entries in the presentation buffer Size of export/import buffer Max.

22 . the configuration changes will be adapted automatically You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note 17285 © 2011 SAP AG.Check Prerequisites RFC Destination SAPOSS SAP Solution Manager needs a working connection to the SAP support backbone  Check if RFC destination SAPOSS is working properly in SM59  If there are connection problems with SAPOSS. All rights reserved. check and maintain the connection settings in transaction OSS1.

All rights reserved.com/user-admin and log on to SMP © 2011 SAP AG. 23 .Check Prerequisites S-User in SAP Service Market Place Make sure that the S-User planned to be assigned to Solution Manager has the right authorizations in SAP Service Market Place  Call URL: http://service.sap.

see SAP note 539977 and 69455 for more details Example Only © 2011 SAP AG. 24 .Check Prerequisites Support Package Levels Ensure that all support package levels for the managing system (Solution Manager) and the managed systems are up to date  The most important components on SAP Solution Manager are ST and ST-SER  The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and ST-A/PI. All rights reserved.

25 . Without the standard Java users from 001 the Java engine will not start after converting UME! To convert the UME open the AS Java User Management and change to Configuration  ABAP System © 2011 SAP AG.Check Prerequisites Optional: Client Copy You can use the SAP delivered client 001 as productive client for SAP Solution Manager If you want to create an own productive client:  Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as the source client for users  Afterwards convert the Java UME to the new productive client Please ensure that you entered 001 as “Source Client User Masters” for your client copy. All rights reserved.

Installation & Upgrade Where To Find The Software
https://service.sap.com/swdc

© 2011 SAP AG. All rights reserved.

26

Configuration of SAP Solution Manager using SolMan Setup
Overview

SAP Solution Manager Configuration with SOLMAN_SETUP
SAP Solution Manager 7.1 is configured using an Automatic Basic Configuration
 Accessible via transaction code SOLMAN_SETUP  Allows an easy, fast and step-by-step configuration of SAP Solution Manager

 Single, easy to use wizard for system preparation & basic configuration  Highly automated configuration  Integrated documentation for each step  Easy access to open tasks and postponed activities  Configuration of all managed systems from one central entry point  Configuration of other scenarios like Technical Monitoring, Data Volume Management,…

© 2011 SAP AG. All rights reserved.

28

such as what needs to be done and what will happen in the background Activities  Lists all single activities during each step along with the documentation for the IMG activity Log  Shows detailed logs per activity © 2011 SAP AG.Automatic Basic Configuration UI components Navigation  Guided procedure with all steps for the basic configuration Help Section  Provides detailed information to each step. All rights reserved. 29 .

and assign the appropriate default roles and to implement the appropriate Central Correction Note (CCN) Basic Configuration  Configures the basic scenarios in SAP Solution Manager (Service Delivery. Maintenance Optimizer. Root Cause Analysis. All rights reserved. 30 . Early Watch Alerts.Automatic Basic Configuration Configuration Roadmap System Preparation  Prepares the system for the configuration  Needs to be performed fully after a new installation  After patches and upgrades needed to update dialog and system users. Issue Management. …)  Needs to be performed after new installations and after support packages to perform delta configuration  Overview screen tells you which configuration needs update Managed Systems Configuration  Connection and configuration of managed systems  Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager  Creation of Logical Components for managed systems © 2011 SAP AG.

All rights reserved.SAP Solution Manager Configuration Overview Screen The overview shows the status of the SAP Solution Manager configuration  Which steps of the configuration have been performed when and by whom  Which steps of the configuration needs an update Check „Update Needed Flag“ to see which activities need to be reperformed after a SP update © 2011 SAP AG. 31 .

32 . So you can decide if a step has been performed successfully or if a reconfiguration is needed for a complete procedure Step was performed successfully Step was performed with errors (check and reexecution needed) Step was performed with warnings (check needed) Step needs reexecution because of changes in the system (SP Update.The new roadmap… …provides detailed status information for each step of a guided configuration scenario.…) © 2011 SAP AG. All rights reserved. configuration changes.

1 Automatic Central Correction Note Check Configuration of needed WebServices Configuration SLD & LMDB Install and configure SAHostAgent Connect SMD agents to Solution Manager Configure LMDB Click on the box to get step details © 2011 SAP AG. All rights reserved. 33 .SAP Solution Manager Configuration System preparation: New steps in 7.

SAP Solution Manager Configuration Basic Configuration: New steps in 7.1 CUA Support for all users Support for Introscope Installation over Diagnostics Agent & Introscope User Management Configuration of Mail/SMS for Solution Manager notification 95% of steps are now automated Click on the box to get step details © 2011 SAP AG. 34 . All rights reserved.

selected 3rd party like Websphere) Technical Scenarios (multiple systems like double stacks) And standalone databases Detailed Status overview: . 35 .RFC working .SAP Solution Manager Configuration Managed Systems Configuration: New steps in 7. All rights reserved.System well defined .ST-API & PI checks Integration of LMDB Technical System maintenance Click on the box to get step details © 2011 SAP AG.1 ABAP/JAVA double stack scenario are automatically created Support for all technical system types (incl.Configuration status .

36 .1 Create and check RFCs for Managed Systems CTS+ and DBA cockpit support Assign Diagnostics Agents to Server Name All Users managed by the Wizard Click on the box to get step details © 2011 SAP AG.SAP Solution Manager Configuration Managed Systems Configuration: New steps in 7. All rights reserved.

Configuration of SAP Solution Manager using SolMan Setup System Preparation .

38 . All rights reserved.System Preparation Steps The System Preparation consists of the following steps:  Create Users  Check Installation  Implement SAP Note  Configure ABAP  Configure Web Service  Prepare Landscape  Complete © 2011 SAP AG.

All rights reserved. you have to create or update dialog and system users.System Preparation Create Users In this step. and assign the appropriate default roles  Select the user you want to create or update  You can create a new user or update the authorizations of an existing user  You can update the authorization either automatically or manually © 2011 SAP AG. 39 .

check the Documentation for information on how to solve the problem  Repeat the check to make sure the problem is fixed  You can exclude checks by setting Execution Status to Postpone or Manual © 2011 SAP AG.System Preparation Check Installation This is an automatic installation check for configuration-relevant parts of the installation  If a check status turns red. 40 . All rights reserved.

41 . Perform the required manual activities. with the SAP Note Assistant (transaction SNOTE) Check the CCN for notes which require manual activities.System Preparation Implement SAP Note In this step. All rights reserved. © 2011 SAP AG. you can download and implement the central correction note (CCN)  The CCN comprises all corrections for the configuration scenarios of the basic configuration  You must implement the central correction SAP Note manually.

All rights reserved. 42 . © 2011 SAP AG.System Preparation Configure ABAP In this step. you automatically perform the following activities:  Create the SAP Solution Manager system in the system landscape (transaction SMSY)  Create logical systems for the SAP Solution Manager  Activate the Service Data Control Center (SDCCN) To avoid manual changes to the definition of the SAP Solution Manager being overwritten in the System Landscape. do not repeat this step after having set up SAP Solution Manager.

509 Certificate Authentication  Ticket Authentication  The activity has to be performed manually as described in the Documentation column  The link in the Navigation column lead you to the Web Dynpro application SOA_MANAGER. you explicitly allow SAP Solution Manager to create web services using the following authentication types:  Basic Authentication  X.System Preparation Configure Web Service In this step. All rights reserved. there you can perform the required setting  Set the Execution Status to “Performed” afterwards © 2011 SAP AG. 43 .

System Preparation Prepare Landscape In the sub-steps of this step:  you make SAP Solution Manager known to the system landscape  you make sure that all relevant information can be transferred from the system landscape to SAP Solution Manager Before configuring the SLD. you need to consider the SLD Landscape Design:  Make sure that all systems are known to the central (runtime) SLD Important: Do not use the local SLD in SAP Solution Manager as runtime SLD together with SAP NetWeaver PI or Web Dynpro Java applications in your system landscape More information on SLD landscape design http://www.sap. 44 . All rights reserved.sdn.com/irj/sdn/nw-sld © 2011 SAP AG.

System Preparation
Select SLD

In this step you enable SAP Solution Manager to access to the System Landscape Directory (SLD):
 If SLDs exist, specify all of them to which either managed systems or Diagnostics agents are connected  For the central SLD select the “Target of SAP Solution Manager DS “ field  If no SLD yet exists, you can set up one in the SAP Solution Manager system automatically

© 2011 SAP AG. All rights reserved.

45

System Preparation
Logical Ports Creation

In this step, you perform the following activities automatically and check the results:
 Create logical ports and end points for web services communication between the ABAP and Java stack of SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager

© 2011 SAP AG. All rights reserved.

46

System Preparation
Prepare Outside Discovery

In this step you prepare the connection of the systems in your landscape to SAP Solution Manager:
 You install the agents on all hosts on which one or more of the following systems is running:  Managed system which should be connected to SAP Solution Manager  CA Wily Introscope Enterprise Manager  Standalone database  Third party product not registered to an SLD  On each virtual host, perform the following steps :  Install Diagnostics Agent  On each physical host, perform the following steps :  Install SAPHost Agent  Establish trusted connection

 On each physical host you need exactly 1 SAP Host Agent  On each host (virtual or physical) you need 1 Diagnostics Agent  1 agent can support several managed systems running on the same named host
47

© 2011 SAP AG. All rights reserved.

All rights reserved.Connecting Agents to the Solution Manager Available connection options Using a direct connection to the message server Using the SLD connection (Agent Candidate Management)  Agent can be installed without having access or credentials to the Solution Manager system  Agent can be provided with new connection data. but also enable the registration in SLD to be able to use the extended connection features (available with Diagnostics Agent 7. even when not connected to the Solution Manager system  Standard when agent is installed together with SAP NetWeaver based product  Connecting the agent to the Solution Manager system can take up to 30 minutes  No additional configuration steps necessary  Is primarily targeted for manual rollout in small landscapes  Agent can be installed and connection is available instantaneous Recommendation: Connect the agent during the installation directly to the Solution Manager.20) © 2011 SAP AG. 48 .

20.com/swdc  Support Packages and Patches  Browse Download Catalog  SAP Technology Components  SAP HOST AGENT  SAP HOST AGENT 7.1 Agents for managed systems SAP Host Agent • You need to install at least patch level 55 of the SAP Host Agent 7. 49 . © 2011 SAP AG.sap.sap. This is described in SAP Note 1473974. so that you can update the Host Agent centrally.20 • This is installation procedure is described in SAP Note 1031096 It is recommended to enable the automatic update feature of the SAP Host Agent. • The installation files are available from http://service.Required Agent Versions Diagnostic Agent • You can use any version of the Diagnostics Agent (already installed agents do not need to be updated) • The agent applications are updated automatically from the Solution Manager • For new installations use the latest available version of the diagnostics agent from http://service. All rights reserved.com/swdc  Browse Download Catalog  SAP Technology Components  SAP SOLUTION MANAGER  SAP SOLUTION MANAGER 7.

All rights reserved.0 / 7.01 SR1 Integrated in NW DVD’s Standalone Version available JVM Default System ID / Instance Support for SLD & direct connection (simultaneously) SSL Support SAProuter Support SAP Host Agent needed Yes No JDK 1.4.2 SMD / J98 7.02 Yes Yes SAPJVM DAA / SMDA97 7. installed / updated) Recommended for new installations © 2011 SAP AG.Differences of the available Diagnostics Agent Versions 7.20 / 7.11 Yes Yes SAPJVM DAA / SMDA97 7.30 Yes Yes SAPJVM DAA / SMDA97 No No No No (saposcol is used) No No No Yes (manual install) Yes Yes Yes Yes (auto install) Yes Yes Yes Yes (auto. 50 .

1  The agents of the following systems need to be connected  Managed Systems  Introscope Enterprise Manager  Solution Manager itself (Self-Monitoring)  Select the agents you want to connect from the list and click „connect“  The status of each agent indicates if the connection data has been written successfully to the SLD © 2011 SAP AG. All rights reserved.System Preparation Connect Diagnostics Agents via SLD In this step you connect all necessary diagnostics agents to the Solution Manager system which are using the SLD connection method:  Select the SLD Server and click „Get Agents“ to retrieve all agents from the selected SLD. 51 . The list of SLD„s is maintained in step 6.

The central SLD provides data via a full content sync 2. you can transfer system landscape data to the LMDB:  The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics Infrastructure and the work center Technical Monitoring  Setup of LMDB: 1. 52 .System Preparation Set Up LMDB – Overview In this step. All rights reserved. Data is migrated from SMSY Important: The activation can take a long time when performed initially © 2011 SAP AG.

System Preparation Set Up LMDB – Details 1 The default input values for the configuration wizard (suitable for most customers) is shown below: You can select the connection type (Remote or Local) and the synchronization direction (Unidirectional or Bidirectional)  If you set the Notification (Y/N) indicator. the user needs the role SAP_SLD_CONTENT_SYNC  If the source is an SLD with a release SAP NetWeaver 7. but at the expense of higher network load For the synchronization process. then the URL is: http://<SLD hostname>:<SLD port> © 2011 SAP AG.1. The sources and the target synchronize faster.0. . you need a user in the source (by default an SLD) with the following authorizations:  If the source is an SLD with a release as of SAP NetWeaver 7. The user needs the role SAP_SLD_GUEST 53 If the source is an SLD. update the support package stack to at least SPS 12. the source will synchronize with the target whenever there is a content change in the source. All rights reserved.

System Preparation Set Up LMDB – Details 2 The default input values for the configuration wizard (suitable for most customers) is shown below: For an SLD. the higher the number. which you should use if you have not created your own namespaces  The rank you enter here should be higher than the rank of the source The rank is a positive whole number which determines the ranking within a synchronization landscape. the higher the ranking. the standard namespace is sld/active. the standard namespace is active. Choose the button Finish to add the new synchronization. All rights reserved. all settings and entries of the previous steps will be displayed. For an LMDB. 54 . In the sixth step of the wizard (Summary). which you should use if you have not created your own namespaces. © 2011 SAP AG.

System Preparation Complete In this step. 55 . All rights reserved. the status of all steps of the System Preparation scenario is displayed:  Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default: SOLMAN_ADMIN) which you have created to start Basic Configuration © 2011 SAP AG.

Configuration of SAP Solution Manager using SolMan Setup Basic Configuration .

57 . All rights reserved.Basic Configuration The Basic Configuration consists of the following steps:       Specify Project Specify User & Connectivity Data Specify Landscape Data Configure Manually Configure Automatically Complete © 2011 SAP AG.

you create a solution for the configuration of SAP Solution Manager:  Additional a logical component for SAP Solution Manager and a Solution will be created  SAP Solution Manager automatically includes all production systems of your landscape which are known to the solution and which are not already part of another solution.Basic Configuration Specify Project In this step. – SAP EarlyWatch Alert is scheduled for all production systems © 2011 SAP AG. All rights reserved. This makes sure that: – You can perform Service Delivery for all production systems. 58 .

you make sure that SAP Solution Manager can be connected to SAP and to other systems © 2011 SAP AG.Basic Configuration Specify User & Connectivity Data In the sub-steps of this step. 59 . All rights reserved.

Basic Configuration Specify Connectivity Data In this step. 60 . you make sure that SAP Solution Manager can be connected to SAP Service Marketplace  Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration  The S-User for SAP Backend will be maintained as the Solution Manager user in the global settings of Solution Manager and it will be used for the RFC connections SAP-OSS and SAP-OSSLIST-O01  The S-User for Communication is the SUser that will be maintained in transaction AISUSER together with the Solution Manager administration user (default: SOLMAN_ADMIN) © 2011 SAP AG. All rights reserved.

This option assumes that the BW is set up in the client you are currently logged on to. to do that you need to perform an additional client copy first  You can use the BW in a separate system. 61 . in this case you have to make sure that: – The level of BI_CONT is always the same as in Solution Manager – The BW works with the “Obsolete Concept with RSR Authorization Objects” Recommendation: To minimize the effort to maintain users. © 2011 SAP AG. select Use Standard SAP Solution Manager BW environment. See SAP note 1487626 for more details. All rights reserved. which is the SAP Solution Manager productive client.Basic Configuration Specify SAP BW System In this step you specify how the SAP Netweaver Business Warehouse (BW) is set up:  You can use the SAP Solution Manager productive client as BW client (recommended)  You can use another client of SAP Solution Manager as BW client.

All rights reserved. 62 . you have to create an SAP Solution Manager administrator on the BW system or update the role profile of an existing BW administrator  You can use the “Test Login” pushbutton the test the credentials of your users © 2011 SAP AG.Basic Configuration Set Up Credentials In this step you assign or create administrator users which can be used for further automatic activities:  Recommendation: Use your previously created administrative user (default SOLMAN_ADMIN) as the SAP Solution Manager administrator. This ensures that the administrator has the required authorizations  Note: If you have set up SAP NetWeaver Business Warehouse (BW) in a separate SAP Solution Manager client or in a separate system.

Basic Configuration Create Users In this step. if BW is in a separate client/system  BI_CALLBACK: user for communication from BW client/system to productive client of SAP Solution Manager © 2011 SAP AG. you have to create or update dialog and system users. and assign the appropriate default roles:  SAPSUPPORT: enables Active Global Support to provide support in the SAP Solution Manager system  SEP_WEBSERV: user for the BMC Appsight License Check Service in the Internet Communication Framework (ICF)  CONTENTSERV: user for services in the Internet Communication Framework (ICF)  SMD_RFC and SMD_BI_RFC: user for RFC communication between the ABAP and Java stack of SAP Solution Manager (also in BW client. if BW is in a separate client/system)  SAPSUPPORT and SMD_BI_RFC are created also in BW client. All rights reserved. 63 .

© 2011 SAP AG. you perform the following activities automatically and check the results:  Create RFC connections between the ABAP and Java stack of SAP Solution Manager  Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents Attention: You have to reperform this step each time you change the users created in the previous step.Basic Configuration Solution Manager Internal Connectivity In this step. 64 . All rights reserved.

and you enable SAP Solution Manager to send notifications via e-mail and SMS © 2011 SAP AG. All rights reserved. 65 .Basic Configuration Specify Landscape Data In the sub-steps of this step. you set up of CA Wily Introscope Enterprise Managers.

you have installed and connected Diagnostics agents on all hosts of your CA Wily Introscope Enterprise Managers (EM) .You need to ensure that the Diagnostics Agent user (smdadm/daaadm/SapServiceDAA) has read write access to the Introscope installation directory © 2011 SAP AG.Basic Configuration Configure CA Wily Introscope – Prerequesites In this step. you connect CA Wily Introscope Enterprise Manager to SAP Solution Manager  You can connect existing CA Wily Introscope Enterprise Managers  or you can install an additional Enterprise Manager using an already installed diagnostic agent. Important prerequesites: . 66 . All rights reserved.In the System Preparation scenario.

Basic Configuration Configure CA Wily Introscope – Connect existing Wily EMs In this step. the administration user of the CA Wily Introscope Enterprise Manager is assigned as the connection user © 2011 SAP AG. All rights reserved. you connect CA Wily Introscope Enterprise Manager to SAP Solution Manager  You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation  You need to assign a connection user to each CA Wily Introscope Enterprise Manager – By default. 67 .

you connect CA Wily Introscope Enterprise Manager to SAP Solution Manager  You can install additional CA Wily Introscope Enterprise Managers. All rights reserved. © 2011 SAP AG.Basic Configuration Configure CA Wily Introscope – Install a new Wily EM In this step. several CA Wily Introscope Enterprise Managers (collector nodes) can be assigned to a Manager of Managers (MoM) Prerequisite for installation: You need to download the Introscope Installation files as well as the OSGI and Eula files and place them in a directory which is accessible to the agent which should install the new instance. 68 . CA Wily Introscope Enterprise Manager are installed as standalone collector nodes  In complex system landscapes. if the capacity of existing ones would be exceeded  Typically.

FTP user names and passwords are transmitted unencrypted. 69 . The saprouttab permission table is security-relevant. © 2011 SAP AG.Basic Configuration Configure SAProuter In this optional step you can allow SAP Solution Manager to access the permission table saprouttab on the SAProuter server via FTP  You do not need to maintain the permission table manually Caution: Unsecured data transfer is used to maintain the saprouttab. All rights reserved. If you allow access via FTP.

. you set up the infrastructure which enables SAP Solution Manager to send notifications via e-mail and SMS:       Node field: enter the name of the SMTP node which handles outgoing e-mail Host field: enter the name of your mail server Port field: enter the port number at which your mail server can be accessed SMTP Active field : enable SAP Solution Manager to send notification via e-mail Fax/Pager Active field: enable SAP Solution Manager to send notification via SMS Domain field: enter the domain name of your organization. if you want to restrict the scope of possible recipients 70 Recommendation: Choose the default value * to ensure that notifications can be sent to any domain. © 2011 SAP AG. All rights reserved.Basic Configuration Configure SAPconnect In this step.

Basic Configuration Configure Manually In this step you have to perform some manual activities in the Solution Manager  Every activity has an IMG documentation were you can find details on what has to be done during the activity Maintain logical systems in transaction SCC4 Configure Service Content Update Specify Transaction Type for Incidents Generate entries in extraction framework © 2011 SAP AG. 71 . All rights reserved.

72 . you can perform the activities manually. or you can postpone the automatic configuration activities © 2011 SAP AG.Basic Configuration Configure Automatically In this step some automatic activities are performed by SAP Solution Manager  If the security regulations of your organization require you to do so. All rights reserved.

the status of all steps of the Basic Configuration of your SAP Solution Manager system is displayed  To make yourself familiar with the functions now available in SAP Solution Manager. choose the Go to SAP Solution Manager Demo Launch Pad link  To connect systems to SAP Solution Manager.Basic Configuration Complete In this step. choose the Go to Managed Systems Configuration link © 2011 SAP AG. 73 . All rights reserved.

Configuration of SAP Solution Manager using SolMan Setup Managed System Configuration .

Managed Systems Configuration The Managed System Configuration consists of the following steps:            Select Product Check Prerequisites Connect Managed System Assign Diagnostics Agent Enter System Parameters Enter Landscape Parameters Configure Automatically Configure Manually Create Logical Components Check Configuration Complete 75 © 2011 SAP AG. . All rights reserved.

All rights reserved. choose the Database tab page If the system that you want to connect is not contained in the technical system list. choose the Technical System tab page  To configure a double (ABAP and Java) stack system. connect the system to an SLD to minimize the effort for maintenance. choose the Technical Scenario tab page – Technical scenarios need to be created manually first  To configure a standalone database.Managed Systems Configuration Configuration of a managed system With the Managed Systems Configuration. 76 . create the technical system manually. © 2011 SAP AG. If required. For more information. you connect systems to SAP Solution Manager  To configure a single system. see SAP Note 1472465.

select the system or scenario and click on the “System Operations  Maintain System or Scenario Operations  Maintain Scenario” button  Via the “Configure System/Scenario/Database” button you open a guided procedure to perform the configuration that connects the technical system. 77 .Managed Systems Configuration Status Overview In the Managed Systems Configuration you have the following options:  Check the status via the traffic lights next to the managed system: – RFC Status (only ABAP): indicated the RFC connection status – Auto Configuration Status: indicates the status of the auto configuration step of the managed system configuration – Plug-in Status (only ABAP): indicates if the ABAP add-ons ST-PI and ST-A/PI are on the fulfill the version requirements in the managed system  Via the „Show Details“ link. you can show detailed status information on the selected system(s) in SAP Solution Manager  To change the information about technical systems and scenarios. All rights reserved. technical scenario or database to SAP Solution Manager  Via the “Export” button you can export the list to Microsoft Excel © 2011 SAP AG.

it must be maintained as Technical Scenario  Technical scenarios group ABAP. Make sure that all needed technical systems … 2. … and the database are known to SAP Solution Manager 3.Managed Systems Configuration Create Technical Scenarios To configure a double stack system. All rights reserved. Create a new scenario 4. type and description of the technical scenario © 2011 SAP AG. Maintain name. 78 . Java and databases that belong together logically  To create a technical scenario choose “Create Scenario” push button on the “Technical Scenarios” tab 1.

. All rights reserved.Managed Systems Configuration Create Technical Scenarios 5. … Review your entries and save! 7. To delete a scenario enter the Technical Scenario Wizard under the Related Links section of the Solution Manager Administration Workcenter 79 © 2011 SAP AG. Select technical systems … 6.

Managed Systems Configuration Roadmap Overview The roadmap of the managed system configuration is dependent on the type / product of the selected managed system. choose the Technical System Details link in the roadmap © 2011 SAP AG. All rights reserved. scenario or database: Database only J2EE system Dual stack system To get more information about the selected system / scenario. 80 .

All rights reserved.Managed Systems Configuration Select Product (1/2) In this step. You go to the Technical System Editor screen. Repeat steps 1 . 3. 2. 4. On the Product Instances tab page. 5. Choose the Edit Products pushbutton. see: SAP Note1472465 81 © 2011 SAP AG.4 for all technical systems To find out the correct product versions and main instances. . Save and exit. you define which product is used for the diagnostics configuration  Based on this selection the appropriate extractors are scheduled 1. Select the technical system. to select the applicable product version and product instance. choose the Add pushbutton.

All rights reserved. you create a product system  Based on this selection the usage of the system in logical components and solutions is determined 1. Landscape Verification Wizard – Create the Product System and assign Technical System Alternative: Create Product Systems with the Edit Product Systems pushbutton to call SMSY Transaction in ABAP Stack © 2011 SAP AG. Select the technical system. 3. Choose the Goto Landscape Verification Wizard pushbutton.Managed Systems Configuration Select Product (2/2) In this step. 2. 82 .

 To perform the activity. All rights reserved. The selected ABAP system is transferred from LMDB into SMSY.  To perform the configuration activities manually. 83 .  To perform the configuration activities automatically. choose the Display link. do the following:  In the Documentation column.Managed Systems Configuration Check Prerequisites In this step. a minimum version for different software components need to be provided. choose the link in the Navigation column. choose Execute All  In the Log screen area. you automatically check the prerequisites for the configuration of SAP Solution Manager  Diagnostics Prerequisites: Depending on the version of SAP Solution Manager and the version of the managed system. © 2011 SAP AG. the system displays messages for the selected prerequisites check.  Fetch system from LMDB to SMSY: This activity ensures the consistency of ABAP systems between SMSY and LMDB.

you activate the Service Data Control Center (SDCCN) in the managed system   In the Clients and existing RFCs screen area. you create RFC connections to each managed system  For each managed system. you have to create at least one READ RFC connections to any client  Additionally.Managed Systems Configuration Connect Managed System In this step. select the client you want to connect Select the RFCs to be created:  Mandatory: RFC Destination and User for Read Access: To enable basic SAP Solution Manager functions you are required to explicitly allow read access  Recommended: TMW Destination and User for Change Manager enables change requests  Optional: RFC Destination for Solution Manager Login Destination: access with logon screen Trusted Destination: without additional authentication. 84 . All rights reserved. Prerequisites: user exists in both systems with authorization object “S_RFCACL” © 2011 SAP AG.

choose the SLD Agent Candidates tab page. you assign the diagnostics agents to the managed systems  You assign a diagnostics agent to each server (virtual host) on which the managed system is running 1. © 2011 SAP AG. On the Agent Assignment tab page. Choose the Assign pushbutton and select the applicable agent from the list. 2. select a server. select the applicable agent from the list and choose the Connect pushbutton. If the applicable diagnostics agent is not displayed in the list. All rights reserved. 85 .Managed Systems Configuration Assign Diagnostics Agent In this step.

Java. you do the following:  Position the cursor on the field  In the context menu. for example ABAP. All rights reserved.Managed Systems Configuration Enter System Parameters In this step. you specify all system parameters required to configure the managed system  The parameters to be specified depend on the type of managed system you configure. select Display Quick Help  © 2011 SAP AG. 86 . database systems To display help on how to enter a value.

verify the landscape parameters carefully. choose the parameter in the Status column © 2011 SAP AG. check the status of each parameter: – The status is set to No Parameters: No input required – The status is set to Default used: Verify the parameter – The status is set to Input missing: Enter the parameter – The status is set to Agent offline: Restart the diagnostics agent  To change or enter values. All rights reserved.Managed Systems Configuration Enter Landscape Parameters In this step. 87 .  In the Landscape Objects hierarchy. you verify or add landscape parameters  Attention: To avoid time-consuming error search.

88 . SAP Solution Manager creates the users in the managed system needed for connection and support  Select user from the list SAPSUPPORT SMDAGENT_SI7  Select Action – Create new user – Update authorizations of existing user – Provide existing user  Choose Execute © 2011 SAP AG.Managed Systems Configuration Create Users In this step. All rights reserved.

messages and other detailed information for a selected automatic activity are displayed in the Log screen area © 2011 SAP AG. choose the Execute All pushbutton  Note: The automatic execution of the configuration activities can take a few minutes. 89 . After the configuration.Managed Systems Configuration Configure Automatically In this step. All rights reserved. SAP Solution Manager performs automatic configuration activities  To start automatic configuration.

select Performed. to open the service connection for the maintenance case  Adjust HTTP Log Parameter: set parameter to enable the analysis of logs written by the Internet Communication Manager  Activate Flight Recorder: set the parameter for J2EE based systems to collect data also in case the J2EE system is crashing  Restart of the Java stack is required to enable Wily metric collection     In the Documentation column. In the Execution Status column.Managed Systems Configuration Configure Manually In this step you perform manual configuration activities  Maintain SAPRouter data: maintain the SAProuter data for the managed system in the Service Market Place. Follow the instructions in the documentation. choose the Display link. All rights reserved. . 90 © 2011 SAP AG. choose the link in the Navigation column. To perform the activity.

usable logical components are displayed  You can assign the system to an existing logical component.Managed Systems Configuration Create Logical Components To use your system in solutions and projects. you assign the selected system to one or more logical components in this step  Depending on the product version of the selected system. choose Save in the navigation bar © 2011 SAP AG. by selecting system and client in the respective column  You can also create a new logical component by choosing the New Logical Component pushbutton  To save you entries . All rights reserved. 91 .

92 . you automatically check whether the system is configured correctly. and you update the statuses in the overview of the Managed Systems Configuration  If you have errors in one of the checks. please check the details in the log area © 2011 SAP AG.Managed Systems Configuration Check Configuration In this step. All rights reserved.

Managed Systems Configuration Complete In this step. 93 . the status of all steps of the Managed Systems Configuration of your SAP Solution Manager system is displayed  Now you can start using Work Centers © 2011 SAP AG. All rights reserved.

94 .com/wiki/display/SMSETUP Solution Manager Authorizations Wiki in SDN http://wiki. Upgrade Guides.sap.sap.sdn.Additional Information Application Lifecycle Management with SAP Solution Manager http://service. Security Guides.1 Where to get the software http://service.sap.com/swdc  Installation & Upgrades  A-Z Index  SAP Solution Manager  SAP Solution Manager 7. Sizing Toolkit.com/alm SolMan_Setup Wiki in SDN http://wiki.com/instguides  SAP Solution Manager  Release 7. …) http://service.sap. Installation Guides.sdn.1 © 2011 SAP AG. All rights reserved.com/wiki/display/SMAUTH Guides for SAP Solution Manager (Master Guide.sap.

Thank You! .

Sign up to vote on this title
UsefulNot useful