Installation Guide › Configuring the Server Post Installation › How the CA RCM Portal Uses Data Files

How the CA RCM Portal Uses Data Files

The CA RCM server's analysis and reporting tools draw on data files in the CA RCM database. The portal's ticket-based business processes - such as certification - also use this data. And the data import processes you set up through the portal feed these data files.

Note: Some parts of the data setup process require use of the Discovery & Audit (DNA) and Data Management (DM) tools. For a detailed description of these tools, see the CA RCM DNA User Guide and DM User Guide. For a detailed description of CA RCM datafiles, data import connections, and other related topics, see the CA RCM Portal User Guide.

You define two special data sets that are used by most functions of the server and portal:

• A Universe is a pair of configuration (.cfg) files: a periodically updated master configuration, and a working clone of the master used to model configuration changes. You can define several universes in the portal. You select which universe to use when you create reports or certification campaigns.
• The Permissions configuration file is used to set up user accounts in the portal, and to determine user privileges to access portal functions. A default permissions configuration file defines basic portal administrator and user roles. In most cases, you replace this default configuration with one based on a universe. RACI analysis of the universe lets the portal automatically assign permissions based on the universe role hierarchy and resource assignments.

Initial data setup typically follows this sequence:

1. Import data and create an initial configuration file and related data. This stage of the process uses the DNA and DM client applications, and may use a manual process to gather data if import links are not yet set up.
2. In the portal, define a Universe based on the initial configuration (Administration, Settings, Universe Settings, Create New).
3. Create a Permissions configuration based on the universe (Administration, Permissions Configuration Settings, Update Permissions configuration with universe users).
4. Perform RACI analysis of the universe (Administration, Create RACI).
5. Configure data connectors for ongoing import and export of configuration changes. This can involve mapping of data fields and configuration of periodic push/pull data transfer, and performing period audit processes on the universe configuration. In addition, the portal's RACI configuration must be synchronized after each data import.