Summary: This document provides basic information about the extension providing Apache Camel support for Java.
Please see Apache Camel - 1.0 - Release Notes for more information.
In what situation should you install this extension?
This extension should be installed when your Java application consists of Apache Camel Routes. Objects created for the components encountered in Apache Camel Route are linked to objects produced by the JEE Analyzer. This will result in better transactions and calculation of Automated Function Points.
Function Point, Quality and Sizing support
- Function Points (transactions): a green tick indicates that Function Point counting and Transaction Risk Index are supported
- Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist
|Quality and Sizing|
CAST AIP compatibility
|CAST AIP release||Supported|
Supported DBMS servers
This extension is compatible with the following DBMS servers:
|Microsoft SQL Server|
|Installation of any compatible release of CAST AIP (see table above)|
Download and installation instructions
Include the extension using the interface in AIP Console:
There is nothing further to do. Any Apache Camel configuration defined in XML files in the application source code will be automatically detected. Follow the instructions below to run a new analysis/snapshot to generate new results:
- Modern application onboarding - run the initial deep analysis
- Legacy application onboarding - Step-by-step onboarding - Run the analysis
What results can you expect?
Once the analysis/snapshot generation is completed, you can view the results in the normal manner (for example via CAST Enlighten):
|Apache Camel HTTP Get Operation|
|Apache Camel JMS Queue Receive||Apache Camel Unknown ActiveMQ Queue Receive|
|Apache Camel HTTP Put Operation|
|Apache Camel JMS QueueCall||Apache Camel Unknown ActiveMQ Queue Call|
|Apache Camel HTTP Post Operation|
|Apache Camel Unknown JMS Queue Receive||Apache Camel RabbitMQ Topic Receive|
|Apache Camel HTTP Delete Operation|
|Apache Camel Unknown JMS Queue Call||Apache Camel RabbitMQ Topic Call|
|Apache Camel HTTP Any Operation|
|Apache Camel IBM Queue Receive||Apache Camel Unknown RabbitMQ Topic Receive|
|Apache Camel Route Call|
|Apache Camel IBM Queue Call||Apache Camel Unknown RabbitMQ Topic Call|
|Apache Camel Route|
|Apache Camel Unknown IBM_Queue Receive||Apache Camel File|
|Apache Camel Bean Call|
|Apache Camel Unknown IBM Queue Call||Apache Camel File Call|
|Apache Camel Process Call|
|Apache Camel ActiveMQ Queue Receive||Apache Camel Kafka Topic Receive|
|Apache Camel Database Query|
|Apache Camel ActiveMQ Queue Call||Apache Camel Kafka Topic Call|
|Apache Camel Unknown Kafka Topic Receive||Apache Camel Unknown Kafka Topic Call|
Only callLinks are created between various objects created by this extension.
XML DSL- callLink between REST POST service and Apache Camel Route Call
Java DSL- callLink between REST POST service and Apache Camel Route Call
XML DSL - callLink between REST DELETE and Apache Camel Route Call
XML DSL - callLink between REST PUT and Apache Camel Route Call
XML DSL - callLink between ApacheCamel Route and Apache Camel Route Call
Java DSL - callLink between Apache Camel Route and Apache Camel Route Call
Java DSL - callLink between Apache Camel Route (seda) and Apache Camel Route Call (direct)
XML DSL - callLinks between Rest POST service and Bean Call, Process Call
Java DSL - callLinks between Rest POST service and Bean Call, Process Call
XML DSL - callLink between Apache Camel Route and Bean Call
XML DSL - callLink between Apache Camel Route and Process Call
Java DSL - callLinks between Apache Camel Route and Bean Call, Process Call
XML DSL - callLinks between REST Post Service and JDBC Query
Java DSL - callLink between REST Post Service and JDBC Query
Java DSL - callLink between JMS Queue Receive and JMS Queue Call
XML DSL - callLink between File and File Call
Java DSL - callLink between File and File Call
Java DSL - callLink between File and Bean Call
Java DSL - callLink between Apache Camel Route and Kafka Topic Call
Java DSL - callLink between Kafka Topic Receive and File Call
callLinks in the complete transaction
- Unknown queue/process/bean/route/file/jms/kafka object is created in case where the exact name can't be retrieved
- Routes defined using route templates result in unknown route objects
- All other route components are ignored. Any Route starting with a component not mentioned in the Object section , the whole of the Route with its components will be ignored.
- Any component created with a customized name will not be handled or created
- There may be missing/multiple links instead of one between process call and process method of the target class
- There may be multiple links instead of one between bean call and target method of the bean
- There may be incorrect bookmarks in few call links and objects
- One of the signature for the overloaded method idempotentConsumer method of org.apache.camel.model.ProcessDefinition is not supported. This suspends the creation of the objects for the components in that route following this method.
- Current version does not support Kafka topic using Kafka idempotent repository
- Consuming messages from multiple Kafka topics is not supported
- Kafka topic receive/call object is always created by the name whatever is present in Kafka component topic. There is a possibility that name mentioned of the topic is an alias and refers to something else. Due to some design constraints, it will not be evaluated to refer to the exact value. Hence, object will be created in the name present in Kafka component.
- More Components Support, Better Linking, Fixing Bookmark Issue, Custom Component Support.