Dear Vikash,Have a look at following adaptTo presentation from this year, it may answer the question you currently have[0].[0] https://adapt.to/2018/en/schedule/migrating-a-large-aem-project-to-touchui.htmlRegards,Peter

Dear James,Deactivate later is OOTB functionality present in AEM.Delete after deactivate is not OOTB and would require a customisation.This customisation can be achieved using AEM Workflow system.Regards,Peter

Are you working through corporate proxy?These things like to intercept POST requests. E.g. upload of .jar is blocked and you get 405 as a response.Regards,Peter

Dear Sir,Have a read through this answer: cURL command to update service config property It details how you should record your curl requests.My expectation is that you do not have correct parameters sent with your request. Therefore, OSGi config manager fails.Regards,Peter

Dear Endoriel,9 is already out of public support window and contains vulnerabilities, most of corporates will stick with JDK 11, so it would be expected you get 11 support.Regards,Peter

Hi Timo,Or even simpler 0 1 * * * to 0 2 * * *You can further debug this by making a newCronTrigger in unit test and verifying the outcome.Regards,Peter

Hi Timo,Then you may want to change the cron to: 0 0 1 * * ? to 0 0 2 * * ?Regards,Peter

Dear Timo,Did you checked /status-slingscheduler as I have suggested, have you noted values you seen there?Have you tried installing SP2 to test whether this issue get's resolved in 6.3.2?Regards,Peter

Dear Timo,Suggest you put it to some soon starting time.Put com.adobe.granite.maintenance in DEBUG log level.Verify the slingscheduler has correct date, then once the date/time is reached. To verify timings open http://localhost:4502/system/console/status-slingscheduler and find your job:DEFAULT.com...

Dear Manasip,The fact that the log file got created in a first place is good. it means that the log service has registered.Are you logging with the info and higher level's to this file?How are you registering your logger through .java code?Do you have any other log file that could be stealing output...