Administration Guide › User Accounts › Tasks Associated with Roles › Administrator Tasks › Services Configuration and Monitoring

Services Configuration and Monitoring

Only users with the role of Administrator can configure and maintain the services accessible from the Administration tab, Services subtab. Configure all services soon after installing CA User Activity Reporting Module.

Administrator tasks involving services include the following:

• Configure global services including the following:
  • Update interval
  • Session timeout
  • Whether authentication is required to view alerts posted to RSS feeds
  • Tags to hide
  • Default profile
• Configure the event log store service.
  • At the global level, configure services that apply to all CA User Activity Reporting Module servers.
  • At the local level, configure auto-archive.

    The event log store on the collection CA User Activity Reporting Module server houses a hot database of new logs. The hot database is compressed into a warm database when it reaches the configured maximum rows.

    • If you configure auto-archive between the collection server and the reporting server, the warm database is copied to the reporting server and then deleted from the collection server.
    • If you configure auto-archive between the reporting server and a remote server that is not a CA User Activity Reporting Module server, warm databases are copied to the remote server on a daily or hourly basis, depending on your auto-archive settings. By default, the reporting server retains the databases until they reach the set disc space or time limits. They are automatically deleted from the reporting server only if you select the Remote ELM Server check box.
    • If you do not configure auto-archive from the reporting server to a remote storage server, manually create a backup of warm databases and move them to long-term storage. The warm database is stored in the event log store of a reporting server (or management/reporting server in a two-server deployment) for the number of days configured as max archive days unless the available space drops below the configured percentage set by archive disk space. In this case, warm databases are deleted, beginning with the oldest.
• Configure the report server service.

  The report server service handles reports and alerts, including retention policies, the format for printed/emailed reports, and keyed values for reports and alerts. Additionally, it handles integration settings for CA IT PAM processes such as event/alert output and dynamic values and for SNMP trap destinations for alerts.

• Configure subscription updates.

  Subscription updates refer to the binary and non-binary files that are made available by CA Technologies Subscription Server to CA User Activity Reporting Module servers, the CA EEM component on the management server, and agents.

• Manage the federation of CA User Activity Reporting Module servers.

  At the management server, you can set a query to extend to federation children and peers. CA User Activity Reporting Module servers can be federated for two purposes:

  • The collection server auto archives each hot database into a warm database and sends it to the related reporting server. Create a federation between the collection server and the reporting server. When you query the management server with federation selected, you can get results not only from the local warm databases but also the hot database of the collection server.
  • Multiple reporting servers can be created to distribute the storage of warm databases among multiple event log stores. Reporting servers can be federated in a mesh with each collection server federated as a child to its reporting server. A federated query from any of the meshed reporting servers returns data from both its meshed (peer) servers and from all of their child servers.

    Note: If you create a restore point CA User Activity Reporting Module for the purpose of restoring archived databases from long-term storage, it is a good practice to leave such a server out of the federation.

• Monitor and manage the system status.

More Information:

Automating Backup and Restore

Query the Archive Catalog

Restore Auto-Archived Files

Restore–Script for Restoring Archived Databases

ODBC Server Considerations

Create a Diagnostics File for Support

Reboot a Host Server

Restart the ELM Services

Review Service Status and Version

Review System Status Self Monitoring Events