Installation for PowerCenter and Data Quality

10.5.5
- 10.5.6
- 10.5.5.1
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0

Back Next

Configuring Native Connectivity

You can configure native connectivity to a Sybase ASE database to increase performance.

The following steps provide a guideline for configuring native connectivity. For specific instructions, see the database documentation.

To configure connectivity to the Data Integration Service, PowerCenter Integration Service, or PowerCenter Repository Service process, log in to the machine as a user who can start the server process.

Set the SYBASE and PATH environment variables.

SYBASE
. Set the variable to the Sybase Open Client installation directory. For example if the client is installed in the /usr/sybase directory:

Using a Bourne shell:

$ SYBASE=/usr/sybase; export SYBASE

Using a C shell:

$ setenv SYBASE /usr/sybase

PATH
. To run the Sybase command line programs, set the variable to include the Sybase OCS bin directory.

Using a Bourne shell:

$ PATH=${PATH}:/usr/sybase/OCS-15_0/bin; export PATH

Using a C shell:

$ setenv PATH ${PATH}:/usr/sybase/OCS-15_0/bin

Set the shared library environment variable.

The Sybase Open Client software contains a number of shared library components that the Data Integration Service, PowerCenter Integration Service, and PowerCenter Repository Service processes load dynamically. Set the shared library environment variable so that the services can find the shared libraries at run time.

The shared library path must also include the installation directory of the Informatica services

(server_dir)

Set the shared library environment variable based on the operating system.

The following table describes the shared library variables for each operating system.

Operating System	Variable
Linux	LD_LIBRARY_PATH
AIX	LIBPATH

For example, use the following syntax for Linux:

Using a Bourne shell:

$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64; export LD_LIBRARY_PATH

Using a C shell:

$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64;

For AIX

Using a Bourne shell:

$ LIBPATH=${LIBPATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64; export LIBPATH

Using a C shell:

$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64;

Edit the .cshrc or .profile to include the complete set of shell commands. Save the file and either log out and log in again, or run the source command.

Using a Bourne shell:

$ source .profile

Using a C shell:

$ source .cshrc

Verify the Sybase ASE server name in the Sybase interfaces file stored in the $SYBASE directory.

Optionally, to connect to the SSL-enabled Sybase ASE database, perform the following tasks:

Specify the following security attributes on the

Security

tab when you configure the data source name in the Sybase driver property:

Attribute	Description
Encryption Method	Indicates whether data is encrypted when transmitted over the network. Select SSL.
Validate Server Certificate	Indicates whether Informatica validates the certificate that is sent by the database server when SSL encryption is enabled.
Trust Store	The location and name of the trust store file.
Trust Store Password	The password to access the contents of the trust store file.
Host Name In Certificate	The host name that is established by the SSL administrator to validate the host name contained in the certificate.

Add the Sybase ASE server certificate to the trusted.txt file in the Sybase ASE client.

Add the following Sybase ASE server connection details to the Sybase interface file:

<server_instance_name>
        master tcp ether <host name> <port number> ssl="CN='common_name"'
        query tcp ether <host name> <port number> ssl="CN='common_name"'

Verify that you can connect to the Sybase ASE database.

To connect to the Sybase ASE database, launch ISQL and enter the connectivity information. If you fail to connect to the database, verify that you correctly entered all of the connectivity information.

Rename Saved Search

Table of Contents

Installation for PowerCenter and Data Quality

Installation for PowerCenter and Data Quality

Configuring Native Connectivity

Configuring Native Connectivity