Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Building maps

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
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map settings
  - Configuring bursts
  - Building maps
    - Referenced maps
    - Multi-platform maps
      You can compile a map to run on multiple platforms, for example, on Microsoft™ Windows™, and Linux™. At run time, HCL Link runs the appropriate version of the map for the platform.
    - Including a static input file in a compiled map
      You can include a static input file in a compiled map to reduce processing overhead in maps that run multiple times.
    - Building a map
      Building a map compiles it into an executable map.
    - Rebuilding a map that has changed
    - Schema errors
    - Map build analysis errors
    - Map build warning messages
    - Map build compile errors
    - Compiled map files
  - 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.

Building maps

After you have entered map rules in an executable map, created necessary functional maps, and entered map rules for the desired output data objects, the next step is to build the executable map. A compiled map file is created when no build errors occur when the executable map, and all referenced maps, are analyzed.

An executable map has a data source or target specified for each of its cards. Executable maps are built. Functional maps are not built.

Data sources and targets specified for an executable map are defaults built into the compiled map file. Data sources and targets, and other map settings, can be overridden when the map is invoked from a RUN map, Command Server, or from a flow.