Skip to end of metadata
Go to start of metadata

PI Monitoring Frequently Asked Questions

Which PI release is required to use PI Monitoring with Solution Manager?

To be able to use PI Monitoring with SAP Solution Manager you need at least SAP PI 7.11 SP06.

To check if your PI systems meets these requirements please follow the steps below.

Open the PI system in LMDB. Note that if your PI system is a double stack you have to check the ABAP and the Java stack separately (even though they should be alike).

Select Software from the left navigation tree.

Go to the tab Software Component Versions and do a search as shown below.

Software Component, which is to be checked, is:

  • For ABAP Systems (including double stacks): PI_BASIS (must be at least 7.11 SP06)
  • For Java Systems: XI ADAPTER FRAMEWORK (also at least 7.11 SP06)

If your PI release is lower than 7.11 SP06 you have to patch or upgrade your PI system before you can use PI Monitoring with SAP Solution Manager

If you plan to use Message Based Alerting and Central User Defined Message Search please note that this is only available with a PI release of 7.31.


How can I synchronize PI Domain data into LMDB of Solution Manager?

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).

Proposed Solution:

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.

  • Are you having a central SLD in front of LMDB (which is SAP recommendation to have that)?
  • 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:

  • 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)
  • 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 (recommended): 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:

  • 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.
  • 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 IntegrationServer to BussinessSystem is 1:n, a BussinessSystem can be connected to only one IntergationServer 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.
  • 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.


How can I update the PI Monitoring Content?

To make sure your PI Monitoring is using the latest PI Monitoring content you can update the content in step 2.5 of the PI Monitoring setup.



What does the status FORWARDED mean in PI Monitoring in Solution Manager?

In Solution Manager you find messages with the status FORWARDED. This status doesn't exist in the single systems on the PI domain. You want to know what it means.

As Solution Manager collects information from all components in the PI domain in the Central PI Message Monitor, the message status overview is displayed for entire PI domain and not only for one component (as is would be in the traditional distributed PI monitoring approach). But this means, if you count successful messages, they are counted in each component and as a sum you will receive the number of successfully counted messages (All successful messages in all components, even if a message was successful in 2 components). This is not the total number of messages in the PI domain, it could be more.

To avoid this discrepancy, the status FORWARDED was introduced, locally on SAP Solution Manager only. This status means, a message was successful on one PI component, it was passed to another PI Component, but it did not reach it's ultimate target and "passed" the PI domain successfully yet. In the single components of the decentralized traditional PI monitoring this distinction is not necessary as you don't have an overall overview over messages in other components, in Solution Manager this status was needed to mark a not finished but so far successful PI message.




Back to Central PI Monitoring with SolMan 7.1


Central PI Monitoring Home Page




  • No labels