-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
- Beginning of the guide
- 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)
- https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-ear-file
- The point about changing the name should be reworded. Renaming is permitted. We should make the users aware how this affects the JNDI bindings
This is the controller panel for Smart Panels app
[CAM-9789] Clarify WLS domain deployment options in installation guide
| Description |
Original:
* Beginning of the guide
** 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. * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-camunda-bpm-platform-shared-libraries ** 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) * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-ear-file ** The point about changing the name should be reworded. Renaming is permitted. We should make the users aware how this affects the JNDI bindings |
New:
* Beginning of the guide
** 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. ** Say that one server (Managed or Admin) is tied to one Camunda version, but that multiple servers can run multiple versions * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-camunda-bpm-platform-shared-libraries ** 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) * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-ear-file ** The point about changing the name should be reworded. Renaming is permitted. We should make the users aware how this affects the JNDI bindings |
| Link | New: This issue is depended on by SUPPORT-5359 [ SUPPORT-5359 ] |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 12688 ] |
| Assignee | New: Tassilo Weidner [ tassilo.weidner ] |
| Rank | New: Ranked higher |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | Original: Tassilo Weidner [ tassilo.weidner ] | New: Thorben Lindhauer [ thorben.lindhauer ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Remaining Estimate | New: 0 minutes [ 0 ] | |
| Original Estimate | New: 0 minutes [ 0 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Description |
Original:
* Beginning of the guide
** 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. ** Say that one server (Managed or Admin) is tied to one Camunda version, but that multiple servers can run multiple versions * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-camunda-bpm-platform-shared-libraries ** 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) * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-ear-file ** The point about changing the name should be reworded. Renaming is permitted. We should make the users aware how this affects the JNDI bindings |
New:
* Beginning of the guide
** 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) * https://docs.camunda.org/manual/7.10/installation/full/wls/manual/#install-the-ear-file ** The point about changing the name should be reworded. Renaming is permitted. We should make the users aware how this affects the JNDI bindings |