Proxy Object Generation

Dear all,
I have tried to generate a proxy object for the google service( http://api.google.com/GoogleSearch.wsdl ) with the following path:
se80 - > local object -> right click -> create -> web service -> proxy object -> URL -> ... But it always return an error. Anyone have idea??
Regards,
Kit

Hi,
Try to use the File local for create the proxy.You need to download the WSDL from internet to your PC. I think that this method works, but you need to create a conection in SM59 ( type G).
Great,

Similar Messages

Proxy Object generation error using Wizard for Web Service Consumption

HI all,
I am using the Web Service Proxy Object Generation Wizard (via SE80) and have successfully been able to create a Proxy Object for a Web Service which resides on our INTRAnet.
...But now I am trying to consume a Web Service out on the INTERnet and I get an error I cannot quite understand when generating the Proxy Object using the URL of the WSDL of the SOAP Web Service.
The initial error in SE80 simply states "No vendor specified", but when I double-click on the error to get the long text I get the following error:
Incorrect value: Namespace prefix q1 of QName q1:RequestArray is undeclared
Exception of class CX_SLIB
Has anyone seen this or have experience with this?
I am a senior ABAP-er but have very little experence on the web development side of things so this looks very foreign to me.
Any input would be GREATLY appreciated!
Thanks!!
-Chris

RESOLVED! ---
I figured it out with further trial and error...
Turns out I was using the SOAP version of the WSDL (I had a choice b/ween SOAP, REST, and XML).
When I simply supply the XML version of the WSDL to the Proxy in the Web Services Wizard, the error vanished and the Proxy Objects generated just fine !!
..Closing this problem.
Edited by: Christopher Twirbutt on May 26, 2009 5:36 PM
Edited by: Christopher Twirbutt on May 26, 2009 5:37 PM
Edited by: Christopher Twirbutt on May 26, 2009 5:39 PM

Web Service Proxy Object Generation

Please refer to my issue in inserted image. To reiterate im getting only one argument in the generated proxy object whereas I get three in Visual Studio. Both PB and VS are using the same WSDL location. Am I missing something?

Hello,
Sorry for the delay; I thought of just making the wsdl content unsearchable by posting it as image and redacting out sensitive functions. I hope the ff. images will help:

Error in activating proxy object

hi
when i m trying to activate my proxy objects in CLIENT PROXY scenario in the ECC , the following error message is being prompted :
Erro in object editing :
"SAP object CLAS CO_PRXY_MI cannot be assigned to
package ZXIPACKAGE:
A package has been created in ECC by the name of zxipackage .
Pl help to rectify the problem
rgds
shazia

Hi,
You should assign it to Z-package ie.e Customized one not SAP package
Use a prefix of Z when doing the generation and you can use your own development class. you are trying to create objects in the SAP namespace.
The Proxy object should have to be in non SAP package only, if its customized.
As while activating the ABAP proxy internally Class and verious methods as well as some data typs get creaetd which are to be assigned it Z-package.
refer below link
Tips for Generating ABAP Proxies
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
thanks
Swarup

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

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

Proxy object to consume web service

Hi,
I want to consume a web service in ABAP (on a WAS 7 box) and have read many blogs/posts about using a proxy object.
I've gone to SE80 and selected create a service consumer, enter the URL for the WSDL.
The generation of the proxy fails with the following messages;
Proxy-Generierung: Fehler aufgetreten
Exception occured in the library handler
not implemented
There is no other help or information in these errors.
Does anyone have any ideas on what is causing this and what I can do to successfully generate a proxy to consume the web service ?
Cheers
James

Hello Torsten,
It seems that the Web Service You are going to consume is a SOAP 1.2 one.
It is apparently making use of the so-called "SOAP Web Method Feature" which is part of the SOAP 1.2 specification (see [Web Method Feature (W3C)|http://www.w3.org/TR/soap12-part2/#WebMethodFeature]).
Unfortunately, SOAP 1.2 is, to the best of my knowledge, not supported as yet by the SOAP Adapter in SAP NW 7.0 / 7.1. That leaves You, in theory, with one of the following options:
- It might be possible to consume that service with the help of Axis framework (see [Using the Axis Framework in the SOAP Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm]). SAP Help states that with the help of the Axis framework SOAP 1.2 can be used. However, there are no further details on that subject, especially whether Web Method feature can be utilised (btw - has anyone tried this?).
- Ask service provider for a SOAP 1.1-compatible WSDL.
- Attempt to reverse engineer the SAP SOAP proxy so that it is capable of consuming a SOAP 1.2 Web Method-based web service (has anyone done this before?).
Would You be so kind to post whether, and how, You were able to consume this web service?
Kind regards
Wiktor Nyckowski

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

SPRX038 error while creatign proxy object from WSDL

Hi,
I am trying to create SE80 --> create Proxy Object using WSDL file..
when i am trying to import WSDL file, it is throwing error.
It says "Proxy generation terminated: WSDL error (<#text> not supported)"
Message no. SPRX038.
when i checked my WSDL there is not <#text> or either any'text' is there in WSDL.
Please help me to resolve the problem...
please find the error...
Proxy generation terminated: WSDL error (<#text> not supported)
Message no. SPRX038
Background
During proxy generation, an interface description in WSDL format is fetched from the Integration Builder or from another source and interpreted. This WSDL document must describe the whole interface correctly.
==> Display Query
==> Display WSDL Document
Diagnosis
The language element
"<#text>"
was used in the WSDL document.
This language element is not supported by ABAP proxy generation.

Hi Isaias,
we are working with this versions:
SAP_BASIS 700 0015 SAPKB70015 SAP Basiskomponente
SAP_AP 700 0013 SAPKNA7013 SAP Application Platform
We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
Thanks,
Fouad

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

SharePoint Foundation Sandboxed Code Service - Unable to activate worker process proxy object within the worker process

Issue:
On a vanilla installation, the sandboxed code service (e.g. SPUCHostService.exe) is started; however, SPUCWorkerProcessProxy.exe and subsequently SPUCWorkerProcess.exe fails to start.
Resolution/Workarounds attempted:
Attempted 2 different Load balancing settings – local and remote (i.e. affinity)
Ensured local computer policy on server for ‘RPC Endpoint Mapper Client Authentication’ and ‘Restrictions for Unauthenticated RPC clients’ is disabled.
Ensured following key in registry is set properly - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\RPC
Attempted to bypass SharePoint’s check for certificate revocations at crl.microsoft.com
Ensured the service account is added to the respective groups (e.g. Performance Log Users, Performance Monitor Users, IIS_IUSRS, WSS_ADMIN_WPG, WSS_WPG)
Increased limit of ‘AbnormalProcessTerminationCount’ of SPUserCodeService via Powershell
We have tried all possible workarounds from the following MSDN reference:
http://blogs.msdn.com/b/sharepointdev/archive/2011/02/08/error-the-sandboxed-code-execution-request-was-refused-because-the-sandboxed-code-host-service-was-too-busy-to-handle-the-request.aspx
ULS:
02/21/2014 05:24:50.64 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service              fe8a
Medium               - - Unable to activate worker process proxy object within the worker process: ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000
02/21/2014 05:24:50.64 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service              fe8c
Medium               - - Error activating the worker process manager instance within the worker process. - Inner Exception: System.InvalidOperationException: Unable to activate worker
process proxy object within the worker process: ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()
02/21/2014 05:24:50.64 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service              ei0t
Medium               - Process creation/initialization threw an exception. Stopping this process. "ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000"
02/21/2014 05:24:50.65 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service
fe87                Medium               - - Error activating the worker process manager instance within
the worker process. - Starting worker process threw - Inner Exception: System.InvalidOperationException: Unable to activate worker process proxy object within the worker process: ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()
Any other insights on how I can troubleshoot the issue described?
Thanks in advance!

Hi ,
For resolving your issue , you can do as the followings:
1. Logged into the Web Server with the Timer Service Account.
2. Ran the powershell command to check the SID of the account running the spucworkerprocessproxy.exe:
$(Get-SPManagedAccount -Identity "THE SERVICE ACCOUNT").Sid.Value
3. Checked the registry :
HKEY_USERS\[SID OF THE SERVICE ACCOUNT]\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing\State
4. Changed the value 0x00023c00 to 0x00023e00
In addition, here are some similar posts for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/aae497df-5f0d-4f86-a724-c7b805ccd07f/sharepoint-sandboxed-code-service-troubles?forum=sharepointgeneralprevious
http://blogs.technet.com/b/operationsguy/archive/2011/01/17/sharepoint-2010-sandboxed-code-solutions-and-web-proxy.aspx
http://social.msdn.microsoft.com/Forums/en-US/c21e2c3a-a259-4d5f-8071-eff52b7bddc3/issue-sandbox-solution-too-busy-to-handle-the-request?forum=sharepointgeneralprevious
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Error while creating the proxy object to connect to a third party tool.

Hi,
I tried creating a proxy object with the wsdl file. I even created a HTTP connection to the third party tool. but when I try to execute the whole proxy object, I am getting the below error. Can anyone help me on this?
"Proxy-Generierung: Fehler aufgetreten"
"Incorrect value: Entity "<<document>>"(92 /3788 ). end tag 'ul' does not match begin tag 'p'"
Thanks & Regards,
Veerabhadra Rao A.

do a check on the wsdl file and how you are passing values in the proxy. The tags for XML are not correct. Open the WSDL in IE and see there must be an error. Or probably when passing the actual values to the XML generated each element is not closed properly. Error says tags dont match.
Edited by: Kshamatha Eda on Mar 5, 2010 10:54 AM

Error when creating a Proxy Object from WSDL

Hi,
when creating a proxy object in abap based on the [WSDL|http://download.mapandguide.com/EN/dev/xserver/XLocate-1.6.0.3.wsdl] i get the error 'Incorrect value: Unknown Type Referencens0:ArrayOfString'.
1- Is there a conflict with the type 'String' that's also a type in ABAP
<complexType name="ArrayOfString">
<sequence>
<element name="String" type="xsd:string" minOccurs="0" maxOccurs="unbounded" nillable="true" />
</sequence>
</complexType>
2- Is it a name space problem?
xmlns:ns0="http://types.xlocate.xserver.ptvag.com"
type="ns0:ArrayOfString"
3- Something else?
Please Help!
Thank
Fouad

Hi Isaias,
we are working with this versions:
SAP_BASIS 700 0015 SAPKB70015 SAP Basiskomponente
SAP_AP 700 0013 SAPKNA7013 SAP Application Platform
We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
Thanks,
Fouad

Error While Generating the Proxy Objects

Hi All,
While Generating the Proxy Obects in SPROXY at SAP R/3 side,
Iam getting this Error
http://img169.imageshack.us/img169/5752/proxylm0.jpg
Can any one Occured this type of Error
Regards
Suman

Hi PT,
Now the Strange Issue came,
While generating the proxy objects i got that above mentioned error
After that i have run the 3 report programs according to the Ramesh Suggession
Now if i goto SPROXY means it is saying that No Conection to Integration Builder .
I have checked the RFC Destination created in SM59 of SAP R/3 of Type H.It is fine
What more i have to check
First of all when ever i open the Sropxy, every time User & pwd is requesting
Can you please through a light where to check
Regards
Suman

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

Proxy Object Generation

Similar Messages

Maybe you are looking for