SAP Connector / Proxy Classes

Hello,
when i wont to call bapi-calls i need proxy classes. with the sap enterprise connetor they will be generated for JCo. Whats about calling with the connector framework? How i become the proxy-classes for my babi-call?
Thanks,
Frank

Hi Michael,
there is API documentation available on the SDN. The API docs of the SAP Java Connector is located here:
http://media.sdn.sap.com/html/submitted_docs/60_sp2_javadocs/sapjco/index.html
In general, API docs of Web AS 6.40 and EP components is available here:
https://www.sdn.sap.com/sdn/developerareas/ep.sdn?page=javadoc.htm
Hope that helps!
Regards,
Ivo

Similar Messages

SAP Connector Proxy Wizard doesn't start

Hi all,
I've just installed VS2003, the SAP .NET connector and the .net framework (1.1) on a freshly installed Windows XP pro machine. If I follow the various tutorials on the web I should be able to create a SAP proxy when doing the following:
- start VS2003
- create a new Windows Application (in C#)
- Add a SAP Connector Proxy
-- A wizard starts
And that is were it starts to go wrong. Instead of a wizard, I get the following:
<?xml version="1.0" encoding="utf-8" ?>
<wsdl:definitions targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
 <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema"></xsd:schema>
</wsdl:types>
<wsdl:portType name="dummy.PortType"></wsdl:portType>
<wsdl:binding name="dummy.SAPBinding" type="s0:dummy.PortType" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 <s0:binding style="rfc" />
 <wiz:GeneratorSettings xmlns:wiz="urn:sap:mw:dotnet:wizard">
 <wiz:ProxyType>Client</wiz:ProxyType>
 <wiz:ClassName>SAPProxy1</wiz:ClassName>
 <wiz:Beautify>True</wiz:Beautify>
 <wiz:CreateAsyncs>False</wiz:CreateAsyncs>
 <wiz:CreateQRFC>False</wiz:CreateQRFC>
 <wiz:CreateTRFC>False</wiz:CreateTRFC>
 </wiz:GeneratorSettings>
</wsdl:binding>
<wsdl:binding name="dummy.Binding" type="s0:dummy.PortType" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:binding>
</wsdl:definitions>
Does anyone know what could be wrong here?
Thank you and kind regards,
Thomas

Hi Thomas,
With the newer version of NCo (> 2.0) there is no wizard. You would have to drag and drop the RFC/BAPI from the server explorer window of visual studio.
First open the solution explorer, click on the SAP icon. Specify the credentials. And then from the list of RFC/BAPI drag and drop on SAP connector proxy page(design view). You can also specify the filter to restrict the listing of RFC/BAPI.
Regards.

Can't see SAP Connector Proxy

Hi experts,
I'm trying to use SAP .Net Connector 2.0 or 3.0 on visual studio 2003, 2005, 2008 or 2010
to call ABAP function modules via RFC .
I have the same problem, once installed the right connector, if I try to add the item SAP Connector Proxy to my project
but I could not find it as option.
Another problem then is yhan I can't connect to my SAP server that is on an external network, even if I reach the
system via SAP Gui.
My tought is that I can't find the Connector because I'm not connected to the Server, but in some forum I found
suggested to first add the item Connector to the project and then connect to the SAP server.
Please if you have some experience also in only one of this problem replay to my thread,
I need to implement the whole thing as soon as possible, every help will be appreciated!!
Greetings,
Paolo F.C.

Please note that this forum is dedicated to development and deployment of .Net applications that connect and interact with BusinessObjects Enterprise, BusinessObjects Edge, or Crystal Reports Server. This includes the development of applications using the BusinessObjects Enterprise, Report Application Server, Report Engine, and Web Services SDKs.
You will have to re-post your query to one of the SAP forums.
Marking this thread as "Assumed answered".
Ludek

JCO 3 with the SAp proxy classes

hi..
i have been using netweaver proxy connectors for connecting to sap...however i now wish to use SAP JCo 3 to create the client...any idea how we can use these with the proxy classes ..

hi,
check this
http://www.winfobase.de/lehre/lv_materialien.nsf/intern01/1DDA0D7896600DF5C125709F0045ED23/$FILE/Tips&Tricks_JCo_Programming.pdf
http://help.sap.com/saphelp_nw04/Helpdata/EN/b6/55e3952a902447847066a0df27b0d6/content.htm
http://www.vogella.de/articles/SAPJCo/article.html
let me know u need any further info
bvr

Error occures while Sap R/3 sytem triggers XI message (using proxy class)

Error occures while Sap R/3 sytem triggers XI message (using proxy class)
1- I prepared message in XI side
2- I used sproxy transaction in R/3 side and generate proxy class
3- I used necessary methods in Abap program in R/3 side
4- Somethimes, message does not work and generate error like below
What must I do to solve this problem. Thanks
Error message (Reported in SXMB_MONI in Sap R/3 side)<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="112" p2="HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten." p3="" p4="">HTTP.HTTP_CLIENT_SEND_FAILED</SAP:Code>
<SAP:Text language="TR">Error during http send: Error code: 112 Error text: HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten.</SAP:Text>
</SAP:ErrorHeader>

Hi,
Check thiss
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Error no 2
Regards
Aashish Sinha
PS : Reward points if helpful

Creating Proxy Classes in Visual Studio 2010 from SAP ES

I am having problems with Microsoft's Visual Studio 2010 creaating a proxy class when importing a WSDL file from SAP's Enterprise Services.
When attempting to define the proxy class by pointing it to the endpoint WSDL, the import seems to work OK but the proxy class is not created.    I don't have this problem with other WSDL's from non-SAP sources.   There seems to be something "special" about the ES endpoint WSDL.
Is anyone else having this problem?

not always the 18th. For me it is the 14th. I think it is because I have some buttons hidden already. But seems like it is always the last one.
// The SAP Crystal Report logo is the last item on the 4th control.
System.Windows.Forms.ToolStrip oToolStrip = (System.Windows.Forms.ToolStrip)crystalReportViewer.Controls[4];
                oToolStrip.Items[oToolStrip.Items.Count-1].Visible = false;

C# Proxy Classes from SAP WSDL files

We are trying to generate proxy classes for SAP eSOA web services using C# and Visual Studio 2005.
When we try to run Microsoft's proxy class generation utility, WSDL.exe, errors are generated that attribute incorrect syntax to the SAP WSDL file:
> Microsoft (R) Web Services Description Language Utility [Microsoft (R)
> .NET Framework, Version 2.0.50727.42] Copyright (C) Microsoft
> Corporation. All rights reserved.
> Warning: This web reference does not conform to WS-I Basic Profile v1.1.
> R2028, R2029: A DESCRIPTION using the WSDL namespace and the WSDL SOAP
> binding n amespace MUST be valid according to the XML Schemas found at
> http://schemas.xmls oap.org/wsdl/2003-02-11.xsd and http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.
> xsd.
> - Warning: The element 'definitions' in namespace
> 'http://schemas.xmlsoap.org /wsdl/' has invalid child element 'properties' in namespace 'urn:com-sap:ifr:v2:
> wsdl'. List of possible elements expected: 'import, types, message,
> portType, bi nding, service' in namespace
> 'http://schemas.xmlsoap.org/wsdl/'. Line 1748, posi tion 4.
>
> SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of
> implementat ion guidelines that recommend how a set of core Web
> services specifications shou ld be used together to develop
> interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
>
> For more details on the WS-I Basic Profile v1.1, see the specification
> at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
The WSDL file is obtained from the SAP ES Workplace, from the following URL:
http://erp.esworkplace.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?&id=4FFC1A97663611DA36BB000F20DAC9EF&fragID=&packageid=DBBB6D8AA3B382F191E0000F20F64781&iv=
We have already tried both SAP files available from this location; neither works.
Any insight you can offer to help us generate these proxy classes is welcome. Note that the SAP PDF file, "ESOA-Roadmap-Workshop.PDF" talks about one syntactic incompatibility with Microsoft WSDL (on page 70), but this solution does not work, and indeed the token 'parameters' does not appear anywhere in either SAP WSDL file for Create Maintenance Request eSOA.
Thanks for any help you can offer!
-- Julian Mensch

I have the same problem after renaming "parameters" to "parameter" and I'm using the same example ES that's in the document:
http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ECC_EMPLOYEEBASICDBYEMPLOYEEQR/version3?sap-client=800&wsdl=1.1
wsdl.exe from .NET Framework 2.0.50727.42 gives me
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementat
ion guidelines that recommend how a set of core Web services specifications shou
ld be used together to develop interoperable Web services. For the 1.1 Profile,
those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification
at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I'm sure it's something really stupid since this example worked at some point for whoever wrote the doc...
It's sad that there is basically no .NET support from the SAP side and apart from a few documents there is basically no developer documentation or samples...

Needed classes for sap connector framework

Hello,
when i installed sap netweaver developer studio 2.0.5 i become all needed classes for sap connector framework?
Or i have to install the pdk? What are in the pdk for developer studio because the needed wizards are there (portal, sap connector ...)
Thanks,
Frank

Torben, try to use class finder plugin as described here /people/maksim.rashchynski/blog/2006/08/14/the-story-about-how-2-eclipse-plugins-helped-me-to-make-a-lot-of-points-on-sdn-forum
To save you some time:
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\ext\tcconnconnectorframework\*.jar
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\com.sapportals.connectors.sap\connector\connectors\SAPCFConnector.rar\SAPCFConnector.jar

RFC lookup with java proxy class, how do I use "fromXml()"?

Hi,
I'm trying to do an RFC lookup in XI using java proxy classes (SAP Enterprise Connector).
The XMLPayload comes from a java proxy class which has been converted to xml using a method called
.fromXml() for this. I just don't know how to use and I can't find any documentation for it.
Would very much appreciate if someone could provide me with an example of how to use this class
Best Regards
Olof Trönnberg

http://xstream.codehaus.org/javadoc/com/thoughtworks/xstream/XStreamer.html#fromXML(com.thoughtworks.xstream.io.HierarchicalStreamDriver,%20java.io.Reader)

File or assembly name SAP.Connector, or one of its dependencies not found

Hello there,
Something very strange is overcoming me when experimenting a little bit with the SAPConnector:
I developped a class that is accessing the proxy-class generated by the SAPConnector wizard and I have put it into a class library. No problems so far.
When I am accessing the class library from into a windows application, no problems are signalized...
However when I try to execute the BAPI from another class library project, I always get the following message:
File or assembly name SAP.Connector, or one of its dependencies, was not found.
I am testing with the following configuration:
- Visual PC 2004
- .Net-framework 1.1 and .Net-framework 2.0
- Visual Studio 2003 and Visual Studio 2005
I tried both SAPConnector 1.0.3 and 2.0, but both return the same message.
Thanks in advance!
Greetz,
Sven

SAP.Connector.DLL (and SAP.Connector.Rfc.DLL in 2.x) must be available for the project to load. The easiest is to put the two DLLs into GAC (which is the default in NCo 2.x). You can also have them in you application directory. The reason that you don't see a problem if you are using NCo directly is the fact that VS automatically copies directly referenced DLLs into the target directory. This is not (allways) the case for inderectly referenced DLLs.

Proxy Class Generation

I am a newbie in SAP and .NET connector technologies.
I have to develop an application for one customer that retrieve accounting information usign the .NET connector. The .NET connector tutorial explain how to generate RFC proxy classes using a SAP connection but I am not allowed to access the customer's SAP Server for the moment.
So : Is there any possibility to generate the wanted proxy classes without connecting his SAP ?

SAP .NET Connector 1.0 also has the possibility to create a proxy from an Integration Repository (IFR) 2.0, but as you don't have access to a SAP system, is even more unlikely that you have access to an IFR.
A good alternative for delopment is using a SAP Mini System and transporting the important function into it. The Mini System edition are partly contained in the ABAP-Objects book or are available from SAP Shop.
Note that you are allowed to develop software with SAP .NET Connector only if you have a valid Developer License.

Proxy classes

Hi experts,
Why the proxy classes get created when a model is imported from back end, and on what basis it will create the classes.
For example for each structure will a class get created?
Thanks & Regards,
Muhammad Imtiyaz

Hi
When you intregrate your RFC , the RFC/BAPI is SAP code and you are calling this in NWDS which understands only java
the proxy classes created are the java classes based on your structure and table created in the RFC/BAPI.
Based on this java classes created you can create objects and create elements and add new data to the structure.
We use JCO (jave connectors ) where you provide the two logical destinations Model Data and MetaData
Model data destination will fetch actual data while metadata destination will contain descrition of the data.
Check this link for more
http://help.sap.com/saphelp_nw04s/helpdata/en/79/c6213e225f9a0be10000000a114084/content.htm
Thanks
Edited by: murali krishna reddy on Jul 27, 2009 10:05 AM

How to populate CONTROLLER in proxy class call?

Hi All
While calling proxy class, i want to populate input variable CONTROLLER. I want to use the method GET_MESSAGE_ID to get the message guid.
CONTROLLER is TYPE REF TO IF_AI_POSTING_CONTROLLER.
How can i get this populated thru my proxy class call?
Sample code is highly appreciated.
Thanks
Chandra

Can you let me know little bit more details. Is this server proxy? If yes, you can use the proxy access class CL_PROXY_ACCESS to access the runtime variables of the proxy. Check http://help.sap.com/saphelp_nw70ehp1/helpdata/en/51/d5cd16235e4643ae8ec92395c4ad97/frameset.htm
Controller is used for controlling the attributes of the message, say for example controlling initial values for fields etc.
Let me know if you need more info.
KK

How to use CL_PROXY_BASIS instead of CL_PROXY_CLIENT your ABAP Proxy class?

Hello experts,
I have a scenario where a new basis release was done in my development and testing SAP boxes (Basis Release 710 I believe) which means from then on when generating an ABAP Proxy class the inheriting class will be used is CL_PROXY_CLIENT as opposed to the previous CL_PROXY_BASIS.
This causes a problem though because the target date for the project, which uses this ABAP proxy, is supposed to be in the production system before the date when the basis release will be done in the production system. Obviously this will cause delays in my project since if I were to move my objects to production before the basis release a dump/syntax error will occur in production because the class CL_PROXY_CLIENT is not expected be production yet.
The next plan is to try to use CL_PROXY_BASIS instead of CL_PROXY_CLIENT, by editing my ABAP Proxy Class be force. My question is, what steps do I need to take so that I can change these classes so CL_PROXY_BASIS will be referenced/used instead of CL_PROXY_CLIENT ?
I hope to hear from all of you soon.
Regards

>
Rich Heilman wrote:
> Bad idea. Your dev and prod boxes should be at the same basis level at all times.
>
Which release and SP level are you still on?

Proxy Classes generated by NWDS 7.1 CE

Dear Experts,
When i try to generate a proxy classes (using NWDS 7.1 CE) for the WSDL file given by PI team,
my generated classes have service.getHTTP_PORT() instead of service.getMyOperationPort().
by this, please let me know, if my proxy classes are generated correctly, if not what should i do to generate them correctly.
Thanks in Advance
Hari Krishna. D

HI,
You are not able to see all those options becuase the NWDs might be not installed completely.
Open NWDS & Goto Help --> software updates, it will update the NWDS from SAP market place and then you may be able to see all those options.
Thanks
Swarup

SAP Connector / Proxy Classes

Similar Messages

Maybe you are looking for