Event level configuration

In Pacemaker Community Edition, additional events are available to add your functions.

That provides events in addition to configured processes with:

It is possible to register global events, plugin and subject-level events as well.

That avoids executing events that only provide functionality for a specific plugin or subject, and they are not triggered for each plugin or subject.

  • It is strongly recommended that, by default, the value for custom-configuration-dir is <magento-install-directory>/app/etc/configuration

  • As soon as a default configuration is copied, changed, extended, or modified and stored under the path specified in custom-configuration-dir, only this configuration takes effect and always overwrites the original configuration

  • The configuration handling is mainly based on the PHP framework Symfony, and therefore unexpected effects maid occur in different configuration constellations

    • Consequently, it is always recommended to test modified configurations concerning unwanted side effects

Event Name Description

app.set.up

The event gets triggered before the import get processed

app.tear.down

The event gets triggered after the import get processed

app.process.transaction.start

The event gets triggered before the application will start the transaction

app.process.transaction.success

The event gets triggered after the application has the transaction committed successfully

app.process.transaction.failure

The event gets triggered after the application has rolled back the transaction

app.process.transaction.finished

The event gets triggered after the application transaction has got finished (successful or not)

subject.artefact.process.start

The event gets triggered before an import artifact will get processed

subject.artefact.process.success

The event gets triggered when an import artifact has successfully get processed

subject.artefact.process.failure

The event gets triggered when an import artifact can not get processed

subject.artefact.row.process.start

The event gets triggered when an import artifact has successfully get processed

subject.artefact.row.process.success

The event gets triggered when an import artifact has successfully get processed

subject.artefact.header.row.process.start

The event gets triggered before an import artifact header row will get processed

plugin.process.start

The event gets triggered before the plugin process() method will get processed

plugin.process.success

The event gets triggered after a plugin process() method has got processed

plugin.process.failure

The event gets triggered when an exception has got thrown during the plugin process() method get processed

plugin.export.start

The event gets triggered before a plugin export() method will get processed

plugin.export.success

The event gets triggered after a plugin export() method has got processed

plugin.export.failure

The event gets triggered when an exception has got thrown during the plugin export() method get processed

subject.import.start

The event gets triggered before a subject import() method will get processed

subject.import.success

The event gets triggered after a subject import() method has got processed

subject.import.failure

The event gets triggered when an exception has got thrown during the subject import() get processed

subject.export.start

The event gets triggered before a subject export() method will get processed

subject.export.success

The event gets triggered after a subject export() method has got processed

subject.export.failure

The event gets triggered when an exception has got thrown during the subject export() get processed