The names of all snap-ins that have been loaded to the System Manager database.

The version number of the snap-in. You cannot install versions of the same snap-in if the version number is identical.

The preferred version of a snap-in. In a cluster, if you choose a preferred version of a snap-in, that particular version is used by default. Even if you install a newer version of the snap-in, the preferred version is continued.

Indicates if the service is loaded or installed. Loaded snap-ins have been loaded to the System Manager database.

Installed indicates that a request has been sent to install the snap-in to the Avaya Breeze® platform instances. This state is an aggregated state across various clusters. To check the actual status of the service installation, see the Service Install Status column on the Avaya Breeze® Instance Status page.

The snap-in deployment type. Possible values include Java, Workflow. JDBC Provider is the custom defined type. The deployment type value is stored in the database. You can filter and sort snap-ins based on the deployment type.

The license mode that the snap-in is currently in. The possible license modes are:

• License Normal Mode: The snap-in has a valid license file for normal operation of the snap-in. License errors are not present.

• License Error Mode: License error is seen in this mode. The snap-in is in the thirty day grace period. There are no restrictions on the functionalities. You must install a valid license file for the snap-in to get it back to the normal mode. This column displays the grace period when the snap-in is in the error mode. After the grace period expires, the snap-in enters the restricted mode.

• License Restricted Mode: The snap-in has exceeded the license grace period. If you do not install a valid license file, the snap-in is uninstalled from the Avaya Breeze® platform clusters. The element manager raises a critical alarm. If you install the license file the snap-in returns to the License Normal mode. You must manually re-install the snap-in to any cluster from which the snap-in was uninstalled.

• Not Applicable: For services that do not require a license file.

Indicates whether the snap-in is Avaya signed. The column displays a green tick mark if the snap-in is signed by Avaya. Else, the column displays Not Signed.

The supplier id for Avaya provided snap-ins is 10000000. The Supplier id uniquely identifies the supplier of a particular snap-in offered through Avaya Snapp Store. All the snap-ins from a given supplier will have the same Supplier Id. This is mandatory for the snap-ins offered through the Avaya Snapp Store and is optional for other snap-ins. For Avaya Snapp Store, go to https://www.devconnectmarketplace.com/marketplace/ and navigate to Avaya Snapp Store.

The total space for the logs of the snap-in declared in the properties.xml file. If the total space is not declared, the system displays the default value of 100MB.

Launches the Load Service window so you can browse to the location of a service and load it. Acceptable services have a file extension of .svar.

Queues up the selected service be installed on all the administered Avaya Breeze® platform instances. Depending on the number of instances, it may take a few minutes to install on all instances

Uninstalls the selected service from all the Avaya Breeze® platform instances. A dialog will display to ask if you want to force uninstall or not. A force uninstall terminates all active connections immediately. Not checking this will cause the service to wait for all active connections to drop before uninstalling the service.

Deletes the selected service. An Installed service can not be deleted. It must first be uninstalled.

Sets the preferred version of a service. The preferred version of any service is cluster specific. You can set the same version of a service as the preferred version across several clusters.

You can set the preferred version for multiple snap-ins in a single transaction.

Starts or restarts the snap-in. Start snap-in is used after installing a higher version of a snap-in, or after making some configuration changes to the snap-in.

Stops the snap-in. Stop snap-in is used while installing a higher version of a snap-in.