Table of Contents
Classes
Configuring classes allows you to categorize existing packages in classes already on the software management level and to specify the class type. Classes always refer to software packages and can be used to define dependencies and/or perform activations under Management > Administration (only AND classes).
Classes provide the basis for the simple and flexible handling of dependencies. Classes do only exist in the Matrix42 Management Console (database). The client does not know about these classes, since they are resolved during the activation process.
Software classes are divided into categories.
- AND Classes: To install a package depending on this class, each package of the class must be installed. If a configuration or software group is assigned an AND class, each package of this class is installed on the client.
- OR Classes: To install a package depending on this class, at least one package of the class must be installed. OR classes cannot be assigned to a configuration or software group, since they are only used to define dependencies. If they are assigned indirectly through a dependent package, the configuration groups list only those class members of an OR class that shall be installed, rather than the whole OR class.
A package can only be defined as class in other packages, when it has been saved at least once, since the SoftwareID that has been created during the first save process is used for the assignment.
From Empirum v14 SP1 on, complete classes with all dependent packages or only the class description could be imported or exported.