Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

tim-schwalbe-NZ
tim-schwalbe-NZ
Offline

Badges

Badges
19

Accepted Solutions

Accepted Solutions
5

Likes Received

Likes Received
14

Posts

Posts
54

Discussions

Discussions
6

Questions

Questions
48

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by tim-schwalbe-NZ
Customize the badges you want to showcase on your profile
Re: Trigger scheduler once after deployment - Adobe Experience Manager 10-02-2018
Yes that what i thought, but then it will block all other components on startup because its maybe running for 30 minutes. So no chance to do it this way. I have to create a new Service and trigger it by a custom scheduler. Thanks for all replies.

Views

1.7K

Likes

0

Replies

0
Re: Trigger scheduler once after deployment - Adobe Experience Manager 09-02-2018
If want to achieve that the scheduler runs directly on statup/after deployment but it seems it just starting after 4 hours for the first time and after that every 4 hours. The problem is the scheduler pulls data into AEM and otherwise I have to wait 4 hours for the very first execution.So the component shows nothing for the first 4 hours.

Views

1.7K

Likes

0

Replies

0
Re: Trigger scheduler once after deployment - Adobe Experience Manager 09-02-2018
@Component(enabled = true, immediate = true, metatype = true, label = "cron job", description = "cron job ")@Service(value = Runnable.class)@Properties({ @Property(name = "scheduler.expression", value = "0 0/15 * * * ?", description = "Cron-job expression Ex: '0 0/15 * * * ?' for 15 Mins"), @Property(name = "scheduler.concurrent", boolValue = false)})@Slf4jpublic class TestScheduler implements Runnable {...}

Views

1.7K

Likes

0

Replies

0
Re: Trigger scheduler once after deployment - Adobe Experience Manager 09-02-2018
I have an actual scheduler but it runs not on startup only after the 4 hours of waiting and I want it the be run immediately.What's that: tireDesignsFetchJobFactory.createJob()

Views

1.7K

Likes

0

Replies

0
Re: Trigger scheduler once after deployment - Adobe Experience Manager 09-02-2018
Can you point me to an example?

Views

1.7K

Likes

0

Replies

0
Trigger scheduler once after deployment - Adobe Experience Manager 09-02-2018
Hi guys,is it possible to trigger a scheduler once after every deployment? So the regular schedule time is 4 hours, but it will took 4 hours for the first run.Any property to set?Br,Tim

Views

4.3K

Likes

2

Replies

16
Re: Error during build -> commons-io sling-mock - Adobe Experience Manager 05-02-2018
I think its more a cross dependency issue with commons-io than an AEM problem.

Views

1.4K

Likes

0

Replies

0
Re: Error during build -> commons-io sling-mock - Adobe Experience Manager 05-02-2018
I don't know it do run locally and does build also in another pipeline.the error occurs building on jenkins an artifact and fails with this message. It's a build process out of my control so I am not really able to reproduce it.

Views

1.4K

Likes

0

Replies

2
Re: Create and Set OSGI config variable through dialog - Adobe Experience Manager 05-02-2018
Yes that's all I found. Is there maybe another way? start a the same service for every domain with different configs, without duplicating the service with another name?GooglemapsService --> config.plGooglemapsService --> config.comGooglemapsService --> config.nl...

Views

1.0K

Likes

0

Replies

0
Re: Create and Set OSGI config variable through dialog - Adobe Experience Manager 05-02-2018
Thanks Ratna So there is really no possibility to create them during runtime? Maybe someone knows a little bit more?

Views

1.0K

Likes

0

Replies

0