Connect to Oracle Database or eBusiness Suite in a BizTalk Services Project
Updated: November 21, 2013
There are three overall steps in creating connectivity to an Oracle database or Oracle eBusiness Suite application from a BizTalk Services project.
Create an LOB Target for Oracle.
Note To create an LOB Target for Oracle, you must be a member of the local Administrators group and have the System Administrator right on the back-end SQL server and the on-premises source Oracle system. Important Visual Studio must be opened with Administrative privileges to use BizTalk Adapter Service.
Use the LOB Target
Generate schema for the operation to be performed on Oracle.
To add an LOB Target for Oracle
In Server Explorer, expand BizTalk Adapter Service, expand the Management URL, and then expand LOB Types.
Right-click Oracle DB or Oracle EBS and click Add Oracle Target. This opens the Add a Target wizard:
In the Welcome window, click Next.
In Connection Parameters, specify the following:
Server: The server name or IP address of the Oracle system and optionally, the port number. If the port number is not specified, port 1521 is used. To specify a different port, enter ComputerName:PortNumber.
Service Name: Required when Server is specified.
Advanced: Click this button to configure additional Connection Properties and any Binding Properties:
In the Binding Properties tab, refer to Working with BizTalk Adapter for Oracle Database Binding Properties or Working with BizTalk Adapter for Oracle E-Business Suite Binding Properties.
Required. Default is 1521, which is the typical Net Listener for Oracle.
Required. The name or the IP address of the Oracle server.
Optional. The name of the Oracle service.
Required. Default is Dedicated. Options include:
Uses a single server process to serve a single user process.
Uses a shared server process that can that can serve multiple user processes.
Optional: The Oracle Transparent Network Substrate (TNS) network alias.
If specifying the ServerAddress and ServiceName, do not enter a DataSource. If not specifying the ServerAddress and ServiceName, enter a DataSource.
Important The TNS network alias may be case-sensitive.
The Oracle Database Connection URI and The Oracle E-Business Suite Connection URI provide additional information.
Specify the credentials: Enter the credentials to authenticate to the on-premises source Oracle system. Options include:
Use Windows Credentials
The logged on user credentials will be used to connect to the source Oracle system.
Use the following UserName and Password:
Enter a User name and Password that can connect to the source Oracle system.
Important User names in Oracle are case-sensitive. For release 10g and earlier, passwords on the Oracle system are not case-sensitive.Click Next. Note Not all options may be available for this LOB adapter.
- Server: The server name or IP address of the Oracle system and optionally, the port number. If the port number is not specified, port 1521 is used. To specify a different port, enter ComputerName:PortNumber.
In Operations, expand the node, select the database operations and click the right arrow:
Browsing, Searching, and Retrieving Metadata for Oracle Operations and Browsing, Searching, and Retrieving Metadata for Oracle E-Business Suite Operations provide additional details on selecting an operation.
To see the operation’s generated WSDL, select the operation, and click Properties.
In Runtime Security, specify the security type. This security type determines how the client message is authenticated with the LOB Target. Options include:
Select this option if you are using a username and password created locally on the LOB system.
Custom SOAP Header
Select this option if you create a custom SOAP header to include the username and password.
Select this option if you are including the logon credentials in the WS-Security header of the message.
In Deployment, choose an existing LOB Relay or create a new LOB Relay.
Tip A single LOB Relay can be used with multiple LOB Targets. There are restrictions based on the security model. As a best practice, group the same security method in one LOB Relay. For example, use the same LOB Relay to host the LOB Targets that use the Message Credential or Fixed Windows credential security type.
To create a new LOB Relay:
Required. Enter your Service Bus namespace because the LOB relay will be created in the Service Bus. The namespace name is available in the Azure Management Portal after you sign-in.
Required. The Service Bus Issuer Name. Issuer Name is available in the Azure Management Portal after you sign-in. The correct Issuer Name must be specified.
Required. The Service Bus Issuer Secret key. Issuer Secret is available in the Azure Management Portal after you sign-in. The correct Issuer Secret must be specified.
Required. Enter the desired name of the relay path. For example, if you use chose Fixed Windows credential option for Runtime Security, you can enter something like WindowsAuthRelay.
Required. Enter a sub-path to make this target unique. For example, you can enter GetOrder.
Target runtime URL
This is automatically populated with the namespace name, relay path and target sub-path specified. If using the examples above, it will be populated with something like:
Summary shows your configured values. Click Create.
When complete, click Finish. The following activities occur in the background:
The LOB Target is created in Server Explorer. It can be disabled, started and deleted. Its configuration can also be exported.
The LOB Target is created as an application in IIS. This application uses the Runtime for this specific LOB Target. Runtime Components: BizTalk Adapter Service describes the IIS components.
- The LOB Target is created in Server Explorer. It can be disabled, started and deleted. Its configuration can also be exported.
To use the LOB Target
Right-click anywhere on the BizTalk Service project design surface, select Properties and update the BizTalk Service URL property to include your BizTalk Services name. This is the name that you provided in Azure Management Portal while provisioning the BizTalk Services.
Set the security property for the relay endpoint.
Right-click the relay endpoint in Server Explorer and select Properties.
In the Properties grid, click the ellipsis (…) against the Runtime Security property.
In the Edit Security dialog box, select the security method you want to use and specify the relevant values.
- Right-click the relay endpoint in Server Explorer and select Properties.
Drag and drop the LOB Target onto the design surface. Note the Entity Name property of the LOB Target. The default value of the property is Relay-Path_target-sub-path.
Open the .config file for the LOB target, which typically has the naming convention as RelayPath_target-sub-path.config. Specify the Service Bus issuer name and issuer secret, as shown below:
<tokenProvider> <sharedSecret issuerName="owner" issuerSecret="issuer_secret" /> </tokenProvider>
Save changes to the config file.
Once a LOB Target is configured and added to the design surface, add a XML One-Way Bridge or a XML Request-Reply Bridge to be the source. Use Connector in the Toolbox to connect the bridge to the LOB Target, similar to the following:
|The bridge uses the Relative Address property of the LOB Target to send messages to the on-premises LOB system.|
To generate the schema
In the BizTalk Service project, in the Server Explorer, right click the LOB Target you created, and then click Add schemas to <project_name>. The Schema Generation dialog pops up.
Specify a file name prefix. This value will be prefixed with all the schema files that are generated. You can also specify the folder name under which the schemas will be added in the Visual Studio Solution Explorer. The default value for the folder is LOB Schemas.
Select a credential type to generate the schema, provided appropriate values for authentication, and then click OK.
The schemas are added to the project under the folder name.