HAI Use Case: Turn on/off BES debugging and view/save/stream the output: Difference between revisions
(New page: {{subst:Template:Use_Case}}) |
No edit summary |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
'''Point Of Contact:''' '' | [[Category:HAI]] | ||
'''Point Of Contact:''' ''[[User:ndp | Nathan Potter]]'' | |||
== Description == | == Description == | ||
Allows the Administrator to control the BES logging framework. | |||
== Goal == | == Goal == | ||
Improving Admin problem solving by allowing the Admin to easily start and stop debug logging for the BES and its component, and to capture to a file or stream the debugging output of the BES. | |||
== Summary == | == Summary == | ||
The Admin logs into the HAI and uses the HAI interface to control and direct the output of the BES logging framework. | |||
== Actors == | == Actors == | ||
* Administrator | |||
* HAI | |||
* Hyrax (OLFS & BES(s)) | |||
== Preconditions == | == Preconditions == | ||
The Administrator has an authentication privileges for an HAI. | |||
== Triggers == | == Triggers == | ||
The Admin wants to view and control the BES logging output. | |||
== Basic Flow == | == Basic Flow == | ||
# [[HAI_Use_Case:_Administrator_Logs_into_the_Hyrax_Admin_Interface | The Admin logs into the HAI]] | |||
# The Admin uses the HAI interface and chooses to control the BES logging activity. | |||
# In the returned page (or portion thereof) the HAI provides an interface through which the Admin can: | |||
## Control the level of logging output for different package/class components of the BES | |||
## Save the logging output to a local file. | |||
## Stream the logging output to the HAI interface. | |||
## View existing log files for the BES. | |||
== Alternate Flow == | == Alternate Flow == |
Latest revision as of 01:11, 9 November 2010
Point Of Contact: Nathan Potter
Description
Allows the Administrator to control the BES logging framework.
Goal
Improving Admin problem solving by allowing the Admin to easily start and stop debug logging for the BES and its component, and to capture to a file or stream the debugging output of the BES.
Summary
The Admin logs into the HAI and uses the HAI interface to control and direct the output of the BES logging framework.
Actors
- Administrator
- HAI
- Hyrax (OLFS & BES(s))
Preconditions
The Administrator has an authentication privileges for an HAI.
Triggers
The Admin wants to view and control the BES logging output.
Basic Flow
- The Admin logs into the HAI
- The Admin uses the HAI interface and chooses to control the BES logging activity.
- In the returned page (or portion thereof) the HAI provides an interface through which the Admin can:
- Control the level of logging output for different package/class components of the BES
- Save the logging output to a local file.
- Stream the logging output to the HAI interface.
- View existing log files for the BES.
Alternate Flow
Here we give any alternate flows that might occur. May include flows that involve error conditions. Or flows that fall outside of the basic flow.
Post Conditions
Here we give any conditions that will be true of the state of the system after the use case has been completed.
Activity Diagram
Here a diagram is given to show the flow of events that surrounds the use case.
Notes
There is always some piece of information that is required that has no other place to go. This is the place for that information.
Resources
In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.
Resource | Owner | Description | Availability | Source System |
name | Organization that owns/ manages resource | Short description of the resource | How often the resource is available | Name of system which provides resource |