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:
Only one job is required to delete messages.
You can schedule all jobs periodically, but you must maintain the job sequence.
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.
To archive messages, the following prerequisites must be fulfilled:
To archive messages, use the archiving object BC_XMB.
Archive infostructures SAP_BC_XMB1 and SAP_BC_XMB_LMS are provided (for user-defined message search).
Another (older) archive infostructure SAP_BC_XMB is also provided. We recommend that you use the newer archive infostructure SAP_BC_XMB_LMS.
If you do not want to use the user-defined message search, then choose archive infostructure SAP_BC_XMB1 instead. This will achieve a higher level of performance.
If you want to read the archive, the archiving infostructure must be activated.
More information: Data Archiving Procedure ).
More information: Archive Information System ).
To delete messages, the following prerequisites must be fulfilled:
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 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:
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. Note
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. Note
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. Note
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. |
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:
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.
For performance reasons, the statistics values are generally imprecise.
To schedule delete jobs, proceed as follows:
For an overview of all jobs, choose Jobs.