Home
Runtimes
Descriptions of Link runtime services.
Map Command Server
To use the Map Command Server to execute a map, you will prepare the maps for execution.
Troubleshooting tools

Runtimes
Descriptions of Link runtime services.
- REST API
  The REST Runtme provides a REST API used to run maps and flows that have been deployed.
- Flow Command Server
  Deploy a flow from the HCL Link to the local filesystem using Execution flow server definition.
- Map Command Server
  To use the Map Command Server to execute a map, you will prepare the maps for execution.
  - Overview
    Map Command Server is used to develop, test, and execute maps in development environments. It can also be used to execute commands in production environments.
  - Executing a map
    After a map has been built for a specific execution platform and transferred, the map can be executed using a Map Command Server.
  - Troubleshooting tools
  - External interfaces for applications, EXIT and RUN
    Maps can interface with other maps, functions in libraries, or programs using the EXIT function, the RUN function or an adapter as a data source or target.
  - Windows platforms
    There are several activities you can do with the Map Command Server that you have installed on your Windows environment.
  - Execution commands
    This documentation includes information about the various ways to use execution commands and their options when executing maps. Execution commands are used to specify how to execute a map.
  - Utility commands
    You can use the utility commands to do various functions.
- SDK
  The LNK programming interface includes language-specific methods and objects that provide common functionality across multiple environments.

Troubleshooting tools

When a map begins to run, the first thing that occurs is the validation of the input data-performed by comparing the data to the schema definition.

After data validation completes, the map rules are evaluated for the output cards and output objects are built.

When a map executes, invalid or unknown input data may be encountered and you may want to analyze what happened during the validation process. You may also want to analyze the output data if the map did not produce the expected results.

Many debugging aids are available to assist you through the troubleshooting process including:

A Map Command Server display of ongoing execution information
Map Command Server return codes and messages
Map audit log files, including data audit, execution audit, map settings, and card settings information
Map trace files
If an adapter is used, adapter-specific return codes and messages, audit log files, and trace files