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.
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.

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.
    - Building a platform-specific map
  - 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.

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.

The

When a map's development is complete, the compiled map file (.mmc) is, by default, ready to be executed by a Windows system-based Map Command Server. For example, you can run a map from the Map Designer interface or a Windows system-based Map Command Server, or the Platform API that has the same byte-order and character set.

The following list summarizes the steps you will do to run maps with the Map Command Server.

Create your map
Build or build for specific platform
Transfer if necessary
Execute with the Map Command Server

To account for environmental differences, some platforms require the map to be compiled or built for that specific platform. The Build for Specific Platform command is available from the Map menu in the Map Designer. After a map is built, it can be transferred to any destination computer hosting the Map Command Server. Using your preferred file transfer method, the file must be transferred in BINARY mode to ensure that the content of the compiled map arrives in its proper format on the destination platform.

Maps already transferred to their destination platform can be executed:

from the command line
as part of a series of maps in a command file
from a program that runs an external program
using a batch file or shell script
as a task within a scheduler