Table of Contents

Search

  1. About the Data Vault Administrator Guide
  2. Introduction to the Data Vault
  3. Data Vault Service Startup and Shutdown
  4. Data Vault Configuration
  5. Data Vault SSL Setup
  6. Data Vault ODBC Setup
  7. Data Vault Administration
  8. Data Repartitioning
  9. Partial Data Vault Copy
  10. Archived Data Migration
  11. Bulk File Uploader
  12. Data Vault Administration Tool
  13. Data Vault Logs
  14. User Account Privileges
  15. ssasql Command Line Program
  16. Data Vault Audit Log
  17. Sample Configuration Files

Data Vault Administrator Guide

Data Vault Administrator Guide

Configuring the Ssa.ini and Nucleus.ini Files

Configuring the Ssa.ini and Nucleus.ini Files

Edit the ssa.ini and nucleus.ini files to configure SSL communication in Data Vault.
  1. For the Data Vault server component installation, add the following entry in both the [AGENT] and [ADMIN] sections:
    CertFile = <full CA certificate file path>
    The [ADMIN] section is not available by default. You must add this section manually.
    For perl utilities, for example ssadbcopy, ssamigrate, ssacleanup, and ssaencrypt, it is important to add the certificate file path entry in the [AGENT] section. These utilities use the location internally.
  2. In the [SERVER] section of ssa.ini, add the following entries:
    CertFile = <full certificate file path>
    PrivateKey = <full private key file path>
  3. If you are not using alternate names as explained in the topic "Alternate Names," then you must add the fully-qualified domain name, for example "myhostname.mydomain.com," for the HOST variable in the [SERVER] section of the ssa.ini file. If you are using alternate names, for example "myhostname," then you can provide the same name for the HOST variable in the [SERVER] section of ssa.ini. Data Vault uses this entry internally when running Perl tools, so it is important for users who run utilities such as ssadbcopy, ssacleanup, ssamigrate, and others.
  4. In the [CONNECTION] section of the nucleus.ini file, add the following parameters:
    CertFile = <full path of the certificate file>
    SSL = 1
    For example:
    [CONNECTIon fas] Port=8507 Host=inkr58dsg519.informatica.com CertFile=/data1/idauser/root.ca.crt SSL=1
    If you are not using alternate names as described in the "Alternate Names" topic, then you must add the fully-qualified domain name for the host variable in the [CONNECTION] section. Otherwise, if you are using subject alternate names, for example "myhostname," then you can provide the same name for HOST in this [CONNECTION] section.

0 COMMENTS

We’d like to hear from you!