Index Changes

Use Cases

Use cases provided here are project-level use cases intended to capture requirements at a very high level. Individual project plans for JBI functional areas (e.g. AddOn, web console, management, etc.) impacted by these use cases should address them in greater detail. For example, the 'Administer DAS target' use case should be broken down into the individual administration use cases (life cycle, deployment, installation, etc.) and discussed in detail.

#DescriptionCommentsImpacts
1 Install JBI AddOn (domain)Need to iron out the process by which an administrator elects to install the JBI AddOn. Is it included by default, selected as an option during installation, or a manual post-installation step?Glassfish, AddOn
2 Install JBI AddOn (Node Agent) If the JBI AddOn is installed in the domain, we need a way to make sure that node agents participating in that domain also include the AddOn Glassfish, AddOn
3 Create a Glassfish/JBI stand-alone instance The JBI framework lifecycle module should be added to the instance configuration. Glassfish, Runtime
4 Create a Glassfish/JBI cluster The JBI framework lifecycle module should be added to the cluster configuration. Glassfish, Runtime
5 Add an instance to an empty cluster Runtime
6 Add an instance to a populated cluster The new instance must be provisioned with JBI artifacts that have been previously installed/deployed into the cluster. Runtime
7 Remove an instance from a cluster None
8 Administer DAS target Install, deploy, and query commands are available on the DAS. Installing and deploying on the DAS is equivalent to adding the component/assembly to the repository. Web console, CLI, Ant, Runtime
9 Administer stand-alone instance target Install, deploy, life cycle, and query commands area available for stand-alone instances Web console, CLI, Ant, Runtime
10 Administer a cluster target Install, deploy, life cycle, and query commands area available for clusters.

NOTE: cluster instances are not independently administrable.

NOTE: Homogeneous topology may create opportunities for metadata collision amongst components and composite applications.
Web console, CLI, Ant, Runtime, components
11 Administer an off-line stand-alone instance Impact should be isolated to JBI runtime; administration tools do not need to treat this as a special case. Runtime
12 Administer an off-line cluster Impact should be isolated to JBI runtime; administration tools do not need to treat this as a special case.
Off-line administration of a cluster is permitted if some or all of its instances are down.
Runtime

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-1) was last changed on 17-Nov-06 10:41 AM, -0800 by sureshp