Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
param1_name = param1_value_with_no_quotes
param2_name = param2_value_with_no_quotes
karaf@trun()>config:edit your_job_name
karaf@trun()>config:property-set param1_name param1_value_with_no_quotes (NOTICE! no equals sign)
karaf@trun()>config:update
karaf@trun()>refresh job_id (NOTICE! you can aquire job_id when you type list into console)
Do I create one cfg file per job? If so, what its naming convention? Where should it reside in order for the job being able to find it?How about this "hack": in the created OSGi bundle jar file, edit the file context\Defaults.properties before deploying it into the runtime environment.
param1_name = param1_value_with_no_quotes
param2_name = param2_value_with_no_quotes
karaf@trun()>config:edit your_job_name
karaf@trun()>config:property-set param1_name param1_value_with_no_quotes (NOTICE! no equals sign)
karaf@trun()>config:update
karaf@trun()>refresh job_id (NOTICE! you can aquire job_id when you type list into console)
context = UAT
prop1=karaf-prop1-override