This section covers general administrative tasks for day-to-day management of the Rhino SLEE, its components and entities deployed in it.
Rhino SLEE uses Java Management Extension (JMX) MBeans for management functionality. This includes both functions defined in the JAIN SLEE 1.1 specification and Rhino extensions that allow additional functionality, beyond what’s in the specification.
Rhino’s command-line console is a front end for these MBeans, providing access to functions for managing the following:
Management may also be performed via the Rhino Element Manager web interface.
State management commands and JMX methods for setting SLEE, Resource Adaptor Entity or Service state that do not take arguments now accept a state change if at least one node in the cluster will change state.
These commands delete any per-node state and set the default desired state to the target state.
This behaviour is similar to enabling symmetric activation state mode for the component being updated in versions of Rhino prior to 3.0.0.
Cluster nodes that are already in the required desired state are ignored, those that need to change transition.
This behaviour is like the "-ifneeded" flag but the operation fails if no nodes are in the prerequisite state to transition to the target state.
The with-node-arg variants create/update (as necessary) per-node state for the requested nodes. All specified nodes must be in the required prerequisite state to transition to the target state.
This behaviour is new in Rhino 3.0.0. It affects the start/stop/activate/deactivate/wait-til rhino-console and Ant tasks.