5 Configuring DAC

System Configuration Handled by the Oracle Universal Installer

The following system configuration for Windows and Linux is handled by the Oracle Universal Installer during the installation process.

• Configuration of config.bat (Windows) and config.sh (Linux).

  On Windows this file is stored in $ORACLE_HOME\bifoundation\dac. On Linux, the directory is $ORACLE_HOME/bifoundation/dac. This file specifies the following:

  • DAC_HOME. The directory where DAC is installed. For example, on Windows:

    \orahome\10gR3_1\bifoundation\dac

  • JAVA_HOME. The directory where the Java SDK is installed. For example, on Windows:

    \orahome\10gR3_3\jdk

• Configuration of dac_env_<Informatica version>.bat (Windows) and dac.env_<Informatica version>.sh (Linux).

  On Windows this file is stored in $ORACLE_HOME\bifoundation\dac. On Linux, the directory is $ORACLE_HOME/bifoundation/dac. This file specifies the installation directories of Informatica components. See the comments at the beginning of the file for more information.

• (Windows only) Registration and configuration of Oracle Merant 5.0 Driver.

  For example:

  REDEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Oracle Merant ODBC Driver]
"APILevel"="1"
"ColumnsAsChar"="1"
"ColumnSizeAsCharacter"="1"
"CPTimeout"="60"
"Driver"="$ORACLE_HOME/bifoundation/dac/utilities/DataDirectODBC/seor820.dll"
"DriverODBCVer"="05.00"
"FileUsage"="0"
"Name"="Siebel Database"
"Setup"="$ORACLE_HOME/bifoundation/dac/utilities/DataDirectODBC/seor820s.dll"
"SQLLevel"="1"
"UsageCount"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
"Oracle Merant ODBC Driver"="Installed"

Installing JDBC Drivers for DAC Database Connectivity

You must install the appropriate JDBC driver in the $ORACLE_HOME\bifoundation\dac\lib directory to enable DAC database connectivity.

To install JDBC drivers in the ORACLE_HOME\bifoundation\dac\lib directory:

• Oracle. If you are using an Oracle database (other than 8.x), find the directory where Oracle is installed. Copy the file named ojdbc14.jar in the jdbc\lib directory and paste it in the $ORACLE_HOME\bifoundation\dac\lib directory.

  • If you are using Oracle 8.x, copy the file named classes12.zip and paste it in the $ORACLE_HOME\bifoundation\dac\lib directory. Also, edit the ORACLELIB setting in the config.bat file as follows:

    set ORACLELIB=%DAC_HOME%\lib\classes12.zip
    

• DB2. If you are using a DB2 database, find the directory where DB2 is installed. In the Java sub-directory copy the file named db2java.zip and paste it in the $ORACLE_HOME\bifoundation\dac\lib directory.

  Note:

  If your source or target database is DB2-UDB, you also need to create DB2-UDB stored procedures to be used during the ETL process. For instructions, see the section on creating stored procedures for DB2-UDB in the Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide.

• MSSQL. DAC is configured for Microsoft SQL Server 2005 JDBC drivers. If you are using a Microsoft SQL Server database, then download the Microsoft SQL Server 2005 JDBC Driver file sqljdbc.jar and copy it to the $ORACLE_HOME\bifoundation\dac\lib\ directory.

  You can use the Microsoft SQL Server 2000 JDBC Driver files if you edit the \conf\connection_templates.xml file and un-comment the section that starts "<!-- THIS SECTION IS FOR SQL SERVER 2000. Comment this section while using SQL Server 2005.-->.

  Download the SQL Server JDBC drivers for SQL Server 2000 from the Microsoft web site. Copy the Copy the files msbase.jar, mssqlserver.jar, and msutil.jar to the $ORACLE_HOME\bifoundation\dac\lib folder.

  Note:

  You need the Microsoft SQL Server 2005 JDBC Driver 1.1 for SQL Server 2000 or SQL Server 2005.

• Teradata. If you are using a Teradata database, copy the files tdgssconfig.jar, TdgssUserConfigFile.xml, terajdbc4.jar, log4j.jar, and tdgssjava.jar from the Teradata installation directory to the $ORACLE_HOME\bifoundation\dac\lib directory. Depending on the Teradata JDBC version, you might not have some of the above files.

Logging into DAC for the First Time

When you log into DAC for the first time, you must first configure a connection to connect to the DAC Repository. DAC stores this connection information for subsequent logins.

After configuring a connection to the DAC Repository and logging in, the DAC will automatically prompt you to upgrade the repository schema.

DAC Repository Database Authentication File

When you configure a connection to the DAC Repository, the configuration process includes creating a new authentication file or selecting an existing authentication file. The authentication file authenticates the database in which the repository resides. If you create a new authentication file, you will specify the table owner and password for the database.

A user with the Administrator role must distribute the authentication file to any user account that needs to access the specified DAC Repository. For information about managing user accounts, see About User Account Management.

To log into DAC for the first time and upgrade the repository schema:

1. Start the DAC Client by navigating to the $ORACLE_HOME\bifoundation\dac directory and double-clicking the startclient.bat file.

   The Login ... dialog box appears.

2. Click Configure.

3. In the Configuring ... dialog box, select Create Connection, and then click Next.

4. Enter the appropriate connection information:

   Field	Required Value
   Name	Enter a unique name for the connection to the DAC Repository.
   Connection type	Select the type of database in which the DAC Repository will be stored.
   Connection String, or Database name, or TNS Name, or Instance	Select the database name or database account name of the DAC Repository. If you are using: Oracle (OCI8), use the tnsnames entry. Oracle (Thin), use the instance name. SQL Server, use the database name. DB2-UDB, use the connect string as defined in the DB2 configuration.
   Database Host	Enter the name of the machine where the DAC Repository will reside.
   Database Port	Enter the port number on which the database listens. For example, for an Oracle database the default port is 1521, or for a SQL Server database the default port is 1433.
   Optional URL	Can be used to override the standard URL for this connection.
   Optional Driver	Can be used to override the standard driver for this connection.
   Authentication File	Click in this field to do one of the following: Select an existing authentication file. Create a new authentication file. Proceed to the next step for detailed instructions.

   
   

5. To select an existing authentication file, do the following:

   1. Click in the Authentication File field of the Configuring... dialog box.

   2. In the Authentication File dialog box, select Choose existing authentication file.

   3. Navigate to the appropriate folder, and select the authentication file. Click OK.

   4. In the Configuring... dialog box, click Test Connection to confirm the connection works.

   5. Click Apply, and then click Finish.

      Note:

      You must distribute this authentication file to all user accounts that need to access this DAC Repository.

6. To create a new authentication file, do the following:

   1. Click in the Authentication File field of the Configuring... dialog box.

   2. In the Authentication File dialog box, select Create authentication file.

   3. Navigate to the folder where you want to save the new authentication file, and click OK.

   4. In the Create Authentication File dialog box, enter a unique name for the authentication file, and click OK.

   5. Enter the Table Owner Name and Password for the database where the repository will reside.

   6. In the Configuring... dialog box, click Test Connection to confirm the connection works.

   7. Click Apply, and then click Finish.

      Note:

      You must distribute this authentication file to all user accounts that need to access this DAC Repository.

7. In the Login... dialog box, do the following:

   1. Select the appropriate Connection from the drop-down list.

   2. Enter Administrator as the User Name.

   3. Enter Administrator as the Password.

   4. Click Login.

8. When asked whether you want to upgrade the DAC Repository schema, click Yes.

Configuring the Connection Between the DAC Server and DAC Repository

You must configure the connection between the DAC Server and the DAC Repository.

On Windows, you can use the DAC Client to configure a DAC Server that runs in the same $ORACLE_HOME\bifoundation\dac folder. Optionally, or to configure a DAC Server installed in another folder or on another Windows machine, use the serverSetupPrompt.bat file to configure the repository connection.

On Linux, use the serverSetupPrompt.sh or serverSetupPrompt.csh script to configure the connection between the DAC Server and the DAC Repository, as follows:

• To configure the DAC Server repository connection using the DAC Client, see How to Configure the DAC Server Repository Connection Using the DAC Client (Windows).

• To configure the DAC Server repository connection using the serverSetupPrompt scripts, see How to Configure the DAC Repository Connection Using serverSetupPrompt Scripts (Windows or Linux).

About User Account Management

The User Management feature includes three roles: Administrator, Developer, and Operator. As shown in Table 5-1, each role has a set of permissions that determines what DAC functionality the role can access.

The User Management dialog box enables a user with the Administrator role to manage user accounts. A user account includes a unique identifier, password, and one or more roles. The Administrator can also inactivate a user account. For instructions on managing user accounts, see "Creating, Deleting and Inactivating User Accounts".

Upon the initial login to a new DAC installation, a user account with the Administrator role is automatically created. This default user account name is Administrator, and the default password is Administrator. It is recommended that after the initial login, the user change the default password.