Table of Contents

Search

  1. Installation Overview
  2. Before You Install the Services
  3. Service Installation
  4. After You Install the Services
  5. Client Installation
  6. Uninstallation
  7. Starting and Stopping Informatica Services
  8. Connecting to Databases from Windows
  9. Connecting to Databases from UNIX
  10. Updating the DynamicSections Parameter of a DB2 Database
  11. Installation and Configuration Checklist
  12. Split Domain Configuration for Metadata Manager

Installation and Configuration Guide

Installation and Configuration Guide

Domain Security

Domain Security

When you install the Informatica services, you can enable options in the Informatica domain to configure security for the domain.

Secure Communication for Services and the Service Manager

You can optionally configure secure communication between services and the Service Manager.
If you choose to use your SSL certificates instead of the default certificates, you must provide information about the SSL certificates during the installation. You can provide a self-signed certificate or a certificate issued by a certificate authority (CA). You must provide SSL certificates in PEM format and in Java Keystore (JKS) files. Informatica requires specific names for the SSL certificate files for the Informatica domain.
Use the following table to record information about the keystore and truststore files that contain the SSL certificates you want to use:
Security Information
Description
Value
Keystore file directory
Directory that contains the keystore files. The directory must contain files named infa_keystore.jks and infa_keystore.pem.
Keystore password
Password for the keystore infa_keystore.jks.
Truststore file directory
Directory that contains the truststore files. The directory must contain files named infa_truststore.jks and infa_truststore.pem.
Truststore password
Password for the infa_truststore.jks file.

Secure Domain Configuration Repository Database

You can optionally create the domain configuration repository in a database that is secured with the SSL protocol.
Access to the secure database requires a truststore that contains the certificates for the database.
Use the following table to record the information about the truststore file for the secure database:
Security Information
Description
Value
Database truststore file
Path and file name of the truststore file for the secure database.
Database truststore password
Password for the truststore file.

Secure Connection for the Administrator Tool

You can optionally configure a secure HTTPS connection for the Administrator tool.
If you choose to use a keystore file that you create instead of the default file, you must provide information about the file during installation.
Use the following table to record information about the keystore file that you want to use:
Security Information
Description
Value
Keystore password
A plain-text password for the keystore file.
Keystore file directory
Location of the keystore file.