Table of Contents

Search

  1. Preface
  2. Part 1: Installation Getting Started
  3. Part 2: Before You Install the Services
  4. Part 3: Run the Services Installer
  5. Part 4: After You Install the Services
  6. Part 5: Informatica Client Installation
  7. Part 6: Uninstallation
  8. Appendix A: Starting and Stopping Informatica Services
  9. Appendix B: Connecting to Databases from UNIX or Linux
  10. Appendix C: Updating the DynamicSections Parameter of a DB2 Database

Installation for Data Engineering

Installation for Data Engineering

Verify Sizing Requirements

Verify Sizing Requirements

Allocate resources for installation and deployment of services based on the expected deployment type of your environment.
Before you allocate resources, you need to identify the deployment type based on your requirements for the volume of processing and the level of concurrency. Based on the deployment type, you can allocate resources for disk space, cores, and RAM. You can also choose to tune services when you run the installer.

Determine the Installation and Service Deployment Type

The following table describes the environment for the different deployment types:
Deployment Type
Environment Description
Sandbox
Used for proof of concepts or as a sandbox with minimal users.
Basic
Used for low volume processing with low levels of concurrency.
Standard
Used for high volume processing with low levels of concurrency.
Advanced
Used for high volume processing with high levels of concurrency.

Identify Sizing Requirements

The following table provides the minimum sizing requirements for PowerCenter or Data Engineering products:
Deployment Type
Disk Space per Node
Total Virtual Cores
RAM per Node
Sandbox
50 GB
16
32 GB
Basic
100 GB
24
64 GB
Standard
100 GB
48
64 GB
Advanced
100 GB
96
128 GB
You can create an Informatica domain with one node and run all application services on the same node. If you create an Informatica domain with multiple nodes, you can run the application services on separate nodes. When you plan the application services for the domain, consider system requirements based on the services that you run on a node.
Based on workload and concurrency requirements, you might need to optimize performance by adding cores and memory on a node.
The following table lists the minimum system requirements for a node based on some common configuration scenarios:
Services
Processor
Memory
Disk Space
One node runs the following services:
  • Analyst Service
  • Content Management Service
  • Data Integration Service
  • Metadata Manager Service
  • Model Repository Service
  • PowerCenter Integration Service
  • PowerCenter Repository Service
  • Search Service
  • Web Services Hub
2 CPUs with multiple cores
12 GB
20 GB
One node runs the following services:
  • Analyst Service
  • Content Management Service
  • Data Integration Service
  • Model Repository Service
  • Search Service
2 CPUs with multiple cores
12 GB
20 GB
One node runs the following service:
  • Analyst Service
1 CPU with multiple cores
4 GB
n/a
One node runs the following service:
  • Search Service
1 CPU with multiple cores
4 GB
10 GB
One node runs the following services:
  • Analyst Service
  • Search Service
1 CPU with multiple cores
4 GB
10 GB
One node runs the following services:
  • Metadata Manager Service
  • PowerCenter Integration Service
  • PowerCenter Repository Service
2 CPUs with multiple cores
8 GB
10 GB
One node runs the following services:
  • Metadata Manager Service
  • PowerCenter Integration Service
  • PowerCenter Repository Service
2 CPUs with multiple cores
8 GB
10 GB
One node runs the following services:
  • PowerCenter Integration Service
  • PowerCenter Repository Service
1 CPU with multiple cores
4 GB
10 GB
One node runs the following services:
  • Data Integration Service
  • Model Repository Service
1 CPU with multiple cores
4 GB
10 GB
One node runs the following services:
  • Data Integration Service
  • Content Management Service
1 CPU with multiple cores
4 GB
10 GB
One node runs the following service:
  • Metadata Manager Service
1 CPU with multiple cores
4 GB
10 GB
One node runs the following service component:
  • Metadata Manager Agent
1 CPU with multiple cores
4 GB
400 MB
One node runs the following service:
  • Web Services Hub
1 CPU with multiple cores
4 GB
5 GB
The sizing requirements account for the following factors:
  • Disk space required to extract the installer
  • Temporary disk space to run the installer
  • Disk space required to install the services and components
  • Disk space required for log directories
  • Requirements to run the application services
The sizing numbers do not account for operational data processing and object caching requirements for native mode of execution.
For cloud deployments, choose machines with a configuration that is closest to the sizing requirements.