New Features › CA Process Automation Release 04.2.00 › Performance Improvements

Performance Improvements

The following summary focuses on performance improvements.

• Many performance improvements are not surfaced directly in the UI, but you will notice that CA Process Automation works faster.
• Messaging Service
  • Formerly, CA Process Automation used JBoss for embedded messaging.
  • Now, CA Process Automation 4.2 uses an external instance of ActiveMQ for messaging. This means that ActiveMQ runs in a separate JVM. However the lifecycle of ActiveMQ (for example, start and stop) is coupled to and managed by the Orchestrator service.
• CA Process Automation run-time performance improvements
  • Speed with which users are authorized to use features.
  • Speed with which the operator Target field is processed when it contains an IP addresses or hostname.
• Optimized Task List retrieval - The amount of time it takes to display the Task Lists on the Home tab and on the Operations tab has been reduced.
• Optimized named dataset locking
  • Formerly, when an operator accessed a named dataset (for read or write), a global cluster-wide lock required other operators accessing other named datasets to wait until this global lock was released.
  • Now, a check box (General Properties) for dataset objects let you specify whether to use the deprecated locking mechanism that implements a cluster-wide lock when an operator accesses a named dataset. If you clear this option, when an operator accesses a named dataset (for read or write), the lock is applied to only the named dataset being accessed. This lock does not interfere with other operators accessing other named datasets. This option is cleared by default for new dataset objects and selected for dataset objects imported from previous versions.

    These details about optimized named dataset locking are documented in the User Interface Reference.