RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine

Hello,
have a strange error.
Our scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
When starting the RFC call from the sender system the error message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active)
- Component monitoring: no errors
- all rfc connections checked: ok
Does anybody have an idea, how to fix that?
Best regards
Dirk

Hello Dirk and all posters,
We get the same problem just as you described.
We also see no entries in the sxi_cache part for the adapter engine which indicates a problem in getting AE metadata from the SLD.
I see we are all not alone so i believe SP12 is the cause for the problem.
We have another SP11 system that works well.
We tried all those things to understand the problem:
1. look at the structure of the calsses maintained in the SLD to make sure the property "adapterType" exists.
2. Checked the log of the SLD with level "Finest" to make sure the data for the property is sent - all OK.
3. Try to completely delete SLD and reimport CIM 1.4 and CR content 2.0 - all the latest from the web - problem still exists.
4. Put a huge trace on the RFC gateway in the ABAP engine to make sure all XML data is received from SLD server including specific proprty. all ok.
5. Of course we made sure all caches are refreshed, access to SLD is performed all right (logs, traces).
6. Try to disable SM59 entry: SAPSLDAPI and look at the trace in SXMB_MONI. It shows error of connection of course instead of the error of the non exsitene property. But it still shows the error for not getting the access data - so this is only a side affect of the real problem.
Now, as you can see we turned the system from inside out.
I beleive the problem is SAP's problem regarding the parsing of the COM model in the CIM client. I believe that if i could debug the actual abap that parses the XML in the ABAP WAS i would find the problem - i could'nt find a way of debugging the actual processing of a message in QRFC so i'm stuck here.
- Does all of you who have the problem has SP12 ?
- Does any one have an idea of anything else we can all check ?
Good luck for us all :->
Yoad Snapir.

Similar Messages

Configuration of JMS Adapter in Central Adapter Engine

Hi all,
I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
Adapter type : JMS
Transport Protocol : WebSphere MQ (non-jms)
Message Protocol : JMS1.x
Adapter Engine : Integration Server
Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
Queue java class : com.ibm.mq.jms.MQQueue
ipadd : localhost
port : 1414
Queue Manager name : TEST.QMGR
Channel Name : CH1
JMS Queue : LQ
CCSID : 437
Protocol : TCP/IP
JMS-compliant : WebSphere MQ(non-jms)
JMS Queue user : MUSR_MQADMIN
Mapping of message : Entire Message = JMS Payload
But the status is red with an error message Sender Details : NULL
Could you please tell me what went wrong?
Regards
Sathya

Hi,
Make sure that Websphere MQ server is running.
If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
Once the java program works then it will be easy to debug the error over here.
Regards,
P.Venkat

Adapter vs. Adapter Engine

What is the distinction between an adapter versus the adapter engine? How are the 2 related?
Also, what is the process flow of a message?
Step 1. Adapter
Step 2. Integration Engine
Step 3. Adapter
What are the steps in between? I am trying to put together a diagram of a message flow in XI. Any help is appreciated!

Hi Daniel -
>>>1. The Integration Server contains the Adapter Engine and Integration Engine.
Yes, Integration Server is pretty much synonymous with "XI". It also houses/contains the Business Process Engine (e.g. for ccBPM).
>>>2. Adapters run on the Adapter Engine.
Basically yes.
If you have access to the SAP Service Marketplace, there's a good presentation on <a href="http://service.sap.com/~sapidb/011000358700004078552003E/PIAdapterFramework.pdf">Adapter Framework and Adapter Strategy</a> that includes a good architecture diagram that might clear some things up.
Regards,
Jin

SRFC-adapter and file adapter with error: no adapter found

Hello,
we have two scenarios here in an XI 3.0 SP12:
First scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
Second scenario uses file adapter to send file from A to B.
When starting the RFC call from the sender system the error message in area "call adapter" for XML message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
Same problem for file adapter!
Here is the message from the file adapter error log entry in SXMB_MONI:
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.kx1.test038</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.kx1.test038</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Looks like an identical problem for both adapter.
What we have done (checked) so far:
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active, file adapter active)
- Component monitoring: no errors, adapters are fine
- all rfc connections checked: ok
- have checked user and pwd and replaced to be sure
- cache refresh: ok
- reimport of SWCV to IR for RFC: done, no result
Does anybody have an idea, how to get rid of that?
Best regards
Dirk

Hello Udo,
in Adapter monitoring all adapters are listed and per adapter (here RFC and FILE) all adapter entries from the scenarios are available (sender / receiver comm. channel entries - in green)!
Pipeline URL in SLD Bus. Syst. is fine ( and an IDOC adapter scenario is running successfully) !
I think this is a really tricky one!
Best regards
Dirk

JCBC Adapter and File adapter not processing messages

Hi
I noticed that messages are being delivered to Adapter engine and the same are visible in Runtime Workbench with status "to be delivered". But, JDBC Adapter and File Adapter not processing these messages.
Any idea where I can find the problem?
I was able to re-deliver successfully via the JDBC Adapter using the MessagingSystem GUI using XISUPER user.
Regards
Chandu

Hi,
1.Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Regards
Agasthuri Doss

IDoc flat file over AS2 adapter to IDoc adapter

Hi,
The scenario is IDoc flat file(.txt) over AS2 adapter to IDoc adapter. Could anyone help on how to convert the IDoc flat file to xml in AS2 adapter to execute the mapping further? we are using PI 7.0.
Thanks in advance!
-zameer

Hi,
Since you are on Pi 7.0, you would not be able to use the modules for this in PI 7.1.
You would need to refer this document for converting from Idoc flat to XML
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a?quicklink=index&overridelayout=true
In your sender AS2 adapter, you can pass the file as is to an abap mapping which will do the conversion to Idoc xml. the output of the abap mapping goes to your message mapping then for conversion.
Another option would be to use a custom adapter module in the sender AS2 adapter to call the Aabap mapping to do the conversion into Idoc xml.
The custom adapter module would do a JCO/RFC call which will do the conversion before passing the data back to the adpter module.
Regards

HTTP Adapter VS XI Adapter

Hi,
XI and HTTP adapter almost have the same parameters. In which circumstance we will use XI adapter instead of HTTP adapter and what is the advantage of using XI adapter over HTTP adapter?
regards
chaks

For proxy we will use Xi adapter. This uses SAP's native XI protocol for communication.
For HTTP communication such as posting a request to a web application we will use HTTP adapter. Also we can use HTTP adapter for Webservices.
Both XI and HTTP adapter in all versions except 7.3, available in Integration Engine. In SAP 7.1 EHP and latest versions, even SOAP adapter can use XI as message protocol for Proxy communications.
Edited by: Baskar Gopal on Jun 20, 2011 11:49 AM

Difference between XI adapter and HTTP adapter

Hi,
I am not very clear on the exact difference between XI adapter and HTTP adapter.
I want to know, when should we use XI adapter and when to use HTTP adapter.
Regards,
Santosh

Hi,
We use HTTP Adapter in case of the Application is trying to post the HTTP Request message to XI and able to receive the HTTP Message from XI also.
While using the HTTP as Sender , HTTP Sits on ABAP Stack and can able to communicate with the Integration Server Directly, No need of any Adapter here, it is adapterless communication
In Case of Client Proxies
Source application can directly interact with the XI by executing the report in SAP R/3 & will be able to send the XML data to IS,
So no need of the XI Adapter in this case to post xml to XI.
In Case of Server Proxies
Now XI has to post the xml data to the Target Application, here some thing shld be there to establish the medium with the Target System. So we use XI adapter here.
In the receiver case, we need XI Adaper to communicate XI integration Server with the Local Integration Engine( Which we made in SAP R/3's Business system as local IE) to post the data
Basically XI adapter will be used in normal scenarios also to communicate Adapter Engine with Integration Server internally while delivering the msg.
Check this Msg Flow how the XI Adapter is used in Normal Scenarios
Understanding message flow in XI
REgards
Seshagiri

Where is do we use adapter type - XI adapter?

Where is do we use adapter type - XI adapter?

Check this:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/frameset.htm
"● XI 3.0
To connect an ABAP-based Integration Engine, Web AS 6.40.
To connect the PCK.
To connect the XI 3.0 J2SE Adapter Engine.
To connect the Java proxy runtime.
● XI 2.0
To connect the XI 2.0 plain J2SE Adapter Engine.
To connect an ABAP-based Integration Engine, Web AS 6.20."

Differences between SOAP Adapter and WS Adapter

Hi Experts,
In order to consume a service in SAP ECC by SAP PI 7.1, I´m using a service based on RFC. I tryed sucessfully to do that using SOAP Adapter and WS Adapter.
What are the differences between using a receiver communication channel with SOAP adapter or WS adapter? Which is the better way ?
Tks in advance.

Hi,
Please go through the below URLs for a discussion of SOAP and WS adapters:
The difference between SOAP adapter and WS adapter in PI 7.1
WS adapter vs. SOAP adapter
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Jan 9, 2009 3:41 PM

RFC destination from XI ABAP engine to 4.5 B system

I tried to create an RFC destination from XI ABAP engine to 4.5 B system.
It does not work and gives an error.
Error Details DETAIL: NiIGetSockName
-Naveen.

Hi Naveen,
First of all try to ping 4.5B system from XI system (Through TELNET)... This is to ensure the connectivity and the access. The error is not a common error, i suppose, So better first we check the phisical connectivity...
Plz. confirm...
Regards,
Audy

The difference between SOAP adapter and WS adapter in PI 7.1

Hello all,
can anybody explain what is the main difference between SOAP adapter and WS adapter in PI 7.1?
I have checked this [link|http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm]
but was not able to find the real difference.
Or better, what can I do with WS adapter I can't do with SOAP adapter? What are their advantages/disadvantages?
Thank you all, Igor.

In addition to RM, ws adapter also support other ws standard like SAML which is not available in SOAP adatper. Beside:
if your sender or receiver is SAP system, you can also monitor the message in the sender/receiver in addition to the PI box. This is a very good thing, because sometime the MONI in PI shows nothing wrong, but the MONI in your receiver will show you error message that's only related to the receiver system.
However, if you define ws sender CC, and your ws client doesn't support RM, you will have issue sending ws request.
And ws CC will generate ws runtime in PI box, if your configuration is wrong (like user name and password not correct), even if you correct it, the ws runtime sometime won't be regenated based on the correction. In this case you need to delete the ws CC/agreement, and re-create it with all correct information.
Beside make sure your basis team configured the PI system properly regarding ws. If not, you will have lot of pain to figure the problem which was my case.
Jayson

How to generate .pdx file using File Adapter and FTP Adapter

Hi,
is it possible to genearate .pdx file using oracle ESB Adapters(File Adapter and FTP adapter).
Can you anyone guide me.
Thanks,
Raj.

hi,
regarding report, there is a dedicated report forum. you should post there.
but answer for your question is form is nothing to do with the pdf generation. you can call the report from the as usual.
In the report you should set the properties like
destype to 'file'
desname to 'path with file name'
desformat to 'pdf'

How to import seeburger adapter and mdm adapter in sap pi 7.3

Hi all,
how to import seeburger adapter and mdm adapter in sap pi 7.3

Hello
To import the Seeburger adapters, follow the instructions in the Master Installation guide and the individual guides for each of the adapters. These are available with the Seeburger software downloads.
Regarding the MDM adapter, this is the wrong forum for that question. Try the MDM forum (but first, try searching the forum as this is a very basic question).
Regards
Mark

When to use Apps adapter and DB adapter?

Hi All,
For invoking a PL/SQL API(either a custom or System API) in Oracle Applications from BPEL Process which is better to use?When to use Apps adapter and DB adapter?
Thanks,
ChitraDevi

As Sen correctly states for the DB adapter you have to set the context manually using the fun_global.apps_initilize or Fnd_Client_Info.SET_ORG_CONTEXT. This is usually done in a wrapper procedure.
I wouldn't say I'm an expert in this field as I have only used the APPS adapter for 11.5.10. I believe things have changed a bit for R12, but from my experience with APPS, things change very slow so although R12 is 10g App Server I'm sure the principles are the same.
Sen is also correct saying that base tables are not accessible via the APPS adapter. Basically the apps adapter is there to expose services, base tables are not services.
My recommendation would be different based on the experience of the developer(s). The APPS adapter simplifies the development but may not have the flexibility. The apps adapters sweet spot is those services that are difficult to integrate with, e.g. business services, xml gateway. If these are used heavily I would use the APPS adapter.
What I personally do, even if I'm not using APPS, if I'm connecting to the database I will implement a function, stored procedure, or AQ. It is a little more hassle during deployment, but it treats it more like a service and you are not impacted if the tables change. This is not an endorsement for you to go down this path because it does have a requirement to have PL/SQL knowledge, and it breaks the notion of service abstraction from the DB.
cheers
James

RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine

Similar Messages

Maybe you are looking for