FAP components

FAP consists of four main components.
  • FAP client - This is an administrative console where the basic settings are applied, some events are triggered, and the FAP log information can be monitored.
  • FAP database - This is a temporary database to which changed facts and data and dimension updates are moved prior to their transformation into the cube. The information in this database is purged at regular intervals.

    Note: The FAP database should not be used by more than one FAP service.
  • FAP service - This moves and transforms the relational IBM® Cognos® Controller data and the dimensions into the cube.
  • TM1® (FAP) cubes - These are the read-only TM1 cubes that contain the IBM Cognos Controller dimensions and trickle-published data.

FAP requires additional server resources for TM1 and the FAP database. For more information about network set up and resource requirements, see the IBM Cognos Proven Practices document (http://public.dhe.ibm.com/software/dw/dm/cognos/performance/cognos_specific/architecture_and_server_sizing_for_cognos_controller85.pdf).