nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Using Scheduler Service: Quartz Persistence configuration

franciscogonzal

Hello,

I would like to know where and how could I configure quartz properties file in Nuxeo DM. I just want to persist triggers, jobs and so on (use org.quartz.impl.jdbcjobstore.JobStoreCMT) ... to avoid to lose them stopping or restarting the instance.

About exact properties to configure, I have worked before with quartz 2.2.0. I have seen that Nuxeo uses quartz 1.5.2, but I suppose the properties are similar. However, I would also like to know if there is something different I would have to take care of.

Could anyone help me please?

Thanks in adnvance

Kind Regards,

Find more posts tagged with

Comments

rg1_

Typically the scheduler service is configured via an XML extension point that gets loaded on startup. See Scheduling Periodic Events. Do you have a need to dynamically configure the scheduler service and persist that configuration?

franciscogonzal

Hello,

Thanks for your fast answer.

Yes, that's my case. I need to register triggers at execution time, with Nuxeo already running. I put an example:

I have defined calendar docType which can be assigned to other certain docTypes. Those calendars have several different features. Among them, one is to set an interval time (for example 1 month) where document would have some characteristics (as permissions, localization, etc...) and when my trigger fires (after that 1 month interval), some other actions would be executed (lifecycle transitions, move to other folder, change permissions, publish... etc).

I am familiar to both, Quartz itself and Nuxeo Scheduler Service. Untill now, in Nuxeo, I have not needed this feature, but now I have and the first idea which came into my mind was just to persist triggers.

Is there any other better solution for my problem? And, in any case, I would like to know how to configure, not just only persistence, but all other properties usually set in a quartz.properties file.

Thanks in advance.

Kind Regards