OMEGAMON multi-tenancy concepts and architecture

Edit online

Use this topic to familiarize yourself with the concepts and architecture upon which the OMEGAMON multi-tenancy feature is based.

Monitoring environment

The monitoring environment for an OMEGAMON multi-tenancy scenario has the following components:
  • Tivoli Enterprise Monitoring Server (TEMS). The OMEGAMON multi-tenancy solution allows data collection from multiple LPARs using a single TEMS.
  • Tivoli Enterprise Monitoring Agents (TEMA)
  • Enhanced 3270 user interface (enhanced 3270UI)
  • Tivoli Enterprise Portal (TEP). The TEP is used for configuration.
  • User-defined Managed Systems Lists (MSLs)
  • User-defined tenant (customer) definitions

Managed systems lists (MSLs)

The OMEGAMON multi-tenancy feature uses Managed Systems Lists (MSLs), which are defined sets of resources, to restrict access to resources by tenant. The following explanation describes how the MSLs are used.

In general, for data collection, an OMEGAMON client issues an SQL query to a TEMS, which in turn is passed to one or more agents. The SQL query requests one or more columns from one or more tables. The key element in the query is the information that tells the TEMS which agent to invoke. This element is called an origin node and is a unique token that the agent registers with the TEMS when the agent starts up.

The following example requests information for a CICS region on an LPAR:
SELECT COLUMN1, COLUMN2, COLUMN3, FROM PRODUCT.CICSTABLE,
WHERE (ORIGINNODE = ‘LPAR.CICSNAME’ )

The origin node is referred to as a Managed System Name (MSN) and identifies one agent monitoring one system or subsystem. However, many requests need to target multiple agents monitoring multiple systems, and so instead of an origin node, a Managed Systems List (MSL) is used. An MSL is a list of MSNs, or origin nodes.

The following example requests information using an MSL:
SELECT COLUMN1, COLUMN2, COLUMN3, FROM PRODUCT.PLEXTABLE,
WHERE SYSTEM.PARMA=('NODELIST',”OMEGAMON-CICS-LIST”,18)
In this example, the OMEGAMON-CICS-LIST is an MSL that contains one MSN for every CICS region that belongs in the same CICSplex.

Each OMEGAMON product provides an out-of-the-box MSL that is used to contain all discovered systems or subsystems that belong to it. In an OMEGAMON single-tenant configuration, the product-provided MSLs are used for data collection, allowing inclusion of all discovered resources. In an OMEGAMON multi-tenancy configuration, for each tenant, you must define one or more MSLs (one MSL for each managed system type) and include only those systems that belong to that tenant. The user-defined MSLs are then used in the system-generated SQL queries for data collection and limit the scope of collection to only those resources that have been included.

OMEGAMON products that generate queries using the following format are supported in multi-tenancy mode: 
SYSTEM.PARMA=('NODELIST',"msl",nn)
Where msl is the product-provided MSL name and nn is the length of the name in characters.
Note: A managed systems list is also referred to as a managed system list and a managed system group.

Silent first workspace

The OMEGAMON multi-tenancy solution uses a silent workspace (KOBLOGON) as the first workspace. The silent first workspace retrieves the multi-tenancy information for the user ID that is logging on, and then calls the designated first workspace to display.