This document outlines the steps for disabling the internal CA Process Automation BIRT reporting functionality.
How is the reporting functionality in CA Process Automation disabled?
Process Automation 4.3.SP03 and earlier
Disabling this functionality is no longer available as of 4.3 SP04 and later.
Please utilize the built-in purge functionality addressed in the reporting database purge setup document.
This should only be performed if you do not use the CA Process Automation reporting – Reports tab.
A backup of your database should be performed prior to any modifications.
Stop all CA Process Automation orchestrator services. The update in step 2 below must be done at all orchestrators in your environment.
TRUNCATE TABLE filetransferserviceoperation
TRUNCATE TABLE mapialertserviceoperation
TRUNCATE TABLE playwaveformalertsvc
TRUNCATE TABLE promptuserserviceoperation
TRUNCATE TABLE soapclientcall
TRUNCATE TABLE startprocessserviceoperation
TRUNCATE TABLE tapialertserviceoperation
TRUNCATE TABLE c2oflowchartinstanceobject
TRUNCATE TABLE c2oreferenceobject
TRUNCATE TABLE c2oconfigcomponents
TRUNCATE TABLE c2oserviceoperationinstance
Additionally, in the Process Automation RUNTIME database, you should also truncate the c2oQueryStore table. This populates the reporting database with information for the reports and serves no other function. Use the same method as above:
TRUNCATE TABLE c2oQueryStore
For Oracle add 'DROP STORAGE;' to the end of each statement as
TRUNCATE TABLE filetransferserviceoperation DROP STORAGE;
Restart the orchestrator service once the database is cleaned up.
To re-enable reporting, comment the oasis.disable.reporting.manager=true line in all oasisconfig.properties files, and restart the orchestrators.
Reports will only be available for processes that started after the restarts of the orchestrators.
TRUNCATE is used rather than DELETE as it is faster, automatically cleans up and releases free space, and there is minimal impact to the transaction log.
The minimum permission required is ALTER on table_name for SQL Server.
In SQL Server, it is possible to receive a foreign key constraint error. To resolve this, you must locate the other table which is referencing the table in the error message via foreign key and then drop the FK constraint on that table.
For ORACLE the table must be in your schema or you must have DROP ANY TABLE system privilege.
For information on TRUNCATE, please see the following:
SQL SERVER: http://msdn.microsoft.com/en-us/library/ms177570.aspx