Home
Projects
A project is a container for HCL Link artifacts.
Schemas
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
Native JSON schema support
This documentation describes the Native JSON schema support.
Using native JSON schemas in a map
A native JSON schema can be used in an input card or an output card.
JSON cards and text encoding
When an input card uses a native JSON schema, the text encoding of input data is determined automatically during map execution.

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.
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
  - About schemas
    A schema defines the contents of at least one input that you intend to map or one output you intend to map.
  - Subtypes
  - Schema hierarchy
  - Defining data
  - Objects, types, and classes
  - Testing part of a schema
    You can test a schema by generating test data for an item or a group. The schema designer creates source and compiled maps that generate and validate the test data. The test-data-generation map automatically runs and produces a text file with the sample data. After that, the test-data-validation map automatically runs on the sample data file.
  - Type properties
  - Item restrictions
  - Components
  - Partitioning
  - Type inheritance
  - Native XML schema support
    HCL Link provides Native XML schema support.
  - Native JSON schema support
    This documentation describes the Native JSON schema support.
    - Importing JSON documents
      A JSON document can be used to define a schema. This process is known as importing a JSON document. Schemas defined in this way are called native JSON schemas.
    - The representation of JSON types in Link schemas
      A JSON object is represented as a group type in a native JSON schema. The components of the group type correspond to the properties of the JSON object. The name of a component, which is the name of the type of the component, corresponds to the name of the property of the JSON object.
    - Using native JSON schemas in a map
      A native JSON schema can be used in an input card or an output card.
      - JSON cards and text encoding
        When an input card uses a native JSON schema, the text encoding of input data is determined automatically during map execution.
  - Error detection
  - Error recovery
  - Schema analyzer
  - Distinguishable objects
  - Return codes and error messages
- 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.

JSON cards and text encoding

When an input card uses a native JSON schema, the text encoding of input data is determined automatically during map execution.

When an output card uses a native JSON schema, the text encoding of card output is determined during map definition. The allowed text encodings for output data are UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, and UTF-32BE.

Prior to Link 1.1.4, the output text encoding of a JSON card was selected by providing a rule on a text item component named “encoding”. The path of this component is encoding:<card name>. For example, the rule could be ‘=NONE’. In this case, UTF-8 is used. As another example, the rule could be ‘=”UTF-16LE”’. In this case, UTF-16LE is used.

In Link 1.1.4, the encoding item component was removed from native JSON schemas. The text encoding of an output card is now determined by selecting a UTF encoding for the Data Language card property. This card property is only applicable to output cards which use a native JSON schema which does not have the encoding item type. If no selection is made, UTF-8 is used for the output card. Previous maps and schemas which use the encoding item type remain valid.