Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Configuring External Procedure Transformation Properties

Configuring External Procedure Transformation Properties

Configure transformation properties on the Properties tab.
The following table describes the External Procedure transformation properties:
Property
Description
Type
Type of external procedure. Use the following types:
  • COM
  • Informatica
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:
{33B17632-1D9F-11D1-8790-0000C044ACF9}
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:
  • Terse
  • Normal
  • Verbose Initialization
  • Verbose Data
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:
  • Always. The order of the output data is consistent between session runs even if the order of the input data is inconsistent between session runs.
  • Based on Input Order. The transformation produces repeatable data between session runs when the order of the input data from all input groups is consistent between session runs. If the input data from any input group is not ordered, then the output is not ordered.
  • Never. The order of the output data is inconsistent between session runs. You cannot configure recovery to resume from the last checkpoint if a transformation does not produce repeatable data.
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.
If you configure a transformation as repeatable and deterministic, it is your responsibility to ensure that the data is repeatable and deterministic. If you try to recover a session with transformations that do not produce the same data between the session and the recovery, the recovery process can result in corrupted data.
The following table describes the environment variables the Integration Service uses to locate the DLL or shared object on the various platforms for the runtime location:
Environment Variables
Operating System
Environment Variable
Windows
PATH
AIX
LIBPATH
HPUX
SHLIB_PATH
Linux
LD_LIBRARY_PATH
Solaris
LD_LIBRARY_PATH

0 COMMENTS

We’d like to hear from you!