0% found this document useful (0 votes)
559 views

SolMan ContentServer Monitoring

SAP Solution Manager Content Server Monitoring

Uploaded by

ediranni
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
559 views

SolMan ContentServer Monitoring

SAP Solution Manager Content Server Monitoring

Uploaded by

ediranni
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

SAP

Content Server 6.40/6.50 Monitoring


with SAP Solution Manager 7.1
Setup Guide

CUSTOMER
Document Version 1.0.1-2017-01-09
This page is left blank for documents that are printed on both
sides.
SAP CONTENT SERVER MONITORING

TABLE OF CONTENTS
INTRODUCTION ........................................................................................................................................... 6

SETUP PROCEDURE OVERVIEW ................................................................................................................... 7

1. INSTALL DIAGNOSTICS AGENT ................................................................................................................. 7

2. REGISTER SAP CONTENT SERVER 6.40/6.50 IN SAP SOLUTION MANAGER .............................................. 8

2.1 Select System type ................................................................................................................................. 8

2.2 Define System ........................................................................................................................................ 8

2.3 Define Extended SID............................................................................................................................... 9

2.4 Confirmation.......................................................................................................................................... 9

2.5 Specify additional system properties ...................................................................................................... 9

2.6 Add SAP CONTENT SERVER 6.40/6.50 as Product Instances ...................................................................10

2.7 Assign Database to the technical system. ..............................................................................................12

3. RUN MANAGED SYSTEM CONFIGURATION ............................................................................................13

3.1 Select Product .......................................................................................................................................13

3.2 Check Prerequisites...............................................................................................................................13

3.3 Assign Diagnostics Agent .......................................................................................................................13

3.4 Enter System Parameters ......................................................................................................................13

3.5 Enter Landscape Parameters .................................................................................................................14

3.6 Configure Automatically........................................................................................................................14

3.7 Complete setup.....................................................................................................................................14

4. RUN MANAGED SYSTEM SETUP FOR MICROSOFT IIS COMPONENTS (WINDOWS ONLY) .......................15

5. RUN TECHNICAL MONITORING SETUP FOR SAP CONTENT SERVER SYSTEM (WINDOWS ONLY) ............17

6. RUN TECHNICAL MONITORING SETUP FOR MICROSOFT IIS SYSTEMS (WINDOWS ONLY) ......................19

ADDITIONAL INFORMATION ......................................................................................................................21

3
SAP CONTENT SERVER MONITORING

4
SAP CONTENT SERVER MONITORING

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

5
SAP CONTENT SERVER MONITORING

Introduction
SAP Solution Manager 7.1 SP10 supports SAP Content Server 6.40 with System Monitoring. This document
describes how to setup and configure System Monitoring in the SAP Solution Manager 7.1 SP10 for SAP
Content Server 6.40 and 6.50.

This guide is part of a global installation and configuration documentation. You may find more information
in the SAP Service Marketplace

· Root Cause Analysis Installation and Upgrade Guide with SOLMAN_SETUP


https://service.sap.com/diagnostics à Installation and Configuration
· Solution Manager Installation Guides
https://service.sap.com/instguides àSAP Components à SAP Solution Manager > Release 7.1
· SAP Solution Manager 7.1 on help.sap.com
http://help.sap.com/solutionmanager71

Up-to-date version of this document is attached to the SAP note 1895715.

6
SAP CONTENT SERVER MONITORING

Setup procedure overview

From the point of view of the System Monitoring, SAP Content Server 6.40 or 6.50 is a database based
system with additional server components. The database (MaxDB) is the core component of a SAP Content
Server installation. In addition SAP Content Server uses the server components: Microsoft ISS components
on Windows and Apache HTTP Server on UNIX. With the SAP Solution Manager 7.1 SP10 you can monitor
the system’s database and the server components on Windows (like MS ISS). No monitoring is available for
Apache HTTP server yet.

The approach is to monitor the SAP Content Server as a technical scenario comprising three systems:
· SAP Content Server system (of the Unspecific Standalone System type) as the representation of the
server components.
· the system database
· MS IIS system on Windows

Perform following steps listed to set up System Monitoring for SAP CONTENT SERVER system (on Windows)

Step 1 Ÿ Install Diagnostics Agent

Step 2 Ÿ Register SAP CONTENT SERVER in SAP Solution Manager

Step 3 Ÿ Run Managed System Setup for SAP CONTENT system

Step 4 Ÿ Run Managed System Setup for Microsoft IIS components

Step 5 Ÿ Run Technical Monitoring Setup for SAP CONTENT system

Step 6 Ÿ Run Technical Monitoring Setup for Microsoft IIS systems

1. Install Diagnostics Agent


Please refer to SAP note 1365123 Installation of Diagnostics Agents.

7
SAP CONTENT SERVER MONITORING

Diagnostics Agent 7.3 installs automatically SAP Host Agent. Please make sure, however, that SAP Host
Agent corresponds to the version in the SAP note 1448655. In addition, please refer to SAP Note 1031096
“Installing Package SAPHOSTAGENT” for details.

2. Register SAP CONTENT SERVER 6.40/6.50 in SAP Solution Manager


Landscape information is the basis for all processes in SAP Solution Manager 7.1. SAP Solution Manager
stores the landscape information in the Landscape Management Database (LMDB). Usually systems
automatically report their landscape data to the SAP Solution Landscape Directory (SLD). Solution Manager
uses one or multiple SAP Software Landscape Directory (SLD) systems to query for the landscape
information. For that purpose SAP Solution Manager 7.1 provides content synchronization mechanism
between SLD and LMDB.

However, SAP Content Server does not provide automatic registration to SLD. The system has to be
registered manually in the SAP Solution Manager. With the Technical System Editor UI in SAP Solution
Manager 7.1 you can manually create, change, and delete technical systems in the LMDB.

Perform following activities to register the SAP Content Server system in SAP Solution Manager:

1. In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Managed


Systems Configuration à Technical Systems à System Operations àCreate System.
2. Select a system type from the input help.
3. Define system data like system name and the host there the system is installed
4. Assign a unique system identifier.
5. Create the system
6. Specify required system properties like the installation path.
7. Add SAP CONTENT SERVER 6.40 resp. 6.50 as the product instance.
8. Assign SAP CONTENT SERVER 6.40/6.50 product and mark it as diagnostics relevant.

2.1 Select System type


Select “Unspecific Standalone Application System” as the system type.

2.2 Define System


Specify the main system properties in the “Define System” step.

8
SAP CONTENT SERVER MONITORING

- Assign a system name – a unique identifier of the new system in the LMDB.
- Select the “Others” as the technology type for the system.
- Specify the host name of the SAP Content Server system.

2.3 Define Extended SID


Specify an appropriate extended system ID and choose next.

An extended system ID is a system-type specific identifier of eight characters that is unique in the SAP
Solution Manager. An extended system ID value is automatically proposed so you can accept it.

2.4 Confirmation
Choose Save to create new SAP Content Server system

2.5 Specify additional system properties


In the System Overview add the installation patch of the SAP Content Server system.

9
SAP CONTENT SERVER MONITORING

Note: the “Installation Path” in above screen shot is required and will be used as an in-built variable to
allocate the system log file (CS_Trace.txt) in system monitoring phase.

2.6 Add SAP CONTENT SERVER 6.40/6.50 as Product Instances


Add all SAP CONTENT SERVER 6.40/6.50 as the Product Instance to the system.

- Select the node “Software” in the navigation tree.

- Choose “Product Instances (Details)” in the right tab panel.

10
SAP CONTENT SERVER MONITORING

- Click on the “Add” button.

- Input “SAP CONTENT SERVER 6.40/6.50” in the input box and click on “Search” button.

11
SAP CONTENT SERVER MONITORING

- Make sure to check the check-box “Installed” and “Diagnostics-Relevant” and then click on “Close”
button.

More Information

For more information, see Landscape Data Management Overview and Maintenance of Product in the
System Landscape in the SAP Community Network.

2.7 Assign Database to the technical system.


Explore the node “System Database” in the navigation tree. Assign a system database to the technical
system. The SAP CONTENT SERVER system’s database is MaxDB and its information will be automatically
12
SAP CONTENT SERVER MONITORING

delivered to Solution Manager by Diagnostics Agent’s outside discovery. For components for which no
automatic registration on SLD can be established, SAP Solution Manager provides the outside discovery
approach. With the outside discovery the Diagnostics Agent automatically collects and stores the
information related the monitored system in the Solution Manager. The data is reported to the LMDB and
is not available in the SLD. The registration exists only in the Solution Manager system. Outside discovery is
currently available for DBMS, operating systems and Microsoft ISS/.NET components.

Click on the “Assign System Database” button and select the correct database system from the list.

3. Run Managed System Configuration


In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Managed Systems
Configuration à Technical Systems, select the SAP Content Server system (the Unspecific system you
create before) and choose Configure System.

3.1 Select Product


The SAP CONTENT SERVER 6.40/6.50 product was already assigned in the Technical System Editor. Continue
with the step 3 Assign Diagnostic Agent.

3.2 Check Prerequisites


There are no prerequisites. Continue with the next step.

3.3 Assign Diagnostics Agent


Connect the Diagnostics Agent to the Solution Manager and assign it to the SAP CONTENT system.

3.4 Enter System Parameters


Enter the database parameter under the step “Enter System Parameters” – “DB Parameters”. And then
click on the button “Setup DBA Cockpit connection”. The “DBA Cockpit Connection Status” will green light
when connected to the managed database successfully. Then choose Save to save the changes and
continue with the next step.

13
SAP CONTENT SERVER MONITORING

3.5 Enter Landscape Parameters


There are no landscape parameters need to be entered. Continue with the next step.

3.6 Configure Automatically


Execute the steps “Extractors Setup”. Continue with the last setup step “Complete”.

3.7 Complete setup


Complete the setup, choose “Finish” to update the setup status and quit the setup procedure.

14
SAP CONTENT SERVER MONITORING

4. Run Managed System Setup for Microsoft IIS components (Windows only)
SAP Solution Manager 7.1 supports Microsoft IIS with System Monitoring. The Microsoft IIS components
which are part of the SAP Content Server installation will be automatically registered in the SAP Solution
Manager by Diagnostics Agent per outside discovery. For components for which no automatic registration
on SLD can be established, SAP Solution Manager provides the outside discovery approach. With the
outside discovery the Diagnostics Agent automatically collects and stores the information related the
monitored system in the Solution Manager. Outside discovery is currently available for DBMS, operating
systems and Microsoft ISS/.NET components.

The Diagnostics Agent will discover Microsoft IIS components installed on the SAP Content Server host and
report them to SAP Solution Manager.

- In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Related Links
àAdministrationà Landscape Browser.
- Look up for Microsoft ISS system IDs. Search for the SAP Content Server host and find the assigned
Microsoft IIS systems in the tree below the host name

- In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Managed


Systems Configuration à Technical Systems, select and choose Configure System for each
Microsoft IIS system component of the SAP Content Server installation.
- Perform the Managed System Configuration for Microsoft IIS systems

15
SAP CONTENT SERVER MONITORING

More Information

For more information on Outside Discovery in SAP Solution Manager, see


http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape SAP
note 1626853. Refer to SAP note 1743474 for more information on how to perform Managed System
Setup for Microsoft IIS.

16
SAP CONTENT SERVER MONITORING

5. Run Technical Monitoring Setup for SAP Content Server system


(Windows only)
For SAP Content Server systems installed on Windows, SAP Solution Manager additionally provides the
exception monitoring.

In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Technical Monitoring >
Define Scope. Select the SAP Content Server system and continue with the next step Setup Monitoring.

· Apply and Activate monitoring template for SAP Content Server technical system.

a. View the metric template settings.

17
SAP CONTENT SERVER MONITORING

Click on the link “Configure Managed Object” and view the metric settings in the pop-up window. Generally,
the settings are set by default and no needs to change them.

· Apply and activate the MaxDB template for SAP CONTENT SERVER database.

18
SAP CONTENT SERVER MONITORING

Click on the link “Configure Managed Object” and view the metric settings in the pop-up window. Generally,
the settings are set by default and no needs to change them.

6. Run Technical Monitoring Setup for Microsoft IIS systems (Windows


only)
In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Technical Monitoring >
Define Scope. Select and perform monitoring setup for each Microsoft IIS system component of the SAP
CONTENT installation.

· Select the Microsoft IIS system in step “Define Scope”.

19
SAP CONTENT SERVER MONITORING

· Go to “Setup Monitoring” step.

Assign the MSPT NET.FRAMEWORK monitoring template of the corresponding version to each Microsoft IIS
instance and apply and activate templates.

20
SAP CONTENT SERVER MONITORING

Additional Information

SAP note 1448655 Installation of Diagnostics agent 7.3

SAP note 1365123 Installation of Diagnostics agent

SAP note 1031096 Installing Package SAPHOSTAGENT

SAP note 790639 SAPOSCOL and ABAP server: Monitoring processes

SAP note 1626853 Outside Discovery in SAP Solution Manager

SAP note 1743474 Monitoring Setup of Microsoft IIS components (the example for Sharepoint
Online appication)

21
www.sap.com

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP


BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products
and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other
countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal


Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business
Objects products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of Business Objects Software
Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and
other Sybase products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Sybase Inc.
Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered
trademarks of Crossgate AG in Germany and other countries. Crossgate 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.

You might also like