XML Gateway configuration, logs, and tuning
This section discusses the XML Gateways configuration, logging, and considerations
for tuning the gateway.
Configuration
Depending on the system that hosts XML Gateway, you can adjust the settings that
affect:
• performance
• logging for XML Gateway
• logging for Backup Managers
• cleanup of unclaimed XML reports and their locations
• timeouts that affect termination of locked Backup Manager jobs
Example XML Gateway configuration file
<XmlgwConfig>
<ResultsFilesPath cleanUpMin = "15" keepFilesMin = "15">
$ARCHIVELOCATION</ResultsFilesPath> <Logging level = "SEVERE">
<LogFilePath>$LOGFILEPATH</LogFilePath>
<Threading reportThreads="5" actionsThreads="5"
<BkmgrLogging level = "0" socketTimeOut = "15">xmlgw1_0.log
</BkmgrLogging>
</Logging>
<Threading reportThreads="5" actionsThreads="5"
actionTimeoutMin="5"/>
<BackupManagerPollTimeFrame hours ="150"/>
</XmlgwConfig>
Cleanup
XML reports are generated by XML Gateway based on requests from the Media
Operations Server. These reports are written to disk and then removed when the
Media Operations Server collects the completed reports. If the server fails to collect
the reports, undeleted reports are removed by the cleanup process.
Diagnostics and tuning158