SAP Network Blog: ABAP Server Proxies Pgina 1 de 5

Blogs

ABAP Server Proxies Subscribe

Siva Maranani Print
Business Card
Permalink
Company: Fujitsu America
Posted on Apr. 03, 2005 09:13 AM in SAP Process Integration (PI) Share

As part of Research & Development @ Satyam NetWeaver Labs, I was responsible for integrating Legacy system with SAP System using Inbound ABAP Proxies. ABAP Server(Inbound) Proxies
enable adapterless integration with SAP Applications on WAS6.20 and above.A server Proxy(Inbound proxy) can be used to

To implement a service that can be addressed by the SAP XI Integration Server

To implement a service that can be called as a Web service

This blog describes the steps involved in Inbound/server Proxy Development.

Design Time:
1. Necessary repository objects are developed during the design phase. The inbound Datatype and the corresponding message interface are shown below.

2. Inbound proxy for the corresponding Inbound Message Interface is generated in the SAP System.

3. Inbound ABAP proxy generates the following Objects:

1. ABAP Interface ( ZII_EMPDETAILS_IN_MI)
2. Structure for the message type in ABAP Data Dictionary (ZEMPDETAILS_MT).
3. Structure for the data type in ABAP Data Dictionary (ZEMPDETAILS_DT).

An ABAP class is generated (if it does not already exists for the ABAP Interface that has been generated) which implements the interface ( ZII_EMPDETAILS_IN_MI). Below are the methods and
parameters of the ABAP Class (ZCL_EMPDETAILS_IN_MI).

http://weblogs.sdn.sap.com/pub/wlg/1457 04-Jan-11
SAP Network Blog: ABAP Server Proxies Pgina 2 de 5

Below is the code snippet of ZII_EMPDETAILS_IN_MI~EXECUTE_ASYNCHRONOUS method. ZEMPMASTER is a function module that inserts the data into corresponding tables.

method ZII_EMPDETAILS_IN_MI~EXECUTE_ASYNCHRONOUS.
*** **** INSERT IMPLEMENTATION HERE **** ***

DATA:

lv_ID type ID,

lv_NAME type NAME,
lv_ROLE type ROLE,
lv_LOCATION type LOCATION,
lv_COUNTRY type COUNTRY.

* Convert Input Parameters

lv_ID = input-EMPDETAILS_MT-ID.
lv_NAME = input-EMPDETAILS_MT-NAME.

Note: Do not forget to activate the Objects that have been generated.

Configuration Time:

XI Uses XI Adapter to communicate to SAP System when the SAP System is implementing proxies. Below are the configuration parameters of XIAdapter.

This document will enable adapter less communication with WAS6.20 Systems and above.
Siva Maranani is an SAP Integration Architect at Fujitsu America.

Comment on this weblog

Showing messages 1 through 18 of 18.

Titles Only Main Topics Oldest First

Hi Siva Maranani
2010-05-06 05:14:09 vijay kns Business Card [Reply]

I am New to the concept of Proxy's . The Blog is very useful to me. Can you please provide me step by step process for implementing Inbound and outbound Proxy's.

Thank u

http://weblogs.sdn.sap.com/pub/wlg/1457 04-Jan-11
SAP Network Blog: ABAP Server Proxies Pgina 3 de 5

FILE TO R/3 (GTS) Synchronous Scenario - Error (7.00 Version)

2008-12-09 22:12:32 Ravindra babu Immadisetty Business Card [Reply]

HI Siva,

I generated the Proxy in GTS, But it is not making the entry in the table SPROXXSL Table for synchronous and it is happening for ashync. While testing i am getting the following error. Did you
come accross this kind of error.

"DBIF_RSQL_INTERNAL_ERROR" " "

"CL_PROXY_STYLESHEET_UTILS=====CP" or "CL_PROXY_STYLESHEET_UTILS=====CM003"
"SAVE_TRANSFORMATION"

Please help me.

Regards
Ravi

excellent
2008-11-27 03:34:52 mattapally pedda Business Card [Reply]

the above blog is excellent

thanks

500 -Internal Server Error in SXMB_MONI

2008-09-23 04:01:42 Laawanya Danasekaran Business Card [Reply]

Hi Siva,
I have implemented an inbound server proxy with all the steps mentioned in the blog, but when iam testing my scenario, I am getting the error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>

when i open the attached HTML error, Iam getting something like :

The URL http://PXECP400:8000/sap/xi/engine was not called due to an error.

Note

The following error text was processed in the system EC6 : This browser is not supported
The error occurred on the application server PXECP400_EC6_00 and in the work process 1 .
The termination type was: ABORT_MESSAGE_STATE
The ABAP call stack was:
Function: ICF_ATTACH_ITS_PLUGIN of program SAPLHTTP_RUNTIME
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP

Could u please tell me how to solve this problem

Call Client Proxy inside a Server Proxy

2008-04-15 07:30:14 Shyam M Business Card [Reply]

Hi Siva,
We have a requirement like... Inside the server proxy i have to call the execute_asynchronous method of other client proxy... So when a Server proxy get triggered from XI it internally again
calls a client proxy to send some other data back to the sender....

I am getting an error when i called the Execute_Asynchronous method of client proxy inside the server proxy... It is telling that in Execute_Asynchronous method of Server PRoxy
*The exception CX_AI_SYSTEM_FAULT is neither caught nor is it declared in the RAISING clause of "EXECUTE_ASYNCHRONOUS".

Could u please tell me how to solve this problem... Or a better way to do Proxy to PRoxy Bidirection data transfer through Asynchronous mode..

HOW TO IMPLEMENT THE CLASS

2007-10-06 02:36:58 Niladri Debnath Business Card [Reply]

Hi,
IN THE BLOG YOU HAVE NOT GIVEN ANY GUIDANCE ABOUT HOW TO IMPLEMENT THE CLASS [ in Properties' tab -> 'implementing class' -> ABAP name : ZMETHOD_NAME - Double Click ]
PLEASE UPDATE YOUR BLOG AND MENTION WHERE TO WRITE THE CODE. OTHERWISE ITS BIT TOO CONFUSING FOR USERS.
Thanks,

Exception handing while calling the EXECUTE_ASYNCHRONOUS

2006-12-05 21:04:33 Udaya Nayak Business Card [Reply]

http://weblogs.sdn.sap.com/pub/wlg/1457 04-Jan-11
SAP Network Blog: ABAP Server Proxies Pgina 4 de 5

Hi,
I have a function module that populates the custom structure and calls the EXECUTE_ASYNCHRONOUS by passing the custom structure.
Do we want to handle any exception while calling the EXECUTE_ASYNCHRONOUS method ?.
Will there be a scenario where in EXECUTE_ASYNCHRONOUS would not be able to send the message to the CRM Inbound Queue ?

Thank you for your reply

Question
2006-07-12 06:17:55 James Kidd Business Card [Reply]

Our scenario:
ABAP server proxy created on the integration server. Problem scenario goes into error because it cannot find a receiver in XI for the interface instead of passing it to the local integration server.

Is it not possible on an XI instance to pass from the XI integration server to the local integration server ?
Thanks

Great Job
2006-06-05 09:47:12 Mohammed Vaseemuddin Business Card [Reply]

Would help better for beginners, if you had mentioned the Transaction codes.

Can you still include them ?

Thanks

Question regarding comm. channel for XI receiver adapter

2005-11-17 12:40:35 KARTHIK MATHRUBOOTHAM Business Card [Reply]

Siva
I have a question regarding the comm.channel parameters that you have given in your weblog.

You have used user id xisuper - I believe you have to give the logon parameters for the business system on which the server proxy is implemented , right ?

If that is the case, please clarify the values to be given in the path & service number parameters.

Your quick response to this is greatly appreciated.

Value Doesn't Update

2005-09-16 09:26:31 Selva Kumar Business Card [Reply]

Hi,

i am working on APABPROXY with help of your weblog. once the value fetched from XI Server i can seen the message in SXMB_MONI as processed Successfully. but the value doesn't update in
R/3 Server. i don't know why so kindly help me.

Thank in advance.

 Value Doesn't Update

2006-07-24 17:25:20 Prashant Rajani Business Card [Reply]

Hi Siva/Selva,

I am also facing the same problem as Selva had faced. Have checked the RFC destination and seems to be working fine. In SXMB_MONI data is received at target message interface. I do
not get test icon as well in SPROXY transaction in Business System. Also, am not able to monitor using SXMB_MONI in business system but can do in XI system. For Business system I have
asked for the authorization for SXMB_MONI but its taking time. Can you please guide me on how to check and proceed?

Thanks a bunch for your help!!

Prashant Rajani

Adapterless?
2005-06-30 11:32:31 Roberto Viana Business Card [Reply]

Siva,

Thank you for this weblog, it is very useful.

However, I have the following remark; You mention in this weblog that by using proxies you do not need any adapter between XI and SAP ("This document will enable adapter less
communication with WAS6.20 Systems and above."
).
At the same time you also explain in this document that between XI and the SAP system(Running on WEB AS 6.2x and up) an XI adapter has to be configured.

I am a bit confused now..Could you please explain this part? As far as I know communication between XI and proxies is done via native XI protocol (i.e. SOAP XI, so no need for any kind of
adapter).

Thanks,

http://weblogs.sdn.sap.com/pub/wlg/1457 04-Jan-11
SAP Network Blog: ABAP Server Proxies Pgina 5 de 5

Roberto.
 Adapterless?
2005-06-30 23:05:40 Siva Maranani Business Card [Reply]

Hi,

Adapters functionality is to handle the data transformations( to convert data from Source format to Target format). It also holds the login credentials of Target system.

When u come to "XIAdapter" (used in proxy communication), it does not do any data transformations ( XML format is retained). It has only the login credentials of external system.

As there are no Data transformations we term it as "adapterless" communication.

Cheers,
Siva Maranani.

 Adapterless?
2007-02-01 10:57:17 Adithya K Business Card [Reply]

Hi Siva,
If you dont mind, can I extend the discussion further? You have replied that, it is "Adapterless" because, it is having only logon credentials of external system. I think, this might not be
the exact reason for that. Even for the RFC adapter or IDoc adapter, its the same. You are going to give only logon credentials of the system. Isnt it?

From,
Adithya K
 Adapterless?
2007-09-19 08:02:52 Krishna M Business Card [Reply]

Hi Aditya,
XI Adapter is a special one. When adapter engine (in integration server) sees the receiver XI adapter in the configuration then XI-XML data coming from pipeline will be directed to
the target application system (WEBAS >= 6.4) local integration engine without any conversion of the data by it. In order to send the XI-XML to the target definitely XI server needs
the details of the target system which is what given in the XI configuration. That's it nothing converting.

Incase of IDOC or RFC also it requires all the details of the target system but as soon as adapter engine detects it is RFC OR IDOC it knows that target system expects XI-XML in
IDOC OR RFC method call so it converts it and sends to the target system.

Hope I am clear.

Thanks
Krish

good one :)
2005-04-03 13:23:46 Michal Krawczyk Business Card [Reply]

Keep on weblogging:)

Regards,
Michal
 Explain:
2005-06-09 21:38:14 DhanyaR Nair Business Card [Reply]

I m new to this area.I need to call a webservice from Abap.In sproxy transaction, i need to create a proxy Object , but how to create interface for that and above objects.From where i can
get the step-wise information.
Regards

Showing messages 1 through 18 of 18.

http://weblogs.sdn.sap.com/pub/wlg/1457 04-Jan-11