System Maintenance Utility (SysManUtil or more commonly abbreviated as SMU) is the primary utility that can be used to maintain table data and transactions in CGI Advantage. When submitting an SMU instance, you must first choose an action (all of which are listed in the next sections), which will determine all additional options you may need to complete the action.
The following features are common to most SMU actions:
Feature |
Description |
Statistics |
An option exists to generating statistics for the actions performed. For example, if transactions are being imported into the system from an XML file, the utility writes to the log, information about the total number of transactions that were imported, how many transactions were successfully imported into the system and how many failed. |
Restart Capability |
The capability exists to store restart information so that if a job fails for any reason the utility can pick up from where it left off and complete the rest of the job. For example, while importing an XML file that has 100 transactions the job fails after importing 45 transactions due to an error in the XML file. The job can be restarted after fixing the XML file and can continue to load the rest of the transactions into the system. |
Chunking Database Commits |
A provision exists to specify a commit block size for certain actions like importing transactions. This is very important for performance while processing a large job so that all the resources are not being used up. For example, while importing an XML file with 10,000 transactions the commit block size can be set to 100 so that the resources that have been used to import 100 transactions will be released once a commit is issued. |
Maximum Errors Allowed |
A provision exists to specify the maximum number of errors permitted while importing transactions or updating/inserting/deleting records from a table. If a value of 0 is specified then SysManUtil stops processing when the first error is encountered. If a value greater than 0 is specified then SysManUtil continues to process even though there are errors until the “maximum errors allowed” limit is reached. The data objects with errors are written to a separate error XML file. If a value of –1 is specified then SysManUtil continues to process until it reaches the end of the input XML file irrespective of the number of errors encountered. |
SysManUtil utility provides the following capabilities: