Goals
- To develop a unified admin console to manage and monitor OpenESB components.
Background and strategic fit
OpenESB is now capable of running on many application servers like Glassfish v2, Glassfish V3, Tomcat, Jboss 5, Jboss 7 and even can run standalone also. This arises a need for managing the JBI components on these many platforms. We need a admin console which can connect to OpenESB running on any platform and be able to manage through this unified console.
Assumptions
- This admin console is UI based. There is a separate requirement for developing command line administration
- We will use JSF framework with Primefaces or any other equivalent as UI layer.
- The UI based admin console will use only JMX for management of JBI components
Requirements
| # | 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 | Must | |
| 2 | Admin console should remember the JMX servers once added | Must | ||
| 3 | User should be able to perform Open ESB management tasks. |
| Must | |
| a. JBI component operations: List, install, uninstall, start, shutdown | Must | |||
| b. Shared Library operations: List, install, uninstall | Must | |||
| c. Service Assembly operations: List, deploy, undeploy, start, stop, shutdown | Must | |||
| d. Configure application variables | Must | |||
| e. Configure application configuration | Must | |||
| f. Configure component configuration | Must | |||
| g. Change log levels | Must |
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|