With my 5 years of journey with SAP(particularly SAP Basis administration) it was pretty exciting when I started configuring Solution Manager 7.1 for our Project Landscape in April 2012. It seemed like a tediuos job to me. I started getting issues in each and every steps as I proceeded.
Thanks to the various notes and wiki sdn I was able to overcome those issues. I would like to share some of the issues which seemed to very common and which any one of you can face. I will be posting more of my experiences on Solution Manager.
Below are the issues heading,description and their resolution. Do provide feedback to this blog 🙂
Issue 1: Landscape Synchronization for PI Domain Data:
Description of the issue:
Usually landscape data are synchronized into SAP Solution Manager via SLD Bridge into a central SLD and then forwarded via SLD Synch into LMDB (which is the source for Landscape data used by SAP Solution Manager).
SLD Bridging deals only with landscape data, that are delivered by SLD Data Supplier, such as Technical Systems, installed SW Components etc. PI Domain data are not delivered by SLD Data supplier and therefore those data needed to be synchronized separately.
It is unclear, how landscape setup should be done to synchronize PI Domain data into LMDB of SAP Solution Manager, which is a prerequisite to implement central PI Monitoring. There are several options possible, but the impact and the requirements are not clear (e.g. SLD release requirements).
In general all below mentioned option must be implemented in a compliant way with the “Planning Guide – System Landscape Directory” (see Wiki Page for “System Landscape Directory”, section Setting Up a System Landscape Directory).
Additionally you judge landscape setup decisions always in relation to all possible aspects for your landscape and not target only the PI monitoring use case.
In general, there are several options for synching data into LMDB. But the following questions have to be answered first.
n are you having a central SLD in front of LMDB (which is SAP recommendation to have that)?
n What release does this SLD have? (In case it is the local SLD of SAP Solution Manager 7.1, it has release 7.02.)
Depending on the answers on these questions, some options mentioned below might get excluded already.
Option 1: In the PI Monitoring Setup PPT (Installation/Setup Guide) a full SLD Content synch between the PI SLD and the central SLD.
This has some disadvantages:
n This synch will synch the entire content of the PI SLD. Sometimes this is not wanted because the data are not needed in central SLD or it violates the so-called “one patch rule” (there should be for all content elements only one source, means one path into a central SLD)
n The central SLD must be at release 7.10 or higher to be able to retrieve content synchs, which means, the SAP Solution Manager SLD cannot be used.
Option 2: To overcome these disadvantages, the latest recommendation is, to use the SLD Bridging for Technical System data (as it is the standard recommendation for all other SLD connections, too). As mentioned already, this will not transfer the PI Domain landscape data. Therefore, those data are transferred via a specific Java report, that is attached (and described in detail) in SAP note 1631346.
This new solution has the following advantages:
n The SAP Solution Manager SLD can be used, since we use a Write API that already exists with SLD releases like 7.02. This means, it is not required to install a separate central SLD with >= 7.10 (or upgrade an existing one) to support PI Monitoring use case.
n The synchronization is done on request and hence can be better controlled. This might be necessary, in case you use same business system in several PI domains.
Remark: Since the association in the landscape model of Integration Server to Business System is 1:n, a Business System can be connected to only one Integration Server in one SLD. This is of course difficult, if everything is synched into a central SLD. Therefore customer can now synch a PI domain, then create a Technical Scenario for PI Monitoring (under Setup Step “Scope Definition”), then synch another PI Domain and create another Technical Scenario for PI Monitoring.
n The only disadvantage is that this synch is not automatically done. It needs to be done manually (or a regular job on OS level needs to be scheduled).
Option 3: Last option, which is sometimes used as “quick and dirty”, is the synch from PI SLD directly into LMDB. This is also possible, but we never recommend this, because several SLD connections need to be maintain in SAP Solution Manager and those different Synchs are running to LMDB. These different synchs might cause performance issues in LMDB (there can be only one synch active at a time).
Result: Therefore, if possible, we recommend the option number 2. This has almost only advantages and almost no disadvantages. All details for this option, which are different to standard synch (SLD bridging), can be found in in SAP note 1631346.
2. Issue 2: Metric Monitor Deactivated or Grey:
3. Issue 3: Data Missing in overview of E2E analysis:
4. Issue 4: No applicable data found error in Workload Analysis:
In E2E Workload Analysis, no data is displayed under the Overview tab and the message “No applicable data found” is shown under all system specific tab screens.
This issue might also cause inconsistencies in the Java data of EarlyWatch Alerts.
Please execute the following checks.
Please make sure that:
a) your systems fulfill all the prerequisites as per SAP Note
1010428 End-to-End Diagnostics
b) the latest version of the basic Solution Manager note is applied to your system according to the release level of your system:
1172948 SAP Solution Manager – Basic functions (SP18/19)
1334252 SAP Solution Manager – Basic functions (SP20/21)
1405878 SAP Solution Manager – Basic functions (SP22 to SP24)
1468591 SAP Solution Manager: Basic functions: SP25 and higher
c) you apply the latest patch level to LM-SERVICE.
Make sure that in transaction SM59, the connection tests finish successfully for the SOLMANDIAG, WEBADMIN and MDX PARSER RFC’s.
For MDX PARSER RFC issues check the following SAP Note:
1032461 MDX parser does not start
· EFWK Resource Manager Job.
The job name is E2E_HK_CONTROLLER. This is the central job that controls all data loading steps. Make sure this job is released in transaction SM37.
- Make sure that you release the job with user SMD_RFC to avoid authority problems.
- Make sure the job is not scheduled more than once for the timestamp.
- Check the spool and check for any errors.
- Check go the Solution Manager Workcenter -> “Extractor FWK Administration”, click on “Latest Job Logs”. Common issues: RFC Resource Cap. Exceeded. Increase the value for all RFCs with this warning in table E2E_RESOURCES in transaction SE16.
- 4.1) Ensure that there are no banned/inconsistent extractors for Solution Manager and relevant satellite system.
To restart banned extractors you can use the Extractor Framework Admin Cockpit. This can be found in the Root Cause Analysis Work Center.
On the left side in the navigation panel you will find the entry “Extractor FWK Administration”. When clicking this link a WebDynpro application will be started. There you can find a tray “Extractors banned / inconsistent”.
You can simply mark the affected extractor and push the button “Restart” or, you can delete the extractors and perform the diagnostics setup for the relevant system again if restarting does not work.
4.2) In the “Managed Systems” tab, select the managed system and click on “Job Log”. The logs will show the status for the latest extractions. Check for any warnings.
· Additional verifications for NON-ABAP
Refer to SAP note 1332428 – Missing data in service sessions from BI/CCDB
In case you find issues with BI activation:
Under certain circumstances, the setup wizard used to activate the BI content required for end-to-end diagnostics may not run correctly. In these cases, activating the content manually is a possible workaround. In this case follow SAP Note 1342231 to proceed with a manual activation of the BI content for E2E Diagnostics.
· Additional verifications for ABAP systems
Make sure the RFCs are established in transaction SOLMAN_SETUP -> “Managed System Configuration”.
· System landscape
Make sure your systems are defined according to the “SAP Solution Manager Landscape Setup Guide” available in http://service.sap.com/diagnostics -> Media Library.
You must define your systems in the Managed Setup wizard as indicated in this document.
· Diagnostics setup
In transaction SOLMAN_SETUP, all the steps of the configuration setup have been performed and finished with no errors.
If you recently upgraded your Solution Manager you must check the “Overview” menu in transaction SOLMAN_SETUP. All activities displayed needs to be re-execute
5. Issue 5: Host data missing error during managed system configuration:
Check saposcol is running or not on the managed system server. Refer Note 1400891 – OSCommand CPU stat fails and missing Wily Host metrics
6. Issue 6: Error in E2E Analysis:
One possible reason for these errors can be configuration file for E2E being old. Always update the E2E configuration file to latest version. Refer Note 1259109 – Latest version of configuration file for E2E CA, EA, WA.
7. Issue 7: Error when starting interactive reporting(Technical Monitoring):
Error message as “An error was detected while parsingthe E2E application configuration data.” occurring.
Refer Note 1615827 – Error when starting Interactive Reporting (SP03) and replace the E2E configuration file.
8. Issue 8: No product assigned for system Error:
Go to Display Technical System Software and select components to put in diagnostic and save it the error goes. Follow screen shots shown below,
9. Issue 9: Automatic alerts not going from technical monitoring:
There can be various reasons for this issue. Please check following things if automatic alerts not coming,
– See that auto notification is setup in technical monitoring settings or not
– Recipient list see if the email recipient is maintained in recipient list and the user email address is maintained in su01.
– See whether the background user SOLMAN_BTC is assigned the role SAP_NOTIF_ADMIN or not and an email address is maintained in su01.
– Also check whether background job SAP_LMDB_NOTIFY_LDB is running or not at correct time intervals.