Alert Configuration in PI 7.31 using SOLMAN based on Payload

Hello Experts,
We have created alert configuration in PI which will be consumed by SOLMAN and alerts will be triggered to respective recipients based on alert rules.
The alert rules are created using standard configuration objects in NWA. Everything is good up to now, But the issue we have here is as follow:
We have interfaces segregated based on country wise so the configuration objects will be different for which alert rules are created without any issues.
But for some countries for which interfaces are developed by re-using the existing PI objects, the problem starts here for us:
Since the configuration PI objects are same, we are not able to segregate here the alert rules using config objects resulting the only common alert rule for all these countries.
In this case, alerts will be routed to all these countries whenever there is an alert generated. Obviously it is not the best way to proceed. But there will be difference in payload of message based on country .
Hope my issue is clear to you
Is there any way to set these alert rules based on payload information rather than config objects of PI.
Please help me to achieve this ..your help is much appreciated.
Thanks,
Venkat

Hi,
XPI Service: AII Config Service
- com.sap.aii.rwb.server.centralmonitoring.r3.ashost
- com.sap.aii.rwb.server.centralmonitoring.r3.sysnr
are set as expected but still there is problem.

Similar Messages

Service Unavailable error in Alert Configuration

Hi all,
I have done all the Alert Configuration in the ABAP Stack using the tcode ALRTCATDEF.as mentioned in weblog:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
But when I click on the Alert Configuration tab in RWB, i get the following error:
Application Stopped:
Details: You have requested an application that is currently stopped
Can anyone tell me what can be the possible reason?
Do i need to start any particular service?
Pls guide
Regards
Neetu

Hi Shekhar
Thanks for your help.
The steps u told to follow are working well and now i can see a logon pad when i click on the Alert Configuration tab in RWB.
But now the problem i am facing is that none of the user id and password work for this logon. The error msg getting displayed is:
Incorrect client, name, or password. Log on again.
I have followed the SAP note: 750287 completely.
I have already used the id for RWB given in ExchangeProfile.
Which other user id and password should i use?
Is there anything else im lacking?
Pls guide.
Regards
Neetu

Not able to use Alert Configuration/Alert Inbox in the Runtime Workbench

Hi Experts,
I have installed PI 7.1 on my system. I'm not able to use the Alert Configuration/Alert Inbox in the Runtime WorkBench. It is asking for a logon and the logon which i used for ABAP & Java Stack is not working.
e.g., For ABAP Stack, the User Id is: "sapuser" & For Java Stack, the User Id is: "pisuper". But, both these User Id's are not working for the Alert Configuration/Alert Inbox in the RWB.
Can someone pls suggest me, how to proceed?
Br
G@nesh

Hi Preethi,
Can u pls help me, how to check whether the relevant roles are assigned to this user i.e., pisuper for the JAVA stack in the UME or not? i even tried to use Alert Configuration/Alert Inbox with the User ID: ddic & j2ee_admin, but it too didn't work...
I would like to use Alert Configuration/Alert Inbox with my User Id: pisuper, which i'm using to logon to the JAVA stack
while exploring, i logged on to the useradmin page i.e., http://p71:58800/useradmin with the User Id: j2ee_admin... If this is correct, can u pls let me know how can i add the necessary roles to my User Id: pisuper so that i can use Alert Configuration/Alert Inbox with my User Id: pisuper
Br
G@nesh

SALRT_CREATE_API with CBMA and/or Central Monitoring using Solman

Hi,
Does anyone know if function SALRT_CREATE_API can be used to raise alerts in Component Based Message Alerting (CBMA) and/or Centralised Monitoring in Solman? I understand SALRT_CREATE_API worked with the classic Alert Framework.
Che

Hi Michal,
Thank you for jumping in on this thread. Great timing with your blog
However the following thread suggests we can still use SALRT_CREATE_API:
XI Alerting and Central Monitoring : some alerts remain on PI
"Try removing the "CentralMonitoringServer-XIAlerts" RFC connection from both systems (proxy and PI). Then, ensure all com.sap.aii.rwb.server.centralmonitoring.* parameters are configured correctly on PI (restart system to apply changes on exchange profile) and try executing the scenarios again.
Check the target CCMS system the RSALERTDISP report and see if the alerts are being received there."
Perhaps the above only applies in the case of a dual stack? I am not quite ready to try some examples but when I do then perhaps options will become clearer to me. I will try to remember to update this thread with what I find.
Thanks
Che

Error during login Alert-Configuration

Hi,
I get following error when I try to login alert-configuration.
SO does anybody know this error and has a solution?
Thanks.
Regards
Stefan
Runtime Error STRING_BAD_REF
Date and Time 29.09.2006 08:58:00
ShrtText
A string reference with destroyed context was destroyed.
What happened?
Error in ABAP application program.
The current ABAP program "CL_BSP_MODEL==================CP" had to be
terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
The system discovered an invalid value while accessing a string
reference:
String reference (hexadecimal): 1900000002000000
String header ID: 2
String header ID (hex): 00000002
Check value (hex): 000000
Shared objects lock flag: 0
Check value (hexadecimal): 19
The check value should be hexadecimal "ED".
This is not the case.
How to correct the error
The contents of the string value were probably overwritten in the
memory of the ABAP application program.
Probably the only way to eliminate the error is to correct the program.
System environment
SAP Release.............. "640"
Application server....... "PROSRVSAP1"
Network address.......... "172.17.0.231"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "PROSRVSAP1"
Database type............ "ORACLE"
Database name............ "XI3"
Database owner........... "SAPXI3"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Nov 4 2004 23:42:53"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "43"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 3135696
Heap..................... 0
Page..................... 0
MM Used.................. 2356504
MM Free.................. 777568
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "CL_BSP_MODEL==================CP"
in "IF_BSP_MODEL_UTIL~SPLIT_BINDING_EXPRESSION".
The main program was "SAPMHTTP ".
The termination occurred in line 1 of the source code of the (Include)
program "CL_BSP_MODEL==================CM00W"
of the source code of program "CL_BSP_MODEL==================CM00W" (when
calling the editor 10).
Source Code Extract
Line
SourceCde
>>>>>
method IF_BSP_MODEL_UTIL~SPLIT_BINDING_EXPRESSION .
2
3
if strlen( binding_expression ) <= 4 or binding_expression(2) <> '//'. return. endif.
4
5
model_name = binding_expression+2(*).
6
split model_name at '/' into model_name attribute_path.
7
8
9
endmethod.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
8
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
85
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
HTTP Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
24 METHOD CL_BSP_MODEL==================CP CL_BSP_MODEL==================CM00W 1
CL_BSP_MODEL=>IF_BSP_MODEL_UTIL~SPLIT_BINDING_EXPRESSION
23 METHOD CL_BSP_ELEMENT_CT_ATTR_VALID==CP CL_BSP_ELEMENT_CT_ATTR_VALID==CM00A 28
CL_BSP_ELEMENT_CT_ATTR_VALID=>INITIAL_CHECKS
22 METHOD CL_BSP_ELEMENT_CT_ATTR_VALID==CP CL_BSP_ELEMENT_CT_ATTR_VALID==CM002 4
CL_BSP_ELEMENT_CT_ATTR_VALID=>TO_BOOLEAN
21 METHOD CL_HTMLB_CONTENT==============CP CL_HTMLB_CONTENT==============CM007 13
CL_HTMLB_CONTENT=>IF_BSP_ELEMENT~COMPILE_TIME_IS_VALID
20 METHOD CL_BSP_ELEMENT_INFO===========CP CL_BSP_ELEMENT_INFO===========CM003 21
CL_BSP_ELEMENT_INFO=>IS_VALID
19 METHOD CL_O2_CO2_PROCESSOR===========CP CL_O2_CO2_PROCESSOR===========CM01C 78
CL_O2_CO2_PROCESSOR=>CHECK_AND_DESCRIBE_TAG
18 METHOD CL_O2_CO2_PROCESSOR===========CP CL_O2_CO2_PROCESSOR===========CM019 102
CL_O2_CO2_PROCESSOR=>TRAVERSE_TAG
17 METHOD CL_O2_CO2_PROCESSOR===========CP CL_O2_CO2_PROCESSOR===========CM00G 55
CL_O2_CO2_PROCESSOR=>TRAVERSE
16 METHOD CL_O2_CO2_PROCESSOR===========CP CL_O2_CO2_PROCESSOR===========CM00E 180
CL_O2_CO2_PROCESSOR=>GENERATE
15 METHOD CL_O2_HELPER==================CP CL_O2_HELPER==================CM00R 143
CL_O2_HELPER=>CALL_O2_COMPILER
14 FUNCTION SAPLO2_WB_SERVICES LO2_WB_SERVICESU15 128
O2_GENERATE_PAGE_INTERNAL
13 FUNCTION SAPLO2_WB_SERVICES LO2_WB_SERVICESU04 117
O2_GENERATE_PAGE
12 METHOD CL_O2_RT_SUPPORT==============CP CL_O2_RT_SUPPORT==============CM004 12
CL_O2_RT_SUPPORT=>GENERATE_IMPL_CLASS
11 METHOD CL_O2_RT_SUPPORT==============CP CL_O2_RT_SUPPORT==============CM003 108
CL_O2_RT_SUPPORT=>GET_CLASS_FOR_PAGE
10 METHOD CL_BSP_PAGE_BASE==============CP CL_BSP_PAGE_BASE==============CM01A 98
CL_BSP_PAGE_BASE=>CREATE_PAGE
9 METHOD CL_BSP_PAGE_BASE==============CP CL_BSP_PAGE_BASE==============CM005 47
CL_BSP_PAGE_BASE=>CREATE_VIEW
8 METHOD CL_BSP_CONTROLLER=============CP CL_BSP_CONTROLLER=============CM005 3
CL_BSP_CONTROLLER=>CREATE_VIEW
7 METHOD CL_XI_ALERT_BSP_MAIN==========CP CL_XI_ALERT_BSP_MAIN==========CM001 10
CL_XI_ALERT_BSP_MAIN=>DO_REQUEST
6 METHOD CL_BSP_CTRL_ADAPTER===========CP CL_BSP_CTRL_ADAPTER===========CM004 47
CL_BSP_CTRL_ADAPTER=>DO_REQUEST
5 METHOD CL_BSP_RUNTIME================CP CL_BSP_RUNTIME================CM002 111
CL_BSP_RUNTIME=>ON_REQUEST
4 METHOD CL_HTTP_EXT_BSP===============CP CL_HTTP_EXT_BSP===============CM001 24
CL_HTTP_EXT_BSP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
3 METHOD CL_HTTP_SERVER================CP CL_HTTP_SERVER================CM01B 346
CL_HTTP_SERVER=>EXECUTE_REQUEST_FROM_MEMORY
2 FUNCTION SAPLHTTP_RUNTIME LHTTP_RUNTIMEU02 886
HTTP_DISPATCH_REQUEST
1 MODULE (PBO) SAPMHTTP SAPMHTTP 13
%_HTTP_START
Chosen variables
Name
Val.
No. 24 Ty. METHOD
Name CL_BSP_MODEL=>IF_BSP_MODEL_UTIL~SPLIT_BINDING_EXPRESSION
BINDING_EXPRESSION
FALSE
44454
61C35
00000
00000
MODEL_NAME
String reference is destroyed
10000000
90002000
ATTRIBUTE_PATH
SYST-REPID
CL_BSP_MODEL==================CP
4454555444443333333333333333334522222222
3CF230FDF45CDDDDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
CL_BSP_MODEL==================CP
4454555444443333333333333333334522222222
3CF230FDF45CDDDDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_ABAP_TYPEDESCR=>TRUE
%_FSREG_001
SPACE
2
0
0
0
No. 23 Ty. METHOD
Name CL_BSP_ELEMENT_CT_ATTR_VALID=>INITIAL_CHECKS
NAME
massDataExtraction
667746764777667666
D133414158421349FE
000000000000000000
000000000000000000
VALUE
FALSE
44454
61C35
00000
00000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
CL_BSP_ELEMENT_CT_ATTR_VALID==CP
4454555444444554554555554444334522222222
3CF230F5C5D5E4F34F1442F61C94DD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->M_ELEMENT_DATA
|
| 3000C000 |
| 60009000 |
| CL_BSP_ELEMENT_DATA=>CO_NO_ATTRIBUTE_VALUE |
| %_NO_ATTRIBUTE_VALUE |
| 25445455544554554454 |
| 5FEFF144292545F61C55 |
| 00000000000000000000 |
| 00000000000000000000 |
| SYST |
| ######################U###############0#########x#############################T###x#####XC#### |
| 0000000000000000000000500000000000000030000000007000000000000000000000000000105000700010540000 |
| 8000101000000000000010501000100000000000000000008000000000000000000000000000604000800000830500 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C |
| ME->M_LAST_VALUE_NOT_SET |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| ME->CO_CHECKS_DONE |
| %_CHECKS_DONE_% |
| 254444455444452 |
| 5F3853B3F4FE5F5 |
| 000000000000000 |
| 000000000000000 |
| CL_BSP_ELEMENT_DATA=>CO_REQUEST_TIME_VALUE |
| %_RUNTIME_ATTRIBUTE |
| 2555454445455544554 |
| 5F25E49D5F144292545 |
| 0000000000000000000 |
| 0000000000000000000 |
| ME->M_LAST_VALUE_ONLY_AT_RUNTIME |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| %_FSREG_001 |
| 6 |
| 3 |
| 6 |
| 0 |
| 0 |
| SYST-REPID |
| CL_BSP_ELEMENT_CT_ATTR_VALID==CP |
| 4454555444444554554555554444334522222222 |
| 3CF230F5C5D5E4F34F1442F61C94DD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| CL_BSP_COMPILER_MESSAGES=>CO_ERROR |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| ATTRIBUTE_INFO |
|
2000D000
90006000
No. 22 Ty. METHOD
Name CL_BSP_ELEMENT_CT_ATTR_VALID=>TO_BOOLEAN
NAME
massDataExtraction
667746764777667666
D133414158421349FE
000000000000000000
000000000000000000
RESULT
2
0
0
0
ME
|
| 3000C000 |
| 3000C000 |
| VALUE |
| |
| ME->CO_CHECKS_DONE |
| %_CHECKS_DONE_% |
| 254444455444452 |
| 5F3853B3F4FE5F5 |
| 000000000000000 |
| 000000000000000 |
| %_SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| CL_BSP_MESSAGES=>CO_SEVERITY_ERROR |
| 2 |
| 0000 |
| 2000 |
| No. 21 Ty. METHOD |
| Name CL_HTMLB_CONTENT=>IF_BSP_ELEMENT~COMPILE_TIME_IS_VALID |
| ELEMENT_INFO |
|
3000C000
70008000
COMPILER_MESSAGES
|
| E0001000 |
| 4000B000 |
| ELEMENT_DATA |
|
3000C000
60009000
VALIDATOR
|
| 3000C000 |
| 3000C000 |
| VALID |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| %_FSREG_001 |
| ??? |
| ?????? |
| ?????? |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| CL_BSP_ELEMENT_DATA=>CO_NO_ATTRIBUTE_VALUE |
| %_NO_ATTRIBUTE_VALUE |
| 25445455544554554454 |
| 5FEFF144292545F61C55 |
| 00000000000000000000 |
| 00000000000000000000 |
| SYST-REPID |
| CL_HTMLB_CONTENT==============CP |
| 4454544454445445333333333333334522222222 |
| 3CF84DC2F3FE45E4DDDDDDDDDDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY |
| ######################U###############0#########x#############################T###x#####XC#### |
| 0000000000000000000000500000000000000030000000007000000000000000000000000000105000700010540000 |
| 8000101000000000000010501000100000000000000000008000000000000000000000000000604000800000830500 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C |
| SY-REPID |
| CL_HTMLB_CONTENT==============CP |
| 4454544454445445333333333333334522222222 |
| 3CF84DC2F3FE45E4DDDDDDDDDDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SYST |
| ######################U###############0#########x#############################T###x#####XC#### |
| 0000000000000000000000500000000000000030000000007000000000000000000000000000105000700010540000 |
| 8000101000000000000010501000100000000000000000008000000000000000000000000000604000800000830500 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C |
| No. 20 Ty. METHOD |
| Name CL_BSP_ELEMENT_INFO=>IS_VALID |
| ELEMENT_DATA |
|
3000C000
60009000
COMPILER_MESSAGES
|
| E0001000 |
| 4000B000 |
| COMPILER_OPTIONS |
| 0.0.0.0.0.0.0.1. |
| C0000000 |
| B0004000 |
| VALID |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| ME->VALIDATOR |
|
3000C000
3000C000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
ME
|
| 3000C000 |
| 70008000 |
| ME->ELEMENT |
|
3000C000
4000B000
SY-REPID
CL_BSP_ELEMENT_INFO===========CP
4454555444444554444333333333334522222222
3CF230F5C5D5E4F9E6FDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->COMPILER_OPTIONS
0.0.0.0.0.0.0.1.
C0000000
90006000
%_FSREG_001
SYST-REPID
CL_BSP_ELEMENT_INFO===========CP
4454555444444554444333333333334522222222
3CF230F5C5D5E4F9E6FDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 19 Ty. METHOD
Name CL_O2_CO2_PROCESSOR=>CHECK_AND_DESCRIBE_TAG
SIG
content CL_HTMLB_CONTENT BCLG_HTMLB_CONTENT X
6667667222222222222222222222224454544454445445222222222222224444545444544454452222222222222522
3FE45E4000000000000000000000003CF84DC2F3FE45E40000000000000023C7F84DC2F3FE45E40000000000000800
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ATTR
í###r#######Ç###
E01070000000C010
D020204010007080
0000000000000000
0010000000000000
ELEMENT
¤###BX X#¯###¯###«###### ###r#####X #
A040452250A040A040A050A05020807000FF5220
40B0280080F000F000B040D02000D02000FF8000
0000000000000000000000000000000000FF0000
0010000000001000100010001000000000FF0000
SY-REPID
CL_O2_CO2_PROCESSOR===========CP
4454354435554445545333333333334522222222
3CFF2F3F2F02F3533F2DDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
EXTENSION_INFO
|
| 3000C000 |
| 80007000 |
| %_SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| TAGID |
| content |
| 6667667 |
| 3FE45E4 |
| 0000000 |
| 0000000 |
| ELEMENT_INFO |
|
3000C000
70008000
%_DUMMY$$
2222
0000
0000
0000
ELEMENT-ARGS
Table IT_365[9x32]
CLASS=CL_O2_CO2_PROCESSORMETHOD=TRAVERSE_TAGDATA=ELEMENT-ARGS
Table reference: 114
TABH+ 0(20) = 70CBF53C28E9F93C00000000720000006D010000
TABH+ 20(20) = 0900000020000000FFFFFFFF04650000900E0000
TABH+ 40( 8) = 10000000C1298000
store = 0x70CBF53C
ext1 = 0x28E9F93C
shmId = 0 (0x00000000)
id = 114 (0x72000000)
label = 365 (0x6D010000)
fill = 9 (0x09000000)
leng = 32 (0x20000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000064
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 3 (user defined)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x60C9F53C
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 101 (0x65000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0xE8C2F53C
hsdir = 0x00000000
ext2 = 0x00000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
TAGARGS_REF
0.0.0.0.0.0.0.1.
C0000000
C0003000
ELEMENT_DATA
|
| 3000C000 |
| 60009000 |
| ELEMENT_REF |
| 0.0.0.0.0.0.0.1. |
| C0000000 |
| B0004000 |
| ME->COMPILER_MESSAGES |
|
E0001000
4000B000
ATTR-ROW
4
0000
4000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IS_VALID
2
0
0
0
ME->FALSE
2
0
0
0
SY-XFORM
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
ME
|
| E0001000 |
| 70008000 |
| SYST |
| ######################U###############0#########x#############################T###x#####XC#### |
| 0000000000000000000000500000000000000030000000007000000000000000000000000000105000700010540000 |
| 8000101000000000000010501000100000000000000000008000000000000000000000000000604000800000830500 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C |
| No. 18 Ty. METHOD |
| Name CL_O2_CO2_PROCESSOR=>TRAVERSE_TAG |
| ATTR |
| í###r#######Ç### |
| E01070000000C010 |
| D020204010007080 |
| 0000000000000000 |
| 0010000000000000 |
| NODE |
|
70008000
2000D000
PREFIX_MAPPER
|
| A0005000 |
| 90006000 |
| NO_SCRIPT |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| RESULT |
| ############î###ï###Ê#####è#######N# ### |
| 00FF00FF00FFE010E000C01000E000FF90402000 |
| 00FF00FF00FFE010F000A050708000FF10E00000 |
| 00FF00FF00FF000000000000000000FF00000000 |
| 00FF00FF00FF001000000000000000FF00000000 |
| ELEMENT-PREFIX |
| htmlb |
| 67666 |
| 84DC2 |
| 00000 |
| 00000 |
| PREFIX |
| htmlb |
| 67666 |
| 84DC2 |
| 00000 |
| 00000 |
| ELEMENT-CLASSNAME |
| CL_HTMLB_CONTENT |
| 4454544454445445 |
| 3CF84DC2F3FE45E4 |
| 0000000000000000 |
| 0000000000000000 |
| TAG_SIG-TAGCLASS |
| CL_HTMLB_CONTENT |
| 445454445444544522222222222222 |
| 3CF84DC2F3FE45E400000000000000 |
| 000000000000000000000000000000 |
| 000000000000000000000000000000 |
| CL_BSP_COMPILER_MESSAGES=>CO_ERROR |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| CL_BSP_RUNTIME=>IF_BSP_RUNTIME~CO_DOMAIN_RELAX_MIN |
| min |
| 666 |
| D9E |
| 000 |
| 000 |
| CHILD |
|
4000B000
0000F000
ME
|
| E0001000 |
| 70008000 |
| NEWTAG |
| content |
| 6667667 |
| 3FE45E4 |
| 0000000 |
| 0000000 |
| ELEMENT |
| ¤###BX X#¯###¯###«###### ###r#####X # |
| A040452250A040A040A050A05020807000FF5220 |
| 40B0280080F000F000B040D02000D02000FF8000 |
| 0000000000000000000000000000000000FF0000 |
| 0010000000001000100010001000000000FF0000 |
| SYST-REPID |
| CL_O2_CO2_PROCESSOR===========CP |
| 4454354435554445545333333333334522222222 |
| 3CFF2F3F2F02F3533F2DDDDDDDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| TAG_SIG |
| content CL_HTMLB_CONTENT BCLG_HTMLB_CONTENT X |
| 6667667222222222222222222222224454544454445445222222222222224444545444544454452222222222222522 |
| 3FE45E4000000000000000000000003CF84DC2F3FE45E40000000000000023C7F84DC2F3FE45E40000000000000800 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| ME->GENERATOR |
|
A0005000
A0005000
COMPILEINFOS
Table[initial]
No. 17 Ty. METHOD
Name CL_O2_CO2_PROCESSOR=>TRAVERSE
IS_FIRST_NODE
2
0
0
0
PREFIX_MAPPER
|
| A0005000 |
| 90006000 |
| NODE |
|
70008000
2000D000
NO_SCRIPT
2
0
0
0
RESULT
############î###ï###Ê#####è#######N# ###
00FF00FF00FFE010E000C01000E000FF90402000
00FF00FF00FFE010F000A050708000FF10E00000
00FF00FF00FF000000000000000000FF00000000
00FF00FF00FF001000000000000000FF00000000
ME
|
| E0001000 |
| 70008000 |
| ATTR |
| í###r#######Ç### |
| E01070000000C010 |
| D020204010007080 |
| 0000000000000000 |
| 0010000000000000 |
| ME->ENV |
|
E0001000
5000A000
ATTR-NAME
TAG
544
417
000
000
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ATTR-ROW
4
0000
4000
No. 16 Ty. METHOD
Name CL_O2_CO2_PROCESSOR=>GENERATE
XML_INPUT
3767766222666637633363666227227226676366236377662323323320373766336366662323323327367276727237
C8C629E2E2534ED568FCFA15F22822922CE57D112CFA443F260D10D22DC32319ECFA1C2F280D20D102D200268232E3
3626763332666627223737623323323326666267373766233272272330263776273766233272272276272766367236
FD053FD100EF9724D2E32070D00D10D101715220E323190D22822927EAFFA4430324790D2282292259232059D20FCF
O2_PARAMS
Table IT_30[2x976]
CLASS=CL_O2_HELPERMETHOD=CALL_O2_COMPILERDATA=PAGE_PARAMS
Table reference: 17
TABH+ 0(20) = C085E23C0000000000000000110000001E000000
TABH+ 20(20) = 02000000D0030000FFFFFFFF045C000080060000
TABH+ 40( 8) = 10000000C1248400
store = 0xC085E23C
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 17 (0x11000000)
label = 30 (0x1E000000)
fill = 2 (0x02000000)
leng = 976 (0xD0030000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000021
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xD8C8EF3C
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 2 (0x02000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 20 (0x14000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
PAGE_URL
MAIN.HTM
44442454
D19EE84D
00000000
00000000
CLASS_NAME
CL_O2EKNVZ07WGTI08DMUX9WUBMS1F
445434445533545433445535544534
3CFF25BE6A077749084D589752D316
000000000000000000000000000000
000000000000000000000000000000
PAKET
SXMSALERT
554544455222222222222222222222
38D31C524000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
NAMESPACE
SAP
545
310
000
000
APPLICATION
SXMS_ALERTRULES
554554445555445
38D3F1C52425C53
000000000000000
000000000000000
OPTIONS
XXD###
55400022
88400000
00000000
00000000
ERROR_TABLE
Table[initial]
RESULT
############î###ï###Ê#####è#######N# ###
00FF00FF00FFE010E000C01000E000FF90402000
00FF00FF00FFE010F000A050708000FF10E00000
00FF00FF00FF000000000000000000FF00000000
00FF00FF00FF001000000000000000FF00000000
ME->GENERATOR
|
| A0005000 |
| A0005000 |
| SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| ATTR |
| ##á#########É### |
| 00E000000000C010 |
| E010001010009060 |
| 0000000000000000 |
| 0000000000000000 |
| ME->TRUE |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| PREFIX_MAPPER |
|
A0005000
90006000
SY
######################U###############0#########x#############################T###x#####XC####
0000000000000000000000500000000000000030000000007000000000000000000000000000105000700010540000
8000101000000000000010501000100000000000000000008000000000000000000000000000604000800000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C
HASPAGE
X
5
8
0
0
NODE
|
| A0005000 |
| 80007000 |
| ELEMENT |
|
B0004000
4000B000
ME
|
| E0001000 |
| 70008000 |
| OPTIONS-NO_SCRIPT |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| OPTIONS-COMPILE |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME->OTR_TABLE |
| Table[initial] |
| OBJ_NAME |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 15 Ty. METHOD |
| Name CL_O2_HELPER=>CALL_O2_COMPILER |
| P_PAGE |
|
E0001000
90006000
P_COMPILE_FLAG
X
5
8
0
0
P_CALL_MODE
G
4
7
0
0
P_USE_RECOV_OTR_GUIDS
2
0
0
0
P_COMMENT_FLAG
2
0
0
0
P_COMPILER_RC
0
0000
0000
P_XML_SOURCE
P_MSGS
0.0.0.0.0.0.0.1.
00FF00FF
00FF00FF
00FF00FF
00FF00FF
P_RESULT
Ï###########ï###ï#######ï########### ###
C01000FF00FFE000E00000FFE00000FF00FF2000
F00000FF00FFF000F00000FFF00000FF00FF0000
000000FF00FF0000000000FF000000FF00FF0000
000000FF00FF0000000000FF000000FF00FF0000
SYST-REPID
CL_O2_HELPER==================CP
4454354445453333333333333333334522222222
3CFF2F85C052DDDDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CLASS_NAME
CL_O2EKNVZ07WGTI08DMUX9WUBMS1F
445434445533545433445535544534
3CFF25BE6A077749084D589752D316
000000000000000000000000000000
000000000000000000000000000000
PAGE_ATTRS-IMPLCLASS
CL_O2EKNVZ07WGTI08DMUX9WUBMS1F
445434445533545433445535544534
3CFF25BE6A077749084D589752D316
000000000000000000000000000000
000000000000000000000000000000
CL_GUI_TEXTEDIT=>FALSE
SY
######################U###############0#########x#############################T###x#####XC####
0000000000000000000000500000000000000030000000007000000000000000000000000000105000700010540000
8000101000000000000010501000100000000000000000008000000000000000000000000000604000800000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C
XML_PROCESSOR
|
| E0001000 |
| 70008000 |
| SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| XML_SOURCE |
| ########################################################################################## |
| 3767766222666637633363666227227226676366236377662323323320373766336366662323323327367276727237 |
| C8C629E2E2534ED568FCFA15F22822922CE57D112CFA443F260D10D22DC32319ECFA1C2F280D20D102D200268232E3 |
| 3626763332666627223737623323323326666267373766233272272330263776273766233272272276272766367236 |
| FD053FD100EF9724D2E32070D00D10D101715220E323190D22822927EAFFA4430324790D2282292259232059D20FCF |
| PAGE_PARAMS |
| Table IT_30[2x976] |
| PAGE_URL |
| MAIN.HTM |
| 44442454 |
| D19EE84D |
| 00000000 |
| 00000000 |
| PAGE_ATTRS-DEVCLASS |
| SXMSALERT |
| 554544455222222222222222222222 |
| 38D31C524000000000000000000000 |
| 000000000000000000000000000000 |
| 000000000000000000000000000000 |
| NAMESPACE |
| SAP |
| 545 |
| 310 |
| 000 |
| 000 |
| APPL_STR |
| SXMS_ALERTRULES |
| 554554445555445 |
| 38D3F1C52425C53 |
| 000000000000000 |
| 000000000000000 |
| OPTIONS |
| XXD### |
| 55400022 |
| 88400000 |
| 00000000 |
| 00000000 |
| ERROR_TABLE |
| Table[initial] |
| CO2_RESULT |
| ############ï###ï#######ï########### ### |
| 00FF00FF00FFE000E00000FFE00000FF00FF2000 |
| 00FF00FF00FFF000F00000FFF00000FF00FF0000 |
| 00FF00FF00FF0000000000FF000000FF00FF0000 |
| 00FF00FF00FF0000000000FF000000FF00FF0000 |
| CL_GUI_TEXTEDIT=>ABAP_COMMENTLINE_IDENTIFIER |
| ??? |
| ?????? |
| ?????? |
| SY-REPID |
| CL_O2_HELPER==================CP |
| 4454354445453333333333333333334522222222 |
| 3CFF2F85C052DDDDDDDDDDDDDDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| P_MS

Hi,
yes, I have activated the SICF-Services as it is mentioned int the documentation.
DO you have any idea?
Thanks.
Regards
Stefan

In XI 3.0 how to set up Alert configuration......

Hi All
     I am new to XI and Pls..help me on this
     How to set up Alert Configuration in XI 3.0 (SP 9)
     What are the settings i need to do in RWB... For particular Purchase order
     How to set up the alert configuration ?
Thanx in advance
Prasad K

Hi,
Please check these links, here you can find something:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
/people/ginger.gatling/blog/2005/12/02/innovative-ways-to-use-alerts
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f2243d711d1893e0000e8323c4f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/2166e6a91d11d188de0000e8216438/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/05/bb223905b61b0ae10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm
Regards,
Wojciech

PI 7.0 Alert Configuration Problem BSP Page Error

Hello,
We are facing the issues for the alert configuration tab in Runtime workbench for PI 7.0.
We have added the fully qualified domain name in exchange profile and 8000 port is also updated for RWB.
We have activated all the SICF services by the report
RSXMB_ACTIVATE_ICF_SERVICES and all the services are activated successfully.
But still When we click on Alert configuration we can see the page but we when we try for
any function, its giving the following error.
Error log is:
Access via 'NULL' object reference not possible.
the termination type was : RABAX_STATE
http://s71cam.corp.wrgrace.com:8000/sap/bc/bsp/sap/sxms_alertrules/main.do was not called due to error
Also in ST22 I can find the following dump:
Dump:     OBJECTS_OBJREF_NOT_ASSIGNED
Error analysis
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Please help.

Hi deepak
follow these sap notes
Note 771317 - BSP call terminates with RABAX_STATE
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=771317
Note 992800 - "RABAX_STATE" dump is coming while paging
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=992800
Note 643933 - RABAX_STATE: Conversion overflow
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=643933
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=rabax_state&cat=sdn_all
thanks
sandeep
if hepful rewartd points

Access to Alert Configuration in Runtime Work bench of PI

Hi Team,
I have created alerts using ALRTCATDEF in ABAP stack of PI. Now, I am able to login to RWB in SAP PI but not able to edit Alert configuration where in we check if the error is related to Integration Engine or Adapter Engine . I want to know what roles does my user need to get added at ABAP level or Javel level to configure alerts. Not sure if this question needs to be posted here. But I am posting since XI administrator might help me with the solution.
Thanks,
Raj

Hi Raj,
I think you should be fine when using role SAP_XI_RWB_SERV_USER. This is the role for the Runtime Workbench User.
Kind regards,
Mark

Alert Configuration for Seeburger Adapter

Dear Team,
I would like to know an information.
For an example,If I use AS2 adapter on the sender side and File on the receiver side,Can we do the Alert Configuration in XI/PI to capture these errors ?
Warm Regards
B.Dheepa

HI
Yes you can use Alert configuration to capture the error from the adapter but the container elements will bring different output as compared to XI adapters.
Thanks
Gaurav

Getting exception when trying to open Alert Configuration in RW

Hello friends,
I am getting the following exception when i am trying to open the Alert Configuration/Alert Inbox in RWB.
Exception:
com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile
        at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:77)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:799)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1462)
        at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getMonitoringServer(SLDAgentObjectImpl0.java:999)
        at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1931)
        at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:493)
        at jsp_alert_inbox1204719699497._jspService(jsp_alert_inbox1204719699497.java:28)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at jsp_FC_Secure1204104271605._jspService(jsp_FC_Secure1204104271605.java:24)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Could you please help me out in solving this problem?
Thanks & Regards,
Senthil

From your error, maybe your profile parameter for alert message server is not properly configured:
I just came cross a post elaborating alerting configuration from Aashish Sinha, hope it helps,
Liang
=====Post from Aashish Sinha=======
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
· For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ? sap ? bc ? bsp ? sap ? alert inbox, and Activate in the context menu.
· For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
· The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ? RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
· If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Hope this will help you.
Regards
Aashish Sinha
============End of the Post=======================

Deleting monitors with alerts configured

Iam running into an issue deleting monitors with alerts configured. It appers that a patch needs to be applied to address the issue. I logged into HP support but I dont have the entitlements under my account, and cant see the avaiable updates.

@Shawnzimm
‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
If you are unfamiliar with the Forum's private messaging please click here to learn more.
Thank you,
Omar
I Work for HP

Regarding Email Alerts configuration

Hi Experts,
I have done the normal alerts configuration, its working fine. Then how to configure the Email Alerts, here I have to use the distributed email list not a single mail address, so how to do the configuration.
After normal alerts configuration we click on fixed receipients and gave user id and in the SU01 transaction we have to give the mail id for the mentioned user id, is it same for the distributed mail (one mail list, internally this list contains many mail IDs) also or any other method is there?
Thnaks & Regards
Ramesh

Hi Rajesh,
Yes I have configured the mail server details. I am able to receive the normal mails also, but my question is how to configure the distributed mail?
Regards
Ramesh

Create rules in RWB - Alert Configuration is not possible.

Hi
I'm setting up alerts on a PI-server.
However, when I try to create alerts in Runtime Workbench -> Alert Configuration, I am not allowed tou2026 I.e the u201CAdd Ruleu201D-button is never possible to use. I add a description and interface names. But the buttons stays dimmed like I'm not authorized or similar.
I do have all roles, even SAP_ALL so it shall be no problem with authorization.
Do I need to setup something in NWA or similar to enable this?
/Best Regards
Joakim

It seems to be a tricky issue.
I do have have the roles:
S_ALM_ROLE
S_ALM_CONF
S_ALM_CUST
and also SAP_ALL
What I do
1) Starts RWB -> Alert config
2) Adds description and interface names for my rule.
3) Tries to select one of the available alert categories below so the AlertCategory is entered and the "Add rule"-button becomes available. (It's always grey).
I also try to do step 3 before step 2.
This is a showstopper... I'll probably create an OSS-case instead. Unless nobody shouts "Herureka, I know the solution!"
/BR
Jocke

Alerts configuration in XI

Hi All,
Could you pls let me know about the Alerts configuration steps in detail or pls let me know use full links
Thanks in advance,
Nousheen.

Hi NOWSHEEN TARIQ ,
Alerting is an function of Runtime Workbench along with Message archiving,End-to-end monitoring, Performance Monitoring,Cache monitoring.
Alerting is no longer dependent on the configuration and activation of end-to-end
monitoring. Consequently, the delay between when an error occurs in message
processing and the creation of an alert is significantly reduced. Furthermore, you no
longer need to schedule the report SXMSALERT_PROCESS_DATA_GET as a
background job.The Runtime Workbench has CCMS Alert Monitor thru which
You can now configure one new CCMS Alert Monitor per Adapter Engine for
adapter-specific processing errors.Alerts triggered by the Runtime Workbench can now be forwarded to the CCMS Alert
Monitor and displayed there.
See also SAP Note 824039.
Thru Runtime Workbench we can access alert inbox, alert configuration
In process Integration with Central SAP Monitoring Infrastructure we Drill down to individual process steps and Use SAP Web AS Alert Framework.
In SAP Web AS Alert Framework, we Classify errors and Alert channels (such as e-mail) available.
Alert-Configuration
Objective: Active Monitoring
CCMS Alerts + message-oriented alerts
Based on SAPu2019s Basis Alert Framework
Alerts propagated through E-Mail, SMS,
In Monitoring the SAP Exchange Infrastructure, Message Alerting is part of Runtime Workbench.
Alerting Framework
Configuration of alerts to reflect the needs of specific processes
Part of SAP Web AS
Alert Configuration
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Inbox
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Notification Step-by-Step
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Defining Alert Classifications
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Triggering Alerts
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Setting up alerts
Setting up alerts in RZ20
Alert Management
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e04141e8-0f11-2a10-adaa-9d97b062c2df
Alert Notification
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90f449a8-a6db-2910-a386-d2b5999f5751
Custom Alerts in CIC Win Client for CRM 5.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/601db2b2-2839-2a10-0381-8807979f6ff8
Understanding u'r SAP EarlyWatch Alert Report
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4b88cb90-0201-0010-5bb1-a65272a329bf
cheers!
gyanaraj
****Pls reward points if u find this helpful

CCMS,CMS and alert configuration guides

hi,
can I have CCMS,CMS and ALERT configuration pdf guides or links please.
I have searched for them on SDN but can't find the exact documents.
thank you for your help.

Hi Babu,
Please find the below links for reference.
CMS :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
CCMS :
/people/dirk.jenrich/blog/2007/01/21/how-to-use-the-monitor-set-sap-ccms-technical-operation-templates
ALERT :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6ce51ae916
How to guides:
Exchange Infrastructure How-to Guides for SAP NetWeaver 2004 [original link is broken]
Thanks & Rgds
J

Alert Configuration in PI 7.31 using SOLMAN based on Payload

Similar Messages

Maybe you are looking for