Hello everyone,
with version 3 Camel has dropped support for multiple Camel contexts,
which we have been using extensively. Our software may be licensed as
on-premises or as cloud service and offers every customer the option of
using Camel to e. g. import files from email servers (or FTP or REST
etc.) or publish files / data via REST / SQL / SMB etc. to external servers.
With Camel 2.x we created a separate Camel context for each customer to
ensure that:
1. every customer can choose a meaningful route id (e. g.
"text-extraction" or "invoices") without duplicates causing errors
2. customers may only edit their own configuration and start / stop
their own routes / context
3. customers do not have access to other customers' routes (e. g. by
allowing the "vm" component to only address routes within the same context)
3. configuration errors do not cause Camel processing of other customers
to stop working
4. we can just copy a customer's Camel configuration from our cloud
system to an on-premises system or vice versa if the customer wishes to
change his license
5. our support team may quickly and easily help in configuring or
troubleshooting Camel without having to identify which routes belong to
whom first
So, my question is: With Camel 3+ how may we achieve the same separation
of services? Info: We use Wildfly application server as environment for
our code to run (on Linux and Windows).
Best regards
Ronny
--
*sc synergy GmbH*
Hilgestrasse 14 | 55294 Bodenheim | Deutschland
Fon: +49 6135 71691 - 000 | Fax: +49 6135 71691 - 199
http://www.scsynergy.com | ronald.fei...@scsynergy.com
Sitz der Gesellschaft Bodenheim, HRB 8830, Amtsgericht Mainz,
Geschäftsführer: Christian Reichert
