CA CEM Configuration

CA CEM monitors business transactions to isolate the causes of problems in the data center. It measures the performance and quality of transactions, identifies defects and variance, and quantifies the impact on users and the business. By proactively detecting trends in degraded transaction response times and providing a variety of actionable reports, you can act before an issue occurs or Service Level Agreements (SLAs) are out of compliance.
apmdevops97
CA CEM monitors business transactions to isolate the causes of problems in the data center. It measures the performance and quality of transactions, identifies defects and variance, and quantifies the impact on users and the business. By proactively detecting trends in degraded transaction response times and providing a variety of actionable reports, you can act before an issue occurs or Service Level Agreements (SLAs) are out of compliance.
CA CEM administrator responsibilities
The CA CEM administrator’s responsibilities vary at each site, depending on environment complexity, type of integration, number of users, support resources, and the growth rate of the CA CEM-monitored applications. 
Frequency
Tasks
Daily
  • Perform and verify the daily backup.
  • Review incidents and if appropriate defects. Resolve issues using Introscope.
  • Report any discovered CA CEM issues to the appropriate groups.
  • Review the TIM and IntroscopeEnterpriseManager logs.
  • Review the system events online or after receiving email notification. 
  • Review the health of CA CEM on the Enterprise Manager using Introscope Workstation.
Weekly
  • Test the backup and restore procedures.
  • Test that the integration with other applications, such as CA SiteMinder and CA Service Desk, are working as expected. 
  • Save off site a copy of the CA CEM configuration and backup files.
  • Review CA CEM administrator list in Embedded Entitlements Manager for unneeded administrators.
  • Review CA CEM audit log for unexpected or unauthorized changes.
  • Review CA CEM CPU, disk, and system utilization.
  • Close resolved or old incidents as appropriate.
  • Review reports for accuracy and trends.
  • Check that email reports are being created and distributed as expected.
  • Review the real-time business transaction metrics and custom dashboards in Introscope.
  • Review integration logs, such as the logs for CA Service Desk and CA SiteMinder.
  • Review the evidence collection logs to determine the business impact and collect evidence for incidents. 
Monthly
  • Check failover procedure, if installed.
  • Clean up old or unneeded users and user groups.
  • Review if new business services or transactions need defining.
  • Review if transaction specification settings need modification.
  • Review if baseline or SLA settings need adjustments.
  • Review monthly reports for accuracy and trends.
  • Review the enabled transactions, business transaction statistics, and HTTP analyzer plug-ins. See the 
    CA APM Transaction Definition Guide
     for information about managing transaction definitions.
Quarterly
  • Review CA CEM architecture for performance, scalability, failover, geographic distribution, and other factors.
  • Determine if CA CEM Professional Services are required for CA CEM customization or integration.
  • Beta test, if appropriate, the next CA CEM release for new features and compatibility.
  • Review user group definitions and modify, as needed.