Informatica PowerCenter Tutorial: Architecture Overview

Lets learn about the Informatica PowerCenter Architecture. The Informatica domain consists of one or more servers, one or more installations of the Informatica software, and at least one relational database.

This article adds information on how nodes work with the database, communications between nodes and services.

Nodes and Domains Architecture

When you install and run the Informatica services, the installation is known as a node. The node becomes part of an Informatica domain which contains one or more nodes.

The domain forms the environment on which the Informatica service processes run evidently one of the nodes in the domain and connects to a relational database.

The database holds the tables for the domain configuration repository. You can add nodes to the domain when you install the node or you can change an existing node and add it to a another domain.


The domain database is a standard relational database. For a domain databases, informatica supports Oracle, IBM DB2, Sybase, and MSSQLServer.
The node that connects to the domain database through JDBC does not use native database connectivity and ODBC.

The supported JDBC drivers are the ones that Informatica licensed from DataDirect which you should use for the Informatica domain.
The domain database acts as ‘backbone’ that supports all of the moving parts in the domain. It holds metadata for services that run on the node. It also stores records of jobs that ran on that node, as well as other data.

The JDBC connection string for the domain database requires the following parameters: user name, password,database host name, database service name and database port number.


Logical representation of the Informatica installation on a server moreover run by Apache Tomcat, a servlet container. Every node runs at least one Java process. The first Java process known as the Service Manager.
The node uses the following configuration files which shows actions to take and what other nodes are in the domain:
The node uses nodemeta.xml to configure itself as either a gateway node or a worker node. nodemeta.xml
always lives in INFA_HOME/isp/config.
It contains the following settings:
• Http port that the node uses for communications with other nodes in the domain.
• Node port that the node uses for client connectivity. The client tools will connect to the node on that port.

JDBC connection information for updating the contents of the domain database. This setting applies to
gateway nodes.

  • The Informatica Administrator port number and the Administrator tool shutdown port number. This setting
    applies to gateway nodes.
    domains.infa contains connection information about the other nodes in the domain which resides in
    INFA_HOME directory. The node uses this file when communicating with the other nodes in the domain,especially the master gateway node.

Repository Service

This service maintains a connection between the clients and PowerCenter repository moreover multi-threaded process that fetches, inserts, and updates the metadata. It also maintains uniformity within the repository metadata.

Reporting Service

Reporting services are responsible for handling the metadata and allowing other services to access the same.
Integration Service – This service engine executes the tasks created in the Informatica tool. It is nothing but a process inside the server waiting for the tasks. As soon as a workflow is executed, the integration service gets the details and executes it.

Workflow Manager and Monitor

Workflow managers and monitors respectively position as effective tools that drive the repository service and connects with all necessary connections with integration.

They also fall within the essential tools confirmed with respect to being used by clients. The integration service has workflow management and monitoring at the heart further helps in the corrective and efficient loading of data to the target system.

Source and Target Systems

Informatica is a Data Integration and ETL tool, you always manage and transform some format of data. Input of the mappings is called the source system. Depending on the requirement, the target system can be a flat or a relational file system.

  • Flat File: Data sources following the relational databases. Flat files are tab-delimited files and comma-separated files. Informatica endorses code pages like Unicode, ASCII.
  • Relational File:  Relation files are database system tables. These are usually owned by the applications that maintain and create data. Applications can be Human Resource Database and CRM Database.

For basic ETL understanding, please visit ETL Basic and for product information visit

Informatica PowerCenter Tutorial: Architecture Overview

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top