Cloud Data Integration for PowerCenter
- Cloud Data Integration for PowerCenter
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Property
| Description
|
|---|---|
Type
| Type of external procedure. Use the following types:
Default is Informatica.
|
Module/Programmatic Identifier
| A module is a base name of the DLL (on Windows) or the shared object (on UNIX) that contains the external procedures. It determines the name of the DLL or shared object on the operating system.
Enter ASCII characters only.
A programmatic identifier, or ProgID, is the logical name for a class. In the Designer, you refer to COM classes through ProgIDs. Internally, classes are identified by numeric CLSID's. For example:
The standard format of a ProgID is
Project.Class[.Version] .
Enter ASCII characters only.
|
Procedure Name
| Name of the external procedure. Enter ASCII characters only.
|
Runtime Location
| Location that contains the DLL or shared library. Enter a path relative to the Integration Service node that runs the External Procedure session. If you enter $PMExtProcDir, then the Integration Service looks in the directory specified by the process variable $PMExtProcDir to locate the library.
If this property is blank, the Integration Service uses the environment variable defined on the on the Integration Service node to locate the DLL or shared library.
You can hard code a path as the Runtime Location. This is not recommended since the path is specific to a single machine only.
You must copy all DLLs or shared libraries to the runtime location or to the environment variable defined on the Integration Service node. The Integration Service fails to load the procedure when it cannot locate the DLL, shared library, or a referenced file.
Default is $PMExtProcDir.
|
Tracing Level
| Amount of transaction detail reported in the session log file. Use the following tracing levels:
Default is Normal.
|
Is Partitionable
| Indicates if you can create multiple partitions in a pipeline that uses this transformation. Use the following values:
- No. The transformation cannot be partitioned. The transformation and other transformations in the same pipeline are limited to one partition.
- Locally. The transformation can be partitioned, but the Integration Service must run all partitions in the pipeline on the same node. Choose Local when different partitions of the BAPI/RFC transformation must share objects in memory.
- Across Grid. The transformation can be partitioned, and the Integration Service can distribute each partition to different nodes.
Default is No.
|
Output is Repeatable
| Indicates whether the transformation generates rows in the same order between session runs. The Integration Service can resume a session from the last checkpoint when the output is repeatable and deterministic. Use the following values:
Default is Based on Input Order.
|
Output is Deterministic
| Indicates whether the transformation generates consistent output data between session runs. You must enable this property to perform recovery on sessions that use this transformation.
Default is disabled.
|
Operating System
| Environment Variable
|
|---|---|
Windows
| PATH
|
Linux
| LD_LIBRARY_PATH
|
