XI - webMethods Adapter

Looking for pros and cons on XI <> webMethods integration using wM's XI Adapter. This Adapter, per webMethods product info, can be directly installed in XI's Adapter Framework and can process XI messages between XI and webMethods integration server (or new Applinx).
Any of you have experience using webMethods's Adapter for XI? Would you recommend it versus using SOAP / HTTP approach for XI to webMethods integration?
Thanks in advance, Rajan

Rajan,
It all depends upon various factors like if the client now has business connector and if they want to upgrade then if they use SAP XI or PI then they have to redo all the work once again (in some cases you can upgrade).
But with webmethods they say they can reuse. If the client already has xi or pi then my suggestion would be to go with XI only.
Also please check this documents where they have given the differences:
http://www.webmethods.cn/wm1/PDF/webMethods_for_SAP-wp.pdf
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10748ef7-b2f0-2910-7cb8-c81e7f284af5
Regards,
---Satish

Similar Messages

JCo error when calling from webmethods sap adapter to SAP BAPI

Hi,
I am getting an error "[SAP.102.9000] JCo error: (104) RFC_ERROR_SYSTEM_FAILURE - connection closed without message (CM_NO_DATA_RECEIVED)" when webmethods sap adapter is calling BAPI in SAP. The BAPI is working fine in SAP.
Can anyone suggest me a possible solution.
Thanks,
Sarath.

BAPI-step by step procedure
http://www.sapgenie.com/abap/bapi/example.htm
list of all BAPI's
http://www.planetsap.com/LIST_ALL_BAPIs.htm

Webmethods to SAP PI

Hi All,
we have a requirement to replace/migrate the existing interfaces in web methods to SAP PI. Could you please provide me with details of how do we go about doing this implementation and what are the measure that we need to consider when we go in for this migration.
Is there a possibility of using the existing details in webmethods as such in PI, or should we completely create new interfaces in PI understanding the existing interface logic.
Also I have seen few blogs showing we need to use the webMethods XI Adapter, do we need to apply some patches when we are using it in PI 7.1
Please provide your inputs.
Regards,
Nithiyanandam

refer my blog,let us know still you need any info.
/people/rajasekhar.reddy14/blog/2010/06/16/points-to-remember-while-working-on-migration-projects-web-methods-sap-bc-to-sap-xipi
Regards,
Raj

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Error while using webmethod JMS provider with JNDI

Hi,
I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc.
While activated the adapter short log shows: Adapter has not provided any status information about this channel"
In the detailed log following error message is displayed: "Obtained connection factory: null#"
#1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
#1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
#1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
#1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
#1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
#1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

Hi,
Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
Regards,
Srini

Following message failing in sender soap adapter

Hi all,
The message below fails when it is sent to our adapter with a 500 error from a webmethods server. however if I pull the soap message out of the mime, and use our client test tool, it posts fine.
What is wrong with the message below?
Message-ID:<28413146.1155935375732.JavaMail.webmethods@exshaw>
MIME-Version: 1.0
Content-Type: multipart/related; type="text/xml"; boundary=X-K12456234-X
X-K12456234---X
content-type: text/xml;charset=UTF-8
content-transfer-encoding: 7bit
Content-ID: <SES>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"></SOAP-ENV:Header>
<SOAP-ENV:Body>
<nr1:ServiceAcknowledgementRequest xmlns:nr1="http://sap.com/xi/SAPGlobal/Global">
 <MessageHeader>
 <ID schemeID="0240">74000003400000000020060329170547</ID>
 <CreationDateTime>2006-03-29T17:05:47Z</CreationDateTime>
 <SenderParty>
 <InternalID schemeID="PartnerID" schemeAgencyID="SSR_100">6000000011</InternalID>
 </SenderParty>
 <RecipientParty>
 <InternalID schemeID="PartnerID" schemeAgencyID="SSR_100">0000000236</InternalID>
 </RecipientParty>
 </MessageHeader>
 <ServiceAcknowledgement>
 <ID schemeAgencyID="SSR_100" schemeAgencySchemeAgencyID="ZZZ">7400000340</ID>
 <BuyerID>7400000340</BuyerID>
 <CreationDateTime>2006-03-29T17:03:55Z</CreationDateTime>
 <Note>Service Entry Sheet#1</Note>
 <Item>
 <ID>10</ID>
 <Quantity unitCode="EA">5.0</Quantity>
 <Product>
 <TypeCode>1</TypeCode>
 <Note>Test Service</Note>
 </Product>
 <Price>
 <NetUnitPrice>
 <Amount currencyCode="USD">1.0</Amount>
 <BaseQuantity unitCode="EA">1.0</BaseQuantity>
 </NetUnitPrice>
 </Price>
 <PurchaseOrderReference>
 <ID>2000000742</ID>
 <ItemID>1</ItemID>
 </PurchaseOrderReference>
 </Item>
 </ServiceAcknowledgement>
</nr1:ServiceAcknowledgementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
X-K12456234---X

Hi Richard,
I think, it is because of the Autorization Problem..i.e
Webservice is not able to execute by SOAP adapter.. So Security Roles etc..
Check this SAP SOAP Note for FAQ-856597 (Question No 1)
A similar symptom is mentioned in this note....
Regards,
Abhy

Read uniquely named file. Sender File Adapter unsuitable for synchronous

Hi All,
We have a requirement to read a specific file that has a unique name based on a transaction ID. The transaction ID will be passed from the source application.
The communication is required to be synchronous. There could be multiple requests/files generated and present at the directory at any given time but each corresponding to a specific transaction ID. If the file is not yet generated for that transaction ID we return back an error to the calling system.
I think we can not use Sender File Adapter - because of the dynamic naming and also because we have to return a synchronous response back depending on the file availability. i.e. We can not have a defined pattern in the file name nor can we specify a wild card as there could be more than one files in the location.
In theory we could use the File Sender adapter to read all the files in the directory and a BPM with correlation set based on the transaction ID and let the process wait for the request. But as far as possible I want to avoid this unnecessary wait or extra demand on the system. More so because the files could get big.
If I were using a tool like SAP Business Connector or webMethods then I would I used a readFile Java service and given it a filename to return the required bytes in a synchronous read.
Is something like this possible in XI? If someone has written a synchronous Java to read file can they share the code? Or do you suggest I write a ABAP server proxy to read the file? The problem however will be how do we map the data to a XML within the code.
All suggestions welcome. There has to be a simple and effective solution to this mundane requirement !
Wishing all SDNers a bright start to this new year,
Thanks,
Charu
Message was edited by:
Charu Kulkarni
"The transaction ID will be passed from the source application so we know what file to pick"

Hi,
You could make the scenario a little simple and avoid custom development if the logic can be put into scripts(out of XI).
Say all the files are coming into a directory called D1.
Here, you could use a script to arrange all these in an order (say ascending) and move the first file into another directory D2.
The sender file adapter would poll this directory D2. The adapter can have a wild card character for the filename field now.
Once the file is in XI, you could check this against the transactionId present(I am not sure how you get this though!), and determine whether to send a mail, or to send a file back.
Here, I have assumed that there is somekind of order present in the files placed in the directory D1.
Again, this is just a suggestion.. I might be wrong with all the assumptions.
Regards,
Smitha.

Replace E1- Adapter with Business Services

Hello,
We are using E1-adapter to communicate with web Methods ( like calling business function, table IO etc..), now we are planning to replace E1- adapter with Business Services. We are using tools 8.98.11 and Application Release E812.
Question is , is it possbile to create a wraper to call any business functions just like E1-adapter? Any help is greatly appriciated.
Thank you.
Edited by: user3448054 on Oct 12, 2009 1:09 PM

Yes, you can use the JDE Business Service Server to simulate the E1-Adapter associated with webMethods. Oracle provides out of the box Business Services for a majority of the E1 transactions. We have implemented Business Services Server with our webMethods and it is working very well.
-Eric

FILE adapter with secure FTP

Hi experts,
i have scenario file to file scenario, communication should happen in secure connection .i searched in blogs & forums
please find berlow forum
How to configure SFTP Adapter in XI?
in that 2 nd reply
there is one option :2. Use the FTP adapter, and encrypt/decrypt the file contents through a user exit in the adapter. Something on the FTP server side will have to do the same.
can anyone please elaborate this one & where can i find user exit for the file adapter.
please help is there any option to provide secure cinnection in file adapter (FTP) like using run operating system command befor or after message processing
Thanks In advance

I think that you can solve in 4 different ways:
-> Using FTPS connection
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
-> Using a 3rd Party Adapter (Seeburger or Aedaptive) for PGP or deploying a custom adapter for PGP
http://www.seeburger.com/9468/
-> PGP OS Level (Installing a PGP software like GnuPGP in your system) Install the PGP software in XI and write the OS command for encryption and decryption at OS level. Call this command in File adapter after or before message processing
PGP ncryption
-> Using an UDF
Check this links:
Is there any FTP API available from SAP?
Send Text file to FTP in binary mode with PGP encryption
http://www.webmethods.com/meta/default/folder/0000007429
Converting IDOC to XML
XI implementation
http://www1.webmethods.com/PDF/webMethods_for_SAP-wp.pdf

Is SOAP Adapter Action field can contain 2 or more "SOAP Actions"

Hi All,
I have following scenario:-
Step 1. Webmethod(sent price querry with material no)->R/3(search price from tables)
step 2. R/3(sent price)->Webmethod
step 3. Webmethod(sent quantity)->R/3(document created in sap)
step 4. R/3(sent confirmation doc no/error)->Webmethod
Q1 How can i implement above scenario in with one URL Webmethod????
(URL:http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel)
Q2 Is it possible with one (Receiver SOAP adapter->Conversion Parameters->SOAP Action) field can contain more than 1 SOAP Action......??????
With more than one message interfaces (inbound synchronous) in one scenario
Q3 Or I have to design two scenarios with two URL's????with different message interfaces (inbound synchronous) 
Q4 Or I use Sender(SOAP) Reciver(Rfc Adapter) in abave case??? With more than one message interfaces (inbound synchronous) in one scenario
Thanks & Regards
Message was edited by: Umesh R

When your scenario consists of sync calls, you have only to define SOAP sender channels. The best approach is to create two channels to keep the reference from interface to channel unique.
For the sync response message you do not need and communication channel (and no SOAP action).
Regards
Stefan

Receiver SOAP adapter in XI 2.0

We are using receiver SOAP adapter in XI 2.0 and 4.6C R/3 system. Recently we started having this problem when vendor upgraded their webmethod server to post invoices to our XI 2.0. When vendor post 10 invoices to XI and all are posted good in XI but some of invoices give the bad response to the vendor's server as below and vendor's server keep posting the invoices with the bad response until they get good response.
<value name="soapResponseData"><SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: response is not an HTTP response</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope></value>
Any help on this is appreciated...
Thanks in advance!
Mrudula

hi,
Check these threads, might be helpful.
Soap Adapter
XI3.0: SOAP-Adapter Exception
Thanks,
Tirumal

XI 2.0 Standalone J2SE SOAP Adapter as client - SOAP:encodingStyle

Hi,
We're setting up the J2SE SOAP Adapter of XI 2.0 to talk to a synchronous web service provided by a webmethods platform.
When we generate the Request message using the WSDL and post it directly via the HTTP test tool the message is understood and a response message is returned.
Here is the Request:
<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:Body>
 <m:callFP091 xmlns:m="http://destserver/FP091.flows" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <iw1_RECTPE xsi:type="xsd:string">String</iw1_RECTPE>
 <iw1_DLRCODE xsi:type="xsd:string">String</iw1_DLRCODE>
 <iw1_FRNCODE xsi:type="xsd:string">String</iw1_FRNCODE>
 <iw1_JOBNUM xsi:type="xsd:string">String</iw1_JOBNUM>
 <iw1_CHASIS xsi:type="xsd:string">String</iw1_CHASIS>
 <iw1_COLOUR xsi:type="xsd:string">String</iw1_COLOUR>
 <iw1_DESCRIP xsi:type="xsd:string">String</iw1_DESCRIP>
 <iw1_INVNUM xsi:type="xsd:string">String</iw1_INVNUM>
 <iw1_CAPAMT xsi:type="xsd:string">String</iw1_CAPAMT>
 <iw1_INTFRE xsi:type="xsd:string">String</iw1_INTFRE>
 <iw1_LOC_IND xsi:type="xsd:string">String</iw1_LOC_IND>
 <iw1_REGISTRATION xsi:type="xsd:string">String</iw1_REGISTRATION>
 <iw1_ENGINE_NUM xsi:type="xsd:string">String</iw1_ENGINE_NUM>
 <iw1_VIN_NUM xsi:type="xsd:string">String</iw1_VIN_NUM>
 </m:callFP091>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When we try to use the SOAP Adapter and pass it the following message from XI:
<m:callFP091 xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:m="http://destserver/FP091.flows"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
 <iw1_RECTPE xsi:type="xsd:string">E1</iw1_RECTPE>
 <iw1_DLRCODE xsi:type="xsd:string">3009838</iw1_DLRCODE>
 <iw1_FRNCODE xsi:type="xsd:string">333</iw1_FRNCODE>
 <iw1_JOBNUM xsi:type="xsd:string">123</iw1_JOBNUM>
 <iw1_CHASIS xsi:type="xsd:string">2</iw1_CHASIS>
 <iw1_COLOUR xsi:type="xsd:string">3</iw1_COLOUR>
 <iw1_DESCRIP xsi:type="xsd:string">4</iw1_DESCRIP>
 <iw1_INVNUM xsi:type="xsd:string">5</iw1_INVNUM>
 <iw1_CAPAMT xsi:type="xsd:string">6</iw1_CAPAMT>
 <iw1_INTFRE xsi:type="xsd:string">7</iw1_INTFRE>
 <iw1_LOC_IND xsi:type="xsd:string">8</iw1_LOC_IND>
 <iw1_REGISTRATION xsi:type="xsd:string">9</iw1_REGISTRATION>
 <iw1_ENGINE_NUM xsi:type="xsd:string">1</iw1_ENGINE_NUM>
 <iw1_VIN_NUM xsi:type="xsd:string">2</iw1_VIN_NUM>
</m:callFP091>
The SOAP adapter wraps the envelope and body around this message, provides an empty header but changes the SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" attribute to SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'.
The generated SOAP message is:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
<m:callFP091 xmlns:m='http://196.11.134.83/FP091.flows'
SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
 <iw1_RECTPE xsi:type='xsd:string'>E1</iw1_RECTPE>
 <iw1_DLRCODE xsi:type='xsd:string'>3009838</iw1_DLRCODE>
 <iw1_FRNCODE xsi:type='xsd:string'>333</iw1_FRNCODE>
 <iw1_JOBNUM xsi:type='xsd:string'>123</iw1_JOBNUM>
 <iw1_CHASIS xsi:type='xsd:string'>2</iw1_CHASIS>
 <iw1_COLOUR xsi:type='xsd:string'>3</iw1_COLOUR>
 <iw1_DESCRIP xsi:type='xsd:string'>4</iw1_DESCRIP>
 <iw1_INVNUM xsi:type='xsd:string'>5</iw1_INVNUM>
 <iw1_CAPAMT xsi:type='xsd:string'>6</iw1_CAPAMT>
 <iw1_INTFRE xsi:type='xsd:string'>7</iw1_INTFRE>
 <iw1_LOC_IND xsi:type='xsd:string'>8</iw1_LOC_IND>
 <iw1_REGISTRATION xsi:type='xsd:string'>9</iw1_REGISTRATION>
 <iw1_ENGINE_NUM xsi:type='xsd:string'>1</iw1_ENGINE_NUM>
 <iw1_VIN_NUM xsi:type='xsd:string'>2</iw1_VIN_NUM>
</m:callFP091>
</SOAP:Body>
</SOAP:Envelope>
This message has no SOAP:encodingStyle attribute and is therefore not understood by the WebMethods web service. Here is the error message from the web service:
[B2BCORE.0076.9201] SOAP Message Coder cannot decode message; no encoding style is specified
How do I configure the outbound SOAP adapter within the XI 2.0 J2SE adapter engine to add the SOAP:encodingStyle attribute to the outbound message?
I have tried playing around with the XMBWS.* parameters outlined in the adapter engine documentation but these don't seem to have any influence on the way the SOAP request message is formed.
Any suggestions would be appreciated.
Regards,
-Derek

Hi,
You could use the webMethods XI adapter to create the connection.
Best Regards,
Sander

Details on XI EDI adapter from seeburger

Hi,
We currently have our B2B integration going through Gentran & Webmethods.
We are having a evaluation process on the different tools available.
Can anyone give information on the licensing details of the XI EDI adapter from seeburger? Also do they have evaluation period? Has anyone gone through this process?
We have written to seeburger on this, but i thought of posting on SDN as the responses would be faster
Thanks & Regards,
Renjith

Hi Renjith,
There is no downloadable trial version available.
You need to contact your local or regional Seeburger sales office.
Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards,
Abhy
Message was edited by: Abhy Thomas

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

Error on WebMetods while calling IDOC Adapter

Folks ,
I am facing a problem calling IDOC adapter from WebMethod, I have all the configuration in ID and IDX1 .
This is the error:
com.sap.mw.jco.JCO$Exception: No Service for system QUANTUM1, client 902 in Integration Directory
Regards,
Manish

Hi,
did you create it exactly as specified:
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
for QUANTUM1 and 902?
I'm not sure what the ID of the system if the system
is not the SAP...
maybe you can just post the idoc via http adapter?
REgards,
michal

XI - webMethods Adapter

Similar Messages

Maybe you are looking for