Using the .NET Web service engine
Generating a .NET assembly
The .NET Web service engine
supports the latest Web service standards. To use this engine, you
must have the wsdl.exe Web service tool on
the development machine. This tool is required to parse WSDL files
and generate C# code for a .NET assembly. The wsdl.exe file
installs with the .NET SDK. It is not required on deployment machines,
although deployment machines must have the .NET Framework to consume
a Web service that depends on the .NET Web service engine.
If you select the .NET Web service engine in the Web Service
Proxy wizard, the wizard generates a .NET assembly (DLL) in addition
to a proxy object. To use the Web service at runtime, you must deploy
the wizard-generated DLL along with your application.
You can also select the .NET Web service engine in the Project
painter for a new Web service proxy. If you select the .NET Web
service engine on the Web Service tab of the Properties dialog box
for the Web Service Proxy Generator, PowerBuilder attempts to generate
an assembly DLL after you click Apply or OK. You cannot use the
Properties dialog box to change the Web service engine for a proxy
that you already generated with the Web Service Proxy wizard.
Naming the DLL
You can name the DLL generated by the Web Service Proxy wizard
or by the Project painter in the Proxy Assembly Name text box. You
do not need to include the DLL extension. The name of the wizard-generated
assembly is Web_service.DLL, where Web_service is
the name you provide in the Proxy Assembly Name field. If you do
not provide a name, the assembly takes the name of the Web service
to be consumed by the DLL. The assembly is generated in the current
target directory.
Deploying the DLL
You must deploy the DLL created for your Web service project
to the directory where you deploy the client executable. You must
also copy the Sybase.PowerBuilder.WebService.Runtime.dll and
the Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll system assemblies
to this directory.
Extension objects
Although you use the same SOAP connection and exception-handling
objects for the .NET Web service engine as for the EasySoap Web
service engine, the objects that reference the .NET Web service
engine require a different extension file or library.
The methods available on the SoapConnection object depend
on which extension file or library you are using and on which Web
service engine you are using. The methods for a .NET Web service
engine allows you to include security information in the SOAP client
header.
For more information, see “Importing objects from an
extension file.”
Temporary directory access requirement
The .NET Web service engine requires client applications to
access the system defined temporary directory on the client computer.
The client must have read/write permission for the temporary
directory or a “Cannot invoke the web service” error occurs. The
temporary directory is set by the TEMP user environment variable.