Configuring the PowerCenter Integration Service Processes
Configuring the PowerCenter Integration Service Processes
When you run a session or a workflow on a grid, a service process runs on each node in the grid. Each service process running on a node must be compatible or configured the same. It must also have access to the directories and input files used by the PowerCenter Integration Service.
To ensure consistent results, complete the following tasks:
Verify the shared storage location. Verify that the shared storage location is accessible to each node in the grid. If the PowerCenter Integration Service uses operating system profiles, the operating system user must have access to the shared storage location.
Configure the service process. Configure $PMRootDir to the shared location on each node in the grid. Configure service process variables with identical absolute paths to the shared directories on each node in the grid. If the PowerCenter Integration Service uses operating system profiles, the service process variables you define in the operating system profile override the service process variable setting for every node. The operating system user must have access to the $PMRootDir configured in the operating system profile on every node in the grid.
Complete the following process to configure the service processes:
Select the PowerCenter Integration Service in the Navigator.
Click the Processes tab.
The tab displays the service process for each node assigned to the grid.
Configure $PMRootDir to point to the shared location.
Configure the following service process settings for each node in the grid:
Code pages. For accurate data movement and transformation, verify that the code pages are compatible for each service process. Use the same code page for each node where possible.
Service process variables. Configure the service process variables the same for each service process. For example, the setting for $PMCacheDir must be identical on each node in the grid.
Directories for Java components. Point to the same Java directory to ensure that java components are available to objects that access Java, such as Custom transformations that use Java coding.