[resolved] Mediation route using TalendJob runtime configuration options?

One Star

[resolved] Mediation route using TalendJob runtime configuration options?

Greetins all,
I have a mediation route (named DLQNotification) using the cTalendJob component.
This cTalendJob component refers to an integration job (named CentricAlertNotificationHandler) and a context.
After exporting the mediation route, the integration job is included in the .kar file automatically I've noticed and also deployed into the runtime after copying the .kar file to the deploy directory.

Question
=======
Is it possible to update the values of the job context variables after deployment in the runtime? The integration job uses a database connection which details of I'd like to externalize of course.
I've tried to create a DLQNotification.cfg file under the etc/ directory(same name as the camel route) no success, only my camel route picks up the values, the integration job ignores the values.
I also tried to create a CentricAlertNotificationHandler.cfg file under the etc/ directory - same effect, parameters in .cfg file are ignored...
The jobs are listed as follows in the runtime:
CentricAlertNotificationHandler (0.1)
DLQNotification (0.1)
Please advice.
All the best,
Robin Huiser

Accepted Solutions
One Star

Re: [resolved] Mediation route using TalendJob runtime configuration options?

Ah, got this working!!!
Seems the Talend Job **DOES NOT** re-read its configuration after a restart:
karaf@trun> config:edit CentricAlertNotificationHandler
config.propset db_hostname "your_db_hostname"
config.propset db_port "your_db_port"
config.propset db_schema "your_db_SID"
config.propset db_username "your_db_user"
config.propset db_username "your_db_password"

# Verify configured settings
karaf@trun> configSmiley Tongueroplist

# Activate modified settings
karaf@trun> config:update
# karaf@trun> restart <PID_of_CentricAlertNotificationHandler>
If you restart the container or uninstall -- install the route (including the Talend Job), it works as expected.

All Replies
One Star

Re: [resolved] Mediation route using TalendJob runtime configuration options?

Ah, got this working!!!
Seems the Talend Job **DOES NOT** re-read its configuration after a restart:
karaf@trun> config:edit CentricAlertNotificationHandler
config.propset db_hostname "your_db_hostname"
config.propset db_port "your_db_port"
config.propset db_schema "your_db_SID"
config.propset db_username "your_db_user"
config.propset db_username "your_db_password"

# Verify configured settings
karaf@trun> configSmiley Tongueroplist

# Activate modified settings
karaf@trun> config:update
# karaf@trun> restart <PID_of_CentricAlertNotificationHandler>
If you restart the container or uninstall -- install the route (including the Talend Job), it works as expected.