on 11-13-2007 11:21 PM
Hi Guys,
For us,recently no. of xml messages are increasing drastically and we r getting a feel that system becoming little bit slow.
Is there any threshold limit set by SAP for XML messages in XI for given database capacity. that means
1) if the number of messages exceeds xxxxxx(number), we have to go for archive or removing some messages.
(or)
2) if databse is xx% full, we need to clear up some messages
Arciving is still not active in production.
Any help is appreciated.........
Thanx,
Kumar.
Hi,
check the following links.
1. XI house keeping jobs in production.
http://help.sap.com/saphelp_nw04/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/content.htm
2. XI Message archival & deletion.
Thanks.
rkk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
>>1) if the number of messages exceeds xxxxxx(number), we have to go for archive or removing some messages.
YES
>>2) if databse is xx% full, we need to clear up some messages
Yes.. Check with Basis team... there will be back ground job to go ahead
>>Arciving is still not active in production.
It is advisicable to have and have to delete the messages down the line....for betteer performance.
Regards
Agasthuri Doss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi kumar,
Message Size
Throughput in terms of bytes per second is much higher for larger messages. This is mainly due to the processing overhead for a single message. Assuming a linear model for the cost of proc-essing a single message of size: sbsa+=τ, the throughput ρincreases linearly with message size for small messages and asymptotically reaches a maximum for large messages.
Furthermore, the Integration Engine stores messages in a compressed format (compression rates for XML messages are normally in the range of 70-80%). Therefore, applications should be designed to use larger messages (if possible). On the other hand, processing larger messages causes higher memory resource consumption. Therefore, you should consider 64bit platforms as there are no ad-dress space issues to limit memory usage.
The database is of crucial importance for overall system performance since XI persists the messages it transports several times.
I/O Distribution
Distributing I/O evenly across available I/O channels (controllers, disks) is a key factor for optimal da-tabase configuration. Therefore, you should use as many independent channels as possible. Separate data areas from log areas (as well as from paging/swap areas).
The XI application profile is characterized by the following:
- High-volume processing in a small number of tables (about 10)
- Some tables (qRFC) with high insert/delete frequency
Check out SAP Note 812158 for more details. and also you can use SXMB_ADM to check IS Configurations.
Regards
Aashish Sinha
PS: Reward Points if Helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.