Index Changes

Difference between version and version     

Back to Extended Management Actions, or Extended Management Actions Info


At line 11 changed 1 line.
Users would like to create more space by deleting old and unwanted records. This applies to both persistence data store and monitoring data store. Providing out of the box scripts to do purging will take out the hassle from end users to write such scripts. The hassle is more pronounced for persistence data since persistence schema is not exposed like monitoring schema.
Users would like to have more free space by deleting old and unwanted records. This applies to both persistence data store and monitoring data store. It's relevance and importance is felt more for monitoring, since monitoring records a whole lot more events than persistence. Providing out of the box scripts to do purging will take out the hassle from end users to write such scripts. The hassle is more pronounced for persistence data since persistence schema is not exposed like monitoring schema.
At line 17 changed 1 line.
Users would like to back up their data before purging or back up their data for various reasons such as auditing or providing analytics. While we recognize that providing out of the box archiving scripts would be useful, we had to drop it for Sierra due to time constraints. At the same time since the monitoring schema is exposed to the users, it is expected that monitoring users writing archival scripts on the exposed schema is not unreasonable. Persistence data is used to recover instances in the unlikely events such as crash of BPEL SE. It is not directly used by the end user and hence is felt that there won't be a requirement to archive the persistence data.
Users would like to back up their data before purging or back up their data for various reasons such as auditing or providing analytics. While we recognize that providing out of the box archiving scripts would be useful, we had to drop it for Sierra due to time constraints. At the same time since the monitoring schema is exposed to the users, it is expected that monitoring users writing archival scripts on the exposed schema is not unreasonable. Primarily persistence data is used to recover instances from events such as system crashes. It is not directly used by the end user and hence is felt that there won't be a requirement to archive the persistence data.
At line 208 added 2 lines.
----
* Back to [SystemicQualities.Monitoring]

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-15) was last changed on 03-Mar-09 02:31 AM, -0800 by Gopalan Suresh Raj