Establishing a Connection to the Oracle Database
The Microsoft BizTalk Adapter for Oracle Database is a Windows Communication Foundation (WCF) custom binding. As such, it enables communication to an Oracle database through a WCF endpoint address. In WCF, the endpoint address is typically expressed as a Uniform Resource Identifier (URI), which identifies the network location of the service. The Oracle Database adapter expresses this location as a connection URI, which contains properties that the Oracle Database adapter uses to establish a connection to the Oracle database.
You must specify a connection URI when you:
Create a channel factory or a channel listener using the WCF channel model or when you create a WCF client or service host using the WCF service model.
Create a physical port binding in a BizTalk Server solution.
Use the Add Adapter Service Reference Visual Studio Plug-in to generate a WCF client class or WCF service interface for a WCF service model solution.
Use the Consume Adapter Service BizTalk Project Add-in to retrieve message schemas from the Oracle Database adapter for a BizTalk Server solution.
Use the ServiceModel Metadata Utility tool (svcutil.exe) to generate a WCF client class or WCF service interface for a WCF service model solution.
The Oracle Database adapter supports two ways of establishing a connection to the Oracle database:
- Using tnsnames.ora. In this approach, the connection URI provided by the adapter client contains only the net service name specified in the tnsnames.ora file. The adapter extracts the connection parameters such as server name, service name, port no, etc. from the net service name entry in the file. To use this approach, the computer running the Oracle client must be configured to include the net service name for the Oracle database in the tnsnames.ora file.
Important Due to an Oracle Client limitation, the DataSourceName parameter (net service name) in the connection URI cannot contain more than 39 characters if you are performing operations in a transaction. Therefore, make sure that the value specified for the DataSourceName parameter is less than or equal to 39 characters if you will be performing operations in a transaction.
- Without using tnsnames.ora. In this approach, the adapter clients specify the connection parameters directly in the connection URI. This does not require the net service name to be present in the tnsnames.ora file on the client computer. This approach does not even require the tnsname.ora file to be present on the client computer.
Important This mode of connectivity is not supported if you are performing operations in a transaction. This is due to a limitation of Oracle Client.
The topics in this section describe how to establish a connection between the Microsoft BizTalk Adapter for Oracle Database and the Oracle database by providing you with:
Information about configuring the Oracle client.
Information about the connection properties and the structure of the Oracle connection URI.
Links to topics that show how to establish a connection by using the Oracle Database adapter.
Information about connecting to the Oracle database using Windows Authentication.