Redpeaks V6.8
Trouble shooting
Monitors Guide
Sidebar
products:promonitor:6.8:monitorsguide:netweaver:piximessagesjava
Book Creator
Add this page to your book
Add this page to your book Book Creator
Remove this page from your book
Remove this page from your book 
Manage book (
Help Table of Contents
PI/XI messages JAVA
This monitor is dedicated to the monitoring of PI/XI messages status of Java stack instances. It will detect messages with an error status and report with alarms and metrics
Prerequisites
- In case of the user management engine (UME) referred to a data source served by an ABAP client stack, the user account to access PI/XI information in the web portal must meet the following prerequisites:
- The web client connection user must be created in the client of the UME associated ABAP system (normally it is the “production” client, ask to the users administrator).
- Following roles must be granted to the user (exclusively, DO NOT USE A COPY)
- SAP_XI_DISPLAY_USER_J2EE
- SAP_XI_RWB_SERV_USER
Configuration hints
- This monitor must be used with a Web portal connector to the target SAP system, with user credentials having access to the PI/XI messages view
- You must specify the XI components that you want to monitor, you cannot use regular expressions for this filter.
- To discover the available XI components from your system, you can call the following servlet with your web browser:
- It will return the available components in the XIComponents tag.
- You can filter in or out certain types of messages by using Sender, Receiver and Interface fields.
- You can adjust the level of alarm severity depending on the type of status or on message characteristic.
- A disabled severity will filter out the messages matching the filters, for all subsequent lines.
- With this monitor, you will have the possibility to be notified when a given number of messages from an XI component are in a given state, within a period of time.
Atomic fields
| Alarm severity for component collection error | Level of the alarm when the probe can't collect information about a component defined in the surveiliance table |
|---|
Surveillance table
| Parameter | Description |
|---|---|
| Active | Use this field to activate or deactivate a line of configuration. |
| Status | Define the type message status to look for. |
| Period | Defines the period of time in which the probe will look for messages. |
| Component | Defines the xi component associated with the messages. The exact component name must be specified here. |
| Sender | A filter for the sender of the messages. |
| Receiver | A filter for the receiver of the messages. |
| Interface | A filter for the message interface. |
| Max. messages | The threshold of the alarm generated if an equal or greater number of messages pass the alarm filter. |
| Aggregates | If not set, threshold will be compared to the number of messages grouped by Sender, Receiver and Interface. If set, the threshold will be compared to the cumulated number of messages. |
| Severity | The default severity to apply when the simple threshold syntax is used. |
| Auto clear | If checked, the alarm will be cleared as soon as the alarm condition is not met anymore. |
| Alarm tag | This field allows to add custom text within the alarm message. %MSG% variable will contain the actual generated message and can be used such as: “my_prefix %MSG% my_suffix”. By default, tag will be used as prefix. |
| Alarm | If checked, this line of surveillance will be used for alarm generation. |
| Metric | If checked, this line of surveillance will be used for metric generation. |
| Report | If checked, this line of surveillance will used for showing threshold and severity in the daily report |
Examples
| Active | Status | Period | Component | Sender | Receiver | Interface | Max. messages | Aggregates | Severity | Auto clear | Alarm tag | Alarm | Metric | Report |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| true | HOLDING | CURRENT_HOUR | mssql.xi.id2 | * | * | * | 5 | true | WARNING | true | true | false | false |
Effect : Sends a WARNING alarm if 5 or more messages are in HOLDING state in the current hour for the component mssql.xi.id2.
Examples
| Active | Status | Period | Component | Sender | Receiver | Interface | Max. messages | Aggregates | Severity | Auto clear | Alarm tag | Alarm | Metric | Report |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| true | SYSTEM ERROR | LAST_DAY | mssql.xi.id2 | SenderX | * | * | 50 | true | MAJOR | true | true | false | false |
Effect : Sends a MAJOR alarm if 50 or more messages are in SYSTEM ERROR state in the previous day, sent by SenderX.
Generated metrics
| metricId | metricUnit | metricTarget | metricDescription |
|---|---|---|---|
| PIXI_JAVA_MESSAGE_STATUS | Message errors | [STATUS][PERIOD][SENDER][RECEIVER][INTERFACE] | Sends TRUE if the corresponding rule generated an alarm, FALSE instead |
| PIXI_JAVA_MESSAGE_STATUS_COUNT | Status | [STATUS][PERIOD][SENDER][RECEIVER][INTERFACE] | Sends the number of messages matching the filter |
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/promonitor/6.8/monitorsguide/netweaver/piximessagesjava.txt · Last modified: 2025/03/24 17:37 by rbariou
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
