Solman 7.2 SP12: System Preparation & Technical Monitoring Steps

Introduction:

In this blog I have covered important steps of Solman configuration and technical monitoring, it is a newly installed solution manager 7.2 SP12 with Sybase 16, I have captured the issues and troubleshooting steps that was encountered during configuration, it captures the below important phases.

1. SLD installation
2. SAP Backbone Connection
3. System Preparation
4. Infrastructure preparation
5. Basic Configuration
6. Managed System Configuration
7. Technical Monitoring Setup

SLD issue:

During Installation of SLD choose UME to client 001 of Solman

During installation of JAVA SLD system, we face an issue with ASE installer, it terminates with return code 255 as per screenshot below

Error Message: Assertion Failed: Unable to install database software, The ASE installer terminated with return code 255.

Kindly check the VAR log message.

Refer SAP Note Number 2234605 and adjust the semaphore value of kernel to 4096 if not set.

To check current value of semaphore run command

cat /proc/sys/kernel/sem

To change the current value, edit file /etc/sysctl.conf and place the value as below

kernel.sem = 250 32000 32 4096

SAP Backbone Connection:

SAP Backbone Connection is required before running Solman Setup Configuration.

Pre-requisite:

1. Request for creation of SAP technical User
2. Download and Install SSL Certificate in SAP PSE Client/ SAP PSE Anonymous both

Please refer SAP Note Number 2631190, to download the certificates

Please Run Task List for SAP backbone connection, Run STC01 for task list SAP_SUPPORT_HUB_CONFIG and execute each of them step by step

We can also refer link below to execute the Steps

Link: https://blogs.sap.com/2019/11/14/step-by-step-guide-on-sap-support-backbone-update-and-enabling-note-assistant-for-digitally-signed-sap-notes/

Once Backbone Task Done, please execute report RCWB_SNOTE_DWNLD_PROC_CONFIG and set the RFC for SAP Note download from SNOTE

System preparation:

In system preparation Phase we must maintain our technical user, and it will create AISUSER and map with technical user.

AISUSERS:

1. SAPSUPPORT
2. SM_SM2B

Infrastructure Preparation

a) SLD Connection:

Two HTTP External RFC must be created

1. LMDB_SLD_TRG1
2. LMDB_SYNCDEST2

Allocate three SLD roles to RFC

SLD Link: http://<FQDN>:5<INST NO>00/sld

Please make sure that username and password are correctly maintained under in Destination of SLD data supplier and SLD client for J2EE_ADM_SID

Under SLD Data supplier Configuration collect and send data must be green

 b) LMDB Synchronization:

It shows yellow amber light, to make LMDB green, please make sure that the latest Model version and CR content is uploaded into SLD under CIM

To Upgrade Model and CR Content version, please upload latest file from SLD administration and import CIM.

For Model version it will take 10 minutes of time and for CR version it will take 4 hours of time.

c) LMDB content check:

We must make sure that Solman ABAP system and SLD JAVA system SID must visible under content check.

we must register Solman ABAP and JAVA both system into SLD.

SLD Link: http://<FQDN>:5<Instanceno>00/sld

To register ABAP system, we must use RZ70

In RZ70, we must maintain the SLD host name and SLD gateway service details, and http destination information for SLD, please also ensure that the gw/acl_mode value for both JAVA and Solman must set to zero

Please also follow note number to register ABAP system into SLD, 2497068 – Comparison method violates its general contract in SLD Log

To register Java system, we must use NWA portal and create two destinations as SLD_Client and SLD_DataSupplier, go to Configuration->Security->Destination

Go to Configuration->Infrastructure-> SLD data Supplier Configuration, click on collect and send data

d) Define http Connectivity: we must endure that all the http ports defined must be open, we can test the same via telnet command

e) Diagnostic agent authentication:

we must ensure that the SMD agent installed for all the sap application including Solman as well and SMD agent must register under Agent Admin Portal.

Agent Admin portal Link: http://FQDN:5<Instanceno>00/AgentAdmin

Step to register SMD to Agent Admin portal as below.

1. Navigate to SMD script directory /usr/sap/DAA/SMDA98/script
2. Check HTTP port number of message server for Solman using Tcode SMMS
3. Run Script from the script directory of SMD agent

[./smdsetup.sh managingconf hostname:”sapms://FQDN” port:”8101″” ]

4. Check Agent Admin Portal for the registered SMD agent
5. If agent is not visible, then check non-authenticated agent box and authenticate it.
6. We must ensure that SMD is up and running fine via command from exe JSMON pf=< instance profile name>

After that we can see the authenticated SMD agent information under diagnostic agent authentication

f) Define CA Introscope:

We must install Willy into solution manager, create folder for Willy inside the path /usr/sap/ccms

1. Download and UNZIP the Willy installer media
2. Change file – ca-eula.txt From reject to accept
3. Install by executing command below
4. ./introscope10.5.2.27linuxAMD64SAP.bin -Djava.awt.headless=true
5. To start/stop and check the status run ./EMctrl.sh <start/stop/status>
6. Check the version installed, read the log /usr/sap/ccms/wilyintroscope/logs

After installation common issue with Willy, it shows offline. To fix the same check below

1. Please make sure the Willy URL is accessible after installation http://<Solman JAVA fqdn>:<java http port>/smd/Introscope?operation=em
2. Check the correct JAVA version and installed with correct Willy version
3. HTTPS port option must uncheck
4. Update the Willy password from User management option of Solman setup
5. Implement SAP note no 3017823, for Solman 7.2 sp12 specially for this version

g) Setup Email Communication: It will pick the host name, SMTP host, domain name and Email information, SMTP node must be active and defined

Basic Configuration

1. Configure Basic function: it will activate all the Basic functionality related to solution manager
2. Schedule Job: This activity creates most of the main job schedules necessary for SAP Solution Manager. Existing job schedules are checked and changed or removed if they are obsolete. We do not recommend performing this activity manually, job by job, using transaction SM36, as each job has its own job definition in an SAP-internal configuration table, with an appropriate periodicity and start time.
3. Configure Manually: In this step, you configure the following:
   • Content update (SAP Solution Manager Content, service content).
   • Connection from SAP to the SAP Solution Manager system.
   • Session housekeeping.

4. Create Basic Dialog users: In this step, you create or update users. Depending on your scenario and step, you also assign roles to the users.

Manage system Configuration:

Before running Manage system configuration for satellite system, we must ensure that the latest ST-PI and ST-API component patch is applied, select system, and run full configuration.

1. Assign Product: This step specifies the software installed on a technical system.

The software that is installed on a technical system is described by several entities in the landscape management database (LMDB): Software component versions are the lowest level.

Product instances are group software component versions that must be installed on a single technical system.

2. Check Pre-requisites: In this step, you check the prerequisites for the configuration of SAP Solution Manager automatically
3. Maintain RFC’S: In this step you create or delete RFC connections to the clients in managed systems, for example, client 200. For each managed system, you should create at least a READ RFC connection to the production client.

Depending on the scenario you want to configure with the managed system, you create RFC connections to several clients. This is the case, for example, in the Change Request Management, Quality Gate Management, PI-System, and Project Management scenarios.

4. Assign Diagnostic agent: In this step, you assign Diagnostics Agents to each server (host) on which managed systems are running.
5. Enter System parameters: In this step, you specify the system parameters that are required to configure the managed system, depending on the type of the managed system, for example, AS ABAP, Java, or database systems. You need a technical user to perform this step. Do not use end user accounts here.
6. Maintain Users: In this step, create new users, update users, and assign roles to:

• Technical users

These users (of type System) are created in ABAP. The password is auto generated, and is not known to the end users

• Dialog users

These users have an initial password that must be changed at their first logon. Dialog users need to change their password regularly. SAP Solution Manager Configuration creates default dialog users, such as for root cause analysis (SAPSUPPORT)

7. Finalize Configuration: In this step, you configure the technical system, and for ABAP systems the client, based on the input which you have provided in the previous steps.
8. Check Configuration: In this step, you automatically check whether the system is configured correctly, and you update the statuses in the overview of the Managed Systems Configuration.

In edit mode, you can do the following to automatically perform the configuration activities:

• You can change the status of an activity to determine whether it is to be performed.

In the Execution Status column, select a status.

• You can perform all automatic activities.

Make sure that the status of all relevant activities is set to Execute and choose Execute All.

Depending on the number of activities, the execution may take several minutes.

• You can perform a single automatic activity.

Make sure that the status of the activity is set to Execute, select the activity, and choose Execute Selected.

You can also perform activities manually:

1. Follow the instructions in the documentation of the activity.
2. After you have performed the activity, select a status in the Execution column:
   • If the activity was executed successfully, select Manually Performed.
   • If any error occurred in the activity, select Manually Performed with Errors.

Note: To display detailed information about an activity, choose Display in the Documentation column.

For each activity that you perform, the system displays log messages in the Log screen area:

1. To display a detailed description of a message, choose the link in the Details column.
2. To analyze an error with an analysis tool, choose the link in the URL column.
3. To check errors in the log of failed batch job executions, open Job Management (SM37) and enter the job name.

System Monitoring:

Click on Application operation and then select system monitoring under Solman setup.

1. Configure Technical Systems: In this step, you configure the monitoring infrastructure. Under Steps, you see a list and a status overview of the sub steps of the Configure Infrastructure step. Use the links to go directly to the sub steps.
2. Check Prerequisites: In this step, you use the automatic activities to check the prerequisites for the configuration of the System & Application Monitoring infrastructure
3. Configure Manually: In this step, you perform manual activities to configure the System and Application Monitoring infrastructure.
4. Default settings: In this step you can enable or disable the following functions for the System & Application Monitoring, click on notification tab and add recipients list.
5. Report settings: In this step, the Health Check results of the BI-based reporting are displayed, so you can see whether the preconditions for successfully activating the BI-based reporting are met. If no Health Check is finished with an error, activate the BI content if you want to use BI-based reporting.
6. House Keeping: In this step, you can specify the lifetimes of the metrics in the BI and the data in the Alert Store and Event Store.
7. Work mode settings: In this step, you configure the standard behavior of the Monitoring Use Case, depending on the Work Mode. The settings affect all metrics and alerts of the Monitoring Use Case. The Work Mode depends on the Monitoring Use Cases.

You can assign Work Modes to:

• Technical Systems, Hosts and Databases
• Technical Scenarios. The Work Mode is inherited by all objects of the Technical Scenario.

To activate monitoring for a Work Mode, select the Monitoring Enabled checkbox.

8. Update Content: A content version contains SAP monitoring content for all System and Application Monitoring When a content version is applied, it updates the content for all scenarios, so this step need not be performed for each scenario. Perform this step in the System Monitoring scenario under Applications Operations > System Monitoring > Configure Infrastructure > Update Content.
9. Standard Users: This optional step creates standard users in the SAP Solution Manager system.
10. Define Scope: We must select and add the systems for which we wanted to enable technical monitoring.
11. Setup Monitoring: When we click next, default template will be assigned to systems for technical monitoring, in our case below are the template.

• Derived from SAP ASE
• Derived from Linux
• SAP ABAP 7.1 and higher
• SAP ABAP central services
• SAP ASE
• Linux

12. Template Maintenance: After knowing the default template list, we have to move the template list, we have to select the template, for our case SAP ABAP 7.1 and higher, and then click on Notification template then add recipients and activate the template, do the same for all the assigned templates.

Once the templates will be added and activated then we will start getting the alert email in SOST transaction list under transmitted filter, please select and configure SMPT and exchange server accordingly to get email in outlook inbox.

Conclusion:

This Blog will be helpful for the audience who is working on Solman configuration first time, and this document is not covering every step of the configuration phase but only focusing on the screen and the area where lot of configuration and manual steps are required, I hope this will help to every one.

Regards,

Madhvendra