New OpenESB monitoring tools.docx
| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
...
| # | User Story Title | User Story Description | Priority | Notes |
|---|---|---|---|---|
| 1 | Capability to add multiple JMX servers for management | The user should be able to add any JMX server | 1 | |
| 2 | Admin console should remember the JMX servers once added | 1 | ||
| 3 | User should be able to perform Open ESB management tasks. |
| 1 | |
| a. JBI component operations: List, install, uninstall, start, shutdown | 1 | |||
| b. Shared Library operations: List, install, uninstall | 1 | |||
| c. Service Assembly operations: List, deploy, undeploy, start, stop, shutdown | 1 | |||
| d. Configure application variables | 1 | |||
| e. Configure application configuration | 1 | |||
| f. Configure component configuration | 1 | |||
| g. Change log levels | 1 | |||
| 4 | All the configurations should be persisted in a xml file | 1 | ||
| 5 | Ability to export and import a configuration along with deployed artifacts | This will help in replicating the configuration to various environments | 2 | |
| 6 | Ability to define groups of instances and manage the groups together | Each instance in a group have same exact configuration. Any operation on a group will trigger operation on each instance in that group. This can be achieved by adding multiple jmx connections to a group. (Refer to New OpenESB monitoring tools.docx written by Paul Perez attached- New OpenESB monitoring tools.docx) | 2 |
User interaction and design
...