Component Monitoing - Adapter engine XP1 status RED

Hi All,
Component monitoring link is incorrect. The URL references the WebDispatcher instead of the XI server. How to analyze this situation ?
Please advise.
Regards
Shiva

Hi,
Try with this...
http://<host>:<port>/rwb/index.jsp
Ramesh

Similar Messages

Message struck in adapter engine with status Hold

Hi,
In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
Regards,
Krishna

Hello,
Below is some information on how to resolve this type of issue:
1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
4 - Sort the messages in ascending order based on the Sequence no.
5 - Check the predecessor message of the first message in status "HOLD"
Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
a - Predecessor is in Failed State/System Error : Cancel/Resend the
first message in status HOLD after this. Then the remaining messages
can be cancelled/resent.
b - Predecessor is in DLVD state(delivered state) : First Holding
message can be resent/cancelled followed by the others.
c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
predecessor message failed and correct the reason for the failure.
Then resend the predecessor message and then cancel/resend the
remaining HOLD messages. Alternatively, you can directly try
resending this NDLV predecessor message and see if it goes. If it
goes, then the remaining HOLD messages can be resent/cancelled.
Another option could be to cancel this NDLV predecessor message so
that it goes to FAILED state and then cancel/resend remaining HOLD
messages.
Regards,
Sarah

In RWB----component monitoring --adapter engine-- status

Hi ,
In the Runtime work bench component monitoring if we click on adapter engine we get two tabls
CCMS Status: Last Retry Jan 26, 2011 1:55:15 PM CET Ping and Self-Test Help
Ping Status: HTTP request failed. Error code: "404". Error message: "Not Found [http://lYYYY:ZZZZ/AdapterFramework/rtc]" Last Retry Jan 26, 2011 2:03:05 PM CET ... Details
Self-Test Status: HTTP request failed. Error code: "404". Error message: "Not Found [http://lYYYY:ZZZZ/AdapterFramework/rtc]" Last Retry Jan 26, 2011 2:03:05 PM CET ... Details

Hi Sandeep,
Besides updating the patch level to the latest and ensure the SP are in the same level, the notes I would recommend would be:
#1285224 - Http 404 error in details display for Adapter Engine
#804124 - HTTP communication with XI Adapter Engine fails (this one you have already mentioned)
Hope it helps too
Regards,
Caio

Component monitoring - adapter engine error, but no channel in error actual

Hi,
We have a problem in displaying a status of Adapter Engine in RWB. In component monitoring there's a red light and the status - "Are communication channels without errors?" says there's an communication channel in error. But when I click the Communication channel monitoring, everything's green there. Yes, there was an error before, but it's ok now. Why is the AE item in Component monitoring still red? How to make it to reflect the current status?
Thank you,
Olian

Hi Olian,
i am saying to use the cache connectivity test button option from RWB -> compnent monitoring , so have you done cache test using this? if yes, click on refresh display to see the latest adapter engine status..............if it is green, then it is okay..............but if it is red here, it means some comm channel is erroring sometimes - i guess it can be a file adapter using ftp or some rfc adapter......................
if it is green here and compnent monitoring - adapter engine status is red because some comm channel errored in past.........then i think some cache is not getting refreshed - i do not know exactly how to rectify it...........but i can tell you some workaround for it..............the comm channel which was erroring just stop it from comm channel monitoring........then close RWB and again open it and see compnent monitoring - adapter engine status again in it - i think it should be green now.......or try by changing any comm channel description data in ID and save and activate it.........then again check your compnent monitoring - adapter engine status..................but dont worry i think this is a temporary problem
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Mar 26, 2008 11:50 AM

Error in RWB - Component Monitoring - Adapter Engine

Hi,
After we install an Additional Application Server Instance, we are facing an issue with the Runtime Workbench, specifically with the Adapter Engine status.
On the RWB we're have this error:
Ping Status: Unable to establish connection to
"http://<Additional AS Host>:<Central Instance JAVA Port>/AdapterFramework/rtc"
All the time it's pointing to the Additional AS with the Primary AS Java Port.
We are using a central SLD in PIP system.
We already reviewed, the point 8.12 of the "SAP NetWeaver PI 7.1 Including SAP EHP 1 - Troubleshooting Guide"
Any idea to solve this?
Regards,
GCC PI

Hi GCC,
Please change in the http://<host>:<j2ee_port>/exchangeProfile this settings:
Exchange Profile
Connections:
- com.sap.aii.connect.directory.name
- com.sap.aii.connect.landscape.name
- com.sap.aii.connect.repository.name
RuntimeWorkbench:
- com.sap.aii.rwb.server.centralmonitoring.r3.ashost
Please change the value in the:
Config Tool -> cluster-data -> Global Server -> Configuration ->
Services -> com.sap.aii.af.cpa.svc ->
   SLD.selfregistration.hostName
   SLD.selfregistration.httpPort
   SLD.selfregistration.httspPort
Also see notes: #1113161 - Links in Component Monitoring not working
and #764176 - Error in XI due to inconsistent SLD contents
After that, please restart the j2ee engine.
Regards,
Luis Diego

JBBD Sender - Problem with Adapter Engine - Message status Delivering -

Hi all,
I've a rare problem. My scenario is JDBC (EO) to IDOC. If the SELECT query from SQL database arrows 8000 lines, the message was sent from PI to R/3 succesfully and Idocs was generated.
But if the query is larger than 10.000 lines, the message was stopped in the sender queue in AE with status "Delivering". In SXMB_MONI I can't see the message, only in RW in Message Monitoring or Component Monitoring in Engine Status.
I've applied note Note 937159 - XI Adapter Engine is stuck, and follow this blog
/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
Using Configtool I modified these parameters (MaxConsumers). But message still puts in sender queue.
I have in PI 7.1 SPs 0004.
Any suggestions??
Edited by: Pablete on Sep 13, 2010 8:41 PM

I have the same requirement and for solving this, I have to apply a very complex select statement.
But it works perfekt for MS SQL:
select * from table where order_no in (SELECT distinct top(1000) order_no FROM table where any_clause) and any_clause order by order_no
update table where invoice_no in (SELECT distinct top(1000) invoice_no FROM table where any_clause) and any_clause
I create an IDoc for each order_no, so I have to make sure, that all lines belonging to one invoice are in the same select.
My select statement has 463 characters

PI 7.1/RWB/Component/Monitoring/Adapter Engine/Test Message/403 Forbidden

Hello guys!
During performing PI 7.1 Readiness Check I have to perform a test message under Runtime Workbench\Adapter Engine\Test Message.
After processing i receive following error:
Error while sending message: 403 Forbidden.
Does anybody know the cause?
Many thanks in advance!
Jochen

Hi Sreeni!
Direct hit!
This was the problem! Missing role!
Many thanks to you!
Additional Information for all:
Readiness Check (PDF)
A compilaton of simple and advanced checks for Process Integration 7.1 (PI 7.1)
Page 44
SAP Note 817920 - XI Readiness Check 3.0/7.0, 7.1
Regards,
Jochen

Adapter Engine Holding Status

Hi,
I am working on an automation of XI message monitoring which includes checking the Adapater engine Holding count.
From where can I fetch the number of messages with HOLDING status.
Regards,
Karthik

Hi,
Just go to Run Time workbench (RWB) from your Integration Builder and then click on message monitoring --> then select the Database from dropdwon box ---> then from filter option "Status" select the "Holding" and press the start button and you will get your restult.
Regards,
Sarvesh

Message stuck in adapter engine with status Hold, how to delete those

Hi,
In Dev system around 6 lac messages are stuck in ;holding' state. How can I delete them. Is there is any standard proge which can delete all these messages.
Can I delete messages of IE with status 'recorded'?
Regards,
Krishna

Hi,
see this wiki
RSXMB_ARCHIVE_MESSAGES Archive XML Messages
RSXMB_CANCEL_NOT_REST_MESSAGES Cancel XI Messages With Errors That Cannot Be Restarted
RSXMB_DELETE_ARCHIVED_MESSAGES Delete Archived XML Messages
RSXMB_DELETE_MESSAGES Delete XML Messages from the Persistency Layer marked for DEL
RSXMB_CANCEL_MESSAGES Mass cancellation of error messages - XI
RSXMB_SHOW_REORG_STATUS & RSXMB_SHOW_STATUS provide an overview for all XML messages in XI persistency layer.
RSXMB_MESSAGE_STATISTICS2 which provides the processing statistics. This report basically analyzed the history table.
RXWF_XI_UNSED_MSGS report helps in converting messages states other than 003 to final state i.e. 003.
SXMS_REFRESH_ADAPTER_STATUS report helps in converting message sates like 001/008 into final state.
http://wiki.sdn.sap.com/wiki/display/XI/PIArchivingConceptual+Overview

Status Adapter Engine

Hello Guys!
I'm having the following error in the RWB, > Component monitoring > Adapter Engine ..> Result of self-test
Internal error: system status for cluster nodes 477459051 not available
can you send me help about this Error?
Thanks in advance.
Notes: We are using the Netweaver 7.1
Edited by: ecruz2010 on Oct 12, 2011 3:44 PM
Edited by: ecruz2010 on Oct 12, 2011 3:45 PM

Hello,
If you go to the NWA: Operations Management > Systems > Start&Stop > Instances
you can check there the Instance status
Sarah

Error in Adapter Engine

Hi Experts,
In the Component Monitoring, the ADAPTER ENGINE have a RED status, show the message:
Details for Ping Status
Message: Cannot construct correct URL for runtime check using entries in SLD for component af.pid.<hostname>; correct entries in SLD
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Cannot construct correct URL for runtime check using entries in SLD for component af.pid.<hostname>; correct entries in SLD
at com.sap.aii.rwb.core.XIJavaRTCComponent.getConnector(XIJavaRTCComponent.java:188)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Any idea.
Tks in advance.

Hi Pedrão, how are you?
Look at Exchange Profile, if the entries about RWB are the same the entries in the SLD.
You can confirm the Technical System type Process/Exchange Integration and its application system is right.
Follow link about troubleshooting guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/b0458509-49c1-2a10-1188-af2aeb97ed9a
Regards.
Bruno

Error in Adapter engine in RWB

Hi,
I'm facing 2 type of issues in RWB,
Issue 1) Adapter Engine is in Red State in Component monitoring,
Error: Details for 'Is the Adapter Engine Running?'
Response from Adapter Engine: Fatal ArchiveJob (Archiving) failed.(Details: Code: MS.JOB.ARCHIVE; Location: com.sap.engine.messaging.impl.core.job.executor.ArchiveExecutor; Reason: java.io.IOException: The HTTP request of command "MODIFYPATH" did not reach the XMLDAS. This may indicate that the credentials for the HTTP destination have expired.; Time: 31.03.2011 00:00:05)Response from Adapter Engine: Fatal ArchiveJob (Archiving) failed.
2) If I click, any one of the option like Communication Channel monitoring, Engine Status etc, I'm getting the error
"Internet Explorer cannot display the webpage"
It seems to be the URL to open these component(Communication Channel monitoring, Engine Status etc ) is wrong. Fromwhere the URL address is taken? Where we need check the host name??
I searched in sdn, but could not find any related topics.
Kindly help me resolve this issue ASAP.
Thanks & Regards,
Baskaran K

Hi Baskaran,
For 1), did you check if the XML DAS communication user (used in destination "DASdefault") is configured correctly according to the documentation http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/68fac39a363d33e10000000a11466f/frameset.htm and is assigned to the "XMLDASSecurityRole" role?
And check if you have configured the rules for your Archiving job (Component Monitoring -> Adapter Engine XIE -> Background Processing).
It seems the archiving does not work because of configuration issues.
An archiving job without rules means: all messages are relevant for archiving. The delete job will only delete messages which are not relevant for archiving. So it does not do anything in this system. It can lead to the database table keeps growing, if it's the case too.
You should check the archiving configuration so that the archiving job runs successfully.
If you do not want to archive the messages, please deactivate the archiving job. Then the delete job should clean the old messages with the next execution.
You may delete it straightly on the Background Processing.
For the 2), "Internet Explorer cannot display the webpage", try using the compatibility mode of your browser.
Regards,
Caio Cagnani

Problem in the RuntimeWorkBench, Adapter Engine

Hi Experts,
In the RWB> Component Monitoring>Adapter Engine if i double click on this, it is showing the following error:
CCMS Status: Last Retry Jan 14, 2009 10.42.32 AM CET
Ping Status: HTTP request failed Error Code: "401" Error message "Unauthorized[http://<hostName:Port Number/AdapterFramework/rtc]"
Last Retry Jan 14, 2009 10.43.57 AM CET
Self-Test Status: HTTP request failed Error Code: "401" Error message "Unauthorized[http://<hostName:Port Number/AdapterFramework/rtc]"
Last Retry Jan 14, 2009 10.44.17 AM CET
Ping Status & Self-Test Status trafic light colur is RED.
and also iam not able to open Message Monitoring it is asking 3 times user id and password finally it is displaying Unauthorized error.
It is production system, can any body help on this issue
Regards
Rohit

Hi Rohit
for not able to open Message Monitoring
Check if you have Runtime workbench access. You will require to have SAP_XI_MONITOR role authorization with your user id.
also Check if the XI users (in ABAP) on the system running the SLD are locked. If some are, unlock them.
There is a Monitoring Guide avaiable which will be very useful for you. Please check the User Profile settings described in it.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6ce51ae916
There is also a post:
Adapters not working, SLDAccess msg in adapter monitor
take help of this post also
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
for HTTP request failed Error Code: "401"
check if user: XIRWBUSER is not locked in R/3
also check if you got a correct password in the XI exchange profile :
com.sap.aii.rwb.serviceuser.name
com.sap.aii.rwb.serviceuser.pwd
com.sap.aii.rwb.serviceuser.language
also try Changed pw in AE and connection is should work
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 15, 2009 5:55 AM

PI 7.0: Message prioritisation in adapter engine for SOAP adapter.

Hi All,
We have both high and low priority synchronous messages using the SOAP sender Channel of the Central AE.
How can we make sure that High Prio messages ALWAYS get a thread right away when entering the AE? Installing a separate AE is not an option.
When I look in RWB->Component Monitoring->Adapter Engine->Engine Status in the Queues tab, I see this:
SOAP_http://sap.com/xi/XI/SystemCall Yes 5(5) 5
SOAP_http://sap.com/xi/XI/SystemRqst Yes 5(5) 5
When a new High Prio message enters, it can take more than one hour before it gets processed, because there are 1000 Low Prio messages also using the same 5 available Threads...
This delay is of course unacceptable for High Prio messages.
I checked in many other threads in SDN, looks like we cannot priortise for particular messages in PI 7.0, as we can do only at adapter level, not at interface level.
I was thinking of going to the approach which was suggested by "Gr, Wout" in the below thread.
xi prioritization in adapter engine (ae, af, adapter framework, java, jca)
Creating own adapter "MYSOAP" by copying the metadata of SOAP adapter. By that we can use our own adapter "MYSOAP" for high priority interfaces.
what you think guys about this approach?
Is there any thing I need to take care going through this approach apart from copying SOAP metadata into my own adapter.?
Thanks
Deepthi

increased thread count for soap adapter

Adapter engine showing error for file adapters

Hi,
I had configured communication channel using FTP . Because of which the Adapter engine is showing red in the component monitoring. It is saying one of the communicaion channel has error. But when I do a check in the CCs they doesn't show any error. I am getting the same error for NFS as well.
Has anyone come across such a kind of situation? Is it because of wrong entry in CC parameters or is it some BASIS configuration (patch) issue?
Could anyone of you give some guidance on this?
Thanks and Regards
Sanil

Sanil,
Just for testing purpose , delete ur comm.channel and check whether still u r facing the errors. If no errors then its bcoz of u comm.channel. Then we can narrow down the approach. Even after deleting the comm.chanel u get error then check all the channels across all clusters.
Note:After deleting the channel ,give some time and check the same.
Best regards,
raj.

Component Monitoing - Adapter engine XP1 status RED

Similar Messages

Maybe you are looking for