Home
Design Server
The documentation provided here describes how to use the Design Server.
Schema designer
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
Schema analyzer
Error and warning messages

Design Server
The documentation provided here describes how to use the Design Server.
- Projects
  This documentation describes Design Server projects.
- Schemas
- Maps
- Flows
  A flow node invokes a sub flow within a flow. Sub-flows need not be wired to other nodes; it is valid to have a flow that is comprised of multiple sub-flows that each have listeners.
- Using Design Server
  How to use the HCL Link Design Server.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Schema designer
  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
  - Error detection
  - Error recovery
  - Schema analyzer
    - Mapping effects
    - Internal consistency
    - Logical analysis
      Logical analysis addresses the integrity of the relationships that you define.
    - Structural analysis
      Structural analysis addresses the integrity of the underlying database.
    - Error and warning messages
  - Distinguishable objects
  - Return codes and error messages

Error and warning messages

Analysis results might contain error and warning messages.

Warnings are relatively insignificant. They indicate an inconsistency that occurred when you changed something in the tree that was resolved. For example, if you change a group to an item, the analyzer removes the components of that type because items do not have components. To remind you of this change, the analyzer issues a warning.

Errors are important. An error is a problem in your type definitions that you should correct. An error may result in unpredictable results in your mapping.

Occasionally there are errors that prevent the analysis of the rest of your definitions (for example, when a component type cannot be found in the tree). Analysis halted before completion is displayed. This error might be due to one of the following:

Undefined COMPONENTs found: ending analysis.
Circular reference found in COMPONENT list: ending analysis.

When this occurs, correct the errors and analyze the tree again.