Problem with adapters

[Former Member]

Hello all,

I have installed PI7.0 Server newely. I created sample scenario file to file in that PI7.0 Server. Messages are Picking by Sender Adapter but when i am checking in SXMB_MONI there are No messages. I also checked in AdapterMonitoring Under Runtime Work Bench. In Adapter Monitoring Sendar and Receiver Adapter are not displaying. Can any body suggest me how to solve.

Thanks

San

[Former Member]

Hi San,

check wheather u have given correct source/target directory name while configuring the adapters .

2)In Adapter Monitoring Sendar and Receiver Adapter are not displaying......?

check if there are some error during mapping in IR .and in RWB ...

check the status of the sender adapter first if its green in color then ur file-sender-adapter is working fine ....and in the same way check for recevier adapter ......if both are green the the status of the adapter is fine and working

Regards

Azeez khan.

[Former Member]

Hi,

There can be some error when you were configuring the sender communication channel.For the sole purpose of testing just try sending the file through the integration engine.

initially i had also faced such errors.

If your file is in the ftp server make sure your file is being picked up.Put the delete mode in the sender communication channel. This will help confirm your file is being picked up.Please also check if the configuration of your ftp server is perfect and that there is no ambiguity in the login requirements.

Thanks,

Sidhvin

[Former Member]

file adapter is now part of communication channel monitoring in RWB,check the sender file adapter over there

Thanx

Aamir

[Former Member]

I checked communication channel monitoring, I got the following error.

com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].

Stack trace for the above error message is:

com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:328)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at jsp_FC_Secure1198091442671._jspService(jsp_FC_Secure1198091442671.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: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:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.lang.NullPointerException

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doProcessAfterInput(CmDynPage.java:61)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:101)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

... 20 more

[Former Member]

check SAP Note 764176

Thanx

Aamir

[Former Member]

Hello All,

The messages are picked by Sendar Communication Channel. In SXMB_MONI the messages are in schedule for outbound processing status. How to resolve this.

Thanks

San

[VijayKonam]

Click on the QID column in SXMB_MONI for this msg. Check if the Q is blocked for any reason.. if it is dev system, delete the top message that is blocking the Q. Alternatively you can do this from the transaction SMQ2.

VJ

[Former Member]

Hi,

You can process these message by selcting message and on clicking "Restart" button.

If message come up that message is already scheduled then goto smq2 and click on blocked queue and process first message which blocked the queue, if error is genuine and can't be processed and QoS is EO then delete LUW and then try to process message again.

Regards,

Gourav

---

reward points if it helps u

[Former Member]

Hi,

You can reprocess message by clicking on "Restart" button, if it says tht message is already scheduled then goto SMQ2 and process first message in queue.

If Qos is EO then u can also delete first message from queue by "Delete LUW" option of right click.

after that unlock queue and it will process.

Regards,

Gourav

---

reward points if it helps you

[agasthuri_doss]

Hi,

>schedule for outbound processing status

Try Restarting the message still if you face the issue as Experts mentioned Delete the Queue .

Regards

Sangeetha