Thursday, March 27, 2014

Sterling Integrator Map Editor translation Process

These steps list the sequence of how the translator executes rules while processing the Input side of a map.
  1. Load the Input definition.
  2. Read a block of data from the Input file.
  3. If the record is the first record of a group, run On_Begin rule, if present.
  4. Load each field within the first/next record within the current group and then execute field level rules (for each field) in the following sequence:
    1. Execute standard rules
    2. Execute extended rules
  5. At the end of the group, execute the On_End rule, if present.
  6. Repeat steps 2 - 5 for each group in the Input file.
 These steps list the sequence of how the translator executes rules while processing the Output side of a map.

  1. Verify whether or not data exists for the first/next record.
  2. If the record is the first record of a group, run On_Begin rule, if present.
  3. Load each field (via simple links) within the first/next record within the current group and then execute field level rules (for each field) in the following sequence:
    1. Execute standard rules
    2. Execute extended rules
  4. Format data according to specified field properties on the Field Properties dialog box.  This refers to field length and field format settings (string, date/time, numeric).
  5. Write the record to the Output file.
  6. At the end of the group, execute On_End rule, if present.
  7. Repeat steps 1 - 6 for each record in the Output file.
  8. Create or update the document entry in the database


No comments:

Post a Comment

Introducing a rate limiter feature in IBM Sterling Integrator allows for comprehensive API functionality without the need to invest in additional API tools.

To activate and integrate the rate limiter feature in Sterling Integrator for comprehensive API functionality, follow these steps. To ...