Report schema mapping

A report schema specifies which entities and attributes can be included in reports. Before an entity and its associated attributes can be specified as reporting criteria and included in custom report data, a report schema must be defined.

Schemas are installed for all of the standard reports during product installation. The administrator does not define schemas for standard reports.

By default, entities and attributes are not included in custom reports. The administrator must define a schema for each custom report template that is created, including designer reports. To create a report schema, we must run the Design Schema task in the console. Map only the entities and attributes for which to generate custom reports. These mappings directly affect the performance of IBM Security Identity Manager. The impact occurs because all of the data from the directory server is copied to the database each time a data synchronization is done.

By defining the schema, we select directory entities that are staged as tables in ISIMs database. Defining the schema involves mapping attributes. After mapping the entities and attributes, we must synchronize the data to make the data available for reporting.

• Mapping attributes
  To create a custom report schema, create an attribute mapping that specifies the entities and entity attributes that can be included in a report.
• Unmapping attributes
  We can unmap previously mapped attributes so that they are no longer available for reporting.

Parent topic: Report customization