SolMan ContentServer Monitoring
SolMan ContentServer Monitoring
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
2.4 Confirmation.......................................................................................................................................... 9
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
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
6
SAP CONTENT SERVER MONITORING
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)
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.
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:
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.
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
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.
10
SAP CONTENT SERVER MONITORING
- 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.
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.
13
SAP CONTENT SERVER MONITORING
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
15
SAP CONTENT SERVER MONITORING
More Information
16
SAP CONTENT SERVER 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.
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.
19
SAP CONTENT SERVER MONITORING
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 1743474 Monitoring Setup of Microsoft IIS components (the example for Sharepoint
Online appication)
21
www.sap.com
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.