1. Summary
This document contains a checklist to be performed
before the go live of a system to be presumed as system monitoring enabled.
2. Table of Contents
Section
3
is to check if the data is coming into solution manager without which, the data
would not be available at the solution manager end. This section contains
checks on solution manager getting system component data of managed system to
the LMDB, the background jobs setup to collect the data from system monitoring
perspective.
Section
4
is to check if the LMDB is updated with the proper data automatically, the
necessary components marked for “Diagnostics” so that the extractors for these
components are enabled.
Section
5
is to check the status of managed system configuration, the RFCs, the system
parameters and the most critical part of “Configure Automatically”.
Section
6
is to check the status of “System Monitoring” in the system.
3. Pre-requisites Check in Solution Manager
3.1 The System Preparation and Basic Configuration
3.2 Check Users
3.3 Check Central Correction Note
3.4 LMDB – SLD Synchronization
3.5 Wily Introscope Enterprise Manager
3.6 Solution Manager Extractor Job
4. LMDB and Technical System
4.1 Definition of Technical System
4.2 Diagnostics Relevant
4.3 Product System
4.4 FQDN for Hosts
4.5 RFC Destination (For ABAP System Only)
5. Managed System Configuration
5.1 Check Status of Managed System Configuration
5.2 Check RFC Destinations
5.3 Diagnostics Agent and Host Agent
5.4 System Parameters
5.5 Configuration Users
5.6 Configure Automatically
5.7 Logical Components
5.8 Extractors
6. System Monitoring
6.1 Configure Infrastructure
6.2 Define Scope
6.3 Setup Monitoring
6.4 Reporting
3. Pre-requisites Check in Solution Manager
3.1 The System Preparation and Basic Configuration
Run transaction SOLMAN_SETUP
Ensure update needed should be blank, that is all the
updates necessary must be performed. The most common update is updating the central
correction note and unlocking of the critical users.
3.2 Check Users
Check the following users and ensure it is unlocked.
SOLMAN_ADMIN
SMD_ADMIN
SM_EXTERN_WS
SM_INTERN_WS
SOLMAN_BTC
3.3 Check Central Correction Note
Check if the latest version of the central correction
note is implemented. Once implemented, proceed to section 3 of “System
Preparation” in SOLMAN_SETUP, execute “Post Processing” manually.
3.4 LMDB – SLD Synchronization
Ensure the following two jobs run in solution manager
successfully at a frequency of 10 minutes.
SAP_LMDB_LDB_0000000001
SAP_LMDB_NOTIFY_LDB_0000000001
3.5 Wily Introscope Enterprise Manager
Ensure that Wily Introscope Enterprise Manager is
always available. To check the availability, proceed to path SM_WORKCENTER -->
Solution Manager Administration --> Infrastructure --> Expert Mode.
The status of Manageable and Status should be green.
3.6 Solution Manager Extractor Job
The most critical job in solution manager is the
extractor job, this job runs every minute once. The job name is
EFWK_RESOURCE_MGR. Check the status of the jobs and the job log. There should
be no line indicating that the resource cap has exceeded.
4. LMDB and Technical System
4.1 Definition of Technical System
The data supplier should be automatic that is it should
be from the SLD; the system should be marked as installed.
4.2 Diagnostics Relevant
Both Application Server ABAP and Process Integration (Functional
component, system taken as an example) should be marked installed and the
Diagnostics relevant flag marked (in this case it is not done). The Product
system should be created and assigned as shown.
4.3 Product System
4.4 FQDN for Hosts
Ideally, all the hosts should have FQDN filled in.
4.5 RFC Destination (For ABAP System Only)
The RFC destinations must be created and maintained (can
be done during managed system configuration as well.
5. Managed System Configuration
5.1 Check Status of Managed System
Configuration
Ideally, all the statuses should be in “Green”. Update
needed should not mark.
5.2 Check RFC Destinations
On choosing “Test”, for the client, the output should
be as shown below.
5.3 Diagnostics Agent and Host Agent
SMD Agent should be in status green and on clicking
“Check Host Agents” the result in the log also should be green as shown below.
System Parameters
5.4 System Parameters
Load balancer host and port should be reached
successfully
On “Check URL…” the return code should be 200.
The user provided should have sufficient roles and
authorizations. Ensure it is provided and updated.
DB Parameter’s must be filled and the system marked for
“Setup DBACockpit / DB extractors”.
5.5 Configuration Users
Configuration users must be created and must be
working. The test of SMDAGENT_CSQ user must pass through.
5.6 Configure Automatically
Configure automatically must be in status green.
5.7 Logical Components
A logical component must be created and the system
assigned to the logical component.
The logical component should be assigned to the
solution. To do this, proceed to transaction SMSY --> Solution Landscape -->
Choose the solution and in edit
mode, add the logical component to the solution.
5.8 Extractors
Ideally all the extractors
created must be in green status. Path to access Extractor: SM_WORKCENTER -->
Solution Manager Administration --> Landscape --> System --> Extractor
Framework
6. System Monitoring
6.1 Configure Infrastructure
All the steps of “Configure Infrastructure” must be in
“Green” status.
6.2 Define Scope
The status of Auto Configure, Monitoring and Reporting
should be green.
6.3 Setup Monitoring
The templates must be active and applied. The
“Assignment Status” must not be yellow – which indicates it has to be
re-applied again.
6.4 Reporting
Reporting should be in status green.
Thanks for Sharing this Information. SAP Basis Institute in Gurgaon
ReplyDelete