ALERT CONFIGURATION STEPS

For generating Alerts we mainly need to do three different kinds of

configurations/settings.
1. Defining Alert Categories in ABAP Stack.
2. Creating Alert Rules in JAVA Stack against the created Alert Categories.
3. Basis Level setting to make the Alerts to trigger automatically.
This document explains the steps that need to be followed for generating ALERTS
(developer responsibilities).

Defining Alert Categories in ABAP Stack.

T-Code : ALRTCATDEF (to access this we require the authorizations of the role
SAP_XI_ADMINISTRATOR)
Once entering into this T-Code we can see a screen as shown below.

Step 1: Under All Classifications folder in top left hand side we can find a Sub-Folder
/XI/, double click it and at the right side we will find an option to create Alert_Category
Step 2: Create a Zcategory and save the category.
Step3: Once the category is created click on it to assign the container objects & technical
attributes as shown.

In the above screen shot we can find 4 tabs, in each of the tab we need to provide the
related information:
TAB 1: Properties-Under this tab we can provide General Description and other details if
needed.
TAB 2 : Container:

This is very important task that we perform in this transaction.

Based on the container variables only we will determine which types of errors
need to be detected and also this variable hold the details of the Service
interfaces , Namespace, Message IDs and many other adapters related
information.
We have many container variables stored where as we will import only the
required set of variables to generate the ALERTS.
The above shown screen shot holds the container variables which are very
important to generate Alerts with considerable information.

Only based on this the mail we receive holds the information of the Interface
Namespace, Service Interface, Reason for message failure and any other
important information.
Apart from the above containers we have many other variable in which few
are given below.

Available Container Variables:

Container Variable

ABAP Dictionary Data Type

Meaning

SXMS_MSG_GUID

SXMSMGUIDC

Message ID

SXMS_RULE_NAME

SXMSDESCR

Description of the alert

rule

SXMS_ERROR_CAT

SXMSERRCAT

Error category

SXMS_ERROR_CODE

CHAR70

Error code

SXMS_FROM_PARTY

SXI_FROM_PARTY

Sender party

SXMS_FROM_SERVICE

SXI_FROM_SERVICE

Sender service

SXMS_FROM_NAMESPACE SXI_FROM_ACTION_NS

Sender namespace

SXMS_FROM_INTERFACE

SXI_FROM_ACTION

Sender interface

SXMS_TO_PARTY

SXI_TO_PARTY

Receiver party

SXMS_TO_SERVICE

SXI_TO_SERVICE

Receiver service

SXMS_TO_NAMESPACE

SXI_TO_ACTION_NS

Receiver namespace

SXMS_TO_INTERFACE

SXI_TO_ACTION

Receiver interface

You cannot use these container variables for alerts of the Business Process Engine (BPE).
Specific Error Information from the Adapter Engine:
Container Element

ABAP Dictionary Data

Type

Meaning

SXMS_TO_ADAPTER_TYPE

CHAR70

Adapter type

SXMS_TO_ADAPTER_ERRTXT CHAR70

Error text from the

Adapter Engine

Specific Error Information from the RNIF Adapter:

Container Element

ABAP Dictionary Data Type

Meaning

SXMS_AF_ERRPAR1 15 CHAR32

Name of error parameters 1 to 15

SXMS_AF_ERRVAL1 15 CHAR70

Content of error parameters 1 to 15

TAB 3 : Long & Short Description :

o Under this tab we need to give some reasonable description, this description will
be processed through the mail to all recipients when an alert mail is generated.
o Short Description appears as Subject Line and Long Description will be in the
body of the mail.

TAB 4: This is not so important.

Here is an example Alert mail which we receive when an error occurs.

Example: If the above specified variables are used under their respective tabs then the
mail is capable of holding the MessageID, Namespace, Interface details, Adapter errors ,
Descriptions etc.

Mail Containing the information:

 Once the required information is filled in the category the next step is assining the
recipients list.

We can see icons in the top as shown above in this T-code.

Once we finish assigning variables and descriptions to category we need to assign
the list of recipients.
Here we can assign recipients in two ways.
i)
By Fixed Recipients: In this we can give individuals user IDs.

ii)

Recipients Via User Roles : In this we can give roles, so that all the users
assigned with that roles will be eligible to receive these alert mails.

Creating of Alert Rules in JAVA Stack :

Below is the screen which shows and explains us about the page which
appears in RWB for creation of Alert Rules.
Steps:
Alert Rule can be created in RWB.
SAP PI JAVA Stack RWB Alert Configuration
Once it is opened the page appears as below.

The below screenshot explains the usage of each window provided

under Alert Configuration tab.

Before creating a rule first we need to select the category which

appears the bottom of the window.
Once the category is selected then that particular selected category
appears at ADDRULE tab.
Then we can continue creating our Alert rule by giving some
reasonable description for the rule.
In the CONDITIONS window we can see several parameters that
need to be provided. This can be provided purely based on our
requirement.
i)
If suppose we need to handle any interface that flows with
sender component as BusService_OLS , then we just need to
provide this sender component name and maintain all other
conditions as * . Then this rule will generate mails for all the
errors that occur with this sender business system.
Note: Similarly, we can create Alert Rules for different combinations
on our interface purely based on our requirement.
We can see all the generated alerts in ALERTINBOX.
You can do it from RWB - Alert inbox
Or from sapgui TCODE - ALRTINBOX
Troubleshooting:
Apart from these configurations in ABAP & JAVA Stacks we need to
do some basis level settings, check all those setting are properly
incorporated or not.
If the mails are not generating, cross check if the recipients list is
maintained or not.
Some other information for troubleshoot:
Alert configuration may sometimes cause some problems.
With this list of steps you can quickly find out what might be the reason.
Step 1
Check if you scheduled the report SXMSALERT_PROCESS_DATA_GET as a
background job.
Step 2

Check the update frequency in the End-to-end monitoring (and set to it to 5

minutes):
- go to Runtime Workbench
- choose End-to-end monitoring
- choose "Further settings"

Step 3
Check if the monitoring systems have at least medium monitoring level (if not
change it to medium or high).

Step 4
If you cannot open Alert configuration tab from RWB take a look at those notes
on how to resolve your problem:
750287 - XI 3.0 Runtime Workbench: Alert configuration does not start
813703 XI RWB alert configuration is incompletely displayed
Step 5

If you cannot open your alert inbox (neither from TCODE - ALRTINBOX nor
from RWB)
check if your alert inbox service is properly activated in SICF:
- go to TCODE - SICF
- check if the service alertinbox is activated (you can test it from here)

Step 6
If you don't receive any alert into your alertinbox but you believe that they are
triggered check if the alerts were created:
- go to TCODE - ALRTCATDEF
- choose Settings - Configuration
- make sure you have the logging parameter checked

- go to TCODE - SLG1
- choose object "ALERT"
- and from here you can check if your alert was generated or not

- if you have a look at "additional information" you can also check the recipients
of the alert

Step 7
If still your alerts don't get triggered one more time take a look at:
Alert Notification Step-by-Step - help.sap.com