Here's what I was looking for....I should award myself points...
<b>Does SAP connector for Microsoft .NET 2.0 support Soap calls to SAP Web Application Server 6.20 and higher?</b>
Yes, SAP connector for Microsoft .NET 2.0 supports Soap.
SAP connector for Microsoft .NET 1.x also supported Soap, but with version 2.0 the use of Soap is easier. It is now fully transparent to a client wheather RFC or Soap is used. The underlying idea is to extend the “Connection” and “Destination” model. With SAP connector for Microsoft .NET 2.0 as well as with SAP connector for Microsoft .NET 1.0, the SAPClient class (and thus all client proxies) have a “Connection” property. In SAP connector for Microsoft .NET 1.0, you had to assign a “SAPConnection” object that was the container for RFC connections. You were able to create such an object directly, for example
“proxy.Connection = new SAPConnection(connString)”
Or you were able to create an object indirectly with the SAPClient’s constructor or the “ConnectionString” property:
“proxy.ConnectionString = “…”” or “SAPProxy1 proxy = new SAPProxy(connStr);”
To build up a connection string, you could use a Destination or SAPLogonDestination object. In SAP connector for Microsoft .NET 2.0, this model has been extended: The SAPClient’s “Connection” property can contain either an object of class “RfcConnection” (which is the successor of SAPConnection) or an object of class “SoapConnection”. The new “SoapConnection” class builds the correct URLs and credentials as expected by the Soap entry of SAP Web Application Server 6.20.
A static function “SAP.Connector.Connection.GetConnection() is available that creates the correct “Connection” class for the connection string.
The following sets a SoapConnection to the proxy:
“proxy.Connection = Connection.GetConnection(“http://appserver:1080/sap/bc/soap/rfc”)
Compare this with the following, which sets an RFC connection:
“proxy.Connection = Connection.GetConnection(“ASHOST=iwdf9401 SYSNR=1 CLIENT=801 USER=hille PASSWD=***** LANG=de).
On the other hand, “Destination” and “SAPLogonDestination” have been extended to create URL connection strings instead of RFC connection strings. Therefore the connection classes have many new properties; of which the most important one is “UseSoap”. When it is set to “False” (default), the “Destination” classes work as before. When it is set to “True”, it produces an URL instead.
Destination destination1 = new Destination();
… // set properties here
destination1.UseSoap = false;
proxy.Connection = Connection.GetConnection(destination1);
// running with RFC
destination1.UseSoap = true;
proxy.Connection = Connection.GetConnection(destination1);
// running with Soap.
Connection.GetConnection exists in several overloads to support different kinds of connection and connection providers, automatic connection pooling, and so on. As it has also designer support (see “A4”), we recommend you to use this method for connection management.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.