To keep the EarlyWatch Alert services list manageable and clear, you can save EarlyWatch Alerts that are no longer needed, that is, remove them from the EWA list. If you have connected an archiving system, you can archive saved EarlyWatch Alerts to reduce database load.
Note
Note that your archiving system is not part of the SAP environment. You must set up an external archiving system (SAP Note 546685).
To archive data, you have made the following settings in the IMG:
.You have the following options:
To save SAP EarlyWatch Alerts no longer needed automatically after a specified time, specify a retention time for the SAP EarlyWatch Alerts of a system:
Choose the SAP Solution Manager Administration work center with the view Solutions and the Operations Setup tab. Choose Configure EarlyWatch Alert.
Enter the required data in the Retention Time column.
Save your changes.
The system automatically removes EarlyWatch Alert sessions that are older than this retention time, along with any attachments, from the EWA list.
To manually save SAP EarlyWatch Alerts no longer required, proceed as follows:
Start the System Monitoring work center.
Select the Reporting view with report view SAP EarlyWatch Alert and navigate to the relevant solution.
You go to the overview of all SAP EarlyWatch Alert services.
Choose Save Services.
Select the service that you want to save.
Choose Save Services.
You return automatically to the SAP EarlyWatch Alert overview screen, in which a new pushbutton, Show Archive Queue, is displayed. You navigate to the overview of saved services by choosing Show Archive Queue.
Choose Show Archive Queue.
Choose Retrieve Service to retrieve the SAP EarlyWatch Alert.
The system returns automatically to the overview screen. The retrieved SAP EarlyWatch Alert service appears in the overview: Archive Sessions
You must put sessions in the repository before you can archive them.
You have the following options:
To archive sessions manually:
Choose Archive Services in the repository.
Specify a date and confirm your entries.
The system archives the sessions that are older than the specified date, along with their attachments.
To archive sessions automatically, schedule automatic archiving:
Schedule the job RDARCH_ARCHIVE_DATA_SOLMAN with transaction SM37.
You can schedule the job to execute regularly, for example, daily, to archive all sessions older than ten days.
The job archives sessions in the repository that are older than a limit specified by you, along with their attachments.
You can access any sessions in the archive. Saved sessions can be displayed, but not changed. When you archive sessions, the system saves them in an external repository and deletes them physically from the database. This reduces the size of the database.
You can display, but not change, saved sessions and their documents by choosing Show Archive Queue.
Note
The job RDARCH_CLEAN_DATABASE, which runs daily, deletes archived sessions and documents physically from the Solution Manager system database. You can then no longer open the archived sessions. You can only display them.