Solution : https://service.sap.com/sap/support/notes/913858 (SAP Service marketplace login required)
Summary :
This SAP Note details troubleshooting steps and configurations for improving the effectiveness of XI Alerting within the SAP XI 3.0 environment. Initially, XI Alerting relies on the Basis Alert Management API for notifications via Alert Inbox and email/SMS, configured through transaction ALRTCATDEF. It specifies necessary adjustments when using a Central Alert Server, clarifying that the system defined as the Central Monitoring Server should be consistent with the Central Alert Server's system. The note includes instructions for handling different scenarios depending on whether the system is before or after the inclusion of Support Package 14, where XI Alerting is decoupled from end-to-end monitoring. Additional configurations and troubleshooting tips, such as testing Alert Management and checking service activation, are also provided.
Key words :
sicf --> default_host --> sap --> bc --> bsp --> sap --> alert inbox, #sap j2ee engine version xxx patchlevel xx, bor container import method, sap xi af core, occupy abap work processes, java server nodes> q16a, basis alert management api, active alert rule exists, adapter framework reacting simultaneously, abap connection 'centralmonitoringserver-xialerts'
Related Notes :
1294312 | XI alerting: SXMS_TO_ADAPTER_ERRTXT is truncated |
1110295 | XI Alerting: Alert rules are not transported |
932085 | XI 'Message based Alerting' - additional information |
906044 | XI Alerting: Wrong hostanme in the URL of the XI Alert |
905896 | XI30 Alerting: Message without recipient creates no alert |
904825 | Synchronous message processing: Error in CCMS connection |
902022 | XI30 Alertrule insensitive to Receiver Interface |
882215 | XI 3.0 Runtime Wkbnch: Java Adaptr does not generate alerts |
876546 | XI 3.0 Runtime Workbench: Missing alerts |
870232 | XI 3.0 Runtime Workbench: New Alerting function |
835031 | Import_from_BOR_container rejects NULL-Values |