Say that the guide explains the case in which Camunda is installed on the Admin Server, but that it can also be applied to install Camunda in an Admin + Managed Server setup.
We should remove the box about creating a shared library via UI, because we found that this does not work with our artifacts (weblogic requires extra MANIFEST.MF entries that define the version of a library (such as Specification Version); if not present, deployment fails)
Wording: Instead of "shared libraries", we should use the term "domain libraries", because shared libraries in WLS speak is the concept that the to-be-removed-box describes
We can document the parameter "weblogic.ext.dirs" that allows to define the location at which domain libraries are located (as this is useful when using different Camunda versions on different managed servers)
Task
L3 - Default