Difference between revisions of "arsadmin"
(Initial edit.) |
m (Formatting) |
||
| Line 1: | Line 1: | ||
In versions prior to Content Manager OnDemand v9.5, 'arsadmin' was a utility that did the majority of the work during the ingestion of data with [[arsload]]. It was responsible for compressing, segmenting, inserting metadata, and storing objects and resources into the cache, [[TSM|Tivoli Storage Manager]], and the database engine. It was also the way that administrators could [[unload]] data from CMOD in case data needed to be removed from the system. | In versions prior to Content Manager OnDemand v9.5, 'arsadmin' was a utility that did the majority of the work during the ingestion of data with [[arsload]]. It was responsible for compressing, segmenting, inserting metadata, and storing objects and resources into the cache, [[TSM|Tivoli Storage Manager]], and the database engine. It was also the way that administrators could [[unload]] data from CMOD in case data needed to be removed from the system. | ||
Revision as of 08:32, 25 March 2015
In versions prior to Content Manager OnDemand v9.5, 'arsadmin' was a utility that did the majority of the work during the ingestion of data with arsload. It was responsible for compressing, segmenting, inserting metadata, and storing objects and resources into the cache, Tivoli Storage Manager, and the database engine. It was also the way that administrators could unload data from CMOD in case data needed to be removed from the system.
In CMOD v9.5 and higher, much of the functionality from the arsadmin command has been integrated into the arsload in order to improve performance by minimizing forking additional processes. This allows more concurrent data ingestion to occur with less CPU overhead, and less wait time.
Links to IBM Documentation
arsadmin Description and Syntax v9.5