Libraries and Connectors

List

Component Description
AHC Perform asynchronous calls to HTTP servers
BBMS Consume BBMS messages
Bean/Class Use custom beans/classes to modify the current body
Decision Insight Messaging System Resilient and safe communication between 2 Decision Insight
Exec Execute system commands
Flatpack Parse fixed width and delimited files
FTP / FTPS / SFTP Call external servers using the FTP, FTPS or SFTP protocol
JDBC (Databases) Load values from a database
Jetty Consume or produce HTTP requests
JNDI Connector to a JNDI-provided connector
JMS Connect to JMS queues or topic using different JMS providers
JMX Connect to JMX and fetch information
JSON Parse JSON data
Kafka Produce or consume from Kafka
Lumberjack Receive messages sent by Filebeat using Lumberjack protocol
MAIL Send emails
QLT - Tracking Objects Receive and decode monitoring events sent by Axway products
QUARTZ Trigger message with cron-like periods
RESTLET Produce or Consume REST services
SPRING-WS Perform web service calls (SOAP requests)
SQL Consume or produce SQL queries
TidyMarkup Parse malformed XML

How to update the non-embedded components

When a non-embedded component is used in the product, it needs to be synchronized with the Camel version used in the product. See How to retrieve the Camel version of Decision Insight.

Procedure:

  1. Update the Data Integration libraries with the proper camel-[component] versions.
  2. You have two ways to take the new libraries into account:
    • Simple but drastic – Restart the node.
    • Precise but longer:
      • Update the associated Data integration connectors (saves the connectors again).
      • Restart the associated Data Integration routes (stop and start).

Connector refresh

The Refresh button is used to load library and/or connector modification. An action on it will instantaneously impact all started routes.

If no refresh is done, no library or connector modification is taken into account.

Troubleshooting guide

A warning icon is displayed in the library section

When a library jar file contains an executable file (.so, .dll, .exe, ...) the whole library is disabled for security reasons and cannot be used.

In that case, an error log is produced, a warning icon is displayed next to the library and the invalid library jar files also have a warning icon.

Related Links