Thursday, April 17, 2008

Save, Retrieve and Archive EarlyWatch Alert

You can save no longer needed EarlyWatch Alerts, i.e. remove them from the EWA list, to keep the EarlyWatch Alert services list short and comprehensible. If you have an archiving system connected, you can archive saved EarlyWatch Alerts, to reduce database load.


Note Note

Your archiving system is not part of the SAP environment. You must set-up an external archiving system (note 546685).

End of the note.

To archive, you have made the following settings in the IMG:  SAP Netweaver  Application Server  Basis Services  Archive Link  .


Save Early Watch Alert

You can:

  • To save no longer needed SAP Early Watch Alerts automatically after a specified time, specify a retention time for the SAP Early Watch Alerts of a system:

    1. Choose transaction  SOLUTION_MANAGER  Settings  Solution Monitoring  EarlyWatch Alert  .

    2. Enter the required data in the Retention Time column.

    3. Save your changes.

      The system automatically removes the EarlyWatch Alert sessions which are older than this retention time, and any attachments, from the EWA list.

  • To save no longer required SAP Early Watch Alerts manually:

    1. Start the transaction SOLUTION_MANAGER.

    2. Choose  Solution Monitoring  EarlyWatch Alert  in the Operations screen

      You go to the overview of all SAP EarlyWatch Alert services.

    3. Choose Save Services.

    4. Select the service that you want to save.

    5. Choose Save Services.

      You go back to the SAP EarlyWatch Alert overview screen, in which a new pushbutton, Display Archive Queue, is displayed. You go to the overview of saved services with Display Archive Queue.

Retrieve EarlyWatch Alert
  1. Choose Display Archive Queue.

  2. Choose Retrieve Service to retrieve the SAP EarlyWatch Alert.

    You go back to the overview screen. The retrieved SAP EarlyWatch Alert service appears in the overview: Archive Sessions

Archive EarlyWatch Alert

You must put sessions in the repository before you can archive them.

You can:

  • To archive sessions manually:

    1. Choose Archive Services in the repository.

    2. Specify a date and confirm your entries.

      The system archives the sessions which are older than the specified date, with their attachments.

  • To archive sessions automatically, schedule automatic archiving:

    1. Schedule the job RDARCH_ARCHIVE_DATA_SOLMAN with transaction SM37.

      You can schedule the job for regular execution, e.g. daily, to archive all sessions which are more than ten days old.

    2. The job archives sessions in the repository which are older than an age specified by you, with their attachments.

You can accesss any session 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, with Display Archive Queue.

Note 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.

No comments:

Blog Archive