Application Service Guide > Application Service Databases > Configure Native Connectivity on Service Machines
  

Configure Native Connectivity on Service Machines

To establish native connectivity between an application service and a database, install the database client software for the database that you want to access.
Native drivers are packaged with the database server and client software. Configure connectivity on the machines that need to access the databases. To ensure compatibility between the application service and the database, install a client software that is compatible with the database version and use the appropriate database client libraries.
The following services use native connectivity to connect to different databases:
Data Integration Service
The Data Integration Service uses native database drivers to connect to the following databases:
When the Data Integration Service runs on a single node or on primary and back-up nodes, install database client software and configure connectivity on the machines where the Data Integration Service runs.
When the Data Integration Service runs on a grid, install database client software and configure connectivity on each machine that represents a node with the compute role or a node with both the service and compute roles.
PowerCenter Repository Service
The PowerCenter Repository Service uses native database drivers to connect to the PowerCenter repository database.
Install database client software and configure connectivity on the machines where the PowerCenter Repository Service and the PowerCenter Repository Service processes run.
PowerCenter Integration Service
The PowerCenter Integration Service uses native database drivers to connect to the following databases:
Install database client software associated with the relational data sources and the repository databases on the machines where the PowerCenter Integration Service runs.
The Data Integration Service uses native database drivers to connect to the following databases:
When the Data Integration Service runs on a single node or on primary and back-up nodes, install database client software and configure connectivity on the machines where the Data Integration Service runs.
When the Data Integration Service runs on a grid, install database client software and configure connectivity on each machine that represents a node with the compute role or a node with both the service and compute roles.

Step 5. Install Database Client SoftwareInstall Database Client Software

You must install the database clients on the required machines based on the types of databases that the application services access.
To ensure compatibility between the application service and the database, use the appropriate database client libraries and install a client software that is compatible with the database version.
When you upgrade Informatica services, ensure that you install the appropriate database client on the machine that runs the Data Integration Service.
Install the following database client software based on the type of database that the application service accesses:
IBM DB2 Client Application Enabler (CAE)
Configure connectivity on the required machines by logging in to the machine as the user who starts Informatica services.
Microsoft SQL Server 2014 Native Client
You must install the Microsoft SQL Server 2014 Native Client for the existing mappings to work.
Download the client from the following Microsoft website: http://www.microsoft.com/en-in/download/details.aspx?id=42295.
Oracle client
Install compatible versions of the Oracle client and Oracle database server. You must also install the same version of the Oracle client on all machines that require it. To verify compatibility, contact Oracle.
Sybase Open Client (OCS)
Install an Open Client version that is compatible with the Sybase ASE database server. You must also install the same version of Open Client on the machines hosting the Sybase ASE database and Informatica. To verify compatibility, contact Sybase.
PostgreSQL client (psql)
Install and run the PostgreSQL interactive terminal program called psql, which allows you to interactively enter, edit, and run SQL commands.
psql is a terminal-based front-end to PostgreSQL. You can type in queries interactively, issue the queries to PostgreSQL, and check the query results. Or, the input can be from a file or from command line arguments.
You can install psql client application for PostgreSQL to work only on Linux or Windows.
Install and run the required software dependency packages to build PostgreSQL, such as GCC compiler package, readline and readline-devel packages, and zlib-devel compression library package. After you install the packages from the GNU Readline library, psql remembers each command you type, and you can use arrow keys to recall and edit previous commands.
You can also run the required library files with the yum install commands.
PostgreSQL on Windows
On Windows, download the psql client from the following link:
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
You must verify that PostgreSQL libraries are present in the following directories on Windows:
PostgreSQL on Linux
On Linux, you also need to install the required postgreSQL libraries, postgresql10-10.10-1PGDG.rhel7.x86_64 and postgresql10-libs-10.10-1PGDG.rhel7.x86_64
For more information about psql, see the psql client documentation in the following link: https://www.postgresql.org/docs/10/app-psql.html

Configure Database Client Environment Variables

Configure database client environment variables on the machines that run the Data Integration Service processes.
Configure database client environment variables on the machines that run the Data Integration Service, PowerCenter Integration Service, and PowerCenter Repository Service processes.
After you configure the database environment variables, you can test the connection to the database from the database client.
The following table lists the database environment variables you need to set:
Database
Environment Variable Name
Database Utility
Value
Oracle
ORACLE_HOME
PATH
LD_LIBRARY_PATH
TNS_ADMIN
INFA_TRUSTSTORE
sqlplus
Set to: <Client InstallDatabasePath>
Add: <DatabasePath>/bin and USER_INSTALL_DIR/server/bin:$PATH
Set to: $Oracle_HOME/lib and USER_INSTALL_DIR/server/bin:$LD_LIBRARY_PATH
Set to location of the tnsnames.ora file: $ORACLE_HOME/network/admin
For default SSL domain, add to: USER_INSTALL_DIR/services/shared/security
For custom SSL domain, set INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD
IBM DB2
DB2DIR
DB2INSTANCE
PATH
db2connect
Set to: <database path>
Set to: <DB2InstanceName>
Add: <database path>/bin
Sybase ASE
SYBASE15
SYBASE_ASE
SYBASE_OCS
PATH
isql
Set to: <database path>/sybase<version>
Set to: ${SYBASE15}/ASE-<version>
Set to: ${SYBASE15}/OCS-<version>
Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:$PATH
PostgreSQL
PGSERVICEFILE
PGHOME
PATH
LD_LIBRARY_PATH
INFA_TRUSTSTORE
Set to the location of the pg_service.conf file: <pg_service.conf file directory>/pg_service.conf
Set to: /usr/pgsql -10
Add to: $PGHOME:${PATH}
Add to: $PGHOME/lib:${LD_LIBRARY_PATH}
For default SSL domain, add to: <InstallationDirectory>/services/shared/security
For custom SSL domain, set INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD
SQL Server
ODBCHOME
ODBCINI
ODBCINST
PATH
LD_LIBRARY_PATH
INFA_TRUSTSTORE
Set to: USER_INSTALL_DIR/ODBC7.1
Set to: $ODBCHOME/odbc.ini
Set to: $ODBCHOME/odbcinst.ini
Add to: /opt/mssql-tools/bin:$PATH$PATHUSER_INSTALL_DIR/ODBC7.1:$PATHUSER_INSTALL_DIR/server/bin:$PATH
Add to: $ODBCHOME/lib
USER_INSTALL_DIR/server/bin:$LD_LIBRARY_PATH
For default SSL domain, add to: USER_INSTALL_DIR/services/shared/security
For custom SSL domain, set INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD