ETEX – Archiving and deletion setup for XI
Archiving and deletion has been set up for XD1, XQ1 and XP1.
Only asynchronous messages can be archived. In the current situation this means that only messages from the TRANSPOREON scenario will be archived. All the other scenario’s have only
synchronous interfaces and their messages are subject to deletion.
2 Customizing steps
Initial customizing settings are done in SPRO under the Mass Data Archiving section:
2.1 Configure Cross-Archiving object
In SPRO – go to the relevant customizing setting
Max MB per session has been set to 2048 MB. That means that write sessions bigger than 2 G will get interrupted when the upper limit has been reached.
As messages will be stored in the file system and not in a storage area, the following setting has been made:
2.2 Create logical file path
As a logical file path definition, the name ZARCHIVE_INTERFACE has been chosen In the section “Assignment of physical path to logical path”, the following settings have been made:
The physical path corresponds with the path that has been made in the XI file system. This is the location where the archive files are stored.
To define the logical filename, the section “Logical file name Definition” has been configured. A logical filename ZARCHIVE_DATA_FILE_XI has been created with the following settings:
The logical filename is assigned here to the before created logical path. The created files will be of the type *.ARCHIVE
Param_1 will be filled with BC
Param_2 will contain a alphanumeric character A-Z, 0-9
Param_3 will contain the archiving runtime object BC_XMB
2.3 Customize Archiving Object
Here the archiving object BC_XMB must be configured
The object must be assigned to the logical file name – here
ZARCHIVE_DATA_FILE_XI. The indicator “Start automatically” has been set for the deletion job so the messages are automatically deleted after they have been archived.
2.4 Flagging the interfaces for archiving and setting retention
In the Integration Administration, go to:
under the configuration section.
Here the following interfaces have been flagged for archiving. That means that from that moment, all messages passing trough these interfaces will get the status ARCH and no more INIT. Attention ! This works only for asynchronous interfaces or synchronous interfaces where messages have a security header. If normal synchronous interfaces are flagged for archiving, they will be skipped and the messages will not be in the ARCH state. So no archiving for these interfaces will take place. It is important to add newly created asynchronous interfaces in the list if archiving have to be performed on these interfaces.
Now click on for setting the correct retention periods
The following settings have been made:
It takes 30 days before asynchronous messages will be archived. If asynchronous interfaces are not flagged for archiving, it will take 30 days before the messages will be deleted.
Synchronous messages with errors will stay 30 days in the database before getting deleted. As synchronous successful messages are not logged, the retention time can stay on 0 which is the default setting.
Remark that automatically, the specific configuration has been adjusted with these settings:
2.5 Job scheduling
The following jobs have been scheduled in all 3 XI systems:
This job is executed weekly at 20:30. That means that 4 archive files per month will be created. If the execution is set on daily, 1 archive file per day will be created.
For deletion, two jobs are scheduled:
This is the normal deletion job which runs daily at 22:00 h.
A second deletion job which will delete the history entries has been scheduled daily at 22:30
2.6 Activation of the info structure
In the transaction SARI, Customizing has been chosen. And the info structure SAP_BC_XMB has been activated so messages can be read from the archive:
3 Monitoring and administration possibilities
The transaction SARA gives access to the Archiving Administration
In “Management” we can have an overview of the archived sessions:
Other possibilities are :
Write: Here we can schedule a job to write to the archive.
Read: Here we can read from the archive: Select the archive file
And the archived messages will be displayed:
Delete: Here we can select the archive files and delete them from the archive. This is interesting if the archive is becoming too full.
In order to have an overview of the messages statuses, the following report will offer valuable information: RSXMB_SHOW_REORG_STATUS
Here we know how many messages are ready to be archived within or out the retention period. The same for deletion.
When archiving was set up, the report showed the following values for deletion:
… and for archiving: