Install the Domain Orchestrator › Prerequisites to Installing the Domain Orchestrator › Database Prerequisites › About CA Process Automation Data Stores

About CA Process Automation Data Stores

Each Orchestrator requires three logical data stores:

• The Repository data store, or Library data store, is a data store that stores the automation objects created in folders in the Library tab in CA Process Automation. The stored data includes the library tree structure, the complete definition of each object, as well as ownership, and versioning information.

  Note: Multiple Orchestrators can share the Repository data store on the Domain Orchestrator or each Orchestrator can have its own.

• The Runtime data store is an Orchestrator-specific data store that stores process instance data for a single Orchestrator or Orchestrator cluster. Data includes information on currently running process instances, instances that have been run but have not yet been moved to the archive table, and archived instances. You can access current and archived data from the Operations tab. Each runtime record includes the state, dataset, and owner for the object instance, as well as scheduling information.

  Note: Each standalone Orchestrator requires a separate Runtime data store. Because an Orchestrator cluster is seen as a single logical Orchestrator, all nodes share the same Runtime data store.

• The Reporting data store stores historical data for process and operator instances. Administrators can generate near real-time reports with this data using the predefined report definitions and custom report definitions in the Reports tab.

  Note: The Reporting data store is typically shared among all Orchestrators.

The CA Process Automation data stores can share a physical database, but the best practice is to have a separate database for each data store. CA Process Automation requires database names to be case insensitive.

We recommend a minimum of 40 GB for your databases. Specific operations such as upgrading CA Process Automation make unusually large demands. Having ample space and periodically monitoring space consumption is a good practice.

Archiving policy considerations

• Runtime data stores grow as processes are run, and the space required to store this data depends on the process instance content size as well as the CA Process Automation archiving policy settings.
• Process instances are stored based on the archiving policy. You can configure the archive purging policy to:
  • Move instances to the archive after a period of time.
  • Delete older instances automatically without moving them to the archive.
  • Take no action.

    Note: When the policy is set to take no action, we recommend that you perform data archiving tasks outside of CA Process Automation.

• The archiving policy is Orchestrator-specific.

  Note: See "Configure Orchestrator Policies" in the Content Administrator Guide.

More information:

Advanced Configuration Options