RWB: Central CCMS monitor not available

[rajan_s]

Hi Experts,

I am getting this message when I click on Component Monitoring in RWB of PI 7.1:

Central CCMS monitor not available

Under Components, I see:

Domain ??? (domain.00.sapPIDci)

Integration Server

Integration Engines

Non-Central Adapter Engines

J2SE Adapter

Tools

System Landscape Directory E4D

Integration Directory PID

Integration Repository PID

Runtime Workbench PID

Please suggest how to fix this problem.

Thanks.

[Former Member · Accepted solution]

Hi Rajan,

Looks 'Central Monitoring System' that is defined in your PI system exchange Profile is either Netweaver 7.10 or higher version hence you get this error.

Thus, you either need to upgrade your Support Pack.

Please refer to SAP note# Note 1131738 - RWB warning 'Central CCMS monitor not available'

Regards

Sekhar

[rajan_s · Accepted solution]

Hi Sekhar,

Thanks for your reply. Is there no other workaround besides upgrading the support pack?

regards,

Rajan

[rajan_s · Accepted solution]

Hi,

We implemented this change and now the CCMS not available error has gone away but the component monitoring has few items with yellow and red LED:

Integration Engine SID Type: XIServerEngine has yellow LED triangle.

Business Process Engine SID Type: XIBusinessProcessEngine has yellow LED triangle.

Mapping Runtime SID Type: XIMappingRuntime has red LED with error.

Proxy Runtime Business System ID Type: XI Integration Engine has red LED with error.

Also, I don't see any communicaiton channels that were created by developers.

Please advice.

Thanks.

[Former Member · Accepted solution]

Hi Rajan,

Please do a full CPA cache refresh and then check if you are able to see the communication channels.

As per the note, have you implemented correction instructions in the note or upgraded the support pack ?

If you have upgraded the particular support pack as per the note, then i recommend to upgrade the complete stack.

Cheers...,

Raghu

[Former Member · Accepted solution]

Hi Rajan,

Please perform below tasks.

1. Check INTEGRATION_DIRECTORY_HMI rfc working fine.

2. Ensure, SAPSLDAPI, LCRSAPRFC working fine.

3. ensure, SLDAPICUST - Test functionality working fine

4. ensure SLDCHECK works fine

5. then, perform full CPA cache refresh using http://<hostname>:<http port>/CPACache/refresh?mode=full

6. If this url prompts for credentials, provide PIDIRUSER/ XIDIRUSER based on your configuration

if this doesn't solve, please restart your J2ee engine and re-try the same....if still issue persists please post us default trace

Regards

Sekhar

[rajan_s · Accepted solution]

Hi,

We implemented the SAP correction note 1131738 after that CCMS monitor not available error went away but components are not displayed correctly with green status.

-

---

Following tasks were checked/performed as per the suggestions:

1. Check INTEGRATION_DIRECTORY_HMI rfc working fine. worked fine.

2. Ensure, SAPSLDAPI, LCRSAPRFC working fine. worked fine.

3. ensure, SLDAPICUST - Test functionality working fine. Worked correctly.

4. ensure SLDCHECK works fine. Worked correctly.

5. then, perform full CPA cache refresh using http://<hostname>:<http port>/CPACache/refresh?mode=full The full cache refresh failed, but existing cache data was reloaded from the local DB.

6. If this url prompts for credentials, provide PIDIRUSER/ XIDIRUSER based on your configuration. PIDIRUSER was used.

Restarted J2EE. Looking at the default trace file, I found the following errors: message contd

-

---

[rajan_s · Accepted solution]

message contd -- errors from default trace --

-

---

#1.5 #000C293A0C5D00AA0000015C0000126400CA8C91136C6169#1260255823774#com.sap.engine.services.servlets_jsp.server.application.SessionServletContext#sap.com/opensqlmonitors#com.sap.engine.services.servlets_jsp.server.application.SessionServletContext#J2EE_GUEST#8849#####Application [10]##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot get user name for OpenSQLMonitor security role.#

#1.5 #000C293A0C5D00AE000000000000126400CA8C9113698309#1260255823821#com.sap.engine.services.deploy##com.sap.engine.services.deploy#######System [112]##0#0#Warning##Plain###

Warning occurred on server 5701250 during stopApp sap.com/opensqlmonitors : Optional container Monitoring Configurator is not active at the moment.#

#1.5 #000C293A0C5D00A30000003C0000126400CA8C91136C9819#1260255823915#com.sap.conn.jco#sap.com/tc_secauth_spnegoear#com.sap.conn.jco#J2EE_GUEST#8850#####Application [7]##0#0#Error#1#/System/Server/Connector/Rfc#Plain###Context does not exist session id=com.sap.engine.session.exec.UserContextImpl@357bed5c[ clientId=null, clientSessions=[], persistent Model=null]#

#1.5 #000C293A0C5D00A30000003E0000126400CA8C91136C9819#1260255823915#com.sap.conn.jco#sap.com/tc_secauth_spnegoear#com.sap.conn.jco#J2EE_GUEST#8850#####Application [7]##0#0#Error#1#/System/Server/Connector/Rfc#Plain###[JCoAPI] JCoClient.connect {{jco.destination.pool_capacity=5, jco.client.lang=EN, jco.client.ashost=localhost, jco.client.destination=UMEBackendConnection, jco.client.user=SAPJSF, propertiesProvider=com.sap.security.core.server.destinations.provider.DestinationsProviderFrame, jco.client.sysnr=$$, jco.destination.peak_limit=10, jco.client.type=A, jco.destination.max_get_client_time=10000, jco.client.client=100}} failed with com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connection parameters: TYPE=A DEST=UMEBackendConnection ASHOST=localhost SYSNR=00 PCS=1

#

#1.5 #000C293A0C5D00420000008D0000136800CA8C91124270E6#1261076882562#System.err#sap.com/com.sap.ip.bi.sdk.monitoring#System.err#J2EE_GUEST#1309####7fa04350eb3f11deb78c000c293a0c5d#HTTP Worker [5]##0#0#Error##Plain###Dec 17, 2009 12:08:02... ...connector.relational.CommonConnection [HTTP Worker [5]] Error: Exception during SAPQuery connection: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=us7031.wdf.sap.corp SYSNR=13 GWHOST=us7031.wdf.sap.corp GWSERV=sapgw13 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR hostname 'us7031.wdf.sap.corp' unknown

TIME Thu Dec 17 12:08:02 2009

RELEASE 710

COMPONENT NI (network interface)

VERSION 39

RC -2

MODULE nixxhsl.cpp

LINE 233

DETAIL NiHsLGetNodeAddr: hostname cached as unknown

COUNTER 6

-

---

[Former Member · Accepted solution]

Check rfc AI_RUNTIME_JCOSERVER & AI_DIRECTORY_JCOSERVER using SM59 Transaction

Regards

Sekhar

[rajan_s]

Thanks to those who helped/replied. Closing this thread as no further replies.