You are on page 1of 7

4.9.

2 Installing the DAC Server on UNIX
Oracle does not provide an installer for DAC on UNIX. To install a DAC Server on UNIX, you need to copy the \dac folder from the Windows machine on which the DAC Client is installed to a UNIX machine, as described in the procedure below. Note: You can also use this procedure to install the DAC Server on Linux. When installing a DAC Server, note the following prerequisites:

On the UNIX machine, make sure the following are installed: o JDK version 1.6.0 or higher o Zip and unzip utility Make sure that Informatica PowerCenter Services is co-located on the machine that will host the DAC Server. For more information, see Section 4.6, "Installing Informatica PowerCenter." Make sure that Informatica has been configured according to the instructions in Section 4.8, "Configuring Informatica PowerCenter Components."

To install the DAC Server on a UNIX machine 1. On the Windows machine on which the DAC Client is installed, create a temporary directory (for example, a directory named \OracleBI_UNIX\). You will use this temporary directory to create a zip file for the UNIX or Linux deployment. 2. On the machine where the DAC Client is installed, copy the \dac directory (that is, the directory installed by the DAC installer in \orahome\10g\bifoundation) to the temporary directory (for example, \OracleBI_UNIX\). 3. From the \dac directory in the temporary directory, remove the \export and \icons subfolders. These folders do not need to be copied to the machine hosting the DAC Server. 4. Zip up the temporary directory (for example, \OracleBI_UNIX\). 5. Copy the zip file to the target UNIX machine. Note: If you use FTP to copy the zip file, use binary mode. 6. On the target UNIX machine, place the zip file in a directory where you want to install the DAC Server. 7. On the target machine, unzip the zip file.

Shell scripts are provided in the /dac directory. The test is successful if the pmrep and pmcmd prompts appear. 4.6. thirdparty JDBC drivers for the databases are not supported. If pmrep and pmcmd are not recognized. Copy the contents of the /dac/unix_script_bkp directory into the /dac directory. The JDBC drivers that are used should be for the databases supported. Verify that the PATH variable includes the path to the Informatica binaries (\Informatica\PowerCenter\server\bin). "About the DAC Server Shell Scripts. you might need to use a MS-DOS to UNIX conversion tool to convert the script files to UNIX format (that is. Note: This section applies to Windows. Currently." 8. A. Edit the config.9. To enable DAC database connectivity. How to Verify the DAC Server Is Able to Use pmrep and pmcmd From a Windows command prompt. The instructions in this section use the Windows folder path format. see Section A. Since JDBC drivers show variations with different database versions.1. you can manually remove the carriage return and line feed characters from the script files. For more information.6.infa file located in the Informatica directory. execute pmrep and then pmcmd. UNIX and Linux. After copying these files to a UNIX machine and before using them. Verify that the INFA_DOMAINS_FILE variable points to the domains.2 How to Set Environment Variables for DAC Server Communication on UNIX . only drivers that are shipped with the database or downloaded from database vendor site and known to be certified for the given database version should be used.3 Installing JDBC Drivers for DAC Database Connectivity DAC requires JDBC drivers for database connectivity. Alternatively.7. then:    Ensure Hotfix 6 has been applied to Informatica PowerCenter 8. remove the carriage return and line feed characters). you must install the appropriate JDBC driver in the dac\lib directory on the machines where the DAC Client and Server are installed. 9.sh file located in the /dac directory to point to the correct version of the JDK by setting the JAVA_HOME environment variable.

3.sh and dac_env_811./config. see Section A. Use the dac_env. . Note: The files dac_env_714. invoke pmcmd.) For example.1/server/bin 4.This procedure is required for DAC Server deployments on UNIX. (Include the file name in the value.sh to set environment. change the following line from: DAC_PMCMD_PATH=%INFORMATICA_SERVER_LOCATION%/server/bin to DAC_PMCMD_PATH=Informatica/PowerCenter8.INFA_FILE_LOCATION% to the directory that contains the domains.sh file for editing. For example. Set the value for each instance of the variable %DOMAINS.sh. change the following line from: export INFA_DOMAINS_FILE=%DOMAINS.INFA_FILE_LOCATION% to How to Verify the DAC Server on UNIX or Linux Is Able to Use pmrep and pmcmd Invoke config.6.sh file to set the appropriate environment variables on UNIX. Then.6. For more information on the DAC Server scripts.infa file. ." Note: When you use the DAC installer to install the DAC Server on Linux. this configuration is done automatically.) For example. Set the value for each instance of the variable %INFORMATICA_SERVER_LOCATION% to the directory that contains the Informatica server directory. "About the DAC Server Shell Scripts.1. (Do not include the server directory.7. To set environment variables for DAC Server Communication on UNIX 1. . 2.sh are backup files used for Information PowerCenter deployments prior to version 8. Navigate to the /DAC directory. Open the dac_env.

sh is pointing to a non-existent or incorrect Java JDK location. Then. or the Java version is lower than 1. and make sure that invoking pmrep starts the pmrep shell.6 export JAVA_HOME A. Verify Java availability and version by typing the following command: 3. For example: . On some shells. invoke pmrep. Table A-2 Oracle Business Analytics Warehouse Scripts for Bash and C Shells . $JAVA –version The Java version is returned. export commands in dac_env. then the location of the PowerCenter Services is not properly added to PATH in dac_env.6. If you get a 'command not found' error. If you get a 'command not found' error.sh might not work correctly. from: export JAVA_HOME=/opt/java1.7 About the DAC Server Shell Scripts Shell scripts are provided in the *. then the JAVA_HOME parameter in config. then the location of the PowerCenter Services is not properly added to PATH in dac_env.sh to set environment. Review all environment variable settings to ensure they are correctly set.sh 2. These files contain comments that provide information about how to configure the scripts.sh and config. If you receive a 'command not found' error message./config.sh.Make sure that invoking pmcmd starts the pmcmd shell.6 To: JAVA_HOME=/opt/java1. Review all environment variable settings to ensure they are correctly set. Table A-2 lists the available shell scripts and their usage. try breaking the commands in two. In this case. A. For example. .sh.sh format. Invoke config.3 How to Verify Java JDK Availability and Version To verify that the DAC Server uses the correct Java JDK: 1.6.

Shuts down the DAC Server. See the file for usage information. and execute permissions.sh startserver. Starts the DAC Server on machines running Solaris or Linux.sh stopserver. Starts the DAC Server on AIX machines.7 About the DAC Server Shell Scripts Shell scripts are provided in the *. Invokes DAC commands on the DAC Server. See the file for usage information.sh Configures the environment variables for DAC_HOME and JAVA_HOME.sh startserver. Configures environment variables for the DAC Server. Starts the DAC Server on machines running Solaris or Linux. and HP. serverSetupPrompt. Table A-2 Oracle Business Analytics Warehouse Scripts for Bash and C Shells Script Purpose config. serverSetupPrompt. and HP. Displays the DAC Server version. write. modify them using the chmod command.sh dac_env. Invokes DAC commands on the DAC Server.sh Configures DAC metadata repository connection information. A.sh Configures the environment variables for DAC_HOME and JAVA_HOME. Configures environment variables for the DAC Server.sh serverinfo.Script Purpose config.sh format. If the files do not have these permissions. These files contain comments that provide information about how to configure the scripts. Displays the DAC Server version.sh Configures DAC metadata repository connection information. Table A-2 lists the available shell scripts and their usage.sh dacCmdLine. .sh dacCmdLine.sh dac_env.sh serverinfo. Note: The files listed in Table A-2 need to have read.sh startserver_aix.

In bash-related shells. In this case. There are many MS-DOS to UNIX conversion tools that are freely available for download on the Internet.sh might not work correctly. Before you can start the DAC Server. try breaking the commands in two. For example. issue the following command: . On some shells.sh 2>&1 & The nohup command allows the DAC Server to run in the background on UNIX even if the DAC Client is disconnected. In bash-related shells./startserver. issue the following command: nohup startserver.sh and dac_env.6 export JAVA_HOME Follow these procedures to start and stop the DAC Server on UNIX. Alternatively.sh files Follow these procedures to start and stop the DAC Server on UNIX.sh To run the DAC Server in the background 1. issue the following command: .6 To: JAVA_HOME=/opt/java1. you must have already configured the config.sh files. remove the carriage return and line feed characters). To stop the DAC Server 1.When you copy across these files. change the command from: export JAVA_HOME=/opt/java1.sh and config. In bash-related shells. you must have already configured the config. you can manually remove the carriage return and line feed characters from the script files. To start the DAC Server 1. convert the script files to UNIX format (that is. Before you can start the DAC Server.sh and dac_env. export commands in dac_env. use a MS-DOS to UNIX conversion tool.

The next time the DAC Server starts. it will shut down even if there is an ETL in progress. . it will set the status to Failed for any uncompleted run./stopserver./stopserver.. The statuses for the ETL run will not be set correctly.sh.sh Note: When you execute . When the server receives the request. the server will issue a warning about the shutdown request.