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.
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.
Config.yaml commands for debugging maps
This documentation presents the config.yaml file settings that you can use for the debugging of adapter connections for maps run using non event-driven execution methods.
Logging
The logging feature enables you to specify the type of information you want to capture about adapter connections in log files.
Logging categories
The logging categories provide a variety of debugging information.

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.
    - Command Server overview
      Use execution commands to override the map settings or card settings in a compiled map when a map is run using one of the following methods:
    - Using Command Server commands
      When you run a map, you can:
    - List of execution commands
      This documentation contains information about the execution commands and associated options, including the syntax of each command and its particular usage.
    - Examples
      This documentation presents a variety of examples involving the execution of maps using various execution commands in a RUN() function and from the command line in UNIX™ and Windows™ environments.
    - Config.yaml commands for debugging maps
      This documentation presents the config.yaml file settings that you can use for the debugging of adapter connections for maps run using non event-driven execution methods.
      - Logging
        The logging feature enables you to specify the type of information you want to capture about adapter connections in log files.
        Logging categories
        The logging categories provide a variety of debugging information.
        Debug
        Use the DebugName and DebugAppend commands configured in the config.yaml file to specify how you want to create the output log file.
  - 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.

Logging categories

The logging categories provide a variety of debugging information.

They are used to determine which severity levels and components to debug.


LogX=n

Provide the specific category, such as Trace, Debug, Info, Warning or Fatal, for the log level and false to turn that logging category off, or true (to turn that category on) for n.

Example: /runtime/Connections Manager/log/
trace: true


Logging Category	Value	Description
trace	`false`	Disabled
	`true`	Enables the logging of sequence of events Example Results: Before Resource Pending <map> After Resource Pending <map>
debug	`false`	Disabled
	`true`	Enables the logging of information to diagnose adapter connection behavior Example Results: New audit file name <name> Adapter wildcard.<wildcard>
info	`false`	Disabled
	`true`	Enables the logging of general information about the state of adapter connections Example Results: :Map started InitPendingHigh reached
warning	`false`	Disabled
	`true`	Enables the logging of issues that are not severe, but might be important to know Example Results: Resource Manager table too small - using default Map warning <map>
error	`false`	Disabled
	`true`	Enables the logging of critical adapter connection errors Example Results: Map failure <map> Socket failure <socket_type>
fatal	`false`	Disabled
	`true`	Enables the logging of a fatal error Example Results: Corrupted MMC file during initialization <mmc_name> Adapter listener Initialization failure <adapter>