Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Getting started
  3. Before you begin
  4. Installing Secure Agents
  5. Create a CDI-PC domain
  6. Join a CDI-PC domain
  7. Run the silent installer
  8. Resuming an installation
  9. Before you migrate the Informatica domain
  10. Migrate the domain
  11. Migrate the domain with changes to node configuration
  12. Migrate the domain in silent mode
  13. After you migrate the domain
  14. Install the CDI-PC Client
  15. EBF installation
  16. Uninstall Cloud Data Integration for PowerCenter (CDI-PC)
  17. Uninstalling the CDI-PC Client
  18. Uninstalling the Secure Agent
  19. Appendix A: CDI-PC components

Installation Guide

Installation Guide

Run the TLS Utility to validate the certificates

Run the TLS Utility to validate the certificates

CDI-PC
requires valid custom keystore and truststore certificates to secure communication between
Informatica Intelligent Cloud Services
and the domain, and between the domain and clients. The TLS utility verifies that the certificates are valid for communication between two hosts. You can choose to run the utility to validate your certificates.
  1. Download the TLS utility from
    Informatica Intelligent Cloud Services
    .
    For information about how to download the utility, see Download the installers from Informatica Intelligent Cloud Services
  2. Copy the certificates that you want to validate to the same machine.
    After you validate the certificates, you can copy them to the host machine.
  3. Extract the ZIP file to any location on the machine.
  4. Open a command prompt from the directory where you extracted the utility, and run the following command to start the utility:
    java -jar CDI-PC_TLS_Utility.jar
    The utility prompts you for the details of the first host.
  5. Enter certificate details of the domain, Secure Agent, or
    CDI-PC Client
    machine.
    If you have multiple domain nodes or multiple Secure Agents, enter the certificate details of all the domain, Secure Agent, or
    CDI-PC Client
    machines.
  6. Enter the following details for the first host and press
    Enter
    after each entry:
    • First host keystore path. The absolute path to the keystore file on the first host.
    • First host keystore password. The keystore password.
    • First host truststore path. The absolute path to the truststore file on the first host.
    • First host truststore password. The keystore password.
    • First host DNS or IP address. The DNS or IP address of the host on which you use the certificate. If you enter the DNS, enter the fully qualified host name and the short name of the host. Enter comma-separated values. If the certificate includes wildcards in the host details, enter the DNS information for each host on which you use the certificate.
  7. Enter the details for the second host.
    With details of both hosts, the utility tries to connect from the first host to the second host and verifies the host entries in the certificates against details entered. If the second host certificates are present on the first host and host entries are validated, the utility returns a message to indicate that the validation is successful.
  8. If the certificates of the second host are not present in the truststore of the first host, you can choose whether you want the utility to import the certificates. The import modifies the truststore of the first host. Enter
    Y
    to import the certificates and continue or
    N
    to exit.
    If you choose to import the certificates, the utility imports the certificates and continues the validation.
  9. The utility then tries to connect from the second host to the first host. If connection and host entry verification succeed, the utility returns a successful validation message. You might be prompted to import the certificates of the first host into the second host if they aren't present in the truststore of the second host.
    If connection and host entry verification succeed, the utility returns a successful validation message.

0 COMMENTS

We’d like to hear from you!