JBoss.orgCommunity Documentation

Chapter 4. Managing Mobicents JAIN SLEE with Mobicents JAIN SLEE Management Console

4.1. "SLEE" View
4.2. "Deployable Units" View
4.2.1. View Deployable Units Details
4.2.2. Search Deployable Units
4.2.3. Install Deployable Units
4.2.4. Uninstall Deployable Units
4.3. "Components" View
4.3.1. View Components Details
4.3.2. Search Components
4.4. "Services" View
4.4.1. View Service Details
4.4.2. View and Change Service State
4.4.3. Service Usage Parameters
4.5. "Resources" View
4.5.1. View Resource Adaptor Details
4.5.2. View and Change Resource Adaptor Entities State
4.5.3. Create a Resource Adaptor Entity
4.5.4. Remove a Resource Adaptor Entity
4.5.5. View Resource Adaptor Entity Details
4.5.6. View and Change Resource Adaptor Entity Configuration Properties
4.5.7. View and Change Resource Adaptor Entity Links
4.5.8. Resource Adaptor Usage Parameters

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.

Figure 4.1. SLEE Main View


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:

  • Start

    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.

  • Stop

    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.

  • Shutdown

    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.

Figure 4.2. Deployable Units Main View


It is possible to see detailed information about the deployable units by clicking on it's name.

Figure 4.3. Deployable Units Details


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 Search button to list the DUs for which the name matches the given string.

Figure 4.4. Deployable Units Search View


Regular Expression not supported in Deployable Unit Search

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 Choose File button, browsing to the desired deployable unit file and clicking the Install button.

Figure 4.5. Deployable Units Install View


Deployable Unit Installation

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.

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.

Figure 4.6. Components Main View


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.

Figure 4.7. Selected Component Type View


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 Search button to list the components for which the name matches the given string.

Figure 4.8. Components Search View


Regular Expression not supported in Component Search

When searching for components, it is not possible to use regular expressions. So using "diam*" may not return anything, while "diameter" may return something.

Figure 4.9. Services Main View


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 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.

Figure 4.10. Services Usage Parameters View


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.

Figure 4.11. Resources Main View


When the existing Resource Adaptor Entities list is shown, the Resource Adaptor Entities state is presented in the State column, it can be:

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.

Figure 4.12. Resource Adaptor Usage Parameters View


In order to view the Usage Parameters for a given set click it's name.

Figure 4.13. Resource Adaptor Usage Parameters Details View


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.

No automatic refresh

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 refresh link.