on 07-07-2008 6:45 AM
Hi Experts,
We are trying to make a decision to go with a proxy..java or abap Server proxy...File to proxy..standard Scenario
Can someone help me by telling us what are all the objects we need for abap proxy..
Data type --Yes : No
Msg type -Yes :No
Msg Intfc
Interface Mappings
Message Mappings
Then go to R/3 system and run sproxy and select the msg interface created above..if i am right..
Business System/Service
Communication Channel :- FileSender Communication Channel
Reciever Determiation
Interface Determination
Reciever Agreeement
Sender Agreement: This i dont think is needed...
Also how is the msg flow..for a file To Proxy Scenario...
Nalini
Edited by: nalini bhaktha on Jul 7, 2008 7:48 AM
hi nalini
check the below blogs for the objecs to be created and generated in case of abap proxy
ABAP-PROXIES ABAP-PROXY
how toactivate proxy
Monitoring for Processed XML messages in ABAP Proxy
Communication between SAP System & Webservice Using Proxies
XI/PI: ABAP Proxies - keep them clean
Prepare your ABAP Proxies in WebAS 6.20 for migration
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5129 [original link is broken] [original link is broken] [original link is broken]
XI: Debug your inbound ABAP Proxy implementation
File to R/3 via ABAP Proxy
XI/PI: Data type enhancements (standard Business Partner)
XI: RFC or ABAP Proxy ? ....ABAP Proxies with attachments
ABAP Server Proxies
How to raise alerts from ABAP Proxy
ABAP Proxy inbound program - sales order creation
regards
kummir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
Client Proxy - When Java or R/3 is calling XI.
R/3 or Java -
> XI----
> Any Application
Server Proxy - When XI is calling Java or R/3
Any Application--
> R/3 or Java.
ABAP CLIENT PROXY
ABAP SERVER PROXY
Consider Client Proxy:
Here source system sends the message to XI in XML format.
Understand here that XI is not connecting to source system to pick up the message. There by connection is not required to maintain, and the message is coming in XML format. So conversion is not required. Hence you do not require any adapter.
Consider Server Proxy:
Here you need to send the message to the target system in XML format. Understand that XI needs to connect to the target system without which posting of the message is not possible.
So for connection purpose we require Adapter and we do not require it for conversion of formats. Hence XI adapter sends XML message without any conversion of formats, but uses the target system details to post the message.
If u generate proxy for outbound interface then its client proxy and for inbound interface its server proxy.
In client proxy u can call the method to send messages but u can't modify it but in server proxy its possible to write a user code within the method to execute proxy.
CLIENT PROXY:
A WSDL description from a UDDI server (or an Internet page) is usually used to make a service executable in the Internet and to describe the interface of this service. You require a client proxy and not a server proxy to call this service by using the Web service infrastructure.
SERVER PROXY:
You can only generate ABAP server proxies from a WSDL description if they originate in the Integration Repository.You can also generate server proxies for Java and client proxies for ABAP from message interfaces.
The chief distinction betwen the two is :
Client proxy: Calls a webservice on the internet
Server Proxy : Provides an inbound interface as a webservice.
cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nalini,
Data type --Yes
Msg type -Yes
Msg Intfc: U have to define out bound and in bound interfaces
Message Mappings: Yes
Interface Mappings: Yes.
Then go to R/3 system and run sproxy and select the msg interface created above:Absolutely right & enter package name & prefix all proxy objects will be stored
under this & activate ur proxy objects.
ID:
Business System/Service:Assisgn ur Business System/Services to ur scenario.
Communication Channel :- FileSender Communication Channel(YES)
Receiver communication channel (Adapter type XI).
Reciever Determiation:YES
Interface Determination:YES
Reciever Agreeement:YES
Sender Agreement: YES
msg flow..for a file To Proxy Scenario...
U can can use trans:SXMB_MONI_BPE
Reward if found useful
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
when ur sender is either ABAP or Java proxy,its called as clinet proxy and when ur receiver is either ABAP or java proxy,its called as server proxy.
one basic condition to use ABAP proxies are that ur WAS>=6.4,proxies are adapterless communications and a lot of times are considered to give better performance that adapters
regards
kummari
HI,
for File to Proxy scenario you do require a sender agreement (For FILE comm channel)
for Proxy to File scenario you do not require a sender agreement.
All object specified by you would be required as per your requiremnets.
In case of File to proxy scenario, flow of message would be from File channel to Xi and from XI to SAP proxy via XI adapter.
Edited by: Sumesh k on Jul 7, 2008 8:27 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
ABAP Proxies:
ON SDN TV
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=abap%20proxy%20xi&cat=sdn_all&start=11#
cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.