Proxy Vs Adapter usage in an Async Communication

Hello All,
Just want to get a better clarification on the proxy usage.
The communication is Asynchronous and there is a standard IDOC existing or an IDoc generated from BAPI.
is it advisiable to use Idoc adapter in this case.
OR
I take the proxy approach.
Regards,
Sita K

Hi Sita,
SAP always recommends usage of ABAP proxies since WAS 6.4 and above due to the presence of local integration engine which enhances the performance. and hence usage of RFC has diminished over the years.
But in your case you already have a standard Idoc for processing. In this case you need to identify two things:
i) Is the incoming payload huge? - In my personal experience if the interface is for Data migration stuffs for some legacy systems, best is to use proxy since in one single Idoc more than 100 records will result in some issues (i dnt remember the exact error but there will be error). For this you need to trigger an Idoc for each 100 or more data. And during Data Migration there will be huge records.
ii) Whether the processing logic would not be easy to implement.
If you can call the standard BAPI or FM from the server proxy and the data is huge go for proxy else go for IDoc.
Hope this clarifies.
Souvik
Rewards point if helpul.

Similar Messages

Sync/Async communication in JMS adapter without BPM

Hi,
as of SP19 XI's JMS adapter offers this new feature for Sync/Async communication through JMS Adapter modules instead of using a BPE.
Now I would be interested to know if anybody has already successfully used this feature especially using WebSphere MQ as a JMS Provider (preferredly in the mode JMS Compliant: WebSphere MQ (non-JMS)).
I experienced some issues with the XI Message ID being used as the JMS Correlation ID which is then mapped to the MQ Correlation ID being truncated after 24 characters. So I don't exactly know whether this is due to wrong setup or some general issues with this messaging system.
Please let me know if you have any experiences at all with this new feature (please do not just post links to the following blogs, which I have thoroughly studied as well as the How-to Guide concerning this topic)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
thanks & regards,
Peter

Hi Peter,
we working on the same Problem. Using IBM Websphere MQ as JMS Provider for the new feature: sync/async bridge without BPE.
we switched on a high level trace for the adapter framework and saw a problem in the receiving Object of the JMS correlation id. The notify bean receives the JMS correlationid in hex format. so the beans have two different correlations, which could not find together.
did you have any solution to get this new feature works with IBM Websphere ?
thanks
joachim

Sync/Async communication in JMS

HI all,
i configured scenario as mentioned in the blog
"Sync/Async communication in JMS adapter without BPM (SP19)
Venkataramanan Parameswaran".
now i am working on PI 7.0
but i am getting the error as fallows.....
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of
RequestOnewayBean.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can anybody tell me why it is?
Thanks,
Kumar

Please refer these links
Sync/Async scenarios without BPM
Async/Sync Communication using JMS adapter without BPM (SP 19)
http://help.sap.com/saphelp_nw70/helpdata/en/45/20d1dec20a0732e10000000a155369/frameset.htm

Regarding proxy and adapter

In the doc, it is said that for SAP WAS > 6.20, we can develop interface and use proxy. So why we still use SOAP adapter when connecting to web service, Is it a must?
Any comments will be greatly appreciated.

hi
Proxies are interfaces which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions.
You can use proxies for systems with WAS >=6.20
XI will communicate in native language with SAP systems via proxies. Proxies uses XML - SOAP based communication for both ABAP and Java Proxies
Proxy generation generates classes and structures for the interfaces and data types written in WSDL. The range of commands in the Integration Builder is restricted to a suitable WSDL subset for system integration."
The WSDL are generated for the Message Interface created, so Proxies use the SOAP protocol, Proxy is not a substitute for SOAP but if you want to perform some operations in R/3 then it is helpful to use ABAP proxy.
ABAP proxy generation gets the WSDL description for message interfaces from the Integration Repository (WSDL Web Service Description Language) by using http. In WSDL, data that is transferred using messages is described using XSD (XML Schema Definition Language).
The Integration Builder does not support the full range of WSDL (for message interfaces) and XSD (for data types) commands; this is not the case for WSDL in the Web service infrastructure, however.
Proxies are used only when sender/receiver and SAP XI understand XI message format. The one most important difference between a proxy and adapter is that the adapter converts the sender/receiver format to the XI message format but where as proxy does not need to do that as they natively understand the XI message format.
For a webservice you should use eitehr a SOAP adapter or HTTP adapter. If your interfaces are going to connect SAP then I would rather suggest to use proxies. If they are externally located and if they are third party interfaces then we can go for webservices
for SAOP adapter Plz chk this link
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
If U hv any further queries then reply..
Thanks
Manas

Sync-Async communication

Hi!
Is it possible to have a sync-async communication like this:
receive - open s/a bridge
send (async idoc with acknowledgement in return)
send - close s/a bridge?
or do I have to use a receive step after the send step in the middle?
I am trying to get a confirmation of Idoc posted to application and send this back to calling application, but I get a timeout error after the send (async idoc with acknowledgement) step...
Thanks!
regards Marianne

Hi
Thanks for you answer. I trust you here, but I have seen someone using this approach here on sdn.
Is it not possible to have the send step wait for acknowledgement and if ack is received then send a message back to the synchronous process. And also have a timeout exception that sends back a fault if acknowledgement is not received?
I know that some have been able to return to sync process wether the Idoc was posted correct or not...
regards Marianne

JDBC adapter type not visible in Communication Channel

Hi All,
I have deployed JDBC driver according to http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b4a020-4ae6-2c10-5a95-fed4ad9a4b60?QuickLink=index&… .
Driver deployed successfully and I have checked it in folder \usr\sap\xxx\DVEBMGS30\j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib and it's found ok. But this adapter type not showing in Communication Channel only RFC and SOAP are showing there. I have restarted the server also. Can any one tell me where the problem is?

Hi Kuldeep,
Have you check the patch level of both java & abap has same ,if some thing different in Patch level of any of this it will not visible in communication channel
Check below links also
https://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
Sender JDBC adapter : data read from db but not in PI
Regards
K.N

JMS adapter Usage

Hi,
JMS Adapter usage: BPEL process1 sends message to a JMS Queue.
Bpel process2 subscribes to the same queue. For some reason Bpel process2 fails.
What happens to the message?
Thanks
Nirmal

If the consumer BPEL is asynchrnous, then the BPEL cannot be a part of the global transaction (with JMS Adapter).
If the consume BPEL is synchronous, then the BPEL can be a part of the global transaction (with JMS Adapter).
In the second case, if the BPEL transaction fails, then the jca.retry will happen i.e., the message is given to the BPEL instance again for jca.retry number of times, if it fails all the times, we can set paramaters such that the message is redirected to another queue...
go to the Delivery Failure tab of the JMS queue/topic, and give the values for the following properties...
Redelivery Limit : 3
Expiration Policy : Redirect
And also give the queue name where you want to redirect the message...
Transaction in Oracle SOA 11g - BPEL
Hope this helps
N

Monitoring inbound processing and Sync/ Async communication on PI7.11

Hi All,
I am new to PI. We have following two requirements to be done on PI 7.11
1)     Monitoring inbound processing (Txn Code SWF_INB_MON)
2)     Monitoring Sync/ Async communication (Txn Code SXMS_SAMON)
Kindly let me know how should I proceed or what document should I follow or any scenario is to be configured.

Hi,
    1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
           Note that you require administrator authorization for transaction SWF_INB_ADM
    2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail."
     3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing. For monitoring individual messages click on "Display Message Packages".
regards,
ganesh.

XI 3.0 PROXY/ File adapter problem

We have XI 3.0. We used the proxy to send a file from R3 to XI and used file adapter in XI to put the file back to R3 file server.
From the SXMB_MONI in R3, the message was successfully sent from R3 to XI.
From the SXMB_MONI in XI, the URL address https://aaaa###.com:52201/MessagingSystem/receive/AFW/XI (the SAI_AE_DETAILS_GET returned) had the SSL service number(port number 52201) that I do not know where it was defined. I checked the communication channel and SM59 but found out nothing about 52201, neither the SSL part.
Would some one please tell me where the SSL security was defined?
Thanks for your help in advance!

Satish,
I checked the communication channel in the Configuration and the the transport protocol was "File System(NFS). We did not use FTP.
Thanks!
Fisher

Proxy RFC-Adapter XI = BI

Hi everybody,
I have to build an interface from XI to BI.
I have to choose beetween proxy mode or the RFC adapter.
I have already looked the differents "how to" and they said to use the proxy because it manages the delta (EOIO).
But if i don't care of the mode delta, someone can tell me the best for each case ?
If you can tell me the differents steps to implement the RFC mode it will be nice
Thank you by advance
Regards
Flavien

Hi Flavient,
There are plenty of blogs available for both RFC and Proxy scenarios. Just for the in the forum. I would go with Proxy as it would be adapter less communication with R3 and XI.
VJ

AS2 adapter not visible in Receiver Communication Channel (Adapter Type)

Hi,
We wish to connect to our customer using AS2 adapter as the receiver communication channel.
We are unable to find the "AS2 adapter type in the in "adapter type" field. (Choose Adapter Metadata).
Our XI version is as following (NW04S_11_REL Service Pack 11).
Version
Service pack:
11
Release:
NW04S_11_REL
Is there add-on to be installed on XI or is there any activation required?
Thanks in Advance,
Rehan

SAP_BASIS
Release 700
Level 0011
Highest Support Package: SAPKB70011

Problem receiving acknowledgement: abap proxy == file adapter

Hi experts,
I am developing an asynchrone interface using PI 7.0. The scenario is: SAP ==> FILE.
In SAP I have created an abap proxy in wich I requested an acknowledgement when calling from the abap code. In PI I have created an Integration Process with a receive step, and a send step. In de send step I am asking for a transport acknowledgement.
When I test the interface and I look in the SXMB_MONI in PI, I see the acknowledgement given back to the IP, but in the SAP backend system I don't receive anything in the abap proxy which had send the original message. In de SXMB_MONI from SAP I see a "?" Still awaiting acknowledgement.
Can anyone help me with this scenario? I really need an acknowledgement from the file adapter in the calling abap proxy.
Regards, Jeroen

You need to crate a REceiver Agreement for this sender...
The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.
If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
-SM

Sync/Async communication with JMS Receiver

Hi all,
I am working on one Sync/Async model without BPM. Sender is RFC which is expecting some response, but we know receiver jms doesnt support response message directly. For this i used modules provided by SAP.
While developing interface i used below objects.
One Outbound Synchronous interface--> for Sender RFC channel
Inbound Synchronous Interface----->for Receiver JMS Channel
outbound asynchronous interface--->for Sender JMS channel
one request mapping and one response mapping
Operational mapping between outbound Synchronous to inbound synchronous.
ID Objects:
2 sender agreements: one with sender jms channel
one with sender rfc channel
1 receiver agreement: with jms receiver channel
1 receiver determination
1 interface determination
In receiver jms and sender jms channels i used modules as specified in the document http://help.sap.com/saphelp_nw04/helpdata/EN/45/20d2b4c20a0732e10000000a155369/content.htm
But my interface is not working end to end successfully.
Please confirm below points
1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
2)In receiver jms channel is it ok if i will put response queue(Q2) name in the field JMS ReplyTo Queue Name or do i need to put in the form queue://<ReplyToQMgr>/<ReplyToQ>
3). what is the format of data type for asynchronous outbound interface which i used for sender agreement of jms sender channel.
4). Do i need to do any other special settings at MQ settings in MQ server.
Note: i am using PI7.1 and i selected the option JMS-compliant for target client in jms channels.
Thanks,
Madhu
Edited by: Madhusudana Reddy on Nov 4, 2009 9:38 AM

1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
The following information is available in SAP note-
Message correlation implies correlating a response message with a request message. With respect to the JMS adapter, this means that you sent have sent a message through a JMS receiver channel to some JMS queue (say queueA) , some external application processes this message and puts the response onto another JMS queue(say queueB) which is then picked up by a JMS sender channel. You need to relate this response message with the original request message.
In the simple case, for all JMS compliant providers this can be done in a straightforward manner:
a) In the JMS receiver channel configuration, set the JMSCorrelationID to the XIMessageID. (or some other XI header which is applicable)
b) Ensure that your external application does not change the value of the JMSCorrelation
c) In the JMS sender channel configuration, set the XIConversationID to the JMSCorrelationID
d) The XIConversationID header of the response XI message now contains the XIMessageID of the request XI message.
For some providers such as Websphere MQ in legacy/native mode this is not so straightforward.
Do i need to do any other special settings at MQ settings in MQ server.
If your using Websphere MQ, refer que#4 in sap note :1086303
Edited by: nagarjuna _s on Nov 4, 2009 11:02 AM

IDOC adapter is not shown in communication channel

hi gurus,
at present i am using PI and in the communication channel list (adapters types) no idoc adapter is displayed ,can anyone help me to solve this problem.
and also when i create any scenario related to idoc those messages where not displayed in communication channel.

Hi Allen,
U r checking for an IDoc channels in Communication channel monitoring.IDoc adapter is reside in ABAP stack.So that u cant see the Idoc communication channels from monitoring of CC's. If Idoc messages is at sender side no need of CC.
If you want to view the source and target messages of Idoc's u can see those from SXMB_MONI.Choose u r processed message,Dbl click,For Idoc as sender u can view the message from payloads of Inbound message,For Idos as Receiver u can view the message from Payloads of Request message Mapping.
Hope it will helps..
Cheers
Veera
>>>Reward points,if it is needful

"Adapter Engine is missing in Communication Channel".

Hi Experts,
I am Unable to Find out the Adapter Engine As Integration Server in the File Sender Communication Channel.
please let me know
Regards
Khanna

hi,
/people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
note : points pls if it helps you

Proxy Vs Adapter usage in an Async Communication

Similar Messages

Maybe you are looking for