Siebel Analytics Applications Installation and Administration Guide > Installing and Configuring Siebel Analytics 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
• Setting the SiebelUnicodeDB 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

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

To set the PATH environment variable for the Informatica server

• In the Windows System Properties window, add to the PATH environment variable the path for the Informatica Server bin directory.

Setting the SiebelUnicodeDB Environment Variable on Windows

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

To set SiebelUnicodeDB 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 your [user_OLTP]@[connectString_OLTP] [user_OLAP]@[ConnectString_OLAP].

   For example, siebel@db204007 siebel@db204008.

   • For Oracle and DB2, leave a space between siebel@db204007 and siebel@db204008.
   • For MSSQL, use the system DNS 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.

To disable bulk loading for DB2/390 databases

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