OMEGAMON multi-tenancy terminology
This topic describes terms as they apply to the OMEGAMON multi-tenancy feature.
- customer
- A tenant in an OMEGAMON multi-tenancy configuration. For each customer, a distinct set of resources (defined with MSLs), users, and groups are defined. A user for a particular customer can only access the resources defined to that customer. Multiple customers can exist in multi-tenancy mode.
- group
- A tenant definition that logically associates one or more users with the same logon experience and working environment. A group defines the first workspace and the product tabs to display when a user logs on.
- managed system group
- See Managed Systems List.
- Managed Systems List (MSL)
- A defined set of resources. Specifically, an MSL is a list of Managed Systems Nodes (MSNs). The MSL is used to control the scope of data collection. Each OMEGAMON product provides an out-of-the-box MSL that contains all discovered systems or subsystems that belong to it. In a multi-tenancy configuration, one or more MSLs are defined for each tenant to limit the scope of collection. Also referred to as a managed system list and a managed system group.
- Managed System Node (MSN)
- A unique token used for agent identification. An MSN is used in data collection to identify one agent monitoring one system or subsystem. Also referred to as an origin node.
- multi-tenancy mode
- A feature in the OMEGAMON enhanced 3270 user interface that allows the monitoring of distinctly separate sets of resources.
- managed system type
- In OMEGAMON multi-tenancy, the managed system type is a pre-defined value used to identify the OMEGAMON agent or type of managed system when specifying user-defined MSLs in customer definitions. For more information, see Creating tenant definitions.
- Origin node
- See Managed System Name (MSN).
- power user
- A designation for a user ID that allows the user access to resources only for the tenant (customer) to which the user is defined, with access to more enhanced 3270 user interface features than the regular tenant user, such as access to all menu options, icons and commands.
- super user
- A designation for a user ID that allows the user to log on to the enhanced 3270 user interface address space, running in multi-tenancy mode, and not be restricted by any multi-tenancy rules. This setting allows an OMEGAMON System Programmer to log on to a multi-tenancy address space and access data from all sources while tenants are restricted to their own customer views.
- tenant
- A monitoring environment consisting of a distinct set of resources for data collection. See also customer.
- tenant user
- A defined user in a multi-tenancy environment. The regular tenant user has access to resources only for the tenant (customer) to which the user is defined and has limited access to some enhanced 3270 user interface features.
- user
- A tenant definition that establishes the group and customer to which a user ID belongs and indicates if the user ID is designated as a power user or a super user. Unless the user is designated as a super user, a user can access only those resources that are assigned to the customer to which the user ID belongs.