A project is a container for HCL Link artifacts.
This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
This section lists the settings available for the Map Rule Node.
Congratulations on your selection of HCL Link as your data integration solution!
A complete desciption of the hardware and software requirements for both Windows and Linux systems.
Everything you need to know to install HCL Link.
Here you will find the tasks that are required for administration of your HCL Link product.
A Map Node invokes an HCL Link map within a flow.
A Flow node invokes a sub-flow within a flow.
Source and Target Nodes provide HCL Link with an outside-in approach to developing integrations.
The Request Node has a single input request terminal and a single output response terminal.
Cache Read and Cache Write node functionality is described in this section.
The Clone Node has one input and two output terminals.
The Decision Node routes input data to the true, or false terminals depending upon the condition.
The Fail Node causes the flow execution to fail.
The Format Converter Node can be used to quickly convert data from one format to another.
This documentation describes the function and use of the JSON Read Node.
The JSON Transform node is used to transform JSON documents from one form to another.
The Java Node invokes a Java class, thus performing user defined functionality based on the properties specified for the Java class to act on the input.
The Join Node gathers the individual results and appends to a single output file or terminal.
The Log Node logs the raw data from the node input into the file and propagates the data from the input to the output terminal.
Lock and Unlock nodes are used to manage resource locking within flow executions. The Lock node controls access to resources and restricts the execution of the current branch in the flow execution. The Unlock node releases the lock previously acquired within the current branch.
The Passthrough Node propagates data from the input to the output terminal.
The REST Client Node provides a simple and powerful way to access REST services.
The Route Node provides a way to route data conditionally to one or more outputs of the node. The node bases decisions by evaluating a condition for a flow variable and determining whether to send the data to output 1 or 2 or both, based on the result of the condition.
The Sleep Node suspends the execution of the flow for the specified number of milliseconds
The SOAP Client Node provides a simple and powerful way to access SOAP services.
A Split Node should be used when there is a need to split CSV or JSON data processing or when a map can run in a burst mode to process data in batches. This might occur when data processing becomes excessively time consuming.
A Status Node can only be used as the first node in a ‘’status flow”, as that what makes a flow a status flow. Similar to an initialization flow, a status flow may be referenced from any other main flow. A status flow has a Status node as its first node which has Success, Error and Always output terminals that provide the flow status JSON to a downstream node.
Flow terminals represent the inputs and outputs to a flow. Every node has input and/or ouptut terminals.
This documentation describes the options for defining the flow schedule.
A Flow that has a Map node as its first node, and uses a File adapter for an input, can enable that node's input to be a Watch.
Flow audits are a way to retrieve more verbose information about a flow instance.
Flow Variables are process data variables that go along with the flow execution, accessible to all nodes in the flow while it is being executed under flow executor/engine context.
Steps required to create a flow.
When you develop a flow in the Flow Designer you can run the flow directly from the Designer either in Link, or on a different runtime environment.
Maps define input and output specifications and mapping rules for data transformation.
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
This documentation describes connections and actions.
Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.
Service definitions define REST services and the endpoints of a service. This guide provides step-by-step instructions for creating, importing, and managing services using the system interface, following Microsoft standards.
This documentation describes the connectors and how they are used.
This documentation contains a description of the server groups and servers.
The variables described here include Configuration variables, flow variables, and cache variables.
A description of HCL Link dashboards, including the Server dashboard and the Kibana dashboard.
Descriptions of Link runtime services.
About the HCL Link Resource Adapters, and how to use them.
Cloud Native Link refers to the HCL Link product installation on a Kubernetes cluster.
This documentation provides HCL Link reference information.
