Persistence Layer Analysis

[Former Member]

Hi Experts,

what do we check in Sxmb_moni - Integration Engine Monitering - Persistence Layer Analysis.

and the utility of the tab - Status records for sync / async communication.

Regards,

Arnab .

[SudhirT · Accepted solution]

Hi Arnab,

Persistent layer analysis gives the detail about total record present in the table SXMSPMAST/SXMSPMAST2. And this is the table used for storing the messages at Integration Engine. Hence the number of entries in this table shows the number of messages stored in this table.

It also gives information whether the switch Delete procedure is activated or deactivated.

Maximum Number of table entries shown can be set in technical setting of table SXMSPMAST.

We use this when we want to analyse how much database is filled. and for monitoring purpose we use this to check if the persistence layer goes beyond 99% the system will stop working because of database.

Thanks!

Edited by: Sudhir Tiwari on Dec 31, 2008 6:57 AM

[Former Member]

hi ,

To monitor the Switch Procedure (Fill Level, Active Container) you

can use transaction SXMB_MONI -> Persistence Layer Analysis.

Based on the value chosen for DROP_MAX_TABLE_LOAD the

"Current Fill Level" entry wii be displayed. The maximum possible number of messages is determined via a DDIC function and can be found via transaction SXMB_MONI -> Persistence Layer

Analysis -> value of entry 'Maximum Number of Table Entries'.

To get an overview over the situation in your persistence layer,

run report RSXMB_SHOW_REORG_STATUS. Chooose the option "Checking

all messages" and execute the report. For details about this

report please go through sap note 696738.

regards,

navneet

[Former Member]

Navneet,

I understand the operation , but i dont understand why and when we use this.

Regards,

Arnab

[Former Member]

Hi,

SXMB_MONI_DB is direct t-code for analysis of the persistence layer.

The central component of sync/async communication is the sync/async bridge, which enables the Integration Server to receive synchronous messages from a sender and send them to a receiver as asynchronous messages. Viceversa, it can send the asynchronous response from the receiver back to the sender as a synchronous response.

To monitor the status information of these persisted messages persistence layer analysis is required.

You can monitor the details in SXMB_MONI, but via persistnace layer monitoring you can direct to the workflow log, by double click on the message ID part.

Thus the whole flow can be monitor. Else for integration process you may need to go for SXMB_MONI_BPE.

Thanks

Swarup

[Former Member]

hi arnab,

when messages is executing through the xi pipeline it got stored in many of the abap tables .

And by the time these table space ll get increasing. if once the table get filled than ur system performence ll get decrease, for example to open the sxmb_moni tcode ll take long time , to display the xi pipe line steps ll take long tine ,system through put ll come don.. to avoid all these prob we have to procerure

1) Archiving.

2) Deletion.

for this u need to scedule the archiving and deletion job in sxmb_adm tcode.after that you need to schedule the retention period time .

for all these you need to activated the table switch

procedure. You can check this via transaction SXMB_ADM -> Configure

delete procedure. The information button on that screen explains

the switch procedure in detail. If the switch procedure is chosen,

then the XML messages will only be removed (via table drop) if

A) the retention time is expired and

B) a specific fill grade of the table is reached.

The default value is 90, that is the deletion will occur when 90%

of the table is filled. You can set this parameter via transaction

SXMB_ADM -> Configure Integration Engine -> Specific Configuration.

Create an entry of category DELETION, parameter

DROP_MAX_TABLE_LOAD, no subparameter.

now to monitor the Switch Procedure you

can use transaction SXMB_MONI -> Persistence Layer Analysis.

now i think ur dought ll be cleared...

thanks. and regards,

navneet

[Former Member]

Hi Navneet ,

doubt cleared,many thanks to you and Sudhir!

[Former Member]

Hi Arnab,

Status records for sync / async communication

USE:

You use the monitor for sync/async communication to display status information about persisted messages where a coupling of synchronous and asynchronous processing has occurred.

The status monitor for sync/async communication provides the following information as the default:

· The number of active synchronous calls that are still waiting for a response

· The number of processes with errors (synchronous calls) whose status has not yet been deleted

· A table containing status information about the involved synchronous request messages

The system displays the following status information:

¡ The overall status with a green, yellow, or red traffic light

Activities

In the status monitor for sync/async communication, you can execute the following activities:

· Close all processes with errors.

· Update the entire display by choosing Update in the application function bar.

· Update the table of displayed messages by choosing Update in the table symbol bar.

· Navigate from the list of displayed messages to the corresponding workflow log. To do this, click the message ID of the respective message.

Regards

Praveen K