PoC platform user exam

What folders can you expect to be visible from a route com.sixt.integration.aena.FilterRentalAgreementsForAENA at runtime?

/data/rental/agreement/aena/share/config

/data/rental/agreement/aena/share/logs

/data/rental/agreement/aena/RentalAccountingMonthly/output

/srv/integration/solutions/rental_agreement/aena/conf/solution-conf

/srv/integration/solutions/rental_agreement/aena/conf/aena-conf

/srv/integration/solutions/rental_agreement/aena/logs

/srv/integration/solutions/rental_agreement/aena/temp

/srv/integration/solutions/rental_agreement/aena/data/solution-input

/srv/integration/solutions/rental_agreement/aena/data/solution-output

/srv/integration/shares/solution_data/rental_agreement/aena/conf/solution-conf

/srv/integration/shares/solution_data/rental_agreement/aena/conf/aena-conf

/srv/integration/shares/solution_data/rental_agreement/aena/logs

/srv/integration/shares/solution_data/rental_agreement/aena/temp

/srv/integration/shares/solution_data/rental_agreement/aena/data/solution-input

/srv/integration/shares/solution_data/rental_agreement/aena/data/solution-output

What expectations hold for folders of type 'conf'?

Conf folders shall always be accessed read-only from solutions

Conf folder content can change at solution runtime without further notice

Conf folders shall never contain binary, I.e. non-text, files

Solution conf folders shall contain just properties files, other file types are forbidden

'conf' folders need to be polled continuously for configuration updates

'conf' folder space is limited to 1MB / solution

What patterns can I use for a message-driven route in order to be resilient against downtimes of a single runtime?

Concurrent consumers (multi-threaded, multi-runtimes)

Exclusive consumers (multi-runtimes)

Concurrent consumers (single-threaded, multi-runtimes)

Concurrent consumers (multi-threaded, single runtime)

Single-server deployment for ordering guarantees

Unlock and Upgrade