Want to access Status in Message Monitoring

Dear All,
I want to get access to the Status Parameter in Message Monitoring so that depending on the Status(Waiting or Syste Error),I can set my logic and send a mail to the developer.
I need help.
1. Where can I find out the Parameter for status in RWB Message Monitoring?
2.Is there any method so that I can set some parameters and it will directly send mail to the developer or I have to use Mail Adapter and write my own scenario?
3.If I am to develop my own scenario,then how to automate the whole process for each of the New messages?
Thank you in Advance.
Sugata

Hi Suresh,
Thank you for your reply.But this is not what I wanted.In my RWB,there are different Message monitoring Status parameters and I want to get hold of that,to be more open,I want that status to come as Subject of my mail.For that reason I need the Status Parameter,and I need to put that in my mail.How to do that?
Cheers..
Sugata

Similar Messages

Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

Hi,
I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
2014-03-26 08:39:10
Information
The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
2014-03-26 08:39:10
Information
Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2014-03-26 08:39:10
Information
Message successfully put into the queue.
2014-03-26 08:52:48
Information
Admin action: Trying to redeliver message.
The connection between the receiver is ok, does this have something to do with the Communication Channels?
Please help.
thank you.

Hi Eng Swee,
there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
this is what is indicated in the Audit Logs
2014-03-26 02:38:47
Information
Admin action: Trying to fail message.
2014-03-26 02:38:47
Error
The message status was set to FAIL.
2014-03-26 02:38:47
Information
Admin action: The message was successfully set to status failed.
2014-03-26 02:38:47
Error
Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
2014-03-26 02:38:47
Error
Asynchronous error reported.
Is this the reason why the messages are stuck?
thank you!

To Be delivered status in Message monitoring

Hi,
There are some messages in TO BE DELIVERED status in Message monitoring while selecting integration server. I could neither cancel nor resend.
any input reg. this will be appreciated.
I didn't see any messages with TO BE delivered status in adapater engine.
I could able to clear What ever messages in system error status in adapter engine by filtering based on sequential id.
I have seen this thread & link also.
To Be Delivered
Re: "To be delivered" status in RWB -- Any solution?
http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
I could not see any entry in SMQ1, SMQ2, SM58 also
Thanks
Praba
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:02 PM
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:04 PM

Hi,
You cannot resend or cancell the messages which are in status "To Be Delivered". Check Receiver adapter File/Jdbc/ OFTP e.t.c. which is processing these messages.
Check with your Basis team to remove the lock of adapters if any. Or to process these messages you require soft restart of Java stack.
I had same kind of issue two days back with OFTP adapter messages and did soft restart of java stack with help of Basis team.
Hope it will helps you
Cheers
Veera

'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>

Message got struck in hold status in message monitoring.

Hi SDNers,
             I am doing Idoc to File scenario. I triggered an Idoc and it is successfully processed in XI and got struck in message monitoring with hold status.
             After repetetive attempts of restarting the message, still it is in hold status.
             Even if I tried to cancel the message, it is not cancelling as it is in hold status.
            Can anybody please help how to process the message or can anybody explain how to cancel the message from message monitoring, which is in hold status.
Regards,
Jayaram.G

Hi,
If the message that has not yet been delivered is not in error state, the problem cause is probably that the message is blocked in the QRFC queues of the Integration Engine.
Check queue status
Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:
u25CF     Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)
u25CF     Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)
u25CF     Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)
u25CF     Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.

Message status "Holding" - Message monitoring adapter framework

Hello,
We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
The blog does not mention what to do when the first message (sequential number) is not available anymore.
Is it possible to restart the messages in the queue in that case?
Thanks
Kind regards
Frank

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
resend or cancel the message to release the queue.
Regards,
Abhishek.

Messages remain in Scheduled status in message monitoring in RWB

Hi PI experts,
I have got a situation where there are several messages showing in the Scheduled status. I followed the path RWB > Message Monitoring > Adapter Engine > Database (Overview) > Display.
QoS for these messages is EOIO, however there are no messages stuck in the queue. All other channels are running smoothly. Only with this particular channel the messages remain in Scheduled status for a long time.
I am neither able to make out the roor cause nor reprocess/resend these messages. Pleaes help.
Regards,
Dhawal

Hi Suraj,
What you said is absolutely correct. However, as I mentioned, the error message was not visible in RWB.
My problem just got resolved. What I did is this,
I followed the link http://<server>:<port>/MessagingSystem/monitor/monitor.jsp which is SAP Message Display Tool.
Here in EOIO Sequence Monitor I found the error message and it's predecessor. When I resent the erroneous message from here, all subsequent Holding messages got processed.
Thank you everyone for your help. Have a gr8 day...
Best Regards,
Dhawal

Scheduled Status in Message Monitoring

Hi All,
We have a scenario from DB- DB using Java Proxies. The Message interfaces are defined as Asynchornously with EO mode.
Usually the sender channel picks data and tirggers Java Proxy. Proxy process all records and send the status back to sender in 5 mins.
But when I started multiple interfaces at the same time, I observe that one interface is taking 15 min and while that interface is in processing state, the other interface which started at that time are also in Scheduled status. But the sender channel picks data for every 5 mins, which is creating duplicate records.
The interfaces which are in Scheduled status are getting processed only after that interface ( taking 15 min) gets processed.
Why is this dependency on other interfaces and is there any way to avoid this dependency?
Please suggest.
Regards,
Srini

you can do queue/message prioritization.
but I suggest to use one status field in DB, when you are polling DB to select records , immidiately change staus to picked and after processing successfully change it to processed.

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

Seeburger Workbench access - restrict users to Message Monitor only

Hi All
Does anyone know if it's possible to restrict users to Message Monitor only access in the Seeburger Workbench?

Hi Andy,
if by "restrict" you mean if you can change the links available in the workbench, then sadly no - this is currently not possible. If you're ok with getting a HTTP Forbidden when clicking on other links than the Message Monitor, then yes - this can be configured within the SAP NetWeaver Administrator -> Identity Management. Check for example to documentation of the Message Monitor
Extracted from there:
    Log on to the NetWeaver Administrator (NWA).
    Open Operation Management | Users and Access | Identity Managemet (UME).
    Create a role and assign the manage action for com.seeburger.xi.frontend.messageidmonitor to that role.
    Now you can assign the newly created role to any user you want to grant access to the SEEBURGER Message ID Monitor.
This is for explicitly granting some user the access to the Message Monitor. The manage action is per default set to "Everyone". You need to remove Everyone on the corresponding frontends (search for actions with name com.seeburger.xi.frontend*)
Hope that helps
Greetings
-Sascha-

Message Monitor - Access rights

Hello,
we want to give some user access rights to look into Message Monitor to track the transfer of IDOCs.
Basically we have the role Role_SAPMEINT which lets us take look into the queue monitor but not the message monitor.
By which UME roles or UME actions is this part is accssible for the user.
I don't want to give the user SAP_XMII_Admin role.
Regards,
Kai

It looks like there are some Actions for the Message Listener Monitor listed in the MII help.
Actions for Permissions - SAP Manufacturing Integration and Intelligence - SAP Library

I have an iMac OS 10.9.5 - Every time I turn on my system I get the message that it can not access icloud and to fix it using iCloud preferences. I do not want to access or use iCloud, how do I get the message to discontinue?

I have an iMac OS 10.9.5 - Every time I turn on my system I get the message that it can not access icloud and to fix it using iCloud preferences. I do not want to access or use iCloud, how do I get the message to discontinue?

Hello mrmacjohn,
Verifying that any iCloud account that may be signed in is signed out should resolve this error.
On your Mac, open iCloud preferences, then click Sign Out.
iCloud: Change iCloud feature settings
http://support.apple.com/kb/PH2613
Cheers,
Allen

I can't access iCloud, i keep getting a message to try again later. This is the first time i have tried to log into icloud. I know my account is working, i want to access it from my macbook. I think its looking for my old icloud email, what to do?

I can't access iCloud, i keep getting a message to try again later. This is the first time i have tried to log into icloud. I know my account is working, i want to access it from my macbook. I think its looking for my old icloud email, what to do? I have a working apple id, i dont understand, could it be linked to an old account iD?

Hi smccarrison,
Thanks for visiting Apple Support Communities.
You may find the steps in this article helpful with troubleshooting signing into iCloud:
iCloud: Account troubleshooting
http://support.apple.com/kb/TS3988
All the best,
Jeremy

Access Denied error message... I want to give alert message

I have Manager service in my portal page. But I don't have the content access from the back end system.
In the portal log viewer it is saying the Access Denied info. So i am getting the below error message in the portal page.
Instead of giving this error message I want to give a alert message like "You are not authorised to view this page...so please contact your Administrator"...
I want to know how to do this. can anyone help me on this
An exception occurred while processing a request for :
iView : pcd:portal_content/com.XYZ.roles.XYZ_Roles/com.XYZ.roles.Human_Resources/com.XYZ.roles.Manager/com.XYZ.hr.wks.se.
Manager_Services/com.XYZ.hr.wks.cl.Overview_MSS/com.XYZ.hr.wks.cl.Compensation_Management/com.XYZ.hr.wks.up.Position_Change_Process/com.XYZ.hr.pag.ac.Select_Team_Member_
and_Form_Pos_Chg/XYZTeamViewerTransfer
Component Name : com.XYZ.hr.pcr.transfer.XYZTeamViewerTransfer.XYZTeamViewerTransfer
The exception was logged. Inform your system administrator..
Exception id: 08:46_17/07/07_0505_24366050
See the details for the exception ID in the log file
Portal log**********
#1.5#000BCD4305DF0043000019C80000290400043574F8F3FA51#1184676416089#com.sap.security.core.util#sap.com/irj#com.sap.security.core.util.
[cf=com.sap.security.core.util.SecurityAudit][md=log(...)][cl=12778]#Guest#192####cd0d7490346311dc931d000bcd4305df#SAPEngine_Application_Thread[impl:3]
_24##0#0#Info##Plain###ObjectID handed over is 'null'!#
#1.5#000BCD4305DF0043000019CA0000290400043574F8F3FC42#1184676416089#com.sap.security.core.util.SecurityAudit#sap.com/irj
#com.sap.security.core.util.SecurityAudit#Guest#192####cd0d7490346311dc931d000bcd4305df#SAPEngine_Application_Thread[impl:3]
_24##0#0#Warning#1#/System/Security/Audit#Plain###Guest | LOGIN.ERROR | NONE = null | | Login Method=[default], UserID=[null], IP Address=[168.133.7.3], Reason=[Access Denied.]#
#1.5#000BCD4305DF0043000019CC0000290400043574F8F4A4CF#1184676416136#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#192
####cd0d7490346311dc931d000bcd4305df#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/System/Server#Java###Exception ID:08:46_17/07/07_0506_24366050
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is denied:
com.sap.portal.heartbeats.PortalHeartbeat - user: Guest
at
com.sapportals.portal.prt.deployment.DeploymentManager.checkPermissions(DeploymentManager.java:2005)at
com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:247)
at
com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at
com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at
com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
at
com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at
com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object:
com.sap.portal.system/security/sap.com/NetWeaver.Portal/high_safety/com.sap.portal.heartbeats/components/PortalHeartbeat)
at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:416)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1095)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1101)
at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1197)
at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1144)
at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:918)
at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)
at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sapportals.portal.prt.deployment.DeploymentManager.checkPermissions(DeploymentManager.java:2000)

Kindly post how u did it. It will be helpful for others.
Thanks in advance.
Pradeep.

In Message Monitoring Message showing holding status

Hi
Can anyone solve this problem.Its urgent for me.
My scenario is IDoc->XI->FILE
The file i am trying to generate is an xml file which i am dropping in XI application server using File system.
The problem is when i am going to see the message using transaction SXMB_MONI the perticular message interface is showing waiting for acknowladgement status .
But in message monitoring in runtime workbench the it is showing following status:
Adapter Engine
Holding
18.11.2005 05:42:09
CORP_SAP_DR2_030 http://limited.com/usa/sap_appl/retail/VendorsSAPAPOToMANU
MIIA_Create
BS_MANU
I am in SP14.
Also the output xml file is not getting created in the XI application server.
Please let me know the solution.
Thanks
Debraj Roy

Hi Debraj
HOLDING is a status which occurs normally for EOIO (Exactly Once In Order), so your message is set to Holding means some earlier message has not gone through. So until those messages are through this message will be in HOLDING state.
Have a look at this link which explains how to handle such scenarios.
http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm
cheers
Sameer
Assign points if it helped you

Want to access Status in Message Monitoring

Similar Messages

Maybe you are looking for