Using the ServiceModel Metadata Utility Tool with the BizTalk Adapter for Oracle Database
You can use the ServiceModel Metadata Utility Tool (svcutil.exe) to generate a WCF client class or a WCF service contract (interface) for operations that the Microsoft BizTalk Adapter for Oracle Database exposes. After you run svcutil.exe to generate either a WCF client class or a WCF service contract, you can include the generated file in your code and create instances of the generated class or implement a WCF service from the contract to perform operations on the Oracle database.
Using svcutil.exe requires you to supply a connection URI that contains credentials. Because, by default, the Oracle Database adapter disables credentials in the connection URI, you must configure svcutil.exe to use a non-default binding for the Oracle Database adapter.
The following sections show you how to configure svcutil.exe and how to use svcutil.exe to generate WCF client code or a WCF service contract with the Oracle Database adapter.
Configuring svcutil.exe for the Oracle Database Adapter
To configure svcutil.exe to use a non-default binding, you must create a local copy of svcutil.exe and then create or modify a local copy of the svcutil.exe.config configuration file.
To configure svcutil.exe for a non-default binding
Create a folder, and copy svcutil.exe into the new folder. You can typically find svcutil.exe at the Windows SDK installation location, specifically, C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin.
Create a file named svcutil.exe.config in the new folder.
Add a binding and a client endpoint to the svcutil.exe.config file. You must run svcutil.exe from the new folder to ensure that the correct configuration is used.
Important The name attribute of the client endpoint must specify the scheme used in the connection URI. This value is case-sensitive.
<configuration> <system.serviceModel> <client> <!-- the name should match the required scheme of the WS-Metadata Exchange endpoint and the contract should be "IMetadataExchange" --> <endpoint name="oracledb" binding="oracleDBBinding" bindingConfiguration="OracleDBBinding" contract="IMetadataExchange" /> </client> <bindings> <oracleDBBinding> <binding name="OracleDBBinding" acceptCredentialsInUri="true" /> </oracleDBBinding> </bindings> </system.serviceModel> </configuration>
|You can set any of the binding properties of the Oracle Database adapter in the binding configuration.|
For more information about configuring a non-default binding for svcutil.exe, see the "Custom Secure Metadata Endpoint" topic in the WCF documentation at http://go.microsoft.com/fwlink/?LinkId=96077.
Configuring a Non-Default Binding for the POLLINGSTMT Operation
To use svcutil.exe to create a WCF service contract for the POLLINGSTMT operation, you must configure the non-default binding to include the pollingStatement property, in addition to acceptCredentialsInUri. The pollingStatement must contain the SELECT statement that targets the table. The Oracle Database adapter uses this property to generate the class that represents the strongly-typed result set that the POLLINGSTMT operation returns. The following example shows a binding configuration that is used to generate a WCF service contract for a POLLINGSTMT operation that targets the /SCOTT/EMP table.
<bindings> <oracleDBBinding> <binding name="OracleDBBinding" acceptCredentialsInUri="true" pollingStatement="SELECT * FROM EMP FOR UPDATE" /> </oracleDBBinding> </bindings>
Creating a WCF Client Class or WCF Service Contract with svcutil.exe
To use svcutil.exe to generate WCF client code or a WCF service contract (interface) for the Oracle Database adapter, you must supply a connection URI that specifies an WS-Metadata Exchange (MEX) endpoint and the operation or operations for which you want svcutil.exe to generate code. You must also specify connection credentials for the Oracle database in the connection URI.
|Before you can use svcutil.exe with the Oracle Database adapter, you must configure it to use a non-default binding; for information about how to do this, see Configuring svcutil.exe for the Oracle Database Adapter.|
You specify a MEX endpoint and target operations in the Oracle Database adapter connection URI in the following manner:
You must include the "wsdl" parameter in the query_string. If it is the first parameter in the query_string, it is specified just after the question mark (?). If it is not the first parameter, it should be preceded with an ampersand (&).
You must follow the "wsdl" parameter by one or more "op" parameters. Each "op" parameter is preceded by an ampersand (&) and specifies the node ID of a target operation.
The following three examples show how to target various operations by using svcutil.exe.
This example creates a WCF client class for an Insert operation on the /SCOTT/EMP table.
This example creates a WCF client class for the Insert and the Delete operations on the /SCOTT/EMP table.
This example creates a WCF service contract for the POLLLINGSTMT operation. (To use svcutil.exe to generate a WCF service contract for the POLLINGSTMT operation, you must configure a non-default binding for svcutil.exe that includes a polling statement.)
|You must place the connection URI in quotation marks on the command line. Otherwise, svcutil.exe attempts to retrieve metadata for operations that the Oracle Database adapter does not support. The results of such an attempt are undefined.|
By default, svcutil.exe places the generated code in the output.cs file; however, you can change the name of the output file and many other options that svcutil.exe uses by setting command-line switches. For more information about the options that svcutil.exe supports, see the "ServiceModel Metadata Utility Tool (Svcutil.exe)" topic in the WCF documentation at http://go.microsoft.com/fwlink/?LinkId=72777.
Svcutil.exe does not provide the capability to search for operations (for example, by using wildcard characters). You must explicitly specify node IDs for the specific operations you want to target. You cannot specify node IDs that refer only to categories. For more information about the node IDs that the Oracle Database adapter surfaces, see Metadata Node IDs.
The Add Adapter Service Reference Visual Studio Plug-in provides advanced browse and search capabilities that can greatly simplify generating a WCF client class and WCF service contract. For more information about the Add Adapter Service Reference Plug-in, see Generating a WCF Client or a WCF Service Contract for Oracle Database Artifacts.
© 2014 Microsoft Corporation. All rights reserved.