What it takes to set up PI Monitoring in SAP Solution Manager
When you read the title of this blog, you could ask yourself the question: Why should there be a blog about such an easy matter? Well, the answer is fairly simple: I’m struggling since the end of last year (*) with the setup of PI monitoring on a SAP Process Orchestration 7.31 (single stack) system and a SAP Solution Manager 7.1 system. And I just want to share the problems and odd situations I encountered during the setup.
XI domain in the SLD
All components must be registered in the SAP Solution Manager’s SLD:
This cannot be achieved using the classical way of registering a system in the SLD.
See OSS Note 1631346 for more information about the registration process. Also implement OSS note 1755427 to fix a bug.
PI Domain Overview
The red traffic light for System Monitoring Configuration Status is not correct. Apply OSS Note 1843838 to fix this bug.
Within this step, background job SMSETUP: MAI_PI_INITIALIZE will be launched on the SAP Solution Manager system, but a short dump (program: SAPLE2E_SETUP and exception: ERROR_IN_RESPONSE ) is generated. Apply OSS note 1850565 to fix this bug.
When you see no activity or no result during the setup in SAP Solution Manager, please use the button Execute Selected instead of Execute All. This is also a bug in SAP Solution Manager 7.1 SP6.
Within this step, SAP Solution Manager can register itself as consumer for SAP NW PI message alerts.
This error was encountered: Error in Message Alerting Web Service for domain domain.01.sappo: SOAP:1.007 SRT: Unsupported xstream found: (“HTTP Code 404 : Not Found”).
This is a bug in the Managed System setup for SAP Solution Manager SP06 and can be fixed by choosing 1 of these options
- Apply LM Service Patch 02 for SP06
- Perform these steps
- Execute function module “E2E_WS_CONN_LOG_PORT_CREATION”
- SYSTEM_ID = <SAP PO SID>
- CLIENT = blank
- SYSTEM_TYPE = JAVA
- USERNAME = SM_COLL_SOL
- PASSWORD = users’ password
- CHECK_ONLY = BLANK
Set the flag for “Upper/Lower cases” because passwords usually contain small letters.
Within this step, managed system parameters and java parameters must be filled in.
Do not confuse the Message Server Port with the Load Balancer Port.
The entries for Load Balancer Host and Load Balancer Port are used to create the URL for HTTP based communication. Also to create logical ports, the system needs to create the endpoint URLs of all the web services, based on these parameters.
When the Web Service call is send to the Message Server Port, it gets redirected to an instance. These redirects are blocked in the Web Service Runtime for security reasons.
The only possible workaround is the usage of a Web Dispatcher or the usage of an http(s) port of any instance in the Managed System setup step.
Please note that, if you change one of these parameters, you have to re-execute the step for logical port creation.
[ Update 09.07.2013 ]
Load meta-data – part II
There was still an error in this part. Make sure OSS note 1883225 is implemented.
Users and authorizations
Make sure the user, used to perform the PI Monitoring setup, also exists on the Process Orchestration system.
Roles to be assigned:
In case you still have an error pointing to missing authorizations, please do the things mentioned below, based on you system:
[ Update 31.07.2013 ]
We recently upgraded our Solution Manager system to SP08 and now, we face the problem that the Business Process Management part is being greyed out:
To solve the problem, take transaction SOLMAN_SETUP -> Technical Monitoring -> System Monitoring -> Define Scope. Take your SAP PI/PO system and go to Setup Monitoring.
On the highest level in the three (in my case <SID>~JAVA), click on assign templates.
Make sure template SAP NetWeaver CE is assigned to product SAP Netweaver CE x.xx (x.xx is your installed version). Apply and activate the settings.
(*) Keep in mind this is the lead time and not the time spent on the solution.