ALERT configuration in RWB : No central monitoring server in exchange prof

[Former Member]

Hi Experts,

I am unable to confgiure alerts in RWB.

I get the No central monitoring server in exch profile as the error.

I checked the exchange profile it has parameters for

com.sap.aii.rwb.server.centralmonitoring.r3.ashost FQDN

com.sap.aii.rwb.server.centralmonitoring.r3.sysnr 00

com.sap.aii.rwb.server.centralmonitoring.r3.httpport 8000

i still get the same error.. ne idea why?

pls help

[Former Member · Accepted solution]

Hi

Please check the following link you may find solution

Thanks,

Amar

[Former Member · Accepted solution]

Ive tried it but no luck

The same link works in QAS..

But I guess after I create the categories in DEV .. I have to transport it right?

I created the category in qas using alrtcatdef an hen I log into RWB to create the category it throws a dump...

Im lost ;-(

Edited by: Ravindra Teja on Oct 17, 2011 9:36 AM

[Former Member · Accepted solution]

any help guys ??

com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile

at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:79)

at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:809)

at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1472)

at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getMonitoringServer(SLDAgentObjectImpl0_0.java:959)

at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1722)

at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:492)

at jsp_alert_inbox1318829931997._jspService(jsp_alert_inbox1318829931997.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:566)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)

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_Secure1303551789508._jspService(jsp_FC_Secure1303551789508.java:15)

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:566)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

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:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Edited by: Ravindra Teja on Oct 17, 2011 12:19 PM

[Former Member · Accepted solution]

Hello,

You could also check the following

- RFC destination CentralMonitoringServer-XIAlerts tests successfully

- ensure all parameters in the Exchange Profile ending in *.name are using the FQDN

- note 1397848 XI Alerting: Load balancing for central monitoring server

- note 750287 Runtime Workbench: Alert configuration does not start

- if high availability is being used note 1052984

Regards,

Sarah

[Former Member]

1. Check and confirm SICF services sxms_alertrules and alertinbox are activated

2. Make sure that com.sap.aii.rwb.server.centralmonitoring.r3* entries are under RuntimeWorkBench and not somewhere else in the exchange profile

3. Ensure that /etc/services contains correct assignment for 32NN

4. Is the port 8000 correct?

5. Check and confirm if the property alerting.isActive is set to true in SAP XI AF CORE service.

[Former Member]

Hi All,

I had to add

com.sap.aii.rwb.server.centralmonitoring.name

com.sap.aii.rwb.server.centralmonitoring.r3.mshost and

reinitialize the rwb ...voila.. done

thanks All