Once-only executable

[rbespalovnc]

A Job definition has a property "Once-only executable" ( JobModel.singleExecutable )

Is it possible to use this property to force Cronjobs derived from this definition to run one after another in a queue?

Some context: datahub sends some data to hybris. For each data import a new cronjob of type ImpEx-Import is created. But they are not always executed in the same order as they were created. I wondered if there is a way to enforce that.

[Former Member]

Have you considered a composite cronjob which includes in itself several cronjobs to be run sequentially?

[rbespalovnc]

I don't think that helps me. Some context: datahub sends some data to hybris. For each data import a new cronjob of type ImpEx-Import is created. But they are not always executed in the same order as they were created. I wondered if there is a way to enforce that.

[Former Member]

You cannot control the execution order of independent tasks once they are in the tasks table where all background processes ended up. Thus you will need to customize the way of what is being executed on Hybris side once the DH initiates publishing.

[bbardakov]

Ruslan, you may fire an event within the cronjob to stnother job