Migrating from VS 2003 to VS 2005 - SAP ESE Explorer

[Former Member]

We are migrating a web application(which uses SAP Conector) from Visual Studio 2003 to 2005.Currently, VS 2003 version is using SAP connector to access SAP functions.Now, in VS 2005 we are planning to use SAP ES Explorer.We need to know how to use the existing sapwsdl file with SAP ES Explorer.Or is there any other way to migrate the application using SAP ES Explorer without using service registry.Please reply as soon as possible as we are not able to proceed further.Expecting your quick response.

Thank You,

Juhi

[Former Member]

Hi,

No information about SAP ES Explorer. But I have another soution method as mentioned above.

You can refer your dll that is created in VS2003 to VS2005. I have an technical article for this desire. you can examine it.

http://www.huseyinakturk.net/2009/01/a-comprehensive-example-for-connection-to-sap-with-visual-studi...

Regards,

Huseyin Akturk

[Former Member]

Hi,

SAP ES Explorer is an Add-in to Microsoft VS 2005/2008 which enables the user to search/browse for SAP eSOA services above SAP Services Registry and generate its proxy class (like "Add Web Reference" / "Add WCF Reference" are doing), which enables you to execute the Web Services.

It is not some kind of "Migration tool" for WSDL's which were discovered by the SAP Connector.

SAP ES Explorer "work" is only on the "design time" side, by searching over the SR and generating the Web Service proxy class, it has no impact on the "Runtime" side of the application.

So, if you need to search for SAP eSOA services over the SR and use them in your application, SAP ES Explorer is the tool for you.

I am not an expert on how to use the SAP Connector, but why do you think that the way you are using the SAP WSDL's on runtime in VS 2003 will not work on VS 2005 or higher ? isn't it working the same way ? i was expecting that VS 2003 will discover the service you look for and generate the proxy class which you should be able to use also on other versions.

you can use the following link for more information about SAP ES Explorer:

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10cacdca-b0bb-2a10-77be-d600de46...

Regards,

Nadav (SAP ES Explorer team member)

[Former Member]

Hi,

We have a web application in VS 2003 which uses the sapwsdl file (created using SAP Connector). So our aim is to convert the existing sapwsdl and use it in VS 2005 web application.

As per the artifacts that we got from SAP site, for using SAP ESE we should have access to SAP registry to access the webservice.

But we checked with our client regarding the SAP registry and we came to know that they don't have any sap registry in place.

So we need to know how to reuse the exiting sapwsdl using SAP ESE (without sap registry) or Is there any other way to access the sap functions using VS 2005.

Thanks Nadav Margalit for the quick response and expecting your quick response for this as our project is not able to proceed further.

Regards,

Juhi

[Former Member]

Hi Juhi,

You can possibly compile the proxy Dll in VS 2003 environment and then refer the same from VS 2005.

VS 2005 design time environment is not supported by .Net Connector however runtime support is there.

Regards.