Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Parameter File Sections

Parameter File Sections

You can define parameters and variables in any section in the parameter file. If you define a service or service process variable in a workflow, worklet, or session section, the variable applies to the service process that runs the task. Similarly, if you define a workflow variable in a session section, the value of the workflow variable applies only when the session runs.
The following table describes the parameter file headings that define each section in the parameter file and the scope of the parameters and variables that you define in each section:
Heading
Scope
[Global]
All Integration Services, Integration Service processes, workflows, worklets, and sessions.
[Service:service name]
The named Integration Service and workflows, worklets, and sessions that this service runs.
[Service:service name.ND:node name]
The named Integration Service process and workflows, worklets, and sessions that this service process runs.
[folder name.WF:workflow name]
The named workflow and all sessions within the workflow.
[folder name.WF:workflow name.WT:worklet name]
The named worklet and all sessions within the worklet.
[folder name.WF:workflow name.WT:worklet name.WT:worklet name...]
The nested worklet and all sessions within the nested worklet.
[folder name.WF:workflow name.ST:session name]
-or-
[folder name.WF:workflow name.WT:worklet name.ST:session name]
-or-
[folder name.session name]
-or-
[session name]
The named session.
Create each heading only once in the parameter file. If you specify the same heading more than once in a parameter file, the Integration Service uses the information in the section below the first heading and ignores the information in the sections below subsequent identical headings. For example, a parameter file contains the following identical headings:
[HET_TGTS.WF:wf_TCOMMIT1] $$platform=windows ... [HET_TGTS.WF:wf_TCOMMIT1] $$platform=unix $DBConnection_ora=Ora2
In workflow wf_TCOMMIT1, the value for mapping parameter
$$platform
is “windows,” not “unix,” and session parameter
$DBConnection_ora
is not defined.
If you define the same parameter or variable in multiple sections in the parameter file, the parameter or variable with the smallest scope takes precedence over parameters or variables with larger scope. For example, a parameter file contains the following sections:
[HET_TGTS.WF:wf_TGTS_ASC_ORDR] $DBConnection_ora=Ora2 [HET_TGTS.WF:wf_TGTS_ASC_ORDR.ST:s_TGTS_ASC_ORDR] $DBConnection_ora=Ora3
In session s_TGTS_ASC_ORDR, the value for session parameter
$DBConnection_ora
is “Ora3.” In all other sessions in the workflow, it is “Ora2.”

0 COMMENTS

We’d like to hear from you!