IntegrationManager 1.3.0
In this section:
Migration Steps
Major Dependency Changes
- IM library dependency version 1.3.0
- Spring boot version 2.3.3
- Camel version 3.5
Camel Official Upgrade Guides
Go through the list of updates mentioned in the following official guides:
- https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_3.html
- https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_4.html
- https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_5.html
Note: Health check has been refactored – if you monitor health of the Camel / Camel routes by yourself, read carefully this guide.
Aggregations
Available aggregation strategies are now by default loaded into the Camel context. If you do not want to use this functionality, set the integration.aggregations.enabled property to false. See the documentation for more details.
Converters
Available converters are now by default loaded into camel context. If you don't want to use this functionality, set property integration.converters.enabled=false. See the documentation for more details.
Improvements
| New Feature Description | ID |
|---|---|
| Custom events are now properly fetched via their eventType and are routable in EventRoute. Use syntax CUSTOM.MYEVENT_TYPE when you want to fetch an event named CUSTOM and eventType named MYEVENT_TYPE. Note that fetching such subtypes must search through a plaintext parameter and might be slower. | PFIMCORE-302 |
| Aggregation strategies are now defined in the Spring context and accessible in the Camel context. | PFIMCORE-559 |
| It is possible now to define, store and use filters via REST API. | PFIMCORE-560 |
| CI/CD release does not commit any artifacts any more. | PFIMCORE-575 |
| It is no longer required to run a manual job im-new-release.sh on nexus when releasing a new version/hotfix. | PFIMCORE-576 |
| Some identified tests which provided a non-deterministic result were enhanced with better asserts. | PFIMCORE-577 |
| Camel is now upgraded to version 3.5. | PFIMCORE-579 |
| Spring Boot is now upgraded to version 2.3.3. | PFIMCORE-580 |
| All application tests were migrated from JUnit to Spock. | PFIMCORE-581 |
| PFX components have been refactored and optimized according to the Camel standard. | PFIMCORE-582 |
| There is a new Converters API which allows to get available converters or convert directly via API. | PFIMCORE-584 |
| Bean lookups moved to a single Lookup service. | PFIMCORE-588 |
| IM REST client now has methods for filters/aggregations/converters. | PFIMCORE-589 |
| Data load is now scalable when data load requests are sent to the kafka topic dataload-requests. | PFIMCORE-591 |
| The integration.configuration property now handles only the FileSystem storage. API for routes, mappers etc. will always be deployed. | PFIMCORE-592 |
| Heapdump endpoint is now available within IM. | PFIMCORE-593 |
| JVM will not shut down when an invalid route from a route repository is loaded. | PFIMCORE-595 |
| When there are multiple active Pricing Parameters, the most relevant by the activeDate is used. | PFIMCORE-596 |
| Routes are now stored in files per route name and contain a real definition (also with the dynamic onCompletion block if applied and customIds). Route cleanup is fixed for two consequent routes. | PFIMCORE-597 |
| Config server can now handle multiple custom IM applications. | PFIMCORE-598 |
| IM will now search for log files using regex defined by the integration.logging.file.pattern property. The default regex is main.*.gz | PFIMCORE-599 |
| Groovy sandbox now permits all converters defined in IM. | PFIMCORE-614 |
| Period config-server checks will no longer appear in logs unless an error occurred. | PFIMCORE-615 |
Fixed Issues
| Bug Description | ID |
|---|---|
| Service call for metadata does not trigger the caching mechanism. | PFIMCORE-558 |
| Deploying routes makes IM freeze and not answer in the given timeout of 10 s. | PFIMCORE-590 |
| Plugin runner does not load routes from camel-context.xml. | PFIMCORE-613 |
IntegrationManager version 5.0.0