Libraries and Connectors
||Perform asynchronous calls to HTTP servers
||Consume BBMS messages
||Use custom beans/classes to modify the current body
|Decision Insight Messaging System
||Resilient and safe communication between 2 Decision Insight
||Execute system commands
||Parse fixed width and delimited files
|FTP / FTPS / SFTP
||Call external servers using the FTP, FTPS or SFTP protocol
||Load values from a database
||Consume or produce HTTP requests
||Connector to a JNDI-provided connector
||Connect to JMS queues or topic using different JMS providers
||Connect to JMX and fetch information
||Parse JSON data
||Produce or consume from Kafka
||Receive messages sent by Filebeat using Lumberjack protocol
|QLT - Tracking Objects
||Receive and decode monitoring events sent by Axway products
||Trigger message with cron-like periods
||Produce or Consume REST services
||Perform web service calls (SOAP requests)
||Consume or produce SQL queries
||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.
- 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).
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.
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.