Destinations for Monitoring and Alerting
Use
The following destinations are relevant for monitoring and alerting.
|
Name |
Description |
Destination Target |
Type |
|
PMISTORE (Java EE destination on each Advanced Adapter Engine) |
Required for the Process Monitoring Infrastructure (PMI) and used for monitoring Advanced Adapter Engines on Java servers More information: Create HTTP Destination for PMI |
Client of Integration Server; Logon and security: user PIRWBUSER required (assigned role SAP_XI_RWB_SERV_USER_MAIN) |
HTTP |
|
PMI* (one for each business system monitored with PMI) |
Used for PMI monitoring on central monitoring server. Maintained on business system. |
client of Integration Server; Logon and security: user PIRWBUSER required (assigned role: SAP_XI_RWB_SERV_USER_MAIN) |
HTTP |
|
User-defined with transaction GRMG using XI_* entries |
Used for GRMG scenarios like heartbeat and self test on central monitoring server |
No client to be specified; Logon and security: user PIRWBUSER required (assigned role: SAP_XI_RWB_SERV_USER_MAIN) |
G |
|
CentralMonitoringServer-XIAlerts |
Enables connection of business system to central alerting server. Maintained on business system. More information: Alert Configuration |
3 |
The following figure shows the communication paths specified by selected destinations listed above.
More Information
For more information in destination types in AS ABAP, choose: Connection Types .