on 2007 Mar 14 12:43 PM
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step -by Michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
Regards,
Jai Shankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You have to attach a custiomizing request to save the alert categories that you created. If you do not have one listed, you can create one using the create option on the same popup( you need authorization to create a request).
This request can be used to transport the alert objects that you created to staging and production xi systems.
Thanks,
Renjith
thanks Renjith .
I was able to save the alert . I have created a new container (SXMS_MSG_GUID) as per michal's blog but not sure what to specify in DType.
In object type i selected 'XML Object Type' . I gets list of object but i don't these means...
Can u give some explanation what are these object types..
Check this out:
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
ABAP Dictionary type for (SXMS_MSG_GUID) is SXMSMGUIDC
Thanks,
Himadri
Ranjeet,
http://iscsapapp4w.idcsap.com:51000/rwb/index.jsp can u run this if u still get the same error let me know.
/default_host/sap/bc/bsp/sap/alertinbox ->activate this serivce
Regards
Sreeram Reddy
Hi Ranjeet,
In SICF transaction /sap/bc/bsp/sap/public/bc
check inside the BC node whether you have activated the 'Alert Inbox' service with the service user id and password. Once you have activated you can do a test service from there and you are done...
or
check for patch that wud solve this issue...check notes OSS note:750287
Also you can check this thread:-
Regards.
Praveen
hi praveen,
I have activated the alert inbox from the given path. But while testing alert I am getting same error which i was getting on clicking 'Alert Inbox' from RWB.
but one is that I have logged in with XISUPER user.Is this correct?
One more pointed to be noted:
when i open my 'AlertInbox' from RWB , url is
http://netweaver:50000/rwb/index.jsp
but when i click 'Test Service' from Xi system the url that is coming is
http://netweaver.india.tcs.com:8000/sap/bc/bsp/sap/alertinbox?sap-client=100
any host name problem?
Hi Rajeet,
Problem
The ExchangeProfile contains the wrong HTTP port and host name for WebAs.
The error also occurs if the host name is changed after the initial maintenance of the ExchangeProfile. For example, the error occurs if a new host name is determined on a system that is operated by a hosting partner and that can be contacted from the customer network. In this case, the exchange profile must be modified as described below.
Solution
Check the following property under "RuntimeWorkbench" in the ExchangeProfile:
com.sap.aii.rwb.server.centralmonitoring.httpport
and, if necessary, set it to the value that the ICM monitor displays as the HTTP port of the WebAs (Transaction SMICM -> Goto -> Services).
You also need to fully identify the host name in the property
com.sap.aii.rwb.server.centralmonitoring.r3.ashost
Regards.
Praveen
Hi Praveen,
This is what I did:
1. longon to administration->exchange profile as xisuper user.
2. change the com.sap.aii.rwb.server.centralmonitoring.httpport 8000 from 5000
as HTTP port in transaction SMICM as 5000.and saved it.
3. com.sap.aii.rwb.server.centralmonitoring.r3.ashost is netweaver.india.tcs.
which is same as in SMICM transaction.
But still I am getting 404 Not Found.
Thing to note:
in R3 RFC Destination CentralMonitoringServer-XIAlerts:
ip address and host name are different. Looks like this is the cause of the problem.
User | Count |
---|---|
74 | |
10 | |
8 | |
8 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.