SOAP Adapter Metadata Missing

Hello,
The SOAP adapter metadata is missing from the http://sap.com/xi/XI/System namespace. All the others are present. How can we get the adapter ?
Does it come as part of some patch.
Regards,
Durga

Hi, we're reimporting the SAP BASIS software component (XI3_0_SAP_BASIS_6.40_00_00.tpz).
The present our situation is:
SAP_JTECHF 6.40 SP11 (1000.6.40.11.0.20050221011822) SAP AG 20050425182200
sap.com SAP-JEECOR 6.40 SP11 (1000.6.40.11.0.20050221011406) SAP AG 20050425182155
sap.com SAP-JEE 6.40 SP11 (1000.6.40.11.0.20050221011617) SAP AG 20050425182238
sap.com SAP_JTECHS 6.40 SP11 (1000.6.40.11.0.20050221012022) SAP AG 20050425182237
sap.com LM-SERVICE 6.40 SP11 (1000.6.40.11.0.20050221012100) SAP AG 20050425182231
sap.com SAP-XIAFC 3.0 SP11 (1000.3.0.11.2.20050407085022) SAP AG 20050425212631
sap.com SAP_XIAF 3.0 SP11 (1000.3.0.11.1.20050324062550) SAP AG 20050425220610
sap.com SAP_XITOOL 3.0 SP11 (1000.3.0.11.3.20050405055844) SAP AG 20050425222949
But the SOAP Adatper still missing.
Is there a newly version to install ?
Regards
Gianfranco

Similar Messages

Duplicate SOAP Adapter metadata

we are using PI 7.11 and would like to know whether it is possible\supported to create a copy of the standard SOAP Adapter metadata in the Integration Builder. We would copy it to a different SWC, namespace and name (e.g. Customer_Basis_SWC, http://customer.com....,CustomerSOAP). The requirement behind this is as follows.
An interface exist between PI and a thrid-party application that causes a large number of timeouts when sending async. SOAP messages to this application. The third-party application can not handle the workload caused by the large number of messages pushed through by SAP PI. The third-party application can not be optimized at this point. We believe the only way around this problem is reducing the number of receiver threads in the SOAP adapter. However by changing the threads on the standard SOAP adapter all other receiver adapters of type SOAP are impacted too. Having a customer\application specific SOAP adapter would probably resolve this issue. We also looked at message prioritization but this wouldn't help in this case either.
If this approach is possible what steps are involved other than copying the metadata to a different SWC, Name and Namespace. We did try this in our sandpit and got an error in the communication channel monitor saying "No adapter registered for this channel", even so the interface we tested with appeared to work using the new adapter. We did not modify the metadata after it was copied into the new SWC. Is there any other configuration step required to get rid of this error message.
Any help would be greatly appreciated.
Dieter

Please check below SAP help on loading metadata.
http://help.sap.com/saphelp_nw73/helpdata/en/65/6f64403899970ae10000000a155106/frameset.htm

Why SOAP Adapter Type is missing ?

Hi all, I'm following the WebLog Invoke Webservices using SAPXI (/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi) and I'm not able to use a SOAP Adapter.
In particular, when I try to select the Adapter Type I obtain the following list:
File
HTTP
IDoc
JDBC
JMS
Marketplace
RFC
RNIF
XI
Why SOAP Adapter Metadata is missing ?
Thanks in advance for your collaboration
Best regards
Gianfranco Bello

Hi, we're reimporting the SAP BASIS software component (XI3_0_SAP_BASIS_6.40_00_00.tpz).
The present our situation is:
SAP_JTECHF 6.40 SP11 (1000.6.40.11.0.20050221011822) SAP AG 20050425182200
sap.com SAP-JEECOR 6.40 SP11 (1000.6.40.11.0.20050221011406) SAP AG 20050425182155
sap.com SAP-JEE 6.40 SP11 (1000.6.40.11.0.20050221011617) SAP AG 20050425182238
sap.com SAP_JTECHS 6.40 SP11 (1000.6.40.11.0.20050221012022) SAP AG 20050425182237
sap.com LM-SERVICE 6.40 SP11 (1000.6.40.11.0.20050221012100) SAP AG 20050425182231
sap.com SAP-XIAFC 3.0 SP11 (1000.3.0.11.2.20050407085022) SAP AG 20050425212631
sap.com SAP_XIAF 3.0 SP11 (1000.3.0.11.1.20050324062550) SAP AG 20050425220610
sap.com SAP_XITOOL 3.0 SP11 (1000.3.0.11.3.20050405055844) SAP AG 20050425222949
But the SOAP Adatper still missing.
Is there a newly version to install ?
Regards
Gianfranco

SOAP Adapter missing payload on receiving web service

Hi there,
I'm having a problem with a File to (asynchronous) SOAP Adapter scenario that is currently baffling me.
I wonder if anyone out there has any troubleshooting ideas for this one?
The source message is being picked up OK and I can see from Communication Channel Monitoring on the Runtime Workbench that it is allegedly being delivered to the Web Service OK.
All the entries in the audit log point to a successful scenario and I can view the payload in the Message Content "payload" area.
However on the web service / server side the message is completely blank. Somewhere along the line the payload has gone missing.
I can copy and paste the payload manually into the web service test area and this is fine.
Any ideas/suggestions as to what could be happening with this or how I might go about troubleshooting it?
Many thanks
Ian

Thanks Bruno,
It looks like you were right...
In the end we used Wireshark - a packet sniffing application - to check what was actually hitting the destination server. We found that the content was arriving at the server but the web service wasn't accepting the format. The creators of the web service are now investigating why and will hopefully will advide me of the format error in the message. But at least I was able to prove that the message was getting there which was the focus of this query.
Regards
Ian

Adapter Metadata Information Missing

Hi XI Guru's ,
Recently i installed PI 7.0 successfully .
At the time of configuring a scenario in Integration Directory my developer is not getting the Adapter metadata information via the drop down tool (i.e. the tool by which we choose the adapter ).
Did i missed something at the time of configuring the PI server ?
Thanks in advance...

Hi,
This might help you more,
Importing the XI Content for Software Component Version SAP Basis
1. Copy XI3_0_SAP_BASIS_7.00_00_00.tpz (latest file ask your BASIS Consultant) from <installation DVD>/XI_CONTENT to
directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
2. On your SAP XI host, call transaction SXMB_IFR.
3. Choose Repository (Design).
4. Choose ? Tools ? Import Development Objects
2. Choose the file /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import
XI3_0_SAP_BASIS_7.00_00_00.tpz (latest file ask your BASIS Consultant)
5. Import the file.
Regards,
Ramesh P
Message was edited by:
Ramesh Parashivamurthy

Adapter specific attributes - SOAP Adapter

Hi,
I am trying to use the adapter specific attributes of the receiver SOAP adapter. But I am not able to view the Dynamic configurations in sxi_monitor corresponding to this message. Any clue why!?
I read through the SOAP adapter help on help.sap.com,
<i>http://help.sap.com/saphelp_nw2004s/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm</i>
Here it says:
<i>If you want to use header fields, set the relevant indicator for Variable Header. The technical names for the fields are XHeaderName1, XHeaderName2, XHeaderName3. The parameters are embedded in the HTTP request under the names you enter here.</i>
But I donot find an option where I can enter the names. Am I missing something here?
Regards,
Smitha.

Hi Smitha,
I did not try to use adapter-specific attributes with SOAP-adapter, but with mail-adapter. The documentation is quite similar, so I excpect similar results...
So as far as I understood, the parameters XHeaderName1, ... etc are for dynamic extension of the set of adapter-specific attributes. For example, if you want to add some more information in the message header, you can program an adapter module and you have now a guide how to name the additional attributes.
Usually, the "standard" adapter-specific attributes are starting with "S" (Sender) or "T" (Receiver). You can find the names in the documentation of the SOAP-adapter.
In order to use the adapter-specific attributes, you have to check both indicators (adapter-specific attributes, variable transport binding). If this still doesn't work, you should use OSS. In my scenario (mail adapter) this didn't work, too. The reason was, that there was a bug in the adapter metadata (Integration Repository) of SAP BASIS. There was a SAP note, where I could download the correct adapter metadata. Maybe you can find a SAP note for the SOAP Adapter.
Although this is probably not the final solution, I hope this guides you a step further.
Regards,
Torsten

PI 7.11 Adapter Metadata

I have installed a new PI 7.11 system.
According to the PI sap help at http://help.sap.com/saphelp_nwpi711/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
SAP ships adapter metadata for all the adapter types it provides. You can find the adapter metadata shipped by SAP in software component SAP BASIS, software component version SAP BASIS 7.10, in namespace http://sap.com/xi/XI/System.
But in our newly installed PI 7.11, under ESR-Software Component u2018SAP Basisu201D, I see SAP Basis 7.11. But I do not find u201CAdapter Metadatau201D under the name space http://sap.com/xi/XI/System
Is it expected? If not, which part could have been missed. What could be done to see the u201CAdapter Metadatau201D (which list all the sub items: BC, CIDX, File, HTTP, IDoc, JDBC, JMS, Mail, Marketplace, RFC, u2026.).
I appreciate any inputs you have.
Thank you very much, and best regards,
Joanna

Abhishek,
You are amazing in response.
The item 8 is:
"XI CONTENT SAP_BASIS 7.11
Maintenance Software Component (Current View)"
This 8th item lists SP01, SP02, SP03, SP04 for XI CONTENT SAP_BASIS 7.11.
Is this item what you've recommended? Or should I down load the
"XI CONTENT SAP_BASIS 7.11
Installation Software Component (Current View)" (which does not have download file on SMP swdc )
Over one week ago, I downloaded the SP04 for XI Content SAP_Basis 7.11 (the file name is XICNTSAPBASIS04_0-10005649.ZIP, size of 5408393 bytes).
I unzipped it, getting the file XI7_11_SAP_BASIS_7.11_04_00.tpz
and then imported it using "Import Design Object" in ESR, and getting the message:
"Import source XI7_11_SAP_BASIS_7.11_04_00_2010-01-15_10-58.tpz imported successfully
Import file moved to server directory importedFiles
4224 object(s) imported"
Also, checked the component system info:
SAP_CNT_SAP_BASIS 7.1100.20081021173332.0000
There is one OSS note 1119255 (not sure it applied to PI 7.11), pointed to by SAP. The note says for PI 7.1:
24/MAR/08....III...XI_CNT_SAP_BASIS and XI_CNT_SAP_ABA stay at start SP
Wirth SP04 import for XI Content SAP_Basis 7.11, I see our version stays at the start SP with 7.110 (instead of expected 7.114).
This problem has been my road blocker for over the last few days. I was not able to get much help from SAP through OSS message.
Thank you very much for all your inputs, and regards,
Joanna

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

PI 7.3 AEX - XI 3.0 message protocol in the SOAP adapter.

Hello,
My client's landscape is on SAP PI 7.3 AEX(Java only installation) and SAP ECC 6.0 EhP4.
I have configured a HTTP-Proxy scenario. For the proxy messages to go into the SAP ECC system, I have configured a SOAP Receiver adapter in PI 7.3 AEX.
I have created a service interface in ESR in PI 7.3 and generated the proxy in the SAP ECC system.
I have configured the SOAP receiver to use the XI 3.0 protocol and by using the Addressing Type as 'URL Address'. The URL that I am using is " http://<SAP_ECC_server>:PORT/sap/xi/engine?type=entry ".
When I try to test the scenario, the messages are not reaching the target ECC destination and in the SOAP Receiver communication channel, I am getting the following error:
Information:                Delivering to channel: SOAP_RECEIVER
Information:                MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Information:                SOAP: request message entering the adapter with user Guest
Error:                          SOAP: call failed: java.io.IOException: unable to create a socket Information                 SOAP: sending a delivery error ack ...
Now, in my client estate there is also a SAP PI 7.11 system, I have replicated the service interface in the ESR on 7.11 and regenerated the proxy in SAP ECC. When I now run the scenario, it works.
Just stressing here on the point that, the abap proxy generated from SAP PI 7.3 ESR did not work(but worked when I generated the abap proxy from SAP PI 7.11 ESR) when configured using the XI protocol on the SOAP adapter.
ALso, I have gone through the 'Note 1247043 - Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1'.
Is the behaviour I am facing a release restriction on SAP PI 7.3
Need suggestions from anyone who has tried configuring this scenario, is there anything that I have missed?
I am happy to share more info if required...
Thanks in advance,
Best Regards,
Karthik

HI Karthik,
Did you able to resolve this in PI 7.3??
Even i am also facing the same issue in receiver soap adapter for abap server proxy:
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Please let me know how did u resolve this?
Thanks,
Prasanthi

Using the Axis Framework in the SOAP Adapter

Hello experts,
I am currenty checking how I can easily manipulate sender and receiver details and how I could get attachments into XI.
I saw in the sap help that it is possible to use the AXIS framework from the SOAP adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/45/a39e244b030063e10000000a11466f/frameset.htm
As usual, the documentation is of the same quality SAP usually provides.
So my first question would be: This is a moduke to be used from the SOAP adapter right? I am asking because they also wirte about the AXIS adapter and its metadata.
In oder to get it working, I created in the NWDStudio a library project, added my libraries (to the root directory) and deployed it via SDM. Deployment is succesful but its not working.
SAPHelp says I should check for a MessageServlet - I ask myself how that could appear suddenly just by packaging some axis libraries...?
I am using for that the ESA box (NW04s SP6) - I was not able to see whether there are some dependencies to the SP - are they?
Thanks for your support!
Helge

Helge,
Axis is outdated and has some issues ..use Apache Soap instead its much better and easy to use.
http://ws.apache.org/soap/
Regards
Ravi

Sender SOAP adapter: get soap header data

Hi,
I've been going through various posts and blogs here on SDN + looked in the how to guide for SOAP adapter, but still find it quite difficult to actually find out how to do it. I've tried to follow recommendations seen, but it doesn't add up.
So can someone please tell me how to get an element situated in the SOAP header of the request sent to XI via sender soap adapter?
Let's for instance say the request looks like this:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Header>
          <SSN>1234567890</SSN>
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
          <event>
               <elem1>data 1</elem1>
               <elem2>data 2</elem2>
               <elem3>data 3</elem3>
          </event>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How can I get the data in the SSN-header element at mapping time?
I'm sure this can be done by using adapter modules as the first step adapter, but I prefer doing it at mapping time if possible.
Best Regards,
Daniel

I solved it on my own now. My missing link was the fact that I'm using XMLSPY to send request and thus need to replace all '&' with & in Connection Endpoint.
Message was edited by:
        Daniel Engsig-Karup

Sender SOAP Adapter, inconsistent behavior

Hi,
We are using XI 3.0 SP17. We have noticed some inconsitent behavior with the sender SOAP adapter:
When sending a valid SOAP message to the adapter, it will reply with:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body/></SOAP:Envelope>
To me this seems errornous, becuase it is missing "<?xml version='1.0'?>" in the beginning, and thus is not valid XML. This leads to errors on the Client that is sending messages to the Sender SOAP adapter.
When sending an errornous SOAP message from the client to the XI Sender SOAP adapter, the error message does include the "<?xml version='1.0'?>" + the corresponding error message, so the behavior seems inconsitent and errournous.
Can someone tell me how the get the Sender SOAP Adapter to include "<?xml version='1.0'?>" in the reply for valid SOAP messages?
Thanks for any help on this subject!
-Hans
PS: Here is an example of an error message from the Sender SOAP adapter, that does include the xml header:
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Body>
          <SOAP:Fault>
               <faultcode>SOAP:Server</faultcode>
               <faultstring>Server Error</faultstring>
               <detail>
                    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                         <context>XIAdapter</context>
                         <code>MalformedMessageException</code>
                         <text><![CDATA[Unexpected content in SOAP:Body; nested exception caused by: com.sap.aii.messaging.util.XMLScanException: Unexpected content in SOAP:Body\tat com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1014)\tat com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:619)\tat com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:611)\tat com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:379)\tat com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)\tat com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:378)\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)\tat com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)\tat com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)\tat com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)\tat com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)\tat com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)\tat java.security.AccessController.doPrivileged(AccessController.java:180)\tat com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)\tat com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>

Hi,
"Do not use SOAP Envelope" is not really an option for us.
From help.sap.com:
If the indicator is set, the adapter expects a message without a SOAP envelope.
If you have set the indicator, you must also enter nosoap=true in the URL.
The adapter then puts the whole message in the XI payloads
So this also requires heavy changes to the client side. It would almost make more sense to use the plain HTTP adapter in that case..
-Hans

Certificate based authentication with sender SOAP adapter. Please help!

Hi Experts,
I have a scenario where first a .Net application makes a webservice call to XI via SOAP Adapter. Then the input from the .Net application is sent to the R/3 system via RFC adapter.
.Net --->SOAP -
>XI -
>RFC -
R/3 System
Now as per client requirement I have to implement certificate based authentication in the sender side for the webservice call. In this case the .Net application is the "client" and XI is the "server". In other words the client has to be authenticated by XI server. In order to accomplish this I have setup the security level in the SOAP sender channel as "HTTPS with client authentication". Additionally I have assigned a .Net userid in the sender agreement under "Assigned users" tab.
I have also installed the SSL certificate in the client side. Then generated the public key and loaded it into the XI server's keystore.
When I test the webservice via SOAPUI tool I am always getting the "401 Unauthorized" error. However if I give the userid/password for XI login in the properties option in the SOAPUI tool then it works fine. But my understanding is that in certificate based authentication, the authentication should happen based on the certificate and hence there is no need for the user to enter userid/password. Is my understanding correct? How to exactly test certificate based authentication?
Am I missing any steps for certificate based authentication?
Please help
Thanks
Gopal
Edited by: gopalkrishna baliga on Feb 5, 2008 10:51 AM

Hi!
Although soapUI is a very goot SOAP testing tool, you can't test certificate based authentication with it. There is no way (since I know) how to import certificat into soapUI.
So, try to find other tool, which can use certificates or tey it directly with the sender system.
Peter

SOAP Adapter XI 3.0 - HTTP 200 response fails

We have a scenario where a request message is sent successfully to a URL by the SOAP Adapter.
However, the response message has an HTTP response of 200 (meaning ok) which is not handled correctly by the
SOAP Adapter.
The error text shown in SXMB_MONI is:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint HTTP 200 OK
Is there something I am missing in the configuration to allow HTTP responses in the SOAP Adapter ? It is very odd that the SOAP Request works fine, but the SOAP Response does not.
Any ideas anyone ?
Kind regards
Colin.

Hi Bill
1. synchronous out / in
2. yes
3. working fine
following the way out to the elocateserver system is working fine.
The soap is working and the responce from the elocteserver is fine . But when the message is pick put the Timeout show up.
below is the Responce from elocateserver to xi
Hope this will help you
thanks olaf
Help
!http://sapnt09:50200/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://sapnt09:50200/sap/public/icman/img/theme.jpg!
500 Connection timed out
Connection timed out (-5)
Error:
-5
Version:
6040
Component:
ICM
Date/Time:
Sat Oct 16 06:13:25 2004
Module:
icxxthr.c
Line:
2556
Server:
sapnt09_M64_02
Detail:
Connection to partner timed out
© 2001-2003, SAP AG

SOAP Adapter in XI 3.0 SP11

Hi,
I do not see the SOAP adapter option in the integration directory for the WS communication channel. I also checked in the J2EE engine with visual admin and I do not see the SOAP adapter, but I have all other adapters.
Do I need to download seperately ? I understand that SOAP adapter is part of standard installation. I would like to know the procedure to install SOAP adapter.
Thanks for help,
Sunil

Shravan,
I do not see the SOAP adapter in the SAP BASIS -> SAP BASIS 6.40 -> http://sap.com/xi/XI/System -> Adapter Objects -> Adapter Metadata path.
reimporing solved the problem
Thanks again,
Sunil
Message was edited by: Sunil Guditi

SOAP Adapter Metadata Missing

Similar Messages

Maybe you are looking for