Known Issues and Workarounds
Chrome browser hangs
When a large number of items with fetch search boxes are opened in the Google Chrome browser, the browser might hang. In such cases, use Mozilla Firefox browser.
Source and Target nodes do not support legacy adapters
The Source and Target nodes do not support legacy database adapters Oracle, Sybase and DB2.
Inconsistent Cache node behaviour in Link
- Native installation – The external cache is shared with the Runtime REST API. All variables can be accessed by both components.
- Docker installation – The external cache is not shared with the Runtime REST API. You can only access variables defined within the scope of each component.
'HIP Cores not available’ error message
When running Link Map Command Server, Flow Command Server or API on Windows Server 2019, you may receive the error message 'HIP Cores not available'. If you receive this message, and you have a valid dtxlic.ini file, you might be receiving this message because you have entered the license server URL and server ID during HIP setup, and the permissions are incorrect.
- Open a command console and run it as ‘Administrator’.
- cd to the Link installation directory, for example C:\HCL Link n.n.n
- Delete the <hostname> directory and all its contents.
- If the hostname is named hip-prod, enter:rmdir /s .hip-prodand confirm with a Y.
You should now be able to run Link Command Server, or API, as a non-Administrator.
Listener set up for ActiveMQ and Kafka
When setting up a listener for ActiveMQ or Kafka, the card with the listener must set up the connection in the card itself instead of using a previously created connection.
HL7 MLLP connection type not fully functional
The HL7 MLLP connection type is included in the list of connection types in the Link web UI, but this connection type is not fully functional. Do not use this connection type when you are defining Connections, Actions and Cards.
Issue with Upload Again option for schemas
There is an issue with using the “Upload Again” option from the context menu of an XSD Schema, or a JSON Schema from the “Schemas” list. JSON templates are not affected by this issue. Instead of using the “Upload Again” option, it is recommended that if you want to update the structure of one of these types of schema, you can instead delete it and reimport the modified .json or .xsd file. Then you can update any references to that schema in your maps and flows.”
Prevention of loss of data between restarts of Redis
Dashboard statistics are kept in Redis. To prevent loss of data between restarts of Redis, persistence must be enabled. Redis, as deployed by Link will have persistence enabled by default.
Flow dashboard and Flow Stop command
Stop Runs is a new flow dashboard function that attempts to abort running flow instances. Only flows that use Split node to run procssing in parallel can be stopped. When the Stop Runs command is executed, the Split node will stop splitting the inpt data and no new threads will be executed to process data after the Split node.