The application server was updated to WildFly 17 and Java 11.0.3.
Also see the official announcement: https://wildfly.org/news/2019/06/10/WildFly17-Final-Released/.
In versions 2.12.x and 2.13.x the following tasks were triggered by internal non-configurable Java-timers. (Up to IOM version 184.108.40.206 they were defined as quartz jobs).
Their configuration can now be modified within the table
The quartz job
"JOB_FRAMEWORK" which was responsible for triggering the due schedules has also been replaced by an internal Java timer. Make sure it is removed from the quartz configuration file (quartz-jobs-cluster.xml)
Prevention of Removal of Core-Schedules
Some triggers prevent the deletion of the core-schedules, but you can deactivate non-required ones. You may check you setup/ migration scripts not to use a non-selective deletion of the table "
For the migration to IOM 220.127.116.11, the schedules with the following values should be reviewed as they may not match your requirements:
|Feature area||since IOM version||Job key||Description||Initial cron-expression||Max. retries||Retry delay||isCoreSchedule|
|Invoicing||18.104.22.168||aggregate_invoices4dispatches_daily||Run invoice aggregation for orders with a dispatch on a daily base.||0 30 23 1/1 * ? *||10||10m||true|
|Invoicing||22.214.171.124||aggregate_invoices4dispatches_weekly||Run invoice aggregation for orders with a dispatch on a weekly base.||0 30 23 ? * FRI *||10||10m||true|
|Invoicing||126.96.36.199||aggregate_invoices4dispatches_monthly||Run invoice aggregation for orders with a dispatch on a monthly base.||0 30 23 L 1/1 ? *||10||10m||true|
|Invoicing||188.8.131.52||aggregate_invoices4dispatches_weekly_cleanup||Run invoice aggregation for orders with a dispatch on a weekly base. This job takes into account all dispatch positions that are not yet invoiced into an invoice. It results that at the end of the month all dispatch positions are invoiced, rega (...).||0 45 23 L 1/1 ? *||10||10m||true|
|Invoicing||184.108.40.206||aggregate_invoices4dispatches_disabled_cleanup||Run invoice creation for orders with a dispatch but no invoice yet. This job takes into account customers that disabled aggregated invoices after using them for a while. The last aggregated invoice could be missing here.||0 50 23 1/1 * ? *||10||10m||true|
|Impex||220.127.116.11||CHECK_FOR_DATAPACK_FILES||Check the content of the $OMS_VAR/importarticle/in the folder for new files to import and trigger the import when required.||0 * * ? * * *||30||10m||true|
|Impex||18.104.22.168||ARTICLE_EOL_DETECTION||Trigger the postgres stored procedure article_eol_detection to possibly set articles as being out of live.||0 33 3 ? * * *||20||27m||true|
|Impex||22.214.171.124||AGGREGATE_ARTICLE_JOB||Check for modified articles and trigger an update of the information contained in the table "ArticleInfoArticleAO".||0 33 4 ? * * *||20||27m||true|
|Impex||126.96.36.199||CLEAN_ARTICLE_IMPORT_ERRORS||Trigger the postgres stored procedure process_clean_article_import_errors: remove import error information older than 30 days.||0 57 4 ? * * *||20||27m||true|
|Impex||188.8.131.52||CLEAN_ARTICLE_EXPORT_FILTER||Trigger the postgres stored procedure process_clean_article_export_filter: delete information on exported articles older than 30 days (in table product."ArticleExportFilteredArticleDO").||0 */1 * ? * *||20||7m||true|
|Impex||184.108.40.206||ARTICLE_EXPORT||Trigger the article export as configured within the postgres table product."ArticleExportConfigDO".||0 */5 * ? * * *||20||7m||true|
|Impex||220.127.116.11||ORDER_EXPORT||Trigger the CSV order export as configured within the postgres table oms."OrderExportConfigDO".||0 17 * ? * * *||20||7m||true|
|Impex||18.104.22.168||CUSTOMER_EXPORT||Trigger the customer export as configured within the table customer."CustomerExportConfigDO"||0 7 * ? * * *||20||7m||true|
|Order Changes||22.214.171.124||ORDERCHANGE_LOCK_CLEANUP_JOB||Fix invalid pending OrderChangeRequest references in OrderDO.||0 */4 * ? * * *||20||27m||true|
For more information on schedules see:
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.