ABAP proxy object

Hi,
I want to use the google web servcices(http://api.google.com/GoogleSearch.wsdl) by creating a proxy object in SE80. But, the system returns "Proxy generation terminated: Message must have exactly one part" during the proxy creation.
Any configration is required prior the proxy create??
Regards,
Kit

/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

Similar Messages

Error while activating ABAP proxy object

Hello,
I can see all the interfaces of PI7.0 in my ECC6.0 system.
I am able to create abap proxy object of a interface.
But when I try to activate that I am getting error as
"RFC system error for destination GTADIR_SERVER".
Pl can you suggest. appreciate quick help in this.
thanks in advance,
Sharada

Hi,
For more details take a look at note: [1063482 - Creating Dictionary objects - RFC error GTADIR_SERVER|https://service.sap.com/sap/support/notes/1063482]
It is written that: Message SGSUB 104 is not an error message, but is merely irrelevant information for customers. You can continue to create objects nevertheless.
To get rid of this annoying error you have to implement the corresponding support package.
Regards,
Jakub

ABAP proxy object and JAVA proxy objects

can anyone explain whether ABAP proxy object and JAVA proxy objects can communicate with each others?
if yes then how???

JCO connectors would be able to do the trick here i guess
regards
krishna

Transporting ABAP proxy objects from one environment to another

Hi
I have ABAP client proxy objects ( classes in ECC 5.0 and the corresponding XI message interfaces on the XI server ) - in my development environment.
I need to move the ABAP proxy objects to the Qa environment. Two ways of doing this come to my mind.
1) Move the proxy classes within the ECC 5.0 Dev --> QA using normal transport organizer in ABAP workbench. Parallely , move the XI SCVs - from dev to QA ( export/import ). After both are done, go to QA environment, setup basic ECC5.0 <-> XI connection and check whether my ABAP proxies work.
2) As an alternate approach to no.1, move only the XI based SCVs from Dev -->QA , go to ECC 5.0 QA environment
and regenerate the ABAP proxies there using SPROXY - perhaps this will not be allowed in the QA environment - since the client will not be setup for any object changes/creation.
Any thoughts/links/weblogs on the above is appreciated.
Thanks in advance for your time.

Hi Kartik,
We recently moved our outbound proxies from dev to QA and we followed the first approach and we did not face any issues with the approach.
Also SAP suugests the same approach...
"You create proxy objects in the development system by using the proxy generation functions. They are transported and shipped by using the tools in the development system. There are separate tools in the Integration Repository (see also: Software Logistics for XI Objects)."
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Regards
Anand
Message was edited by: Anand Torgal

Error while generating ABAP proxy

Hi,
We created a WSDL using lotus notes (Domino) tools. While creating a proxy object using ABAP (transaction SE80), we get the error message "Cannot generate proxy (object missing in WSDL, see long text)" Message no. SPRX084.
We looked at OSS notes and applied 1046046 - Proxy generation problem with external definitions and all dependent notes as we are on a lower support pack. (WAS 6.40. SAPKB64019).
We are wondering if it is anything to do with the format/defintions in the WSDL. Can anyone send me a sample WSDL file that has been used to create an ABAP proxy object successfully. We would like compare the domino generated file. Please note that XI is not involved, we are using ABAP to call a webservice in the internal network application.
Thanks,
Girish

Hi,
I've implemented this proxy without problem and it's working fine in my case (I didn't have to store WSDL file localy and do any changes in it - Netweaver 7.2). If it's not SAP issue as Brad proposed then maybe network admins have set filters that are blocking communication with this service
Best regards
Marcin Cholewczuk

ABAP Proxy not generate in QAS

Hi All,
I´m with problem in Abap Proxy objects, I developer and transported to QAS environment but has not generate in QAS.
I checked this objects in environment QAS and all were transported.
When I go to transaction SPROXY, it´s with not generate.
Can someone help me?
tks

Hi,
probably your developer forgot.... a few things while developing the proxy
they are mentioned here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/content.htm
Regards,
Michal Krawczyk

WSDL error during generation of ABAP proxy for web service

Hi friends,
I am getting error during the generation of ABAP proxy object for web service developed in .NET .
Error : Proxy generation terminated: WSDL error (<extension> not supported).
How to make this WSDL file compatible for ABAP proxy.
I have tried to edit WSDL file in XML Spy but did not get any option to replace/remove the tag <extention>.
If any one worked on this. Please help me its urgent.
Thanks and regards,
Shivanand.

HI ,
I am having the same issue!!!
Does ABAP Proxy Generation support <extension> ?
Is there a list available of what is supported and what not (please consider I do not have access to sap notes)?
Thanks

ABAP Proxy To XI

Hi All,
I hope i can get an answer to lingering problem that we have currently.
We manage to configure to have XI --> ECC 5.0 (through Proxy / XI Adapter)
We have another scenario where we are using ECC 5.0 through ABAP proxy to send messages to XI. However, we are facing the following error message :
<SAP:Code area="INTERNAL">DESTINATION_NOT_FOUND</SAP:Code>
<SAP:Stack>HTTP Destination_Receiver missing (system , transaction SM59)</SAP:Stack>
1. SM59 ECC --> XI HTTP Connection Test is Ok
2. SCIF T-Code. XI services all activated
3. SM59 XI --> ECC HTTP connection test was ok
4. XI --> ECC (via XI Adapter Scenario --This is ok)
5. SM59 - Deleted and recreate the connection
6. Regeneration of the Message Interface in ECC
Thank you
Sulaiman

hi asari,
ABAP proxy objects can only be generated for SAP systems that are based on SAP Web Application Server 6.40.
The proxy generation retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 u2013 see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).
Example configuration for accessing
interfaces in the Integration Repository (exchange profile)
check link
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/frameset.htm
reward points if helpfull
regards
kummari

ABAP proxy regenration

Hi,
I've got the following problem with ABAP proxy objects (acting as receiver).
We are using XI 3.0 to connect to WAS 6.20.
APPINT 200_620 0006 SAPK-20006INAPPINT SAP Exchange Infrastructure 2.0 Add-On Support Pack.
We have changed the max length size of one tag (leaf in the deep structure) in the message. The new max length is longer than before (was 10 is 12). Proxy was regenerated and activated.
On the ABAP side this field has new size (12).
After sending a message with value 000071108000 in this tag I've got the following error:
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Request Message" p2="CX_XSLT_DESERIALIZATION_ERROR" p3="/1SAI/XS00000000000000000009: 0000000252" p4="Tree Position: abap.values.1.1.2.2.2.14.10 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: 000071108000">APPLICATIONCALL.PARSE_APPLICATION_DATA</SAP:Code>
<SAP:Text language="EN">Error when handling Request Message; XSLT error: CX_XSLT_have_ERROR: XSLT program and source line: /1SAI/XS00000000000000000009: 0000000252; Tree Position: abap.values.1.1.2.2.2.14.10 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: 000071108000</SAP:Text>
</SAP:ErrorHeader>
Pls help.
Regards
Artur

Hi Artur,
you can also check if the tables that you've changed
are reflected in transports have you checked that?
there's a report for invoking those changes: SAP note 853554
Let me know if you check it
Regards,
michal

Interfaces of different SCVs are always assigned to the same proxy object

Hi,
for clean versioning and maintenance of development branches we use different versions of a software component in the ESR. It looks like this:
SC_NAME 1.1 of namespace.com
+- http://namespace.com/project/a
   +- Service Interfaces
      +- Interface1
      +- Interface2
      +- Interface3
SC_NAME 1.2 of namespace.com
+- http://namespace.com/project/a
   +- Service Interfaces
      +- Interface1
      +- Interface2
      +- Interface3
SC_NAME 1.3 of namespace.com
+- http://namespace.com/project/a
   +- Service Interfaces
      +- Interface1
      +- Interface2
      +- Interface3
Here is the problem:
Service interfaces are assigned to proxy objects by using the key type/name/namespace of the repository object (refer SAP note [886682|https://service.sap.com/sap/support/notes/886682]). That means that the software component version of the repository objects is ignored when generating ABAP proxy objects.
Since in our case (see above) all service interfaces have the same type/name/namespace combination, all services interfaces get assigned automatically to the same ABAP proxy object. That makes it impossible to maintain different versions of ABAP proxies for the corresponding service interfaces!
As a workaround we only have two opportunities:
Either we add the version number of the SCV to the namespace (e.g. http://namespace.com/project/a/v1, http://namespace.com/project/a/v2, ...) or we add the version number to the interface name (e.g. Interface1_v1, Interface1_v2, ...) in order to distinguish the service interfaces for the proxy generation.
Both solutions are very ugly in my opinion, since they make our clean versioning with SAP's software component model useless.
Are these solutions the only way to seperate the generated ABAP proxies for each version of a SVC? If yes, then I can hardly believe, that nobody else in the SDN ever mentioned this - in my opinion - huge flaw in the ABAP proxy generation.
Please correct me, if I missed something.
Regards,
Adam
Edited by: Adam Sosnowski on Dec 3, 2009 11:25 AM

Hi Stefan,
thank you for the quick response. It really looks like a bug, since it undermines the versioning with the software component model.
Inside an SAP system, there is only one valid SWCV. So when you decide to use version 1.1 for one system, you cannot use 1.2 for the same system.
I don't exactly know, what you mean with "inside an SAP system". We connect different versions of a client application to different versions of service applications. Newer version may contain an enhanced data model (new fields in the messages, etc.). For that reason, we split the development into branches using different SWCVs in order to handle e.g. change requests for older versions seperately. This approach is a common pattern and it is also the purpose of using software component versions.
Regards,
Adam

How Abap proxy works?

Hi friends,
Can anybody explain me that how actually ABAP proxy works(in both cases clent and server proxy). when shuld we go for proxy.And how proxy seprates business application from technical infrastructure?
If u have any presentation or document on ABAP proxies ,plz send me
Thanks in advance
Shweta

Hi
Adapters are part of the Adapter Framework. Adapters provide the technical connectivity to enable the integration of SAP and non-SAP applications through XIs Integration Engine.Again, Adapters are used for connectivity from and to external systems with XI that cannot communicate via proxies.Adapters are only required in SAP systems older than 6.20 and external systems.
Systems based on 6.20or higher can communicate directly with proxies.
Proxies
The literal definition of a proxy is an object / process authorized to act for another; an agent or a substitute. In simpler terms, proxies in the XI context are objects used to encapsulate the creation (from a sender system) or parsing of XML (at a receiver system) as well as the communication with the relevant runtime components required to send or receive those messages.
Proxies are generated from Message Interface in IR.
The Proxy Runtime controls these objects / processes, and can itself be controlled by the applications it communicates with. The Proxy Runtime currently has the following components available: 1. ABAP Proxy Runtime Communication using XI or Web Services a. Web Service Runtime 2. Java Proxy Runtime Communication using XI (J2EE) The objects that the Proxy Runtime then controls are created via Proxy Generation, for both ABAP and Java. In the following sections a client proxy is used by an application to send messages outside of the system it resides in (normally to the IS in this context). Conversely, a server proxy is used by an application to receive messages from sources outside itself (again, normally the IS in this context).
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.
mainly we go for proxies for adapters less communicaton there
Client Proxy: Proxies created out of Outbound message Interfaces.Here XI is receiving some information and is
acting as a client.
Server Proxy : Proxies created out of Inbound message Interfaces.Here XI sends the information to some other system acting as the Server.
we can create the ABAP proxy in ABAP workbench.
Use
Using ABAP the proxy generation function you can generate ABAP proxy objects to an SAP system from an interface description in the SAP Exchange Infrastructure Integration Repository.
Prerequisites
ABAP proxy objects can only be generated for SAP systems that are based on SAP Web Application Server 6.40.
The proxy generation retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 u2013 see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
How to Activate Proxy.
How do you activate ABAP Proxies?
ABAP Server Proxies (Inbound Proxy)
ABAP Server Proxies
OutBound Proxy (Client Proxy)
Smarter Approach for coding ABAP Proxies
ABAP Proxies in XI(Client Proxy)
File to R/3 via ABAP Proxy with good example
File to R/3 via ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
go thru the weblog How do you activate ABAP Proxies? which explains how to activate proxies
Check this for Use Of Proxies
Choose the Right Adapter to integrate with SAP systems
Hope this is useful and clears your doubts
Thanks
Saiyog

How to create a proxy object for MOSS integration via WebDynpro For ABAP

Hello all,
I have a question about the creation of an ABAP proxy class in SE80.
When i follow this link:
[https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6066fbe8-edc4-2910-9584-a9601649747d&overridelayout=true]
i see on page 7 that there is: a tab under create called Enterprise Service/ Web Service with under this tab a tab called proxy object.
When i do this in my SE80 i only see Enterprise Service and not proxy object.
Screenshot
[http://picasaweb.google.be/panneels.robin/SAPScreens#5377623235095894546]
Is there a extra configuration or add-on needed to do this action? Or is there a work-arround for this?
Because we need this for abap web dynpro for communication with MOSS.
Thanks in advance for all your help.
With kind regards,
Robin Panneels

Hi James,
If you like to use SAP web dispatcher as a solution for load balancing portal application, you no need to create system object under systems..
You have to install web dispatcher as separate instance where you need to configure portal apps into it..
Configure web dispatcher like to hit the admin port, use http://<webdisp-server>:<adminport>/sap/admin
For normal portal access, use http://<friendly URL>/irj/portal
The good news is that the webdispatcher knows that the portal supports SSL
Another advantage of this config, is the webdisp, will just replace the apache redirect server. Users will access mycompany.com, without any port number, since we are redirecting 80 to the backend j2ee. Also, https should work like in the normal world.
Profile will be like below...
SAPSYSTEMNAME = WEB
SAPSYSTEM = 00
INSTANCE_NAME = W00
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_CT_RUN)
Accesssability of Message Server
Message Server Parameters ##########
NOTE: The "ms/http_port" must match the profile on the Central Instance
rdisp/mshost = <FQDN of portal CI Host>
ms/http_port = <Ms port of portal>
SAP Web Dispatcher Ports
#icm/server_port_0 = PROT=HTTP,PORT=81$$
icm/server_port_0 = PROT=HTTP,PORT=80, TIMEOUT=3600, EXTBIND=1 (some OS will not allow to bind ports <1024)
Admin port details
icm/server_port_1 = PROT=HTTP,PORT=3200
#, EXTBIND=1
icm/HTTP/admin_0 =
PREFIX=/sap/admin,DOCROOT=./admin,PORT=3200,AUTHFILE=/usr/sap/WEB/SYS/global/security/data/icmauth.txt
SSL
icm/HTTP/redirect_0 = PREFIX=/ , TO=http://<friendly URL name>/irj/portal
WebAS Message Server Parameters
rdisp/TRACE = 1
icm/trace_secured_data = 1
Regards
Suresh

How to transport proxy object abap part

Hi ,
I am working with one outbound proxy . The proxy was working fine in production ,now one requirement came in which we have to add one extra field to Proxy .field has been added in message type and proxy was generated in respective ABAP box
abap coding every thing was done and it worked fine in Dev . I transported the PI part ( DT,MT,MI and MM ) .
However I am not sure how to transport the ABAP proxy in ECC from dev to prod .
Can you kindly please tell me all steps I tried to search in SDN but getting confused in what object I have to transport and how from ECC .
Regards,
Saurabh

Hi Sarvesh ,
Thanks a lot for all your reply .
It partially worked as I created the transport with proxy object but not toatally as all my objects are not included in the transport .
when I am doublicking the My proxy interface and then going in used object TAB then I am able to see the structures .
Abap team wants to include these structure in the transport .
Actually the code has already been transported and it is throwing the dump value as it is unable to find the new field as the new strucutre is not transported .
Should I tell Abap team to manually make some random change in the str now and save them again so that when I re generate proxy then it will be added to transport.
Regards,
Saurabh

Problem with Configuration in Production ( ABAP Proxy - XI - FILE)

Hi All,
I have a ABAP Proxy -> XI -> FILE scenario wich is working perfectly in DEV and QAS environment.
When the person responsible for transporting tried to transport the objects in QAS to PRD, the following error happened:
Direction of communication channel |BS_MA_FileServer_PRD | CC_File_PedidosServ_MA_FileServer_IA is incorrect.
Correct the direction or choose another communication channel
BS_MA_FileServer_PRD - Business System (FILE)
CC_File_PedidosServ_MA_FileServer_IA - My FILE Communication Channel
This was what the Basis person sent to me. I don't have access to know exactly what happened. And I really don't know what could be wrong or if maybe a component was created wrongly in Production.
Hope you can help.
Points will be given.
tks.. Daniela

You have mentioned FILE is on the receiving side and ABAP proxy is on sender side.
But the error pasted by you clearly shows syntax of a Sender Agreement .
For receiver agreement it should be |<Sender Service>| |BS_MA_FileServer_PRD | CC_File_PedidosServ_MA_FileServer_IA
Bipin

ABAP Proxy error

Dear Friends,
I am facing a problem when i use a ABAP client proxy (asynchronously)
An error is raised during proxy method call-
<CODE>SERIALIZE_APPLICATION_DATA</CODE>
<b> <ERRORTEXT>Conversion error ABAP => XML (Request Message; error ID: CX_ST_INVALID_XML;
(/1SAI/TAS00000000000000000005 XML Bytepos.: 0 XML Path:
Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document) )</ERRORTEXT></b>
The same proxy runs fine in upstream system (dev) but doesnot run in downstream system (QA) even though all proxy objects have been transferred.
This proxy & another proxy from the same calling report program is serialized in a queue.The first proxy is raising this error, but the second proxy call is successful.
Can someone help,
Thanks
Prasenjit

Hi Guru,
All the fields in the data type have string - also this roxy works fine in devpt. system- but it doesnt work in downstream QA system.
Other proxy interfaces in the QA system work fine.
The error message when i single test the proxy is as follows-
- <CX_XMS_SYSTEM_ERROR>
<ID>SERIALIZE_APPLICATION_DATA</ID>
<P1>Request Message</P1>
<P2>CX_ST_INVALID_XML</P2>
<P3>/1SAI/TAS00000000000000000005</P3>
<P4>XML Bytepos.: 0 XML Path: Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document</P4>
<INFO />
<CATEGORY>XIProxy</CATEGORY>
<AREA>ABAP</AREA>
<CX_ST_ERROR>
<ST_PROGNAME>/1SAI/TAS00000000000000000005</ST_PROGNAME>
<X-ML_OFFSET>0</X-ML_OFFSET>
<X-ML_PATH />
<ST_IC>2</ST_IC>
<ST_TIMESTAMP>20070907163313</ST_TIMESTAMP>
</CX_ST_ERROR>
Any other possible solutions ?
thanks
Prasenjit

ABAP proxy object

Similar Messages

Maybe you are looking for