PI 7.0 Performance: Monitoring the Persistance Layer Fill Level

I came across different situations on where I had to analyze some specific PI performance issues.

Besides all the technical aspects you have to consider when implementing a PI solution (correct hardware sizing, network traffic design, and so on), you have to carefully plan a Data Archiving solution so your Database does not grow up quickly and PI tables become unmanageable.

First thing to watch is your current Persistance Layer Fill Level (where all XML messages are stored).

Call transaction SXMB_ADMIN --> Monitoring --> Persistance Layer Analysis.

The number you get in the results should be steady even decrease over time, as new data gets in, old data is being archived to filesystem and deleted from DB through the Archiving & Deletion policy.

You configure Archiving & Deletion thresholds and jobs from within SXMB_ADMIN.

• You first go to Configuration --> Define Interfaces for Archiving and Retetion Periods. That is, the interfaces you want to Archive and their retetion period.

You input data for Async XML messages, and Sync XML messages. Also you set a retention period for all the already Archived & (flagged as) Deleted from Database.

• You set the Archiving and Delete Jobs from the Administration menu in SXMB_ADMIN.

Some pre-requisites might be needed to correctly configure Archiving objects in transaction SARA, but this is common archiving configuration for all Basis releases.

Additionally for PI, and depending on your functional implementation, there are additional objects you might have to consider for Archiving, please check OSS note 872388.