Oracle^® Business Intelligence Applications Installation and Configuration Guide > Installing and Configuring Oracle BI Applications on Windows >

Setting Environment Variables on Windows

This section includes instructions for setting the following environment variables:

• Setting the PATH Environment Variable for the Informatica Server and Informatica Repository Server
• Setting the Siebel UnicodeDB Environment Variable on Windows
• Setting the Bulk Load Registry for DB2/390 Databases

NOTE:  You need to reboot your machine after setting the environment variables for the change to take effect.

Setting the PATH Environment Variable for the Informatica Server and Informatica Repository Server

The DAC server uses the pmcmd program to run the Informatica workflows on the Informatica servers. This requires the path to the bin directory for the Informatica server and repository server to be added to the Windows system PATH environment variable.

To set the PATH environment variables for Informatica

• In the Windows System Properties window, add the path for the Informatica Server bin directory (for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\bin) to the PATH environment variable.
• In the Windows System Properties window, add the path for the Informatica Repository Server bin directory (for example, C:\Program Files\Informatica PowerCenter 7.1.4\RepositoryServer\bin) to the PATH environment variable.

Setting the Siebel UnicodeDB Environment Variable on Windows

If you are using the Unicode character data mode, you need to set the Siebel UnicodeDB environment variable.

To set Siebel UnicodeDB for Windows

1. In Windows, click Start > Run.
2. In the Open field, enter regedit.
3. Navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > PowerMart > Parameters > Configuration.
4. On the right window panel, right-click and select New > String Value.
5. Rename the new string value SiebelUnicodeDB.
6. Double-click SiebelUnicodeDB.
7. In the Value data field, enter the connection string for your transactional database followed by the connect string for your data warehouse database, using the following format:

   [user_OLTP]@[connectString_OLTP] [user_OLAP]@[ConnectString_OLAP].

   For example, oltp.oltp@db204007.host.com olap.olap@db204008.host.com.

   • Always leave a space between the connection strings.
   • For MSSQL, use the system DSN name for [connectString_OLTP] and [connectString_OLAP].

     NOTE:  You must enter the user names and connect strings in the same case as you used in the Workflow Manager > Connections > Relational settings.

Setting the Bulk Load Registry for DB2/390 Databases

DB2/390 databases do not support bulk loading; therefore, you need to disable bulk loading in the Windows registry: HKEY_LOCAL_MACHINE\..\System\CurrentControlSet\Services\Powermart\Configuration area.

To disable bulk loading for DB2/390 databases

• For DB2/390 databases, enter DisableDB2BulkMode = Yes in the Windows registry.