Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Print Bookmark Alert me when this article is updated


Implementation Planning for Informatica Platform
The user has installed the Informatica Platform and using it. 
They want to know how to use these tools and implementation planning for the Informatica Platform​.
  1. First, download and read the Installation and Configuration guide from the​ portal.
    If you don't already have an account there, create one. It's valuable.
    Either way, you will learn the following:
    • What operating systems are supported for the tools?
    • What preparation on the server and for databases do I need to make prior to the install?
    • What rights do I need for the repository databases and on the server to be able to install successfully?
    • Are there security ports that need to be opened to be able to install and execute the software?​​
  2. Some of this planning, including how much memory and CPU to use for your needs is important to do before an install engagement.
    You'll have to request hardware, user IDs, database repositories and space, apply system patches, request shared network storage, and download the Informatica software and license keys.

  3. At this point, you are ready to install and configure the tools.
    You'll need to plan for the names of the Domain in each environment and the names of the Application Services. A list of the ones you'll need is in the Installation Guide, or in the pre-install guide IPS provided.
    You'll need the databases and schemas for each environment configured on one of the supported databases that can be used for the Informatica Platform repositories (Oracle, DB2, SQL Server).
    You'll need user IDs for the servers, and database privileges. Database driver software (Oracle Client, DB2 Client, etc.) should be installed on the server, Oracle tnsnames entries for all databases to which we'd like to connect should be in the tnsnames.ora file.
    Some environment variables and paths need to be set.

  4. The server installation is not hard, but the thing that trips us up most often is connecting to the repository databases and being sure that required settings, like the number of open files, is set appropriately on the server.
    Getting these things right sometimes makes the install on the first server (node) take longer, but once it is done, the installs tend to be routine.
    It's best to have a system administrator and DBA available in case there needs to be setting adjustments if something was missed.

  5. Once the server binaries are installed, it is time to open the Administrator tool, a web-based tool, that allows you to configure the Application Services that make everything else run in the tools and also enables security.
    There are a lot of selections and things to create for all of the Informatica Platform features you've licensed to be active.
    Again, review the Installation and Application Service guides. Engaging IPS can make this faster for you too.
    The binaries need to be installed on each node (server) in your grid, but the Application Services are installed once within the Domain.
    You'll have a separate Domain for each environment, for example, Development, Test, Production.

  6. The Application Services are created, repository content has been created, the services are enabled, the PowerCenter Repository is in Normal Operating Mode, and you are ready to go.
More Information


Applies To
Product: Data Quality; PowerCenter
Problem Type: Installation
User Type: Administrator; Architect; Developer
Project Phase: Configure; Implement
Product Version:
Operating System:
Other Software:
Velocity Phase:
Velocity Packages:
IPS Document Type:
Last Modified Date: 6/1/2020 4:42 PM ID: 608587
People who viewed this also viewed


Did this KB document help you?

What can we do to improve this information (2000 or fewer characters)