Multiple message resend in Runtime workbench

hello experts,
Right now i m facing some problem to resend multiple messages at a time in the Runtime workbench.
If i get too many error message in Runtime workbench -> message monitoring then will anybody tell me that how i can send them at a time?
Please help me out in this case... because it is very difficult for my client to send messages one by one....
Thank you very much.
Regards,
Chaitanya.....

Hey experts,
Thanx for quick replies... but the matter is i m getting error in data... so i will not be able to get that message in error into the SXMB_MONI.
Suppose i have 2 scenarios... 1 related to invoice and 1 related to orders... now the situation is like if order will be present into my receiver system then only it will accept invoice otherwise my invoice message will go into the error... this error i will get into the RWB only.
so suppose first my invoice message come and it went into the error in RWB... and then order message went into the receiver... so now without change i can resend the message and it will give into the reciever system.....
so if i have nearly 50-60 msg in error then if i want to resend it once how i can do?
Hey i hv already tried that multiple selection option but it is allowing me to select multiple messages but it is sending only one message at a time...
So number of times i have to press resend button.... so please tell me if any other settings are required....
Thanks in advance...
Regards,
Chaitanya.............

Similar Messages

Messages on Holding at Message Monitoring under Runtime Workbench

Hello Colleagues,
we have currently the problem that a lot of messages for some interfaces are in status Holding under Message Monitoring at Runtime Workbench for PI 7.1.
I'm not able to resend the messages with status Holding as well as change status to cancel.
Quality of Service for the Interfaces are Exactly Once in Order.
I assume an error message blocks the queue and due to the fact we have Exactly Once in Order configured all following messages be in status Holding.
Is my assumption right?
But, I am not abel to find any messages in status error with blocks the queue!
How can I solve that issue?
Many thanks in advance!
Jochen

I assume an error message blocks the queue and due to the fact we have Exactly Once in Order
configured all following messages be in status Holding.
AE should have least number of EOIO messages at a given instance...otherwise Holding is what you get.....and holding is common with EOIO....so see if you can chagne the QoS of some messages to EO
But, I am not abel to find any messages in status error with blocks the queue!
Never you will get an error in SXMB_MONI....or the queue blocked....
When your message goes out of IE...the corresposding message entry is marked with chequered flag...observe in MONI you will see this....however in AE the message can fail if not able to send to the target system....
For some more understanding refer my answer in this thread:
Re: Restarting Error's in SXMB_MONI
Regards,
Abhishek.

"Error in message monitoring in runtime workbench"

Hello All,
I have an error in message monitoring in runtime workbench.
We have installed PI7.0 and it should run on port 50000.But it is running on port 50100.
Please suggest what are the steps involved to resolve this problem.
Thanks and Regards
SAN
null
k san

San,
Can you please copy / paste error message.
Also check if you have set correct port in Exchange profile under Runtimeworkbench.
Nilesh

Any docs or info on runtime workbench

Can anyone provide some docs or helpful info about runtime workbench?
I have seen a button "resend" in Message Monitoring of runtime workbench. what does it function? any more infomation?
Message was edited by: Spring Tang
add button "resend"
Message was edited by: Spring Tang
Message was edited by: Spring Tang

Hi Spring,
You can see your message at any stage in XI. This can be viewed with the help of Runtime WorkBench(RWB). A few options available in the Runtime Workbench are:
1. ADAPTER MONITORING This allows you to trace out the errors and problems occuring in your Adapters running on the j2ee engine.
2. END to END Monitoring This is similar to your SXMB_MONI and allows you to monitor the entire message flow.
3. PERFORMANCE MONITORING This is used to monitor the performance of your entire XI server.
Also, go through these links for further info,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cbc7d790-0201-0010-bea6-c549902e93e2
http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/96/0a2441509fa831e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/25/9c2f3ffed33d67e10000000a114084/content.htm
Hope this helps.
Regards,
abhy

Testing or postingmultiple messages in runtime workbench

Hi,
I want to know if there is any shortcut to automatically post multiple messages say around 130 in runtime workbench at a time without clicking send message button for each message?
let me know if any tools are available
With Regards,
Deepika.

Hi,
I am assuming you are talking about sending new messages to XI system for testing.
- You can create sender file channel in test mode and it will keep sending messages to XI system and dump all type of messages in this folder for load testing.
- You can use SOAP UI (search google for free SOAP UI), various UI tools support multiple sending for messages in one go for testing.
Regards,
Gourav

SOAP Adapter + asynchronous message + Runtime Workbench

Hi
I have problem with error monitoring in Runtime Workbench -> Message Monitoring
I have SOAP adapter deployed on Apache Axis.
I have flow SOAP->XI->SOAP (asynchronous mode)
It works great until receiver adapter generate error.
I can see error message in defaultTrace log but in
Message Monitoring-> Details I see only "SOAP: response message
contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault".
SOAP message from receiver adapter (with error) looks like that
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
 <soapenv:Fault>
 <faultcode>Client</faultcode>
 <faultstring>Internal Server Error</faultstring>
 <detail>
 <myfaultmessage>
 <type>RABAX_STATE</type>
 <message>Divide by 0 (type 1).</message>
 </myfaultmessage>
 <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">pslupkowski</ns1:hostname>
 </detail>
 </soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
I'm think that this message is not well formated and
Adapter Engine can't find some tags during parsing this
message. Any ideas how to solve this problem?
I'm just want to see error description from <myfaultmessage> tag in Message Monitoring

Hi,
Did you check the log on adapter engine?
http://<host>:<port>/MessagingSystem/monitor/monitor.jsp
Take a look to this monitor, here you can see both messages (request and response).
Cheers,
Ricardo.

Messages are on HOLD in runtime workbench

Hi All,
I need your help. I don't know how to solve the following problem.
We have a message (idoc xml with a standard business document header from a gs1 xml) which will be send from a logical system in XI to another logical system in xi (same system).
The mapping is from one message - to more messages. This means one message comes in and dependent from the message two different message types could be go out (only one at one time). If the mapping is to one of these interface then it is also possible that one incoming message can create two or more output messages (same message type). And with this I have the problem. If more then one message is created in this mapping then this messages stay on hold in the runtime workbench. (If only one message is created, it is working fine). The QoS is for the messages "Exactly Once In Order" - thats what I see in the runtime workbench. The QoS in the sender communication channel is "Exactly Once".
Do you have any idea?
Thanks and regards
Manuela

Hi Mathias,
thats the information in the rwb:
Attribute     Value
Status     Holding
Repeatable     Yes
Cancelable     Yes
Error Category
Error Code
Start     07.02.2008 10:46:59
End
Sender Party
Sender Service     EU_GBO
Receiver Party
Receiver Service     EU_GBO
Interface     http://unilever.com/Xproc/ProcComm/GS1/ItmDtaNot/xi
Align_Item_Data_Notification_V2_1_ABS
Quality of Service     Exactly Once in Order
Message     47aa17db-8e63-0158-0000-000091374080
Reference
Conversation ID     MMFSERIALIZE0018
Version     0
Edited     No
Serialization Context     INBOUND_MMFSERIALIZE0018__
Direction     INBOUND
Message Type     Recv
Profile     XI
Connection     SOAP_http://sap.com/xi/XI/System
Transport     HTTP
End Point     http://ex1c002a:58300/MessagingSystem/receive/AFW/XI
Authorization
Sequential Number     105
Number of Retries     3
Failed     0
Retries     300000
Valid to
Persist Until     14.02.2008 10:46:59
Schedule Time     07.02.2008 10:46:59
2008-02-07 10:46:59     Success     Processing child message of multi-message with message ID 47aa0c4f-ce91-0122-0000-000091374080
2008-02-07 10:46:59     Success     Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-02-07 10:46:59     Success     Message successfully put into the queue.
2008-02-07 10:46:59     Success     The message was successfully retrieved from the receive queue.
2008-02-07 10:46:59     Success     The message status set to HOLD.
MMh external I think is not possible. Because it comes from a logical system in XI and goes from a logical system to XI. But on step before it comes from a SAP system. COuld it be there?
REgards
Manuela

Service user XIISUSER locked when resending multiple messages

Hi All,
Scenario: Idoc to 2 file receiver (1 defined as a Business Service). We notice that occasionally when we send multiple idocs from R/3 or when we restart multiple messages from the same scenario, we will get a HTTP 401 error and will find our service user XIISUSER locked.
i.Has anyone come across anything like this before?
ii. In receiver determination, the "Terminate message processing with Error(Restart Possible) radio button is chosen. Out of interest, what kind of error does this give if either 1 or the receivers cannot be found during runtime?

Basically the error will be HTTP 401 Unauthorized and we will find XIISUSER locked. This usually happens when we send multiple idocs for the scenario or when we restart multiple messages that belongs to the scenario. By multiple i mean 5-10 messages and not a really big number.
Once the XIISUSER is unlocked, I can just restart the message and it will be processed successfully. What I would like to know is what is causing the XIISUSER to be locked in the first place. can this be caused by the branching of the messages?

Soap-xml messages in runtime workbench monitoring?

soap-xml messages in runtime workbench monitoring? how u montor soap xml message in runtime workbench... thanq/../

All the messages in the RWB are monitored by only one way.
Select the Message montioring and select the filter criterias. like interface name and namespace and all and u can monitor the same.
regards,
Vishal

Unable to send a test message (XML file) at the runtime workbench..

Hi,
we are not able to send a test message (XML file) at the runtime workbench just to test Idoc's. From the component monitoring, under the integration engine, test message- i have given all the parameters like sender and receiver service, interface namespace with the user id and password details. when i say send message it is throwing error while sending. not even displaying any error to attach here. I beleive it is a configuration problem in the integration directory. what do you reckon guys?
OS- win 2003 DB-Oracle 10.2.0.4
SAP PI 2004s basis SPS 18
Appreciate your much needed help!
Thx
Sree

It is a sender Idoc. we are using sender agreement and comm channel.
Why are you using a channel and agreement for IDOC....we dont need it when IDOC is sender!
All the channels and agreements (if created) are in XI/ PI and we can delete them if they are not required
Edited by: abhishek salvi on Mar 11, 2010 11:49 AM

Resend AS2 messages from the Seeburger Workbench

Hello,
We have a EDI integration scenario where we are sending an asynchronous AS2 message via the Seeburger EDI adapter. As part of sending the message, we also request a synchronous MDN.
In cases where we have successfully sent the message but not received an MDN back (due to an error in the target system), is it possible to resend the original message from the Seeburger Workbench?
Thanks
Manish

Hi,
no it's not possible. The adapter will try to re-send the message a couple of times and then will mark the message as failed.
I think you can re-send it from RWB if you have the right authorizations.
Horia

In Runtime Workbench the messages fails with the error

Hi,
Os : Sun Solaris
Database: oracle
Sap: XI 7.0
In Runtime Workbench the messages fails with the following error:
2007-09-28 15:46:38 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
system messages fails with following Error Message:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 503 with the description Service Unavailable Error while sending by HTTP (error code: 503, error text: Service Unavailable)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Appreciate the response.
Thanks,
Sri.

Hi,
1)Check your J2EEs server is up
2)Check the adapter engine/status in RWB
The might help
1) 503 service unavailable
2) Note-803145
Regards
Agasthuri Doss

Unknown Erro while sending atest message through Runtime Workbench

Hi,
SInce none of my interfaces are running or generating any message, i tried sending the test message from Runtime Workbench.
And I am getting following message
Error when sending message: 403 Forbidden
What could be the reason for this message, is there any authorisation issue.
Regards
Ria
Message was edited by: ria sen

Hi ria,
Refer these threads they might be useful :
403 ERROR
HTTP 403 using the AdapterFramework
Regards
Suraj

Log on to Runtime Workbench : click display error on page

Dear all,
when i try to log on to Runtime Workbench and click on display message , i am getting error that error on page,
we have already done post implementation steps for PI(XI),,
what to do, to test the senario from Runtime Workbench.
Best regards,
dushyant.

Hi,
This will help you
SAP Note-768456 & SAP Note-928862
http://help.sap.com/saphelp_nw2004s/helpdata/en/06/5d1741b393f26fe10000000a1550b0/content.htm
Regards
Agasthuri Doss

Problem with Runtime Workbench and with sending data from XI to SLD

Hello 
 
Could I have a little help, a hint in the two following topics: 
 
1. I run Runtime Workbench -> Component Monitoring -> Display All and I get this error: 
 
Error during communication with System Landscape Directory: User credentials are invalid or user is denied access 
 
In filesystem log I can find like this: 
 
XIRWB.com.sap.aii.mdt.frames.jsp_error [SAPEngine_Application_Thread[impl:3]_40] Fatal: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access 
Thrown: 
MESSAGE ID: com.sap.aii.rwb.agent.server.rb_LCRAgent.landscapeCommunicationError 
com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access
 at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:773)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
 at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getXIDomain(SLDAgentObjectImpl0_0.java:375)
 at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
 at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
 at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
 at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
 at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117) 
 at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
 at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
 at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at jsp_FC_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.java:24)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 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(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
Root cause: 
com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access 
 at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577)
 at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341)
 at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:280)
 at com.sap.lcr.api.cimclient.CIMOMClient.performBatchOperation(CIMOMClient.java:1251)
 at com.sap.lcr.api.cimclient.CIMClient.performBatchOperation(CIMClient.java:2268)
 at com.sap.aii.utilxi.sld.MRSldProxy.stage1(MRSldProxy.java:989)
 at com.sap.aii.utilxi.sld.MRSldProxy.loadComponents(MRSldProxy.java:918)
 at com.sap.aii.utilxi.sld.MRSldProxy.loadSld(MRSldProxy.java:907)
 at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:373)
 at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:434)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:764)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
 at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getXIDomain(SLDAgentObjectImpl0_0.java:375)
 at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
 at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
 at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
 at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
 at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117)
 at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
 at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
 at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at jsp_FC_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.java:24)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 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(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 
 
 
I don't know what is wrong. 
I have configured: 
- SLDCHECK work properly, 
- none of the users PI* type not lock, 
- password to the PI* users in exchangeProfile entered correctly, 
- In VA in the JCo RFC Provider I have properly configure: AI_RUNTIME_JCOSERVER, LCRSAPRFC, SAPSLDAPI_SID - from the ABAP I can connect to this programs ID 
- In VA in SLD Data Supplier I have properly configure bookmarks HTTP Settings and CIM Client Generation Settings. CIMClient Test is OK 
 
I do not know what else I can see, what else I have properly configured ... I looked at the notes:: 936093 jak i 721548... 
 
 
2. I can't send data from XI to SLD, ie makes me a system definition in Web As Abap and Web as Java but nothing appear to me in Exchange Infrastructure. Exchange Infrastructure is empty - what is wrong?? 
I carried out the recommendation by 764176 and 1031321 notes 
 
I restart below applications (no effect)... 
com.sap.xi.directory (Integration Builder/Configuration) 
com.sap.aii.af.app (Adapter Engine) 
com.sap.xi.rwb (Runtime Workbench) 
com.sap.xi.repository (Integration Builder/Design) 
 
Can I ask for help and guidance in these topics? 
 
Regards 
RP 

I increased logging in the NWA (Configuration -> Log Configuration) - and increased the some things here to log ALL. So that from the NWA (Monitoring -> Logs and Traces) I see a little more information (but does not follow that with which the user is a problem). 
 
Here are some interesting logs ... 
I was most rash or irritation of those that say about the lack of credentials u2013 I must use Viusal Administrator and set good service ... 
 
What do I have done: 
In the Visual Administrator -> Cluster -> Server -> Services -> SLD Data Supplier 
I have set in the HTTP Settings tab the host and port SLD, the user name and password is also entered as it is in the SLD. To be sure, already have set for the user entered here such roles as: 
SAP_SLD_ADMINISTRATOR 
SAP_SLD_CONFIGURATOR 
SAP_SLD_DEVELOPER 
SAP_SLD_GUEST 
SAP_SLD_ORGANIZER 
Maybe we are talking in this place about a different user? 
 
Similarly, when it comes to tab CIM Client Generation Settings - here's all the same thing done. CIMClient test shows that everything is OK. 
When I click the button: This trigger the transfer of data to the SLD gets the message that everything was shipped correctly. Indeed, I received an instance of JAVA in SLD 
Also clicked on this icon: Assign application roles to user group - got information that everything is attached properly. 
 
By ABAP side, the connections: INTEGRATION_DIRECTORY_HMI, SAPSLDAPI, LCRSAPRFC, AI_RUNTIME_JCOSERVER and AI_DIRECTORY_JCOSERVER work correctly, ie I can perform the test - which means that programs ID are properly positioned in JCO Provider in VA. 
 
Puzzling is this message: 
The SLD data is inconsistent. 
 
Strange also that the message (from the ABAP everything is available in SMGW no errors): 
Connect to SAP gateway failed 
 
And what is this error: 
 
could not sync ExchangeProfile: 
Thrown: 
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
 
Below is a list of some interesting logs ... 
 
########### 
 
Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'. 
 
############# 
 
SLD is not accessible. Check SLD Data Supplier service settings. 
 
########### 
 
"Warning","2012-02-22","07:53:50:986","Data get on com.sap.sldserv.data.GetSAPBCCentralServiceInstance class processing failed. htThe SLD data is inconsistent. This is an internal processing problem.","/System/Server/SLDService","com.sap.sldserv.DataCollector","n/a","saptest2","Server 0 60_36694", 
 
######### 
 
com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access 
 
################ 
 
Full Message Text
CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://saptest2.unx.era.pl:56000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xit.saptest2), due to: HTTP 503: Service Unavailable
 
################## 
 
Full Message Text 
 
could not sync ExchangeProfile: 
Thrown: 
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457) 
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015) 
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238) 
at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101) 
at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1288) 
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:195) 
at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177) 
at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165) 
at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:582) 
at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43) 
at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52) 
at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167) 
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) 
at java.security.AccessController.doPrivileged(AccessController.java:219) 
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
 
############## 
 
Full Message Text 
 
Import of software component version list from component repository failed 
Thrown: 
com.sap.lcr.api.cimclient.LcrException: User credentials are invalid or user is denied access 
at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577) 
at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341) 
at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:198) 
at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:146) 
at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstancesImpl(CIMOMClient.java:443) 
at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstances(CIMOMClient.java:747) 
at com.sap.lcr.api.cimclient.CIMClient.enumerateInstances(CIMClient.java:980) 
at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.enumerateInstances(JavaCIMObjectAccessor.java:211) 
at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateInstances(SAP_SoftwareComponentAccessor.java:204) 
at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateSAP_SoftwareComponentInstances(SAP_SoftwareComponentAccessor.java:239) 
at com.sap.aii.ibrep.server.sldaccess.interfaces.CRAccess.getSwcLinks(CRAccess.java:82) 
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.getEoLinks(SwcAccessor.java:59) 
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.getEoLinks(EOAServiceImpl.java:75) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.getEoLinks(EOAServiceBean.java:66) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.getEoLinks(EOAServiceRemoteObjectImpl1_0.java:527) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:232) 
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) 
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) 
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) 
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(AccessController.java:219) 
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
 
############## 
 
Full Message Text 
 
An exception was thrown in the UME/ABAP user management connector. Message: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=localhost SYSNR=60 GWHOST=localhost GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner '127.0.0.1:sapgw60' not reached 
TIME Thu Feb 23 07:28:06 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 16

Multiple message resend in Runtime workbench

Similar Messages

Maybe you are looking for