Creating tenant definitions
Create the customer, group, and user definitions for an OMEGAMON multi-tenancy environment.
About this task
For each tenant, you must define the customer and the relationships between the customer and the
MSLs. This process requires the definition of the following components:
- Customer. A customer definition contains a customer ID (up to 10 characters), a descriptive customer name (up to 50 characters), and the list of MSLs for the customer. Each managed system type requires a unique MSL. One customer definition is created for each tenant.
- Group. A group definition defines the group to which a user will belong. For each group, you also specify the first workspace to display at logon and the OMEGAMON tabs to display in the workspace. Multiple groups can be defined and can be used by multiple tenants.
- User. A user definition specifies information for an individual z/OS TSO
user ID. This information includes the group and the customer to which the user belongs; a user can
belong to one group and one customer only. A user can also be defined as a power
user or a super user. The differences between the multi-tenancy user types are as follows:
- A 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.
- A power user has 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.
- A super user has access to all resources for all customers and can access all enhanced 3270 user interface features.
You can create the tenant definitions in PDS members or in RACF, which can provide greater security. Because the RACF implementation typically requires the involvement of your RACF administrator, it is recommended that you test your tenant definitions using PDS members and then, when satisfied, transfer the definitions to RACF.