Installing and Configuring Informatica Libraries

Note: For Unix, add these entries in user's profile located in the user's home directory. For example: .profile or .bash_profile (Linux). You need to source the profile after applying all profile updates. For example, .~/.profile. Once these steps are performed, restart the master for the configurations to take affect.

To install and configure the Informatica Libraries:

Copy the Informatica Library archive appropriate for your configuration from the TA InformaticaBridge folder.

Note: For 64-bit library versions, you must also run with 64-bit Java. If your Java release is not 64-bit, use the 32-bit versions of the libraries.

Note: To support Informatica Power Center 9.6.2 connections on a 64-bit Solaris platform, choose the 9.6.1 upgraded Solaris 64-bit library version.

Note: To support Informatica Power Center 10.2 HF2 & 10.4, use the respective libraries from the Informatica Bridge folder.

Extract the library from the infalib archive to the master machine:
1. Create a directory under the master services directory called infa.
  
  Windows:
  
  C:\Program Files\TIDAL\master\services\infa\
  
  Unix:
  
  /opt/tidal/master/services/infa
2. Extract the archive to this location. The archive distribution contains directories: lib and locale. The system will be configured to refer to these locations in the next steps.
Configure the System Path to include the Informatica Library Path (i.e. lib directory):

Windows:

C:\Program Files\TIDAL\master\services\infa\lib

Note: For Windows, include the library path in the "Path" Environment Variable.

Unix:

/opt/master/services/infa/lib or master/services/infa/lib
- For Solaris/Linux, include the library path in "LD_LIBRARY_PATH".
- For AIX, include the path in "LIBPATH". For 64-bit also include "LD_LIBRARY_PATH".
- For HPUX, include the path for "SHLIB_PATH". For 64-bit also include "LD_LIBRARY_PATH".

Create or update the INFA_DOMAINS_FILE Environment Variable to the location of the Informatica domains.infa file for the Power Center configuration.

This requires that the domains.infa file be local to the Master machine; copy it from your Power Center installation as needed. Put this file in the infa directory created in step 2a above.

Note: To configure connections to multiple Power Center servers, modify the local domains.infa file that was copied to the Master machine. Add values for the vector xml tag corresponding to each Server that will be configured as an adapter.

This includes server information to two Power Center servers, one to Dev and another for Prod. These are referred to as dev-infa and prod-infa, respectively in the sample domains.infa file.

<Portals xmlns:common="http://www.informatica.com/pcsf/common"

xmlns:usermanagement="http://www.informatica.com/pcsf/usermanagement"

xmlns:domainservice="http://www.informatica.com/pcsf/domainservice"

xmlns:logservice="http://www.informatica.com/pcsf/logservice"

xmlns:domainbackup="http://www.informatica.com/pcsf/domainbackup"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:metadata="http://www.informatica.com/pcsf/metadata"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:domainconfigservice="http://www.informatica.com/pcsf/domainconfigservice"

xmlns:alertservice="http://www.informatica.com/pcsf/alertservice"

xmlns:licenseusage="http://www.informatica.com/pcsf/licenseusage"

xmlns:webserviceshub="http://www.informatica.com/pcsf/webserviceshub" xsi:type="common:PCSFVector" objVersion="1.1.19">
<vector xsi:type="domainservice:Portals" objVersion="1.1.19">
<domainName>Domain_dev-infa</domainName>
<address xsi:type="metadata:NodeRef" objVersion="1.1.19">
<host>dev-infa</host>
<port>6001</port>
</address>
</vector>
<vector xsi:type="domainservice:Portals" objVersion="1.1.19">
<domainName>Domain_prod-infa</domainName>
<address xsi:type="metadata:NodeRef" objVersion="1.1.19">
<host>prod-infa</host>
<port>6001</port>
</address>
</vector>
</Portals>

Example: Windows: INFA_DOMAINS_FILE=C:\Program Files\TIDAL\master\services\infa\domains.infa

Example: Unix: export INFA_DOMAINS_FILE=/opt/TIDAL/master/services/infa/domains.infa

Configure the Locale Path for the Informatica Library by setting the TDLINFA_LOCALE service.props value of the adapter as described below. See Configuring service.props below for more details.

In the config directory located under the Adapter’s GUID directory, create or update the service.props file, create the directory and file if it does not yet exist. Include an entry for TDLINFA_LOCALE that points to the Load Manager Library locale directory.

Windows:
```
C:\Program Files\TIDAL\Scheduler\master\services\{7640B420-5530-11DE-8812-7B8656D89593}\config\service.props 
```
Unix:
```
/opt/tidal/master/services/{7640B420-5530-11DE-8812-7B8656D89593}/config/service.props
```
Example: The service.props entry
Windows:
TDLINFA_LOCALE=C:\\ProgramFiles\\TIDAL\\Scheduler\\master\\services\\infalib\\locale

Example: The service.props entry
Unix:
TDLINFA_LOCALE=/opt/tidal/master/services/infa/locale
You need access to the Database JDBC Drivers for connectivity to the Power Center Repository database. Obtain the JDBC jar files from the vendor as needed, copy them to the master machine and add the location of the jar files to the master CLASSPATH property in the master.props file. (Or) Edit CLASSPATH value in service.props of the adapter as described below. See Configuring service.props for more details.

In the config directory located under the Adapter’s GUID directory, create or update the service.props file, create the directory and file if it does not yet exist. Include an entry for CLASSPATH that points to the location of the driver.

Windows:
```
C:\Program Files\TIDAL\Scheduler\master\services\{7640B420-5530-11DE-8812-7B8656D89593}\config\ service.props
```
Unix:
```
/opt/tidal/master/services/{7640B420-5530-11DE-8812-7B8656D89593}/config/service.props
```
Example: Service.props entry example for Windows:CLASSPATH=C:\\driver-jar\\ojdbc6.jar;${CLASSPATH}

Example: Service.props entry example for Unix: CLASSPATH=/home/user/drivers/ojdbc6.jar:${CLASSPATH}\
Edit the adapter service.props file to help control logout issues:
1. In a text editor, open the service.props file in the \config directory where the TA files are installed.
2. Optionally, add one or more of these parameters on separate line(s) in the file:
  - DISCONN_ON_LOSTCONN=Y. Setting this flag to Y avoids an unnecessary logout call to the Informatica server when the connection is lost. This logout call usually hangs.
  - OUTPUT_ASYNC_LOGOUT=Y. Setting this flag to Y avoids jobs getting stuck in Gathering Output status.
  - SCANFOR_SESSIONSTATS=N. Setting this parameter to N turns off the default behavior of Informatica jobs collecting the session statistics during the job run.
  - SCANFOR_SESSIONSTATS_AFTER_WF_ENDS=Y. Setting this parameter to Y turns off the gathering of session statistics during each poll for the status of Informatica jobs.
3. Save the changes and close the service.props file.
  
  Note: See Configuring service.props for documentation about these and other properties that can be set using service.props.
Reboot the Master machine on Windows as needed. Source the profile file as needed on Unix.
Restart the Master.