Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Card settings
Input card settings
Failure Action

Projects
A project is a container for HCL Link artifacts.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Maps
  Maps define input and output specifications and mapping rules for data transformation.
  - Using Maps
  - Create maps to specify sources and targets
  - Maps and map source files
    Basic tasks involved in creating and managing maps.
  - Input and output cards
  - Card settings
    - Schema
    - Input card settings
      - Input data retrieval
      - WorkArea
      - Fetch Unit
      - Connection
      - Command Line
      - Action properties
        Each adapter defines a set of properties that are configured to specify the source of the data for the input card.
      - Transaction settings
      - Success Action
      - Failure Action
      - Transaction Scope
    - Output card settings
    - Input and output card settings
    - Effects of modifying a schema
    - Changing a type that is used for a card
    - SyntaxCard
      The SyntaxCard setting defines the output card as a syntax card.
    - Editing a card
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map settings
  - Configuring bursts
  - Building maps
  - Running a map
  - Managing invalid data
  - Map audit overview
  - Troubleshooting
  - Error and warning messages
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
- Connections and Actions
  This documentation describes connections and actions.
- Files
  Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.

Failure Action

The Failure Action setting specifies the location of the source data if the map, burst, or card does not successfully complete.

Note: The exact meaning and availability of the options for this setting is adapter-specific. See your adapter documentation for more information.

The Failure Action setting works with the Scope setting, which defines when to apply the action specified with the Failure Action setting.

Value

Description

Rollback

Any changes made during map processing are rolled back and the original state of the data is restored.

If the map, burst, or card does not complete successfully, rollback any changes that were made to the source data during map execution.

For example, if the source of the input data was a stored procedure in a database that changed the contents of one or more tables, such as with an INSERT or UPDATE statement, if the map fails, the Rollback option would restore the affected tables to their original state.

Commit

If the map, burst, or card does not complete successfully, commit any changes that were made to the source data during map execution.

If the map fails, send the message produced for the output card to the specified message queue.

For example, if the source of the data was a message on a message queue and the message is removed from the source message queue, regardless of whether the map succeeds or not.