Besides cross‑referencing resource rules, X‑RGP records can cross‑reference each other. This cross‑reference function lets you define groups in larger groups. For example, you have three groups of transactions. Some users can access all three groups while others can access only one of the three groups. You need to define each of the three individual groups of transactions and one larger group that consists of all three individual groups to CA ACF2 for VM.
To do this, define a total of four X‑RGP records, one for each individual group of transactions, and one for the larger group that consists of all three of the individual transaction groups. Use the names of the transaction groups for the record IDs of the X‑RGP records. You will have X‑RGP records with record IDs such as TRANA, TRANB, TRANC, and GROUP1, where GROUP1 consists of TRANA, TRANB, and TRANC.
After you define all of the X‑RGP records, write one resource rule for each X‑RGP record, and use the record IDs (TRANA, TRANB, TRANC, GROUP1) for the $KEY resource names. You also must ensure that the type codes you specify in the X‑RGP records match the type codes in the corresponding resource rule records.
You can also have a set of X‑RGP records cross‑reference another set of X‑RGP records. Extending the scenario just described, suppose that you want some users to have access to the set of transaction groups indicated in the X‑RGP GROUP1 record and another set of transaction groups defined in the X‑RGP GROUP2 record. In this case, you define an X‑RGP record called GROUPA. GROUPA consists of GROUP1 and GROUP2. You can use this X‑RGP to X‑RGP cross‑reference ability as an indexing process to define as many as 25 levels.
|
Copyright © 2009 CA Technologies.
All rights reserved.
|
|