Data visibility groups

Use data visibility groups (DVGs) when there is a need to limit what data (events) a specific user can monitor.

For example, assume that a company has one Sterling Connect:Direct® server that performs both Payroll and Order Processing work. The IBM® Sterling Control Center Monitor administrator wants to give both Payroll and Order Processing personnel access to IBM Sterling Control Center Monitor functions. However, the administrator does not want Order Processing personnel to have any visibility to Payroll file activity; nor Payroll personnel to have any access to Order Processing activity.

Data visibility groups in IBM Sterling Control Center Monitor provide this capability.

Data visibility groups are basically a set of rules that are applied to events that are created in IBM Sterling Control Center Monitor. When the rule matches the criteria that are specified, the name of the data visibility group is added to the attributes of the event. So, the IBM Sterling Control Center Monitor administrator can set up a data visibility group called Payroll. This DVG classifies events as “Payroll” events (by tagging them with the “Payroll” Data Visibility Group attribute) when any one of the following criteria is met:

  • Any Process that is submitted by the user PAY01 is a Payroll process.
  • Any Process that runs between this Sterling Connect:Direct server and the remote Payroll server is a Payroll process.
  • Any Process Step that deals with a file that contains corp.payroll in the name is a Payroll Process Step.

And the IBM Sterling Control Center Monitor administrator can set up a data visibility group called OrderProcessing. This data visibility group classifies events as “OrderProcessing” events when any one of these criteria is met:

  • All Processes that are submitted by user ORD01 are Order Processing processes.
  • All Processes that are submitted by user ORD02 are Order Processing processes.
  • All Process Steps that deal with files that begin with ORDER are Order Processing processes.
  1. For the Payroll data visibility group, the administrator would set up the following criteria:
    Name Key Operator Value
    Payroll Criteria - User PAY01 Submitter Matches PAY01
    Payroll Criteria - User PAY01 Servers and Server Groups Matches (CDServer)()
    Payroll Criteria - Remote Node Remote Node Matches ABCPayrollNode
    Payroll Criteria - Remote Node Servers and Server Groups Matches (CDServer)()
    Payroll Criteria - Payroll File Destination File Wildcard corp.payroll*
    Payroll Criteria - Payroll File Source File Wildcard corp.payroll*
  2. For the OrderProcessing data visibility group, the administrator would set up the following criteria:
    Name Key Operator Value
    OrderProcessing Criteria 1 - User ORD01 Submitter Matches ORD01*
    OrderProcessing Criteria 1 - User ORD01 Servers and Server Groups Matches (CDServer)()
    OrderProcessing Criteria 2 - User ORD02 Submitter Matches ORD02
    OrderProcessing Criteria 2 - User ORD02 Servers and Server Groups Matches (CDServer)()
    OrderProcessing Criteria 3 - File ORDER Destination File Matches ORDER*
    OrderProcessing Criteria 3 - File ORDER Source File Matches ORDER*
    OrderProcessing Criteria 3 - File ORDER Server and Server Groups Matches (CDServer)()
  3. An IBM Sterling Control Center Monitor role can now be defined that is restricted to data visibility group Payroll. The administrator creates a role name Payroll-Role. On the Restrictions tab of the Role Properties sheet, the administrator moves the Payroll DVG to the Selected Data Visibility Groups.
    Name Value
    Selected Data Visibility Groups Payroll
  4. Another role can be defined that is restricted to data visibility group OrderProcessing. The administrator creates a role that is named OrderProcessing - Role. On the Restrictions tab of the Role Properties sheet, the administrator moves the OrderProcessing DVG to the Selected Data Visibility Groups.
    Name Value
    Selected Data Visibility Groups OrderProcessing
  5. IBM Sterling Control Center Monitor users can now be defined and assigned the appropriate Payroll or Order Processing roles. The administrator sets up the following criteria for the Payroll-Role on the User Properties page:
    Name Value
    User ID PayrollUser
    Password **********
    Retype Password **********
    Role Payroll-Role
  6. The administrator sets up the following criteria for the Order Processing role on the User Properties tab:
    Name Value
    User ID OrderProcessingUser
    Password **********
    Retype Password **********
    Role OrderProcessing-Role

    When the PayrollUser user signs on to the IBM Sterling Control Center Monitor console, only Payroll activities are displayed due to the DVG restriction of that user. It is as if those activities were the only activities in the Sterling Connect:Direct server.

    And User OrderProcessingUser sees Order Processing activities only.

    If the Payroll role is permitted to define rules or SLCs, those rules or SLCs apply to Payroll activity only. The rules do not affect Order Processing activity.