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

Similar Messages

Unable to see audit log in Adapter Engine (Communication channel monitoring

Hi
I am unable to see audit log in Adapter Engine (Communication channel monitoring).
Could please suggest what parameter to set to display in PI 7.0 visual administrator.

/people/kenny.scott/blog/2009/03/08/pi-71-af-messaging-system-audit-log-persistence
Did you tried this paramter even though the above is applicable for PI 7.1
Rajesh

PI 7.1/RWB/Component/Monitoring/Adapter Engine/Test Message/403 Forbidden

Hello guys!
During performing PI 7.1 Readiness Check I have to perform a test message under Runtime Workbench\Adapter Engine\Test Message.
After processing i receive following error:
Error while sending message: 403 Forbidden.
Does anybody know the cause?
Many thanks in advance!
Jochen

Hi Sreeni!
Direct hit!
This was the problem! Missing role!
Many thanks to you!
Additional Information for all:
Readiness Check (PDF)
A compilaton of simple and advanced checks for Process Integration 7.1 (PI 7.1)
Page 44
SAP Note 817920 - XI Readiness Check 3.0/7.0, 7.1
Regards,
Jochen

Message flow between advanced adapter engine and messaging system for ICO scenarios

Dear all,
I'm working on a PI 7.31 AEX box and created an ICO object for one interface with HTTP_AAE2IDoc scenario. The interface works quite well. When I looked in to message log of messages for this interface in PI monitor, I noticed that the internal XI message are put totally 5 times into the send queue and retrieved from send queue. In some steps I only see after retrieving a message from send queue and immediately put it back into send queue. Can someone please kindly explain the message flow between advanced adapter engine and messaging system and what exactly happens after each retrieving a message from send queue?
Below is an example of message log for one message:
12/08/2014 09:26:06.472    Information    MP: processing local module localejbs/CallSapAdapter
12/08/2014 09:26:06.472    Information    Application attempting to send an XI message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.478    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.499    Information    Message successfully put into the queue
12/08/2014 09:26:06.499    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.499    Information    The application sent the message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System. Returning to application
12/08/2014 09:26:06.500    Information    HTTP adapter successfully processed interface PlantResponse_Out
12/08/2014 09:26:06.501    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.501    Information    Message status set to DLNG
12/08/2014 09:26:06.513    Information    Message successfully put into the queue
12/08/2014 09:26:06.513    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.515    Information    Message status set to DLNG
12/08/2014 09:26:06.533    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.548    Information    Message successfully put into the queue
12/08/2014 09:26:06.548    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.550    Information    Message status set to DLNG
12/08/2014 09:26:06.551    Information    Executing Request Mapping "http://styrolution.com/pi/Integration/PlantMaintenance/PlantResponse/PlantResponse_to_Zcol_Basf_Inotif02_Inotif01_Zeupm_Inotif01_Ludwigshafen" (SWCV 085d2320fb3b11e2cc0bf4d50aea8c33)
12/08/2014 09:26:06.563    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.571    Information    Message successfully put into the queue
12/08/2014 09:26:06.571    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.573    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.573    Information    Message status set to DLNG
12/08/2014 09:26:06.580    Information    Message successfully put into the queue
12/08/2014 09:26:06.580    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.582    Information    Message status set to DLNG
12/08/2014 09:26:06.583    Information    Delivering to channel: IDOC_R
12/08/2014 09:26:06.583    Information    MP: processing local module localejbs/IDocOutboundModuleBean
12/08/2014 09:26:06.583    Information    XI message received for processing
12/08/2014 09:26:06.587    Information    Sender Party: Sender Service:SXX Receiver Party: Receiver Service:RXXCLNT200 Communication Channel:IDOC_R
12/08/2014 09:26:06.588    Information    IDOC metadata repository is RXX
12/08/2014 09:26:06.589    Information    Control record is not mandatory - control record will be added if not available
12/08/2014 09:26:06.590    Information    XML Payload parsed to idoc document list with number of idocs: 1
12/08/2014 09:26:06.595    Information    Sending idoc message to receiver R/3 system with TID XIh{lsRI824UITC0009OalmW
12/08/2014 09:26:06.813    Information    IDOC message sent to receiver R/3 system
12/08/2014 09:26:06.817    Information    TID XIh{lsRI824UITC0009OalmW confirmed
12/08/2014 09:26:06.819    Information    Message was successfully transmitted to endpoint <local> using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.821    Information    Message status set to DLVD
Thanks & regards
Dingjun

Hello All,
Thanks for the prompt responses and with best information, But apart from this,I need how an adapter(File/JDBC) works along
with AAE in PI 7.1. When does the job of File/JDBC adapter is completed and resumed in a synchronous case. That is,
File Location --> file adapter -
> XI(AAE) --> JDBC adapter --> database.
In file sender, lets suppose we have synchronous settings(Best Effort). Now when File adapter's job is finished and when it
gets back the response back from XI. Please explain step by step from starting(file adapter polling the location) to getting the response coming back to XI.
Regards,
Achari.

Adapter Engine Error Message on RWB

Hello
We are getting an Red color error message on Adapter engine on RWB
monitoring ---> Component Monitoring.
Here is the error message:
SLD access SLD host:port = sap03:50000
Error getting JPR configuration from SLD. Exception: No entity of class
SAP_BusinessSystem for XID.SystemHome.sap03 found
No access to get JPR configuration
Please advise for solving the error message on adapter engine.
Thanks & regards
AK
SAP Version : NW04 (XI 3.0) SP20

Hi Senthil,
As suggested by others there is no problem with your communication channels ,,, the problem you face is because Your DBA has initiated the SHUTDOWN IMMEDIATE command. This will shutdown Oracle and terminate all active operations.
Please tell him to start the services and Wait until Oracle has been restarted by your DBA.
Regards
joel

Missing "SAP XI Adapter engine" in CCMS Monitor

Dear all,
we try to configure PI CCMS monitor but we can't find the subtree "SAP XI Adapter engine " in Visual admin.
In detail:
the subtree "SAP XI Adapter engine "is not displayed in Visual administrato under
server->service->monitoring->Monitor tree ->Root application .
So we have set to true the value "CCMSEnabled" of seervice "SAP XI AF core" , and we have restarted the instance.
After the restart i DO NOT find the "SAP XI Adapter engine " in
SAP NetWeaver Administrator,
'System Management' -> 'Monitoring' -> 'Java System Reports' -> 'Reports'. From the dropdown list 'Report' choose 'Monitor Browser', and display all monitors
So I can't activate the monitor.
and if the subtree is not present , i can't see the MTE in "SAP XI Adapter engine " RZ20.
Additional info:
- In RZ20 I have my system under SAP J2ee Monitor template->All system
but the MTE "J2EE Applications" is grayed.
- In file application.xml under /usr/sap/ccms/XIT_10/j2ee<server0> i do not find the tag:
<app name="application sap.com/com.sap.aii.af.app">
<node>\XIT\XIT 10 Appl .... sp30t0\SAP XI Adapter Engine</node>
</app>
I think this is the correct procedure that we have done in other different landscape whithout problems.
Is there something else to check ?
I've alredy checked following Blogs
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
Thanks in advance
Steven

Hi Sekhar,
I am using PI 7.0 instead so I have followed the instruction in (http://help.sap.com/saphelp_nw70/helpdata/en/e5/5d1741b393f26fe10000000a1550b0/frameset.htm) instead.
The problem is, Adapter Engine is still not listed as one of the application avaialble for Monitoring in Visual Admin even though the SAP XI AF Core has definitely been set with CCMSEnabled = true.
Any further suggestions?
Thanks,
Wi

FQDN problem in adapter engine,communication channel monitoring

Hi all,
Recently i configured FQDN for PI system while configuring END to END monitoring. Everything is going fine and end to end monitored worked smoothly.
But Problem started in comminuication channel monitring.adapter engine status and others. Because its trying to retrieval the URl without FQDN and its showing an error as requested resource does not exist.
I changed the exchange profile paramters also. But still i am afcing the problem.
So,please suggest me to overcome from this issue.
Regards
Vijay

/people/kenny.scott/blog/2009/03/08/pi-71-af-messaging-system-audit-log-persistence
Did you tried this paramter even though the above is applicable for PI 7.1
Rajesh

Audit log is empty in RWB CC Monitoring

Hi experts,
I am facing a problem with the message monitoring in the RWB. The Audit Log tab for the message details has nothing while the Message Content and Message data contain information about the message. I have set the parameter message.auditLogEnabled to false for the service com.sap.aii.af.svc in the NWA and restarted the instance but with no luck. Please help me out.
Regards.

Hi Prateek,
That parameter was 'true' by default.
As per this blog,
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417800)ID0321728450DB01035845556380020404End?blog=/pub/wlg/13456
I changed it to 'false'. The persistence of messages is 24 hours, which is fine.
I am now trying to look at the table XI_AF_MSG_AUDIT. It has about 800K records in it, in which about 80k have 'DLNG' as their status. Do you think this is causing any problem?
Regards.

No Adapter Engine in Component Monitoring

Hi, perhaps u have read my previous post concerning problems while refreshing cache.
Well i found out that my adapter engine is not listed in component monitor in RWB.
I have no clue why this now all happens because i did no changes! I am not able to refresh IB Directory stuff, therefore nothing is processed via XI.
..and the adapter engine is not listed.
What might be the problems. I already studied the XI-Cache-HowTo!
br

Hi Agasthuri,
the SWC are imported "well". It all seems to be fine after restarting the server.
But still i am not able to refresh the cache - it's explizit the ABAP-Cache!
SXI_CACHE offers error while attempting to refresh the cache!
The Cache connectivity test in RWB says that an error occured while attempting to connect to Integration Directory!
any ideas...?

Messages taking few seconds to pass through Adapter Engine

Hi All,
I am dealing with Synchronous scenarios.Sender is SOAP adapter and receiver is proxy.
When I monitor the message monitoring audit log for Adapter engine I can see in the message is taking 4-5 seconds to reach the Integration engine from the SOAP sender adapter.
This delay is in the Audit log when the message goes from the step "Trying to put the message into the call queue" to "Message successfully put into the queue".
Is there any setting by which I can eliminate this delay time in adapter.
Can somebody help me out on this?
Note : CPU Utilisation is around 7 % and there are around 700000 messages per day.
Thanks,
Zabiulla

Zabiulla,
it's a performance tunning task. Unfortunately most of the actions SAP suggested for performance tunning are aimed at async communication, for SOAP, what you can at least try is to: Instead of using the SOAP sender adapter, you can directly send a SOAP request to the entry point of the Integration Engine pipeline bypassing the Adapter Engine. As a prerequisite, the URL/query string should include the XI parameters like in the example below:
http://<server>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Try this to bypass adatper engine, this should help in your case.
Jayson

Diff bteween trace,log and audit log

Diff bteween trace,log and audit log....?
Harsha

Hi,
Audit Log :The adapter engine uses the messaging system to log the messages at every stage, This log is called the Audit Log.
The audit log can be viewed from the runtime work bench(RWB) to look into the details of the life cycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Audit logs are mainly used to trace our messages. In case of any failures, we can easily trace where message stands. we can give the entries for the logs in UDFs, custom modules etc..
Audit logs are generally gives us the sequence of the steps from where the message is picked up with file name and path and how the message is sent to the I.E pipeline..it also shows the status of the message like DLNG,DLVD like that...generally we look into the audit logs if there are any errors in message processing...
It gives the complete log of your message.
Go to RWB --> Component Monitoring --> Adapter Engine --> Communication channel Monitoring --> Select the Communicatin channel --> click on use filter --> then click on the Message Id.
Trace Log:
Log file:
A log file contains generally intelligible information for system administrators. The information is sorted by categories and is used for system monitoring. Problem sources or critical information about the status of the system are logged in this file. If error messages occur, you can determine the software component that has caused the error using the location. If the log message does not provide enough details to eliminate the problem, you can find more detailed information about the error in the trace file.
The log file is located in the file system under
"/usr/sap/SID/instance/j2ee/cluster/server[N]/log/applications.[n].log" for every N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Trace file:
A trace file contains detailed information for developers. This information can be very cryptic and extensive. It is sorted by location, which means by software packages in the Java environment, for example, "com.sap.aii.af". The trace file is used to analyze runtime errors. By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments on class and method level. The file should be analyzed by SAP developers or experienced administrators.
The trace file is located in the file system under
"/usr/sap/SID/instance/j2ee/cluster/server[N]/log/defaultTrace.[x].trc" for each N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Thanks
Virkanth

Errors in Message Display tool in Integration engine in Message Moni in RWB

Hi,
We are facing issues with the Message Monitoring in RWB.
When we are selecting the Integration Engine and selecting the message and then clinking on details.
We are able to see 4 tabs :
1. Message Data
2. Message Content
3. Inbound Adapter
4. Queue Monitor
Is it right to display these 4 tabs for Integration engine ?
Where will be this setting ? What tabs shud be there ?
We are using XI 7.0 SP10.
When we are selecting the Adapter Engine in Message Monitoring then we are getting Page cannot be displayed.
Please provide your precious inputs to resolve this issue.
Thanks
Ramesh

Hi Krishna,
We have restarted the system but its not working.
Adapter engine is working fine without any issues.
Only the issues are unable to view the Message monitoring as it shud be.
In Message Monitoing => Integartion Engine => Message Selected =>Click Details=> Message Display tool => Message Data Tab is fine.
Message Content Tab => if we open we are getting the following error with SAP screen.
**************************SSO logon not possible; browser logon ticket cannot be accepted
Choose "Logon" to continue A dialog box appears in which you can enter your user and password
No switch to HTTPS occurred, so it is not secure to send a password ****************************
Please suggest us.
Thanks,
Ramesh

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>axis2ns1:Server</faultcode>
         <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                            database default values were set. See the associated message for more information.
           BMXAA4190E - Country NZ is not in the value list.</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                      - Validation failed when the database default values were set. See the associated message for more information.
     BMXAA4190E - Country NZ is not in the value list.
            /Exception>
         </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 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.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

Delay of Message in the Adapter Engine when put into queue

Hi XI/PI Experts,
We are having problems in the Adapter Engine wherein messages are staying longer in the AE queue as usual. Sometimes, it stays longer in Delivering status also. Is there any way we can monitor and try to push the message out of AE to avoid delays? I know we can do this in the ABAP side (Integration Engine)...but how can we do this in the Adapter Engine?
See below sample logs in AE RWB:
2008-07-17 13:28:13 Success Using connection SOAP*****. Trying to put the message into the receive queue.
2008-07-17 13:28:13 Success Message successfully put into the queue.
2008-07-17 13:34:12 Success The message was successfully retrieved from the receive queue.
2008-07-17 13:34:12 Success The message status set to DLNG.
As you can see there is a gap of 4 minutes.
Hope you can help me. Thank you so much in advance.
Grace

Hi.
Thanks for your answers but the messages are not set into EOIO but just EO. So the messages are not ending up in Holding Status.
I also believe that issue is not occurring because of too many messages in error in AE nor because of the receiving system is down. Issue is happening when message is about to be sent to the SOAP communication channel in AE. As you can see in the sample log I provided above, in RWB AE, after the message was put into queue, it took several minutes to be delivered to corresponding comm channel. My questions are:
1. Is there a way we can monitor the queue in AE like the way we monitor the queue in IE? (e.g. smq1 and smq2 transactions) .
2. If there is a way, how are we going to intervene manually on the queues in AE? (we can intervene with smq1 and smq2 in IE)
3. For messages with Delivering Status in AE, sometimes it is taking hours to move to "Successful/Delivered" Status. Is there a way we can intervene with that? I believe we can resend messages with "System Error" Status and Staus "To be Delivered" but for status "Delivering"...it is not possible (from what I know -- I hope there is a way).
I look forward to hearing from you guys/gals.
Grace

Messages Stuck in adapter engine but passing through Integration engine

Hi All,
SOAPFault Error. Error Code/Category: XI Protocol/ Wrong Value...Received HTTP Response Code 500: Error during Parsing of SOAP Header
Above error as system error appears in adapter engine when messages are coming into SAP PI. At sender, we are having sender mail adapter.
Adapter Modules are also configured in mail adapter.What could be the possible reason.
Please suggest
Regards,
Kanisha

Below is the error log. As per scenario, Mail To File.
Please Suggest
Regards,
Kanisha

Missing Audit Log of Adapter Engine in Message Monitoring

Similar Messages

Maybe you are looking for