The dropins
directory can contain manually added JARs, that extend or modify the default bundles of the Axon Ivy Engine.
Any bundle JAR that is placed in this directory will be loaded and added to the Axon Ivy Engine runtime on start. So this is a good place to add third party process elements or similar. E.g. from github.com/axonivy/bpm-beans.
You should never manually modify the content of the plugins or features directory within the installation directory. As they should only contain artifacts that were installed automatically. The clear separation of manually installed plugins simplifies the migration to newer versions of Axon Ivy.
To see resolved and started bundles of the Axon Ivy Engine run it in console mode. Type ss
as soon as the engine is started.
osgi> ss
"Framework is launched."
id State Bundle
0 ACTIVE org.eclipse.osgi_3.10.2.v20150203-1939
13 ACTIVE ch.ivyteam.ivy.bpm.engine_6.6.2.201707111243
141 RESOLVED ch.ivyteam.ivy.extension.birt_6.6.0.201707101423
In order to see analyzed dropins and configuration changes do the following:
.options
with the content
org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true
-debug
. On windows simply start AxonIvyEngineC.exe -debug
from a CLI.-consoleLog
More documentation about the `dropins` directory can be found in the eclipse wiki.