Using Linked Servers Technology Specific Requirements

7-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator ■ Windows Firewall should be configured to allow the MSDTC service on the network. By default, the Windows Firewall blocks the MSDTC program. ■ The Microsoft SQL Server must be started after MSDTC has completed its startup. See the following links for more information about configuring the MSDTC Service: ■ http:support.microsoft.com?kbid=816701 ■ http:support.microsoft.com?kbid=839279

7.2.3 Connectivity Requirements

This section lists the requirements for connecting to a Microsoft SQL Server database. JDBC Driver Oracle Data Integrator is installed with a default Microsoft SQL Server Datadirect Driver. This drivers directly uses the TCPIP network layer and requires no other installed component or configuration. You can alternatively use the drivers provided by Microsoft for SQL Server.

7.3 Setting up the Topology

Setting up the Topology consists of: 1. Creating a Microsoft SQL Server Data Server 2. Creating a Microsoft SQL Server Physical Schema

7.3.1 Creating a Microsoft SQL Server Data Server

A Microsoft SQL Server data server corresponds to a Microsoft SQL Server server connected with a specific user account. This user will have access to several databases in this server, corresponding to the physical schemas in Oracle Data Integrator created under the data server.

7.3.1.1 Creation of the Data Server

Create a data server for the Microsoft SQL Server technology using the standard procedure, as described in Creating a Data Server of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. This section details only the fields required or specific for defining a Microsoft SQL data server: 1. In the Definition tab: ■ Name : Name of the data server that will appear in Oracle Data Integrator ■ Server : Physical name of the data server ■ UserPassword : Microsoft SQLServer user with its password 2. In the JDBC tab: ■ JDBC Driver : weblogic.jdbc.sqlserver.SQLServerDriver ■ JDBC URL : jdbc:weblogic:sqlserver:hostname:port[;property=value[;...]] Microsoft SQL Server 7-5

7.3.2 Creating a Microsoft SQL Server Physical Schema

Create a Microsoft SQL Server physical schema using the standard procedure, as described in Creating a Physical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. The work schema and data schema in this physical schema correspond each to a databaseowner pair. The work schema should point to a temporary database and the data schema should point to the database hosting the data to integrate. Create for this physical schema a logical schema using the standard procedure, as described in Creating a Logical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator and associate it in a given context.

7.4 Setting Up an Integration Project

Setting up a project using the Microsoft SQL Server database follows the standard procedure. See Creating an Integration Project of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. It is recommended to import the following knowledge modules into your project for getting started with Microsoft SQL Server: ■ IKM MSSQL Incremental Update ■ IKM MSSQL Slowly Changing Dimension ■ JKM MSSQL Consistent ■ JKM MSSQL Simple ■ LKM File to MSSQL BULK ■ LKM MSSQL to MSSQL BCP ■ LKM MSSQL to MSSQL LINKED SERVERS ■ LKM MSSQL to ORACLE BCP SQLLDR ■ LKM SQL to MSSQL BULK ■ LKM SQL to MSSQL ■ CKM SQL. This generic KM is used for performing integrity check for SQL Server. ■ RKM MSSQL

7.5 Creating and Reverse-Engineering a Microsoft SQL Server Model

This section contains the following topics: ■ Create a Microsoft SQL Server Model ■ Reverse-engineer a Microsoft SQL Server Model

7.5.1 Create a Microsoft SQL Server Model

Create a Microsoft SQL Server Model using the standard procedure, as described in Creating a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator.