About Archived Logs

Logs can be archived locally or exported to an FTP server. From the WMC, you can download locally archived logs: Logs > Archive Logs.

You can archive or purge orchestration monitoring logs. When you configure parameters to archive orchestration monitoring log files, the Integration Appliance archives the log files before polling for conditions that trigger the Integration Appliance to purge additional orchestration monitoring data. You can archive orchestration monitoring data to a local disk on the Integration Appliance or export the archives to an FTP server. If you do not configure archive settings, the Integration Appliance purges all orchestration monitoring data that meets the default purging trigger conditions.

You can view archived log files by selecting Logs > Archive Logs in the Navigation page. When you export the logs, the Integration Appliance names exported orchestration monitoring logs using the following convention: orcmon_export_<timestamp>.xml.

Archiving Orchestration Monitoring Logs Locally

About this task

When you select the Archive Purged Monitor Data to a Local File option and one of the log purging trigger conditions is met, the Integration Appliance exports orchestration monitoring logs to a local disk on the Integration Appliance.
Note: When you archive orchestration monitoring logs locally, you decrease the availability of disk space on the Integration Appliance. As the disk space is filled up, the purging trigger conditions generate archives much quicker.

Procedure

  1. From the Navigation pane, select Logs > Job Log. The Results page displays all orchestration monitoring logs.
  2. Click Settings. The Job Log Settings dialog is displayed.
  3. Click Archive.
  4. In the Archive Settings section, select Archive Purged Monitor Data to be a Local File .
  5. Select Replace Exported File to replace previously exported orchestration monitoring logs. If you do not select this option, the Integration Appliance cumulatively stores orchestration monitoring logs. This can cause the Integration Appliance to run out of disk space very quickly and prematurely trigger a purge.
  6. Click Save.

Results

The Integration Appliance archives Orchestration Monitoring logs locally. You can download locally stored archives by selecting the archive from the Archive list and clicking Download.

Archiving Orchestration Monitoring Logs to an FTP Server

About this task

When you select the Archive Purged Monitor Data to a Local File option and the Transmit Archive to FTP Server option and one of the log purging trigger conditions is met, the Integration Appliance exports orchestration monitoring logs to an FTP server. You can chose to archive all the exported log files on the FTP server or chose to have the latest archive replace the previous archive.

Procedure

  1. From the Navigation pane, select Logs > Job Log. The Results page displays all orchestration monitoring logs.
  2. Click Settings. The Job Log Settings dialog is displayed.
  3. Click Archive.
  4. In the Archive Settings section, select Archive Purged Monitor Data to be a Local File .
  5. Select Transmit Archive to FTP Server (After a Purge).
  6. (Optional) Select Replace Exported File to replace previously exported logs.
  7. Specify FTP settings. See the following table below:Table 1 for more information about the FTP settings.
  8. Click Save.

Archiving Utilization Data to an FTP Server

About this task

The Integration Appliance collects data about disk usage, memory usage, garbage collection, and the number of running jobs. This resource utilization data can help you analyze the overall health of the runtime and calculate available capacity for additional projects. The Integration Appliance stores this data in a file called maestro.stat and provides an option to archive a snapshot of the data to an FTP server. When you select the appropriate option, all the utilization data available on the Integration Appliance is collected and archived to the specified FTP server.

After an archive file has been created and transmitted to an FTP server, the Integration Appliance continues to aggregate new utilization data to the historic utilization data. Historic utilization data is not purged from the Integration Appliance when an archive is transmitted to an FTP server.

Selecting the Transmit Archive to FTP Server option transmits a snapshot of the utilization data daily at midnight. The following procedure describes how to select the option.

Procedure

  1. From the Navigation pane, select Logs > Job Log. The Results page displays all orchestration monitoring logs.
  2. Click Settings. The Job Log Settings dialog is displayed.
  3. Click Archive.
  4. Select Transmit archive utilization data to FTP Server (at midnight) .
  5. Specify FTP settings. See the following table below: Table 1 for more information about the FTP settings.
  6. Click Save.

FTP Settings

Specifying FTP settings to archive orchestration monitoring logs and utilization data.

Table 1. Job Log FTP Settings
Parameter Description
Host Specifies the name of the FTP server, where the exported log files are archived.
Port Specifies the port number of the FTP server, where the exported log files are archived.
Username Specifies the user ID that the Integration Appliance uses to log in to the FTP server, where the exported log files are archived.
User Password Specifies the password that the Integration Appliance uses to log in to the FTP server, where the exported log files are archived.
Hide Password Text If you clear this option, the password you entered displays in plain text and is no longer encrypted.
Directory Specifies the FTP directory to which the Integration Appliance exports the log file.



Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.appliance.doc/ApplianceHelp/Working_with_Logs/archivingJobLogs.html