JBoss.orgCommunity Documentation
In this view, it is possible to view the ID of the server, such as name, vendor, version and codename and also the SLEE state.
The following states can be observed:
STOPPED
The SLEE environment is configured and initialized, ready to be started. This means resource adaptor objects for resource adaptor entities in the ACTIVE
state are loaded and initialized, and SBBs corresponding to Services in the ACTIVE
state are loaded and ready to be instantiated. However the entire event-driven subsystem is idle. Resource adaptor entities and the SLEE are not actively producing events, and the event router is not operating. SBB entities are not created in this state.
STARTING
Any vendor-specific starting state tasks may be performed here. Services in the ACTIVE
state are made ready to receive events, but SBB entities are still not created in this state. The SLEE spontaneously moves out of this state when (a) startup tasks are complete, which causes transition to the RUNNING
state; (b) some startup task fails, which causes transition to the STOPPING
state.
RUNNING
Resource adaptor objects that are in the ACTIVE
(or STOPPING
) state are actively firing events as conditions dictate. The SLEE may also be firing events. The event router is instantiating SBB entities and delivering events to them as required.
STOPPING
This state is identical to the RUNNING
state except no new Activity objects are accepted by the SLEE from resource adaptor objects, and no new Activity objects are created by the SLEE. If this state is reached from the STARTING
state, there will be no Activity objects and transition to the STOPPED
state should immediately occur. If this state is reached from the RUNNING
state, any existing Activity objects are allowed to end (subject to an arbitrary vendor-specified timeout). Once all Activity objects generated by a particular resource adaptor entity have ended, resource adaptor objects of that resource adaptor entity transition to the INACTIVE
state. The SLEE transitions out of the STOPPING
state once all Activity objects have ended and all resource adaptor objects have transitioned to the INACTIVE
state.
It is also possible to manage the SLEE state from this view, by using the following buttons:
In order to use this button the SLEE must be in the STOPPED
state. It will move the SLEE to the STARTING
state and once the start operations complete, switch to the RUNNING
state.
In order to use this button the SLEE must be in the STARTED
state. It will move the SLEE to the STOPING
state and once the stop operations complete, switch to the STOPPED
state.
In order to use this button the SLEE must be in the STOPPED
state. It will shutdown completely the SLEE container as well as the JBoss Application Server.
In this view, it is possible to view, search, install and uninstall Deployable Units in the SLEE. A list showing the deployable units, identified by their filename, is shown.
It is possible to see detailed information about the deployable units by clicking on it's name.
The following fields are shown:
Name
The Deployable Unit name, extracted from it's filename.
ID
The SLEE identifier for this Deployable Unit.
Date
The deployment date for this Deployable Unit.
URL
The URL from where this deployable unit was deployed from.
Components
The SLEE components included and deployed with this deployable unit.
In order to find specific deployable units, use the Search tab, where it is possible to specify a string to search for and click the button to list the DUs for which the name matches the given string.
When searching for deployable units, it is not possible to use regular expressions. So using "diam*" may not return anything, while "diameter" may return something.
A deployable unit can be installed to SLEE by going to the Install tab, clicking the button, browsing to the desired deployable unit file and clicking the button.
Please note that only the deployable unit will be installed, no further operations will be performed. If you need to, you will need to activate services, create Resource Adaptor Entities and Links, etc.
A deployable unit can be uninstalled from SLEE in the list view (both in Browse or Search tabs) by clicking the link.
Please note that the deployable unit will be uninstalled, only if there are no components depending on it, no Links or Entities in case of Resource Adaptors and in case of services, they must be deactivated.
In this view, the components installed in SLEE are shown, grouped by their types. It is possible to view the components, their details and search for specific components.
In the Browse Components tab a list of components is shown, grouped by their type. When clicking on one of the Component Types, a list of the available components of that type is shown, identified by their Name, Vendor and Version.
If one of this components is clicked, it's details are shown. The following component types and details are available:
The following details are common to all component types:
Name
The SLEE component Name identifier.
ID
The SLEE component identifier, built from the component type, name, vendor and version.
Vendor
The SLEE component Vendor identifier.
Version
The SLEE component Version identifier.
Source
The path to the jar containing this component, inside the deployable unit jar.
Deployable Unit
The deployable unit used to deploy this component.
Library References
The libraries this component refers, if any.
The following are specific to each component type:
Event Type
Event Class Name
The class name for this event type.
Profile Specification
CMP Interface Name
The interface name for the Profile CMP.
SBB
Address Profile Specification
The profile specification to be used as the Address Profile Specification for this SBB.
Event Types
The event types referenced by this SBB, either for Fire and/or Receive.
Profile Specifications
The profile specs referenced by this SBB.
Resource Adaptor Entity Links
The resource adaptor links required by this SBB.
Resource Adaptor Types
The resource adaptor types referenced by this SBB, either for Fire and/or Receive.
SBBs
The child SBBs this SBB has.
Resource Adaptor Type
Event Types
The event types referenced by this Resource Adaptor Type, that it can fire.
Resource Adaptor
Event Types
The Resource Adaptor Type implemented by this Resource Adaptor.
Service
Address Profile Table
The Address Profile Table name to be used by this service, if any.
Resource Info Profile Table
The Resource Info Profile Table name to be used by this service, if any.
Root SBB
The SBB to be used as the Root SBB for this service.
Library
Library Jars
The JARs exposed by this Library component.
In order to find specific components, use the Search tab, where it is possible to specify a string to search for and click the button to list the components for which the name matches the given string.
When searching for components, it is not possible to use regular expressions. So using "diam*" may not return anything, while "diameter" may return something.
In this view, the services present in SLEE are shown, along with their state. It is possible to view the services, their details, view and change the service state.
In the Services tab the list of services is shown. When clicking on one of the services' name, it's details are shown. The following details are displayed:
Name
The SLEE component Name identifier.
ID
The SLEE component identifier, built from the component type, name, vendor and version.
Vendor
The SLEE component Vendor identifier.
Version
The SLEE component Version identifier.
Source
The path to the jar containing this component, inside the deployable unit jar.
Deployable Unit
The deployable unit used to deploy this component.
Library References
The libraries this component refers, if any.
Address Profile Table
The Address Profile Table name to be used by this service, if any.
Resource Info Profile Table
The Resource Info Profile Table name to be used by this service, if any.
Root SBB
The SBB to be used as the Root SBB for this service. This entry is clickable and will lead to the details view for this SBB component.
When the existing services list is shown, the service state is presented, it can be:
INACTIVE
The Service has been installed successfully and is ready to be activated. The Service is not running, i.e. root SBB entities of the Service’s root SBB will not be created to process events.
In this state it is possible to activate the service by clicking the
link.ACTIVE
The Service has been activated, i.e. it is running. The SLEE will create root SBB entities of the Service’s root SBB to receive initial events and invoke SBB entities in the SBB entity trees of the Service.
In this state it is possible to deactivate the service by clicking the
link.STOPPING
The Service is being deactivated. However, some SBB entity trees of the Service still exist in the SLEE and have not completed their processing. The SLEE is waiting for the SBB entities in these SBB entity trees to complete processing so that they can be reclaimed. An SBB entity has completed processing and can be reclaimed when it and all of its child SBB entities are no longer attached to any Activity Context.
No state changing operations are available in this state, as this is a transition state, from ACTIVE to INACTIVE.
In the Usage Parameters tab is possible to view and manage the service SBBs Usage Parameters. In this screen, select a Service and an SBB and if a SBB Usage Parameter Interface is defined, this view will present the default and other available Usage Parameter Sets.
In order to view the Usage Parameters for a given set click it's name. The following types are displayed:
Counter Type
A counter-type usage parameter can be incremented or decremented. The current (approximate) value of the counter-type usage parameter is displayed under the Value column is shown.
Sample Type
A sample-type usage parameter accumulates sample data, when a SLEE Component submit samples to the usage parameter. The current (approximate) minimum, maximum, mean, and the number of sample values added to the sample-type usage parameter are shown.
In order to keep a low impact on the SLEE no real-time update is performed with regards to the Usage Parameters. To update the displayed values, please click the
link.It is possible to reset a single Usage Parameter, when viewing the Service Usage Parameters list, by clicking the
link, next to each, both for Counter and Sample type usage parameters.In order to reset all the Usage Parameters for a given service, in the main Usage Parameters view click the
button and all will be reset.In addition to the default usage parameter set created by the SLEE, it is possible to create additional usage parameter sets for the same notification source, which must have a name. To create one, in the main Usage Parameters view, fill the New parameter set with the name and press the button and the new set is created.
To remove a created Usage Parameter Set, in the main Usage Parameters view, under the Parameter Sets list, in the Actions column, click the link and the set will be removed.
Only named Usage Parameters Sets can be removed, the "default" will always exist when there's a Usage Parameter Interface defined for this component.
In this view, the resource adaptors present in SLEE are shown, identified by their name, vendor, version and RA Type implemented. It is possible to view the resources, their details, view and manage Resource Adaptor Entities and Links.
In the Resources tab the list of Resource Adaptors is shown. When clicking on one of the resource adpators' name, it's details are shown. The following details are displayed:
Name
The SLEE component Name identifier.
ID
The SLEE component identifier, built from the component type, name, vendor and version.
Vendor
The SLEE component Vendor identifier.
Version
The SLEE component Version identifier.
Source
The path to the jar containing this component, inside the deployable unit jar.
Deployable Unit
The deployable unit used to deploy this component.
Library References
The libraries this component refers, if any.
Resource Adaptor Entities
A list of the created Resource Adaptor Entities for this Resource Adaptor. These entities are clickable, and will lead to view the Entities details.
When the existing Resource Adaptor Entities list is shown, the Resource Adaptor Entities state is presented in the State column, it can be:
INACTIVE
The resource adaptor entity has been successfully created in the SLEE. An Inactive resource adaptor entity is ready to be activated.
In this state it is possible to activate the resource adaptor entity by clicking the
link.ACTIVE
The resource adaptor entity has been activated. If the SLEE is in the Running state, resource adaptor objects associated with the resource adaptor entity can create new activities, submit events on activities, and end activities. If the SLEE is in the Stopping state, resource adaptor objects associated with the resource adaptor entity cannot start new activities, but may submit events on existing activities and end activities.
In this state it is possible to deactivate the resource adaptor entity by clicking the
link.STOPPING
The resource adaptor entity is being deactivated. However, some activities created by the resource adaptor objects associated with the resource adaptor entity may still exist in the SLEE and have not completed their processing. The SLEE is waiting for these activities to end. Once all activities owned by resource adaptor objects of the resource adaptor entity have ended, the SLEE will transition the resource adaptor entity back to the Inactive state.
No state changing operations are available in this state, as this is a transition state, from ACTIVE to INACTIVE.
In order to create a new Resource Adaptor Entity, after selecting the Resource Adaptor, fill the new entity name in the textbox next to Create entity and click the button. A new Entity will be created with default properties and in INACTIVE
state.
To remove a Resource Adaptor Entity, there should be no Resource Adaptor Entity Links for this entity and it should be in INACTIVE
state.
In order to remove a Resource Adaptor Entity, after selecting the Resource Adaptor, click the
link. Make sure the above pre-requirements above are fulfilled.After selecting the Resource Adaptor, a list of the existent Resource Adaptor Entities can be found in the bottom of the panel. By clicking one of the Entities, the following details can be observed:
Name
The Resource Adaptor Entity Name.
State
The current state of the Resource Adaptor Entity.
Entity Configuration Properties
The Resource Adaptor configuration properties provide a standardized mechanism for configuration of a resource adaptor entity. The consist of a triplet, Name, Type and Value.
Entity Links
The Resource Adaptor Entity Links provide a link to an entity, to be used by SBBs.
After selecting the Resource Adaptor Entity, a list of the Resource Adaptor Entity Configuration Properties is shown. They are displayed as <name>
:: <type>
- <value>
. Only the value can be changed.
To edit the Resource Adaptor Entity, if the Resource Adaptor does not support reconfiguration in ACTIVE
state, it must be in INACTIVE
state.
To change these values, click the
. The values will change to an editable form. Change the values accordingly and click the button.After selecting the Resource Adaptor Entity, a list of the Resource Adaptor Entity Links is shown. It is possible to remove existing and add new links.
To remove a Resource Adaptor Entity Link, there should be no SBBs referring it.
To create a new Resource Adaptor Entity Link, fill the new link name in the Bind entity link textbox and click the button.
To remove an existing Resource Adaptor Entity Link, click the
link.In the Usage Parameters tab is possible to view and manage the Resource Adaptors' Entities Usage Parameters. In this screen, select a Resource Adaptor and a Resource Adaptor Entity and if a Resource Adaptor Usage Parameter Interface is defined, this view will present the default and other available Usage Parameter Sets.
In order to view the Usage Parameters for a given set click it's name.
The following types are displayed:
Counter Type
A counter-type usage parameter can be incremented or decremented. The current (approximate) value of the counter-type usage parameter is displayed under the Value column is shown.
Sample Type
A sample-type usage parameter accumulates sample data, when a SLEE Component submit samples to the usage parameter. The current (approximate) minimum, maximum, mean, and the number of sample values added to the sample-type usage parameter are shown.
In order to keep a low impact on the SLEE no real-time update is performed with regards to the Usage Parameters. To update the displayed values, please click the
link.It is possible to reset a single Usage Parameter, when viewing the Resource Adaptor Usage Parameters list, by clicking the
link, next to each, both for Counter and Sample type usage parameters.In order to reset all the Usage Parameters for a given Resource Adaptor, in the main Usage Parameters view click the
button and all will be reset.In addition to the default usage parameter set created by the SLEE, it is possible to create additional usage parameter sets for the same notification source, which must have a name. To create one, in the main Usage Parameters view, fill the New parameter set with the name and press the button and the new set is created.
To remove a created Usage Parameter Set, in the main Usage Parameters view, under the Parameter Sets list, in the Actions column, click the link and the set will be removed.
Only named Usage Parameters Sets can be removed, the "default" will always exist when there's a Usage Parameter Interface defined for this component.