Table of Contents

Search

  1. Preface
  2. Part 1: Installation Getting Started
  3. Part 2: Before You Install the Services
  4. Part 3: Run the Services Installer
  5. Part 4: After You Install the Services
  6. Part 5: Informatica Client Installation
  7. Part 6: Uninstallation
  8. Appendix A: Starting and Stopping Informatica Services
  9. Appendix B: Connecting to Databases from UNIX or Linux
  10. Appendix C: Connecting to Databases from Windows
  11. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Installation for PowerCenter and Data Quality

Installation for PowerCenter and Data Quality

Set Up Keystore and Truststore Files

Set Up Keystore and Truststore Files

When you install the Informatica services, you can configure secure communication for the domain and set up a secure connection to Informatica Administrator (the Administrator tool). If you configure these security options, you must set up keystore and truststore files.
Before you install the Informatica services, set up the files for secure communication within the Informatica domain or for a secure connection to the Administrator tool. To create the required files, you can use the following programs:
keytool
You can use keytool to create an SSL certificate or a Certificate Signing Request (CSR) as well as keystores and truststores in JKS format.
For more information about using keytool, see the documentation on the following web site: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html.
OpenSSL
You can use OpenSSL to create an SSL certificate or CSR as well as convert a keystore in JKS format to PEM format.
For more information about OpenSSL, see the documentation on the following website: https://www.openssl.org/docs/
For a higher level of security, send your CSR to a Certificate Authority (CA) to get a signed certificate.
The software available for download at the referenced links belongs to a third party or third parties, not Informatica LLC. The download links are subject to the possibility of errors, omissions or change. Informatica assumes no responsibility for such links and/or such software, disclaims all warranties, either express or implied, including but not limited to, implied warranties of merchantability, fitness for a particular purpose, title and non-infringement, and disclaims all liability relating thereto.

Secure Communication Within the Informatica domain

Before you enable secure communication within the Informatica domain, verify that the following requirements are met:
You created a certificate signing request (CSR) and private key.
You can use keytool or OpenSSL to create the CSR and private key.
If you use RSA encryption, you must use more than 512 bits.
You have a signed SSL certificate.
The certificate can be self-signed or CA signed. Informatica recommends a CA signed certificate.
You imported the certificate into keystores.
You must have a keystore in PEM format named
infa_keystore.pem
and a keystore in JKS format named
infa_keystore.jks
.
The keystore files must contain the root and intermediate SSL certificates.
The password for the keystore in JKS format must be the same as the private key pass phrase used to generate the SSL certificate.
You imported the certificate into truststores.
You must have a truststore in PEM format named
infa_truststore.pem
and a truststore in JKS format named
infa_truststore.jks
.
The truststore files must contain the root, intermediate, and end user SSL certificates.
The keystores and truststores are in the correct directory.
The keystore and truststore must be in a directory that is accessible to the installer.

Secure Connection to the Administrator tool

Before you secure the connection to the Administrator tool, verify that the following requirements are met:
You created a certificate signing request (CSR) and private key.
You can use keytool or OpenSSL to create the CSR and private key.
If you use RSA encryption, you must use more than 512 bits.
You have a signed SSL certificate.
The certificate can be self-signed or CA signed. Informatica recommends a CA signed certificate.
You imported the certificate into a keystore in JKS format.
A keystore must contain only one certificate. If you use a unique certificate for each web application service, create a separate keystore for each certificate. Alternatively, you can use a shared certificate and keystore.
If you use the installer-generated SSL certificate for the Administrator tool, you do not need to import the certificate into a keystore in JKS format.
The keystore is in the correct directory.
The keystore must be in a directory that is accessible to the installer.

0 COMMENTS

We’d like to hear from you!