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

Configure the Developer Tool workspace directory

Configure the Developer Tool workspace directory

Configure Informatica Developer (the Developer tool) to write the workspace metadata to the machine where the user is logged in.
If you have installed the CDI-PC clients and performed this task, you do not need to repeat this task.
  1. Go to the following directory:
    <CDI-PC installation directory>\clients\DeveloperClient\configuration\
  2. Locate the config.ini file.
  3. Create a backup copy of the config.ini file.
  4. Use a text editor to open the config.ini file.
  5. Add the
    osgi.instance.area.default
    variable to the end of the
    config.ini
    file and set the variable to the directory location where you want to save the workspace metadata. The file path cannot contain non-ANSI characters. Folder names in the workspace directory cannot contain the number sign (#) character. If folder names in the workspace directory contain spaces, enclose the full directory in double quotes.
    • If you run the Developer tool from the local machine, set the variable to the absolute path of the workspace directory:
      osgi.instance.area.default=<Drive>/<WorkspaceDirectory>
      or
      osgi.instance.area.default=<Drive>\\<WorkspaceDirectory>
    • If you run the Developer tool from a remote machine, set the variable to the directory location on the local machine:
      osgi.instance.area.default=\\\\<LocalMachine>/<WorkspaceDirectory>
      or
      osgi.instance.area.default=\\\\<LocalMachine>\\<WorkspaceDirectory>
      You must have write permission to the local workspace directory.
The Developer tool writes the workspace metadata to the workspace directory. If you log into the Developer tool from a local machine, the Developer tool writes the workspace metadata to the local machine. If the workspace directory doesn't exist on the machine from which you logged in, the Developer tool creates the directory when it writes the files.
You can override the workspace directory when you start the Developer tool.

0 COMMENTS

We’d like to hear from you!