Monitor Health of the Task Persistence Database

You can now monitor health of the Task Persistence database and the Java Messaging System (JMS) at any given time. Based on the health results, you can take appropriate action to ease the load on the Task Persistence database.
cim140
You can now monitor health of the Task Persistence database and the Java Messaging System (JMS) at any given time. Based on the health results, you can take appropriate action to ease the load on the Task Persistence database.
You can now check health of the task message system health to know the effectiveness of interaction between the Task Persistence database and application server. Use this option to check the maximum number of transactions that can be processed successfully in your environment.
  • Message queue information checks whether the messaging queue is configured properly, whether the messages are posted to the JMS queue, and whether the queue is able to deliver the messages for task completion.
  • Task Persistence information involves checking whether the Task Persistence database is getting updated for the generated transactions.
 Perform health check of the message system after configuring your Application Server cluster in each target environment (development / staging / production). This action lets you verify that the message system is properly configured for distributed processing of events across the cluster nodes.
This article contains the following sections:
��
 
View Health of the Task Persistence Database
Use the following procedure to view the health of the Task Persistence database.
 
Follow these steps:
 
  1. Log in to the CA Identity Manager UI.
  2. Navigate to 
    System
    Task Runtime Management
    Task Persistence Monitor
    .
  3. Click 
    Check Database
    .
    The load on the Task Persistence database for the following object types are displayed in percentage:.
    • Task Rows
    • Event Rows
    • EventObject Rows
    If the percentage is more than 80%, then you can archive to ease the load on the database.
    The legend for the progress bar of the object types is as follows:
  • Less than 60% - Green
  • Between 60% to 85% - Yellow
  • More than 85% - Red
View Health of the Task Message System
Use the following procedure to view the health of the Task message system.
 
Follow these steps:
 
  1. Log in to the CA Identity Manager UI.
  2. Navigate to 
    System
    Task Runtime Management
    Task Persistence Monitor
    .
  3. In 
    Synthetic Task Count
    , specify the number of transactions to be submitted to the App Server for checking the health of App Server’s messaging system and the interaction with the Task Persistence database.
  4. Click 
    Check Message Health
    .
    The progress about the transactions that are completed are displayed in the progress bar and in percentage.
  5. Click 
    Refresh
     to view the progress of the remaining transactions.
Configure Database Block Size
 
Note:
 Applicable if the task persistence database is Oracle.
You can configure the block size of the database in your environment for improved performance.
 
Follow these steps:
 
  1. Log in to the CA Identity Manager UI.
  2. Navigate to 
    Roles
     
    and Tasks
    Admin Tasks
    Modify Admin Tasks
    .
  3. Search for a Task Persistence Monitor task and select that task.
  4. In the 
    Profile
     tab, click 
    Configuration Properties
    .
  5. Click 
    Add
     to add the DB_BLOCK_SIZE property.
    Default:
     8192
  6. If necessary, update the value of the DB_BLOCK_SIZE property
  7. Click 
    OK
    .
  8. Click 
    Submit
    .
The database block size is updated.