RegoXchange
  • The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment. The following metrics are monitored: Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours
  • The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment. The following metrics are monitored: Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours  
  • The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment.   The following metrics are monitored:   Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours       Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment.   The following metrics are monitored:   Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours       Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours
  • The CA Clarity Hidden Page Flush Caches document provides an overview of how to clear the cache on an application server without exiting the CA Clarity Application itself utilizing a hidden page within the system.
  • The CA Clarity Hidden Page Security Locks document provides an overview of how to view and remove the locks currently being held on the system using the Security Locks hidden page.
  • The CA Clarity Hidden Page WSDL document provides an overview of how to access the system documentation page for you CA Clarity application from the web.
  • Ensure you are keeping tabs on your Clarity environment. Clarity has key components that require monitoring to ensure consistent processing: - identify key modules like processes, jobs, financials, among others - identify customizations and common errors that can be improved - Overall maintenance recommendations for Clarity Studio and MUX
  • A presentation slide deck from Rego University 2022.   This document reviews best practices for maintaining Clarity.
    • Why is it required?
    • When?
    • Processes
    • Jobs
    • DWH
    • High Volume Data
    • Access Rights
    • Volatile Date
    • Rego’s Recommendations
  • "Ensure you are keeping tabs on your Clarity environment. Clarity has key components that require monitoring to ensure consistent processing: - identify key modules like processes, jobs, financials, among others - identify customizations and common errors that can be improved"
  • Want to keep your Clarity environment running efficiently? In this class we'll discuss how to maintain your Clarity environment through the use of jobs, processes, and configuration. We'll also cover recommended maintenance activities to ensure your environment is running optimally.
  • What integrations are the most requested and the most utilized? This class will review the most common interfaces to and from Clarity, including best practice use cases and lessons learned from real implementations.
  • What integrations are the most requested and the most utilized? This class will review the most common interfaces to and from Clarity, including best practice use cases and lessons learned from real implementations.
Go to Top