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

Installing and Configuring the Informatica Server on UNIX

The instructions in this section for installing and configuring the Informatica Server are meant to be followed immediately after the Informatica Repository Server installation, without exiting the installer. If you exited the installer after installing the Repository Server, you may want to review Installing and Configuring the Informatica Repository Server on UNIX.

NOTE:  You can install and configure two Informatica Server instances on the same UNIX machine. This configuration requires two copies of pmserver.cfg and pmrepserver.cfg files. Each file must have a unique name, for example, pmserverdev.cfg and pmserverQA.cfg. Each config file will define unique ports for each instance of the Informatica Server.

NOTE:  Even if you run the Informatica server from a different machine to the DAC server machine, you still must install Informatica on the DAC server machine, because the DAC server requires the Informatica libraries (utility pmcmd).

To install and configure the Informatica Server

1. Select Informatica PowerCenter Server from the list of components available to install.
2. Specify the directory where the Informatica Server will be installed.
3. Enter the appropriate values for the options listed below.

   Option	Required/Optional	Description
   Configuration file name	Required	The name of the Informatica Server configuration file.
   ServerName	Required	The name of the Informatica Server registered with the repository. It is recommended that you use ORACLE_BI_DW_SERVER.
   RepositoryName	Required	The repository name entered when creating or upgrading a repository. It is recommended that you use Oracle_BI_DW_Base.
   PMUser	Required	The repository user name used to connect to the repository. It is recommended that you use Administrator
   PMPassword	Required	The password corresponding to the repository user (PMUser). It is recommended that you use Administrator.
   RepServerHostName	Required	The host name of the machine hosting the Repository Server.
   RepServerPortNumber	Required	The port number the Repository Server uses to communicate with repository client applications.
   RepServerTimeout	Required	The maximum number of seconds the Informatica Server tries to establish a connection to the Repository Server.
   LogFileName	Optional	The filename of the Informatica Server log file.
   DataMovementMode	Required	Possible values are ASCII and UNICODE. The default data movement mode is ASCII, which passes 7-bit ASCII character data. To pass 8-bit ASCII and multibyte character data from sources to targets, use the Unicode mode. NOTE:  If you use the UNICODE mode, you should set the ValidateDataCodePages option as No and the SessionLogInUTF8 option as Yes.
   ValidateDataCode Pages	Required	If set to Yes, the Informatica Server enforces data code page compatibility. If set to No, the Informatica Server lifts restrictions for source and target data code page selection, stored procedure and lookup database code page selection, and session sort order selection. NOTE:  If you set the DataMovementMode option to UNICODE, you should set the ValidateDataCodePages option as No.
   SessionLogInUTF8	Required	If set to Yes, the Informatica Server writes to the session log using the UTF-8 character set. If set to No, the Informatica Server writes to the session log using the Informatica Server code page. NOTE:  If you set the DataMovementMode option to UNICODE, you should set the SessionLogInUTF8 option as Yes.
   MaxSessions	Required	The maximum number of sessions stored in shared memory. This sets the maximum number of sessions the Informatica Server can run in parallel.
   LMSharedMem	Required	The amount of shared memory available for use by the Informatica Server Load Manager process. For every 10 sessions in MaxSessions, you need at least 2,000,000 bytes reserved in LMSharedMem. The default is 2,000,000 bytes.
   TimeStampWorkflowLogMessages	Optional	Set to Yes if you want to append a time stamp to messages written to the workflow log.
   FailSessionIfMax SessionsReached	Optional	Set to Yes to have the Informatica Server fail the session if the number of sessions already running is equal to the value configured for MaxSessions. If you set this option to No, the Informatica Server places the session in a ready queue until a session slot becomes available.
   ExportSessionLogLibName	Optional	If you want the Informatica Server to write session log messages to an external library, enter the name of the library file.
   ErrorSeverityLevel	Optional	The level of error messages written to the Informatica Server log. Specify one of the following message levels: Error. Writes ERROR code messages to the log. Warning. Writes WARNING and ERROR code messages to the log. Information. Writes INFO, WARNING, and ERROR code messages to the log. Tracing. Writes TRACE, INFO, WARNING, and ERROR code messages to the log. Debug. Writes DEBUG, TRACE, INFO, WARNING, and ERROR code messages to the log.
   DateHandling40 Compatibility	Optional	Set to Yes if you want the Informatica Server to handle dates as in PowerCenter 1.0/PowerMart 4.0. Set to No if you want the Informatica Server to handle dates as defined in the current version of PowerCenter. Date handling significantly improved in PowerCenter 1.5 and PowerMart 4.5. If you need to revert to PowerCenter 1.0 or PowerMart 4.0 behavior, you can configure the Informatica Server to handle dates as in PowerCenter 1.0 and PowerMart 4.0.
   PMServer3X Compatibility	Optional	Set to Yes if you want the Informatica Server to handle dates as in PowerCenter 1.0/PowerMart 4.0. Set to No if you want the Informatica Server to handle dates as defined in the current version of PowerCenter. Date handling significantly improved in PowerCenter 1.5 and PowerMart 4.5. If you need to revert to PowerCenter 1.0 or PowerMart 4.0 behavior, you can configure the Informatica Server to handle dates as in PowerCenter 1.0 and PowerMart 4.0.
   AggregateTreatNull AsZero	Optional	Set to 1 to have the Informatica Server treat nulls as zero in Aggregator transformations. Set to 0 to have the Informatica Server treat nulls as nulls in aggregate calculations.
   AggregateTreatRow AsInsert	Optional	Set to 1 to have the Informatica Server perform aggregate calculations before flagging records for insert, update, delete, or reject in Update Strategy expressions. Set to 0 to have the Informatica Server perform aggregate calculations based on the Update Strategy transformation.
   DateDisplayFormat	Required	If specified, the Informatica Server validates the date display format and uses it in session log and server log entries. If the date display format is invalid, the Informatica Server uses the default date display format. The default date display format is DY MON DD HH 24:MI:SS YYYY.
   JoinerSourceOrder 6xCompatibility	Optional	If set to Yes, the Informatica Server processes master and detail pipelines sequentially as it did in versions prior to 7.0. The Informatica Server processes all data from the master pipeline before starting to process the detail pipeline. Also, if you enable this option, you cannot specify the Transaction level transformation scope for Joiner transformations. If set to No, the Informatica Server processes the master and detail pipelines concurrently.
   TreatNullIn ComparisonOperatorAs	Required	Determines how the Informatica Server evaluates null values in comparison operations. Specify one of the following options: Null. The Informatica Server evaluates null values as null in comparison expressions. If either operand is null, the result is null. This is the default behavior. High. The Informatica Server evaluates null values as greater than non-null values in comparison expressions. If both operands are null, the Informatica Server evaluates them as equal. When you choose High, comparison expressions never result in null. Low. The Informatica Server evaluates null values as less than nonnull values in comparison expressions. If both operands are null, the Informatica Server treats them as equal. When you choose Low, comparison expressions never result in null.
   WriterWaitTimeOut	Optional	In target-based commit mode, the amount of time in seconds the writer remains idle before it issues a commit when the following conditions are true: The Informatica Server has written data to the target. The Informatica Server has not issued a committed. The Informatica Server may commit to the target before or after the configured commit interval. Default is 60 seconds. If you configure the timeout to be 0 or a negative number, the Informatica Server defaults to 60 seconds.
   LoadManagerAllow Debugging	Optional	If set to Yes, you can run the Debugger.
   CreateIndicatorFiles	Optional	If set to Yes, the Informatica Server creates indicator files when you run a workflow with a flat file target.
   XMLWarnDupRows	Optional	If set to Yes, the Informatica Server writes duplicate row warnings and duplicate rows for XML targets to the session log.
   OutputMetaData ForFF	Optional	If you specify this option, the Informatica Server writes column headers to flat file targets. It writes the target definition port names to the flat file target in the first line, starting with the # symbol. By default, this option is disabled.
   MaxLookupSPDB Connections	Optional	Allows you to specify a maximum number of connections to a lookup or stored procedure database when you start a session. If the number of connections needed exceeds this value, session threads must share connections. This can result in a performance loss. If you do not specify a value, the Informatica Server allows an unlimited number of connections to the lookup or stored procedure database. If the Informatica Server allows an unlimited number of connections, but the database user does not have permission for the number of connections required by the session, the session fails.
   MaxMSSQL Connections	Optional	Allows you to specify a maximum number of connections to a MSSQL Server database when you start a session. If the number of connections required by the session is greater than this value, the session fails.
   NumOfDeadlock Retries	Optional	Allows you to specify the number of times the Informatica Server retries a target write on a database deadlock.
   DeadlockSleep	Optional	Allows you to specify the number of seconds before the Informatica Server retries a target write on database deadlock. If set to 0 seconds, the Informatica Server retries the target write immediately.
   LicenseFile	Required	The name of the file that contains the license keys. The default file name is pm.lic. It is recommended that you use this file name. During the installation, the product license key is automatically added to this file. After the installation, you must add any additional Option and Connectivity license keys to this file. For instructions, see Updating the Informatica License Files on UNIX.
   JVMDllPath	Optional	The absolute path to the JVM library file.
   JVMClassPath	Optional	You can set the CLASSPATH to any JAR files you need to run a session using a web service source, target, or transformation. The Informatica Server appends the values you set to the system CLASSPATH.
   JVMMinMemory	Optional	Set this value to increase the minimum amount of memory for JVM to use during an Informatica Server session. The default value is 32 MB. If the session fails due to a lack of memory, you may want to increase this value.
   JVMMaxMemory	Optional	Set this value to increase the maximum amount of memory for JVM to use during an Informatica Server session. The default value is 64 MB. If the session fails due to a lack of memory, you may want to increase this value.
   TrustStore	Optional	Enter the value for TrustStore using the following syntax: <path>/<filename>
   ClientStore	Optional	Enter the value for ClientStore using the following syntax: <path>/<filename>
   JvmOptionName[n]	Optional	You can enter names and values for up to 10 custom VM options. Use the following syntax: JvmOption[n]=-D<VMOption_prefix>=<VMOption_value> n can range from 1 to 10 and must be unique for each option.
   JCEProvider	Optional	Enter the JCEProvider class name to support NTLM authentication.
   HttpProxyServer	Required	Name of the HTTP proxy server.
   HttpProxyPort	Required	Port number of the HTTP proxy server. This must be a number.
   HttpProxyUser	Optional	Authenticated username for the HTTP proxy server.
   HttpProxyPassword	Optional	Password for the authenticated user.
   HttpProxyDomain	Optional	Domain for authentication.

4. When the installation is complete, proceed to Updating the Informatica License Files on UNIX.