Performance header in message monitoring

Hello
I have scenario XI -> synch RFC Receiver.
In message monitoring I select response message and performance header part.
There are entries:
INBOUND, Request MAPPING, OUTBOUND, CALL ADAPTER, Response MAPIING
Does this time include RFC call through RFC Adapter?
Or it includes only IE processing like mapping.
What will include the time: <b>last time entry - first time entry</b>?
Whill it equal: request mappingRFC callresponse mapping?

Hi Denis,
the best way to monitor the performance
is the performance monitor tab in RWB
have you tried it?
you can monitor single interfaces and
also aggeregated
Regards,
michal

Similar Messages

How to delete the messages in message monitoring

hi all,
can anyone tell me is there any way to delete the messages in message monitoring.

Hi,
Please Refer these Blogs
/people/prasad.illapani/blog/2007/03/08/performance-tuning-checks-in-sap-exchange-infrastructure
/people/prasad.illapani/blog/2007/04/20/performance-tuning-checks-in-sap-exchange-infrastructurexi-part-ii
/people/prasad.illapani/blog/2007/04/27/performance-tuning-checks-in-sap-exchange-infrastructurexi-part-iii
<b>Reward Points if Helpful</b>
Regards
sasi

Error in message monitoring while creating new record in R/3

Hi All,
I am getting the following error in message monitoring while creating a new record from SAP Mobile client.
Service name: Validation_Service
Message: BackendKeys are not filled in table HEADER returned by getDetails
I am passing some random number from Client to SAP R/3 create function module.
When i pass the same value in create FM as in message monitoring. I am able to create the record successfully,
Corresponding to newly created record, i can see the data in getdetail header also.
Not sure why this error is coming.
Appreciate your help!!
Thanks & Regards
Devendra

The CREATE FM should not only create the entry, it should also EXPORT the key that it uses to create the entry. Is it doing that?
i.e. the CREATE signature is usually something like:
CREATE_BLAH
IMPORTING header TYPE header_row
EXPORTING key type header_row-key_field.
So the 'key' here should be filled by the FM and returned to DOE.

File Adapter picks up the file but cant see it in MONI/Message Monitoring

Hi
I am using FCC in Sender File Adapter and have only one sub structure under Recordset hence I have not used the 'Key Field Name' though ''Key Field Type' by default is 'String(Case-Sensitive)'. Besides the 'fieldNames' heading I have mentioned all the fields of the sub structure in the same order as I have mentioned in the Data Type.
The problem that I am facing is that even though the file is picked up from ftp successfully still I cant see any traces of it in either MONI or Message Monitoring though
The error that I receive in the MDT is -
Success : Entire file content converted to XML format
Warning : Empty document found. Proceed without sending message
Success : File "Test.csv" deleted after processing
and I have data in the file.
Can u suggest a solution?
Warm regards,
Vaibhav

> Hey
> >>So I have filled my test excel file with the values
> A and B in adjacent columns
> are you picking up some .xls file?if yes,then Content
> conversion wont work,You have to create adapter
> module processor and you have to add to your module
> processor bean to the adapter...Just check the
> following procedure...
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 1967
> Thanx
> Aamir suhail
Hi Aamir
I had a look at the blog and according to that I will need to create a module...the prob with that is in the blog he hasnt provided the full steps for that. Also I had tried this thing earlier of using an excel file and saving it in .csv format and it had worked. I cant figure out what the error is this time
Have u worked on creating amodule for excel files b4?
Vaibhav

Problem with message monitor in pi 7.4 ( AEX)

Hi All,
I have been wondering if the SXMB_MONI features are all intact in the JAVA only stack.
While in the ABAP stack i could see the XI SOAP header but in the new stack i only see XML message -> payload without the message headers,
Was wondering where the old one .Am i missing any config steps to help enable the below steps as i see them.
Basically. I want to see the SOAP headers if it delivers the user id from PI or if it delivers the user id from request.

Hi,
Check your sender SOAP communication channel and play around with the settings available.
You will see the difference within the message monitor.
Kind regards,
Dimitri

Missing Audit Log of Adapter Engine in Message Monitoring

Hi!
I've a problem with a fresh installed PI:
The Adapter Engine doesn't log anything in the Message Monitoring. The Integration Engine logs everything properly, but all entries from the adapter engine are missing. It looks like no message was processed by the AE, but in fact AE is processing the messages properly, only logging fails.
What can cause this behaviour?
Best regards,
Daniel

Hi Agasthuri,
yes, maybe something gone wrong in the post install, I will ask the guy which did the installation of the PI. Therefore I didn't have the logon data for performing a cache refresh, but in the log entries it seems that this is working properly.
Hi Praveen,
in Communication Channel Monitoring (In PI this is no longer found under Adapter Monitoring), I can see that the messages are delivered, but I can't see the Audit Log entries there.
I checked the MDT, but there are also no messages displayed.
End-to-End-Monitoring seems to be a good solution, but it seems that it is something configured wrong in this installation I will try to get the guy which cares for Basis to look after it.
Best regards,
Daniel

Message monitoring of synchronous messages

Guys,
whenever I check a synchronous message in message monitoring, its audit log is correctly shown but the message (header and payload) are not shown, returning the message "The message was deleted to save memory" or something like that.
Does anyone knows how to enable message monitoring to show the messages from sync messages?
Thanks in advance,
Henrique.

Hi Henrique,
From SP12, the payload of sync messages is cached in memory rather than persisted. These payloads are deleted to prevent them from accumulating in memory.
You just have to set:
messaging.syncMessageRemover.removeBody = false
in the AF messaging service in the visual admin
and you'll be able to trace sync calls
you only need this for sync
if you set this you'll see sync messages in,
http://hostname:portnumber/MessagingSystem/monitor/monitor.jsp
(so in the monitor for adapters)
async are logged there by default so no need to change anything for async calls...
Regards,
Abhy
Message was edited by: Abhy Thomas

Messages in Message Monitoring are being deleted?

Hi folks!
I'm facing a strage situation in our PI PRD system.
When I have to search for a message in the RWB Message Monitoring, sometimes happens that I got a specific message with its message ID, and then.. i look for it an hour later and the message isn't found anymore.. as it is being deleted or something.. the fact is I lose some messages there..
Does anybody know where can I find something about this? or where to look if they are being deleted?
Thanx in advance!
Juan

Hello Juan
What is the Quality of Service of the message?
Synchronous Message Processing (BE)
The message is only persisted by the Integration Engine in case of error (as an error version). Once a message has been processed in the target system it performs an implicit database commit.
Quality of Service
http://help.sap.com/saphelp_nw70/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/content.htm
If you have configured Archiving and Deletion, check the link below:
Defining Interfaces and Retention Periods for Archiving
http://help.sap.com/saphelp_nw70/helpdata/en/41/b715015ffc11d5b3ea0050da403d6a/content.htm
Regards
Mark

Regarding Message Monitoring

Hi All ,
Whats the differance between Message Monitoring using SXMB_MONI and Message Monitoring in RWB .
Whats the use of Transaction Code SXI_MONITOR .
Thnaks ,
hem.

Hi Hem,
As per the answers u have got from the above i want to add few points...
RWB---> it is the place where you can monitor the complete message flow. From the time it is picked to the time it is posted. Added to it u have the provision of Channel Monitoring,performance monitoring where you can check the performance(time to execute),End to End Monitoring etc... This really helps in debugging the problems.
where as is in Sxmb_moni you can just see the messages generated in the integration server. messages generated in the adapter engine cannot be viewed in SXMB_MONI or SXI_MONITOR.
you can view the same dynpro as in SXMB_MONI in the RWB.
Regards
Gopi

'System Error' status at Message Monitoring( HTTP to FILE )

I have created a scenario HTTP to FTP. I sent message to XI server using the HTTP Client.
After sending the message I am getting the response at browser.
Result:
http-Status: 200 Message accepted
Payload:
But when I look in to the Message monitoring at RWB, I am getting the message status as
System error. while going to the details i can see below error category.
Error Category MAPPING
Error Code EXCEPTION_DURING_EXECUTE
(Is the password different for port 50000 and 8000)
Please help me to solve this issue.
Thanks in Advance,
John

This is the trace message that I got for this error
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:72) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>

System error in message monitoring

Hello,
Scenario is proxy to database. Status seems to sytem error in message monitoring. Error detail is In audit log of message details as belows:
JDBC Message processing failed, due to Error processing request in sax parser: Error when executing statement for table/stored proc. 'If_test ' (structure 'STATEMENT'): java.sql.SQLException: ORA-00936: missing expression
I should resent this message content. When i press Resend tab in message monitoring, error status is not being changed.
Thanks in advance

Hi,
Check the payload received is correct or not in this case ...
Take payload and check at mapping level...
if you are using insert or update statement you can enable log at the receiver jdbc channel in advance mode(logSQLStaement to true) to see how the statement is getting framed ...
HTH
Rajesh

Message details not getting displayed in Message monitoring of RWB

Hi,
I am trying to see how many messages in Message Monitoring by selecting Integration Engine option, Message counts are getting displayed like how many has been processed successfully,processed with errors as well.
When I click on message count a pop up screen opens and gives me no messages are not available even for the same day messages.
Can any body give me an idea like where i can set any parameter to display in detail of messages in integration engine for one week back as well.
Thanks...

>When i click on count of messages which got processed with in one hour then it shows details of that messages, but when i select other messages which got processed on the same day but more than one hour then its not displaying any details of the messages.
I guess in this case your retention period is set to zero in SXMB_ADM. And this is the reason you cannot see the message even if they are an hour old.
>Is there any where where we can set parameters or any oss note to be implemented in order to see details of any messages with in a week or 10 days.
In XI run tcode SXMB_ADM and then follow "Integration Engine Configuration ---> Specific Configuration". Now check the Archive & Deletion Current & Default Values and set the Retention period as per you need.
For more information see page 11 of this document.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50?quicklink=index&overridelayout=true

How to delete the error message in the Web page Message Monitoring

Hi All:
I'd like to ask a question.If there is error message in the T-code sxmb_moni->Monitor for Processed XML Messages,I can cancel the error message manually and archive the message. After that,I can delete the message from "Monitor for Processed XML Messages".
But after those operation,I find in the web page " Message Monitoring", there are still messages in the "Messages from Component Integration Server and/or Adapter Engine".
How can I delete those message both successful and error.
Thanks All
Elliott

Hi Elliot,
SXMB_ADM
Integration Engine Configuration
Specific Configuration
Category: DELETION
Parameters: PERSIST_DURATION, PERSIST_DURATION_ERROR
Subparameters: SYNC, ASYNC
Change "Current Value".
and execute your delete job again!
Regards,
Udo

Message monitoring Status Waiting for email receiver

Hi Guru,
Scenario: SAP ECC will call Error Handling interface class. The communication channel for the Error Handling interface is Email Adapter.
Below is CC setting:
Adapter Type: Mail (Receiver)
Transport Protocol: SMTP
Message Protocol: XIALL
Adapter Engine: Integration Server
URL: smtp://11.11.11.111/
Check - Configure User Authentication
User : user1
Password: password
Mail Attributes:
From: [email protected]
To : [email protected]
Subject : test
Content Encoding: base64
I encountered one problem where my email receiver status in message monitoring is always 'Waiting'. I do not know what went wrong in the setting? Does anyone know how to solve my problem ?
Thanks in advance.
Regards

XI tries 3 times before changing the status of the message to System Error. One can Manually resend the error messages by using the RESEND button in RWB. In scenarios where XI was trying to send the message to an end system that was down for maintenance, you would want XI to resubmit the message automatically without human intervention. What would be nice is to able to tune the retries like IS_Retry which is available for Integration engine.
We can achieve this by changing the retry count used by the Adapter Engine, by default its set to 3 times, 5 minutes apart. This count can be changed in Visual Admin->server->services-> SAP XI Adapter: XI.
Here change the number Retries parameter from 3 to 10 and change the retry retryInterval to around 10minutes. For these configuration changes to be picked up, restart SAP XI Adapter: XI.
please visit the blog
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

System Error in Message Monitoring while it shows checked flag in SXMB_MONI

Hia,
We are working on ABAP Proxy --> SAP PI 7.1 --> SOAP (Asynchronous Scenario).
(ECC -> PI -> Legacy CRM)
I have following queries:
1. While sending messge across to Legacy system, we can see CHECKED flag in SXMB_MONI but there is System Error in Message Monitoring. When checked legacy system is unable to receive any message. Cannot understand the issue.
2. Is there any way to check in PI system whether the message has reached Legacy System other than making scneario synchronous?
Regards

System is getting connected and able to send asynchronous messages to legacy system. But getting following error while sending synchronous error:
2010-05-10 13:15:05     Information     Delivering to channel: CC_SOAP_SOReject_Out
2010-05-10 13:15:05     Information     SOAP: request message entering the adapter with user J2EE_GUEST
2010-05-10 13:15:05     Information     SOAP: completed the processing
2010-05-10 13:15:05     Information     SOAP: continuing to response message f33caa90-5c07-11df-c659-96d147c2ff0f
2010-05-10 13:15:05     Error     SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.. Setting message to status failed.
2010-05-10 13:15:06     Error     The message status was set to FAIL.
I have already checked Data Structure and it is fine.
Regards
In this scenarios we are using XSLT mapping using CDATA.
Please suggest solution.

Performance header in message monitoring

Similar Messages

Maybe you are looking for