PowerCenter Integration Service Processes
The PowerCenter Integration Service can run each PowerCenter Integration Service process on a different node. When you select the PowerCenter Integration Service in the Administrator tool, you can view the PowerCenter Integration Service process nodes on the Processes tab.
You can change the following properties to configure the way that a PowerCenter Integration Service process runs on a node:
- •General properties
- •Custom properties
- •Environment variables
General properties include the code page and directories for PowerCenter Integration Service files and Java components.
To configure the properties, select the PowerCenter Integration Service in the Administrator tool and click the Processes view. When you select a PowerCenter Integration Service process, the detail panel displays the properties for the service process.
Code Pages
You must specify the code page of each PowerCenter Integration Service process node. The node where the process runs uses the code page when it extracts, transforms, or loads data.
Before you can select a code page for a PowerCenter Integration Service process, you must select an associated repository for the PowerCenter Integration Service. The code page for each PowerCenter Integration Service process node must be a subset of the repository code page. When you edit this property, the field displays code pages that are a subset of the associated PowerCenter Repository Service code page.
When you configure the PowerCenter Integration Service to run on a grid or a backup node, you can use a different code page for each PowerCenter Integration Service process node. However, all codes pages for the PowerCenter Integration Service process nodes must be compatible.
Directories for PowerCenter Integration Service Files
PowerCenter Integration Service files include run-time files, state of operation files, and session log files.
The PowerCenter Integration Service creates files to store the state of operations for the service. The state of operations includes information such as the active service requests, scheduled tasks, and completed and running processes. If the service fails, the PowerCenter Integration Service can restore the state and recover operations from the point of interruption.
The PowerCenter Integration Service process uses run-time files to run workflows and sessions. Run-time files include parameter files, cache files, input files, and output files. If the PowerCenter Integration Service uses operating system profiles, the operating system user specified in the profile must have access to the run-time files.
By default, the installation program creates a set of PowerCenter Integration Service directories in the server\infa_shared directory. You can set the shared location for these directories by configuring the service process variable $PMRootDir to point to the same location for each PowerCenter Integration Service process. Each PowerCenter Integration Service can use a separate shared location.
Configuring $PMRootDir
When you configure the PowerCenter Integration Service process variables, you specify the paths for the root directory and its subdirectories. You can specify an absolute directory for the service process variables. Make sure all directories specified for service process variables exist before running a workflow.
Set the root directory in the $PMRootDir service process variable. The syntax for $PMRootDir is different for Windows and UNIX:
- •On Windows, enter a path beginning with a drive letter, colon, and backslash. For example:
C:\Informatica\<infa_vesion>\server\infa_shared
- •On UNIX: Enter an absolute path beginning with a slash. For example:
/Informatica/<infa_vesion>/server/infa_shared
You can use $PMRootDir to define subdirectories for other service process variable values. For example, set the $PMSessionLogDir service process variable to $PMRootDir/SessLogs.
Configuring Service Process Variables for Multiple Nodes
When you configure the PowerCenter Integration Service to run on a grid or a backup node, all PowerCenter Integration Service processes associated with a PowerCenter Integration Service must use the same shared directories for PowerCenter Integration Service files.
Configure service process variables with identical absolute paths to the shared directories on each node that is configured to run the PowerCenter Integration Service. If you use a mounted drive or a mapped drive, the absolute path to the shared location must also be identical.
For example, if you have a primary and a backup node for the PowerCenter Integration Service, recovery fails when nodes use the following drives for the storage directory:
- •Mapped drive on node1: F:\shared\Informatica\<infa_version>\infa_shared\Storage
- •Mapped drive on node2: G:\shared\Informatica\<infa_version>\infa_shared\Storage
Recovery also fails when nodes use the following drives for the storage directory:
- •Mounted drive on node1: /mnt/shared/Informatica/<infa_version>/infa_shared/Storage
- •Mounted drive on node2: /mnt/shared_filesystem/Informatica/<infa_version>/infa_shared/Storage
To use the mapped or mounted drives successfully, both nodes must use the same drive.
Service Process Variables for Operating System Profiles
When you use operating system profiles, define the absolute or relative directory path for $PMWorkflowLogDir in the PowerCenter Integration Service properties. Define the absolute directory path for $PMStorageDir in the PowerCenter Integration Service properties and the operating system profile.
The PowerCenter Integration Service writes the workflow log file in the directory specified in $PMWorkflowLogDir. The PowerCenter Integration Service saves workflow recovery files to the $PMStorageDir configured in the PowerCenter Integration Service properties and saves the session recovery files to the $PMStorageDir configured in the operating system profile. Define the other service process variables within each operating system profile.
You can use a relative directory path to define $PMWorkflowLogDir, but you must use an absolute directory path to define $PMStorageDir.
Directories for Java Components
You must specify the directory containing the Java components. The PowerCenter Integration Service uses the Java components for the following PowerCenter components:
- •Custom transformation that uses Java code
- •Java transformation
- •PowerExchange for JMS
- •PowerExchange for Web Services
- •PowerExchange for webMethods
General Properties
The following table describes the general properties:
Property | Description |
|---|
Codepage | Code page of the PowerCenter Integration Service process node. |
$PMRootDir | Root directory accessible by the node. This is the root directory for other service process variables. It cannot include the following special characters: * ? < > “ | , Default is <Installation_Directory>\server\infa_shared. The installation directory is based on the service version of the service that you created. When you upgrade the PowerCenter Integration Service, the $PMRootDir is not updated to the upgraded service version installation directory. |
$PMSessionLogDir | Default directory for session logs. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/SessLogs. |
$PMBadFileDir | Default directory for reject files. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/BadFiles. |
$PMCacheDir | Default directory for index and data cache files. You can increase performance when the cache directory is a drive local to the PowerCenter Integration Service process. Do not use a mapped or mounted drive for cache files. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/Cache. |
$PMTargetFileDir | Default directory for target files. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/TgtFiles. |
$PMSourceFileDir | Default directory for source files. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/SrcFiles. Note: If you use Metadata Manager, use the default value. Metadata Manager stores transformed metadata for packaged and universal resources in files in the $PMRootDir/SrcFiles directory. If you change this property, Metadata Manager cannot retrieve the transformed metadata when you load a packaged or universal resource. |
$PMExtProcDir | Default directory for external procedures. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/ExtProc. |
$PMTempDir | Default directory for temporary files. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/Temp. |
$PMWorkflowLogDir | Default directory for workflow logs. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/WorkflowLogs. |
$PMLookupFileDir | Default directory for lookup files. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/LkpFiles. |
$PMStorageDir | Default directory for state of operation files. The PowerCenter Integration Service uses these files for recovery if you have the high availability option or if you enable a workflow for recovery. These files store the state of each workflow and session operation. It cannot include the following special characters: * ? < > “ | , Default is $PMRootDir/Storage. |
Java SDK ClassPath | Java SDK classpath. You can set the classpath to any JAR files you need to run a session that require java components. The PowerCenter Integration Service appends the values you set to the system CLASSPATH. For more information, see Directories for Java Components. |
Java SDK Minimum Memory | Minimum amount of memory the Java SDK uses during a session. If the session fails due to a lack of memory, you may want to increase this value. Default is 32 MB. |
Java SDK Maximum Memory | Maximum amount of memory the Java SDK uses during a session. If the session fails due to a lack of memory, you may want to increase this value. Default is 64 MB. |
Custom Properties for the PowerCenter Integration Service Process
Configure custom properties that are unique to specific environments.
You might need to apply custom properties in special cases. When you define a custom property, enter the property name and an initial value. Define custom properties only at the request of Informatica Global Customer Support.
Environment Variables
The database client path on a node is controlled by an environment variable.
Set the database client path environment variable for the PowerCenter Integration Service process if the PowerCenter Integration Service process requires a different database client than another PowerCenter Integration Service process that is running on the same node. For example, the service version of each PowerCenter Integration Service running on the node requires a different database client version. You can configure each PowerCenter Integration Service process to use a different value for the database client environment variable.
The database client code page on a node is usually controlled by an environment variable. For example, Oracle uses NLS_LANG, and IBM DB2 uses DB2CODEPAGE. All PowerCenter Integration Services and PowerCenter Repository Services that run on this node use the same environment variable. You can configure a PowerCenter Integration Service process to use a different value for the database client code page environment variable than the value set for the node.
You might want to configure the code page environment variable for a PowerCenter Integration Service process for the following reasons:
- •A PowerCenter Integration Service and PowerCenter Repository Service running on the node require different database client code pages. For example, you have a Shift-JIS repository that requires that the code page environment variable be set to Shift-JIS. However, the PowerCenter Integration Service reads from and writes to databases using the UTF-8 code page. The PowerCenter Integration Service requires that the code page environment variable be set to UTF-8.
Set the environment variable on the node to Shift-JIS. Then add the environment variable to the PowerCenter Integration Service process properties and set the value to UTF-8.
- •Multiple PowerCenter Integration Services running on the node use different data movement modes. For example, you have one PowerCenter Integration Service running in Unicode mode and another running in ASCII mode on the same node. The PowerCenter Integration Service running in Unicode mode requires that the code page environment variable be set to UTF-8. For optimal performance, the PowerCenter Integration Service running in ASCII mode requires that the code page environment variable be set to 7-bit ASCII.
Set the environment variable on the node to UTF-8. Then add the environment variable to the properties of the PowerCenter Integration Service process running in ASCII mode and set the value to 7-bit ASCII.
If the PowerCenter Integration Service uses operating system profiles, environment variables configured in the operating system profile override the environment variables set in the general properties for the PowerCenter Integration Service process.