XI Adapter ? No messages in the adapter engine in RWB

Hi Guys,
I have the scenario SOAP-PROXY. I have configured XI Adapter on the receiver side. I have used xml spy to post the messages directly to the IS. I could not see any messages in the adapter engine in RWB.
I have seen the messages processed successfully in the integration engine under RWB.
can anybody explain why i could not see any messages in the adapter engine ? Is It normal with the xi adapter on the receiver side ?
Thanks,
Raj
Message was edited by:
raj reddy

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

Similar Messages

Auto Cancellation of Messages in the Integration Engine.

Dear all,
Issue: Auto Cancellation of Messages in the Integration Engine.
Description: Actually Today, I'm facing Problem in message mapping and its showing error "JCO_SYSTEM_FAILURE". Finally the message is Auto Canceled and showing the status in the Message Monitoring as Canceled with Errors.
I have doubt here how the messages are Auto Canceled with Error? Is there any system or ABAP program which cancelling these messages?
Waiting for yours valuable reply on the above issueu2026
Edited by: BhavinPatel on Oct 7, 2010 8:15 AM

Hi Bhavin,
Two report program are there to cancel error msgs automatically..
1) RSQIWKEX
2) RSXMB_CANCEL_MESSAGES
Regds,
Pinangshuk.

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

"Non-Central Adapter Engines" in RWB

Hi.
We install XI system and we changed host name according to notes 757692.
After then, We found one problem in RWB.
When we run Component Monitor in RWB, Adapter engine is in "Non-Central Adapter Engines".
Why Adapter engine is in "Non-Central Adapter Engines" node ?
Any ideas ?
Regards, Arnold.

Hello Sonali
This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
#764176 Error in XI due to inconsistent SLD contents
#1117249 Incomplete Registration of PI components in SLD
#1334053 No automatic PI 7.10 SLD Registration
Also search the forum for similar issues registering the adapter engine in the SLD components.
Regards
Mark

Change status for 18 million messages in the Integration Engine

Hello there!
I have the following situation and I wonder that maybe you could help. Currently I have more than 18 million messages for the BC_XMB object in the Integration Engine for a BI System (connected to a PI system).
The problem here is that the archiving/deletion jobs in this BI system are faulty since maybe a couple of years ago and all of these messages are marked as "Archivable":
What I'm trying to do here is to change the status for these 18 million messages from "can be archived" to "to be deleted" since there is no way that I can archive this 18 million messages (filesystem capacity). I've been looking many option but I cannot figure out how to do it.
Maybe, if you know an alternative way to do this, I will be very pleased to hear it.
Thanks a lot in advance.
Carlos

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

How to process stucked holding messages in the Adapter Engine.

Hi experts,
This question is may be familier to all...
There are thousands of messages are in holding status in the Adapter engine in RWB.
I tried to found system error in these messages. There is no system error from the last in my investigation. I tried to restart of the communication channels of the combination of these messages. But it is also not use to fix this problem.
Instead of the restart of the Java engine please let me know is there any possibility to fix this issue.
Regards
Mahesh

Hello Mahesh
You can try restarting some of the XI services (e.g. com.sap.aii.af.svc) but usually a java restart is required to free up these blocked threads/queues.
Most likely these messages are in Holding status because there is a blockage in one of the Adapter queues. This can be monitored in the RWB
-> Component Monitoring
-> Adatper Engine XIP
-> Engine Status
-> Additional Data
Find out what adapter queues are causing the blockage and increase the number of threads/queues available to it. This will help prevent the issue occuring again.
See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
See these blogs for more details:
1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements
Ensure note #937159 XI Adapter Engine is stuck, has been applied.
Regards
Mark

Adapter engine messaging URL returns HTTP 403

Hi all,
I currently have a problem with the following scenario: SOAP Adapter -> XI -> JDBC Adapter. I have configured the scenario and everything seems to be running correctly (in the component monitoring the adapters and the integration engine are green). However when I send a request to the SOAP Adapter I get the following response:
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                         <context>XIAdapter</context>
                         <code>DeliveryException</code>
                         <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
     at
Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 403.
</text>
</s:SystemError>
In the Message Display tool of the runtime workbench I get the following trace:
2005-06-05 11:03:08 Success SOAP: request message leaving the adapter (call)
2005-06-05 11:03:08 Success Application attempting to send an XI message synchronously using connection AFW.
2005-06-05 11:03:08 Success Trying to put the message into the call queue.
2005-06-05 11:03:08 Success The message was successfully retrieved from the call queue.
2005-06-05 11:03:08 Success The message status set to DLNG.
2005-06-05 11:03:08 Success Message successfully put into the queue.
2005-06-05 11:03:08 Error Returning synchronous error notification to calling application: Received HTTP response code 403..
2005-06-05 11:03:08 Error Transmitting the message using connection http://<host>:8000/sap/xi/engine?type=entry failed, due to: Received HTTP response code 403..
2005-06-05 11:03:08 Error The message status set to FAIL.
2005-06-05 11:03:08 Error Returning to application. Exception: Received HTTP response code 403.
So it seem that somehow the adapter framework is not allowed to send a message to the integration engine via the messaging URL.
Any ideas how to resolve this problem?
Thanks for you help,
Christian

Hi,
If you've changed the passwords for XI service users
then you may also want to check this note: 721548
XI 3.0: Changing the passwords of the XI service users
Regards,
michal

Message in adapter engine

Hi all,
We monitor messages in adapter engine through RWB.
Can anyone tell me where these messages are stored?

hi,
it has the misconception that RWB uses the same data base as of sxmb_moni.
but this is not true. actually RWB has a java componenet and IE is a abap componenet.
RWB getting tha data from SXMB_MONI db(abap table) through the jrfc call and storing it into the XI_AF_MSG table. this can be verified because, when u try to fatch payload for the sych message in RWB ,it is showing payload is deleted to save memory . but the same message with the payload can be displayed at SXMB_MONI .but for this u need to set the retention period at sxmb_adm---intigration engine configuration.by default value for this is 0 days.please have a look of below link.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/xi%252btables
the XI_AF_MSG_AUDIT table stored the detail of all the audit log.thats why the no of entrieds in this table is more than XI_AF_MSG table.
now Q is how to access these DB.
these DB can be access through the DB tool say SQLplus.
to get the total no of entries byststus u can use the fllowing query.
select status, count(1) as
current_number from sap[sid]db.xi_af_msg
group by status;
regards,
navneet

Adapter Engine Error Message on RWB

Hello
We are getting an Red color error message on Adapter engine on RWB
monitoring ---> Component Monitoring.
Here is the error message:
SLD access SLD host:port = sap03:50000
Error getting JPR configuration from SLD. Exception: No entity of class
SAP_BusinessSystem for XID.SystemHome.sap03 found
No access to get JPR configuration
Please advise for solving the error message on adapter engine.
Thanks & regards
AK
SAP Version : NW04 (XI 3.0) SP20

Hi Senthil,
As suggested by others there is no problem with your communication channels ,,, the problem you face is because Your DBA has initiated the SHUTDOWN IMMEDIATE command. This will shutdown Oracle and terminate all active operations.
Please tell him to start the services and Wait until Oracle has been restarted by your DBA.
Regards
joel

Messages are not reaching to Adapter Engine (JMS receiver)

Hi Friends,
We have one scenario running on Production env.
Scenario is: R3(IDOC) -> XI ->JMS Provider
IDOC to JMS.
Sometime we found messsages are successful in SXMB_MONI, but those messages entries are not found under AE.
Means they are not reaching to JMS.
Communication channel is green, without any error.
This happens sometime only, and no changes have been done to JMS adapter parameters.
What might have happen to these messages, which are successful in MONI but not visible under AE.(Even not in Archived option)?
I searched on SDN, but most of the questions are unanswered.
Please let me know your inputs.
Divyesh Vasani

Hi Divyesh,
check under message monitoring in RWB
if u r not finding the message there , those might be archived.
did u confirm with the destination system .. if they got the messages?
if at all messages are stuch in AE ... and if u search the correct message u should be able to see the message.
if the Integration engine unable to put messages in AE , then in some pipeline step in MONI it will show error

Difference between Testing Message in Integarion Engine and Adapter Engine

Hi Experts,
in project, we always test message in runtime workbench>component monitoring>integration engine-->Test Messge
however, i also find that in runtime workbench>component monitoring>adapter engine also exists a Test Message tab.
we don't have access to test messages in this tab, so can anyone tell that what is the difference between testing message in integration engine and adapter engine?
thanks in advance.

The usual flow of messages in scenarios which use adapters at both sender and receiver end is as follows
Sender system -> Adapter Engine -> Integration Engine -> Adapter Engine -> Receiver system
When you use the testing option in IE, then you are basically posting the message directly to the Integration Engine.
When you use the testing option in AE, then you are trying to post the message to the adapter engine, which will then forward the message to the Integration Engine. IN this testing, you are also testing the sender adapter also.
Regards,
Ravi Kanth Talagana

Help!Cache status of object for Central Adapter Engine is incorrect

this problem cconfused me several days!
version:PI 7.1
after i activate the communication channel, the cache not update for central adapter engine
problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
the update for integration server and mapping run time are all correct.
then when i display wsdl for sender agreement(SOAP sender), show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
who can help me solve this problem.
thank you in advance.

Hi cheng,
Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
And you may check the following notes:
#1031321 - Self-Registration of Adapter Engine and RWB fails
#1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
Regards,
Caio Cagnani

Bad adapter engine configuration - File Sender scenery doesn't work

In file sender scenery, the adapter doesnu2019t pass any message to the Integration Engine.
When I take a look to the communication channel monitoring it shows the channel with status OK (Green). But when I look into the audit log of the incoming message I see the following error:
Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR ErrorText: ErrorStack: Error in sender agreement for party , service VLTEST, interface namespace urn:damm.es:vialactea:logistica, interface oa_SimpleLine No sender agreement found for , , , , ,
The sender agreement exists in the Directory and the status of the cache is OK.
But in the Message Data I see this End Point URL: http://asrmd:8082/sap/xi/engine/?type=entry
This is adapter is attached to a development system instance number 80 and the port of the above URL is a reference to the TEST system instance number 82. I investigate this issue but I canu2019t find where the miss-configuration is causing this bad End Point.
Have anybody an idea about this problem. Itu2019s the first time I found this kind of miss-configuration.
All other adapters are working fine. The file receiver adapter is working fine too.
Thanks in advanced.

Hi Sergi,
Now is clear. Sorry but I didn´t see your posts properly. I didn't move the cross bar until the final.
So now I change my point of view.
Go to Runtime Workbech --> Component Monitoring --> Integration Engine --> Test Message. Which URL is displayed here? is it right?
If don't, effectively you have wrong configured your URL of the Integration Engine.
Go to SLD --> Business Systems --> Select your XI business System. At the Integration Configuration tag check the URL, if it is wrong, change it and save the changes. Remember that the rol must be Integration Server.
Refresh the caches.
Hope it is usefull.
Carlos

Adapter Engine missing in SLD and RWB

Hi all,
I have no Adapter Engine in RWB or under technical systems in the SLD.
In Integration Directory I have "central adapter engine" in the adapter engine field in my File adapter .
But I get this message when I open the communication Channel:
"No SLD elements of type SAP_XIAdapterFramework found"
Please advice,
Thanks!

Hi Thomas,
Your Adapter Framework is probably not registered in the SLD. You may force the
registration if you perform the action as follows:
1. In the J2EE administrator tool in cluster - server - services - deploy
(application view), stop the J2EE applications:
a. sap.com/com.sap.aii.af.service.cpa.monitor
b. sap.com/com.sap.aii.af.
2. Restart the sap.com/com.sap.aii.af application.
Refer sapnote in chapter 8.2 for more in the link provided below on Trouble shooting.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
Cheers,
Ram.

Unable to find URL for Adapter Engine af.xid.xidev ?

Hi,
I have scenario.
Abap proxy -
> ccBPM -
> RFC (synchronous).
The error happen for ccBPM -
> RFC
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.xid.xidev</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any idea for what happening ?
Cheers
Fernand

Hi.
Have you tried with this
Re: Wrong Adapter Engine on RWB?
Regards
Seshagiri

XI Adapter ? No messages in the adapter engine in RWB

Similar Messages

Maybe you are looking for