Archiving and Deleting 

Use

●      Archiving and deleting messages:

Messages that have been processed correctly are deleted by default. You must archive all messages that are not to be deleted.

To archive messages, you must first define their corresponding interfaces and then schedule the archiving.

Since correctly processed messages are flagged as either To Be Archived or To Be Deleted (and because this indicator cannot be changed), you must decide which messages you want to archive before the first message is processed.

Messages that have been modified or cancelled manually are archived automatically.

You require two archiving jobs to archive messages:

○       A job to write the messages to the archive

○       A job to delete the archived message

Only one job is required to delete messages.

You can schedule all jobs periodically, but you must maintain the job sequence.

You can select and display archived messages.

●      Deleting history entries for processed messages

History entries are spots for observing message processing. They are generated by persisting at the end of a processing step for a message and contain the current status and the execution date.

History entries remain in the database for an unspecified length of time and must be deleted at some stage so that the database table does not overflow. The deletion process only deletes history entries for messages that have already been archived or deleted. The history entry is kept in the database for at least seven days after a message has been deleted. This is necessary since history entries are also required for the quality of service Exactly Once.

The default retention period is 30 days. You can change this value in the configuration of the Integration Engine by using the HISTORY subparameter of the PERSIST_DURATION parameter in the DELETION category.

Prerequisites

To archive messages, the following prerequisites must be fulfilled:

●      You have defined the interfaces for the messages to be archived by choosing Configuration → Define Interfaces for Archiving and Retention Periods in the Integration Engine menu.

To archive messages, use the archiving object BC_XMB and use SAP_BC_XMB as the archiving infostructure. If you want to read the archive, the archiving infostructure must be activated.

●      You have used transaction Archive Administration (SARA) to set up archiving for the archiving object BC_XMB to archive messages.

More Information: Data Archiving Procedure).

●      You have used transaction Archive Information System (SARI) to activate the archive infrastructure SAP_BC_XMB to read archived messages.

More information: Archive Information System

To delete messages, the following prerequisites must be fulfilled:

●      You have defined the deletion procedure required to delete messages by choosing Configuration → Configure Delete Job from theIntegration Engine menu.

The Simple Deletion Procedure is set as the default. No steps are required to activate the deletion procedure.

If you want to use the Switch Procedure, select the Switch Procedure Activated checkbox. You can do this at any point. The delete jobs react correspondingly, and with immediate effect. However, you can only deactivate the switch procedure when the original tables are active and the counter for the number of deleted records in the original tables is at zero. If this is not the case at the time of configuration, this is noted by the system and the switch procedure is deactivated the next time that table entries are copied from the table copies to the original tables.

For more information about the simple deletion procedure and the switch procedure, see the documentation, which is displayed when you call the function.

To delete history entries, the following prerequisites must be fulfilled:

●      You have already deleted or archived the messages that belong to the history entries because you cannot delete history entries for messages that are still in the database.

Scheduling Archiving Jobs

You schedule an archiving job, which in turn schedules the jobs to write the message to the archive and delete the archived messages. To do this, proceed as follows:

...

       1.      In the Integration Engine → Administration menu, choose Schedule Archiving Job. This takes you to the Integration Engine: Archiving screen.

       2.      Specify the following.

Archiving Specifications:

Specification	Description
Client	Current client
Parallel Processing	Level of parallel processing You can specify the level of parallel processing by using the configuration parameter ARCHIVE_PARALLEL in the ARCHIVE category. If the value is greater than 1, parallel archiving takes place, which generally speeds up the archiving process.
User Name	Your user name You can also enter a different user name that has the corresponding authorizations.
Start Time	The start time of the archiving action The system displays a dialog box, where you define the start time and maintain the parameters in the corresponding fields. If jobs are to be executed periodically, choose Period values to enter the start values. To enter restrictions for the start time and date, choose Restrictions. The start time only applies to the execution of the first action. It is retained until the end of the archiving session.
Spool Parameters	Controls the print output of the generated archiving log The system displays a dialog box in which you maintain the general parameters Output Device, Number of copies and Number of pages. You can choose Properties to maintain additional properties of the spool request. You do not generally change these properties for each spool request. Spool parameters that are already specified in the user defaults or in the user-specific print parameters are automatically applied. Otherwise, you only have to specify the spool parameters for the execution of the first action in an archiving session. They are retained until the end of the archiving session.

       3.      To schedule your job, choose Schedule Archiving.

       4.      To display the scheduled job in the job overview, choose Job Overview.

       5.      To use the SAP archive administration options, choose Archive Administration and then enter the archiving object BC-XMB in the Object name field.

Do not schedule your write or delete jobs by using archive administration, but use the Integration Engine archiving functions.

The following options are also available:

○       To read messages that have already been archived, choose Read.

You can start the read program for your archiving object either in the background or in dialog mode. The latter corresponds to choosing Archived XML Messages (Search Using Archive) in the Integration Engine → Monitoring menu.

○       To display an overview of archiving sessions that have already run for your archiving object, choose Management.

○       To display statistics for the individual archiving jobs, choose Statistics .

For performance reasons, the statistics values are generally imprecise.

       6.      To migrate archive administration data, choose Archive Migration.

Scheduling Delete Jobs

To schedule delete jobs, proceed as follows:

...

       1.      In the Integration Engine → Administration menu, choose Schedule Delete Jobs.

       2.      Select the job(s) to be scheduled.

       3.      Specify the start time and date.

       4.      Specify the period you want to use and choose Schedule.

For an overview of all jobs, choose Jobs.