Cache-Connectivity-Test in RWB

Hello gurus,
when we are starting a Cache-Connectivity-Test in RWB what might be the error:
com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name,* is.73.10*, string], target element type: SAP_BusinessSystem)
We can also cannot see the Domain - see [screenshot|http://koekce.com/XI/domainxi.PNG]
Could someone help?
Best Regards,
FK

Hi,
Check these:
0) Go to RWB-->Cache Connectivity Test and check the status.. and run the refresh over there
1) execute SLDCHECK in XI box
2) Go to SXI_CACHE and refresh the cache also delete the Adapter metadata
3) Check the SAP BASIS SWCV is imported into IntegratioN Repository
4) Refersh the Adapter Metadata cache in SLD>Adminisration>Cache Overview ->Adapter Metadata Cache Refresh
this doc may help u :https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/08438c77-0501-0010-50a0-e39fe8fa0446
Hope it helps
Regards,
Surya

Similar Messages

Cache Connectivity Test in RWB fails

Hi Guys,
When I go to RWB in Cache Connectivity Test, I get the following error:
" Error during last test run executed by EGKATZIOS, on 10 u039Du03BFu03B5 2009 3:35:37 u03BCu03BC: Error executing testClientServerException exception:Communication with JMS server failed
com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed"
Any ideas ?
Also in IR, in Cache Notifications, remain in Red Status "Not Yet Started" and I have to manually Execute them.
Which I realized is related to an error I get when I activate the Change List in IR "Communication with JMS server failed Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service". However, activation works with a second attempt.
Everything else, SXI_CACHE, HTTP Connections, SLDCHECK, Service Users, HTTP and JMS services in VA work fine.

Hi,
Pls follow this path,
login to J2EE Visual aadmin>cluster>services.JMS connector>runtime(Righ hand side tab)->check the factories / destinations (if anything is in red color X mark).
Ask your basis admin to correct this.Final possible solution is to restart the server....
Hope dis will help.
Regds,
Pinangshuk.

PI : unable to connect to IR with cache connectivity test via RWB

Hi,
Please help to resolve the issues.
Server Details: SAP PI 7.0, SUNSOLARIS with DB2.
PI server was working fine without any issues for the past 2 weeks, Unfortunately issue is the connection failure.
PI services were unable to interlink internally.
cache connection Test Error Below:
Connection to system null using application null lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/conntest/int?" with user "PIRWBUSER". Response code is 404, response message is "Not Found"
SLDCHECK done with success,SPROXY no issues,
users are not locked & password not changed.
Thanks,
Bala

After full cache refresh. with SXI_CACHE i got cache error "UPDATE" detail error as below.
com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/hmi_service_swc_manager/int?container=any" with user "PIDIRUSER". Response code is 404, response message is "Not Found"
     at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doGet(HmisServletImpl.java:640)
     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.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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

RWB Component Monitoring - Cache Connectivity Test failure

Hi,
I have done the Cache Connectivity test in RWB-Component monitoring.
For the Integration Server - Integration Engine XYZ.
I am getting error
Result of Self-Test
   Can the SLD be reached?   ... Details OK
   Does the Integration Engine know the business system?   ... Details   OK
   Are roles in SXMS_CONF_ITEMS and SLD consistent?   ... Details Error
   Is Web service security available?   ... Details
The error message os
Details for 'Are roles in SXMS_CONF_ITEMS and SLD consistent?'
Inconsistent roles. System Landscape: Integration Server. SXMSGLOBAL: Application System
How to solve this issue.
Regards
Farhat

Hi
Use Tcode SXMB_ADM -> integration engine ,Assign proper Client to Integration Server.
look this similar thread
Are roles in SXMS_CONF_ITEMS and SLD consistent?

RWB - Cache Connectivity Test - Adapter Engine shows error

Hello Friends,
In our one production system (PI 7.1), while do 'Cache Connectivity Test' from RWB -> Component Monitoring, it shows the following error for Adapter Engine under Integration Directory.
Error:
Cache notification from Integration Directory failed Error when accessing the System Landscape Directory.
No SLD elements of type SAP_XIAdapterFramework found
But, Integration Server - ABAP, Integration Server - JAVA shows green color. The messages are flowing through the Adapter Engine fine. i.e I am seeing 2 Adapter Engines under Integration Server in Component Monitoring. One Adapter Engine is in grey and another Adapter Engine shows green color.
When I click the grey color adapter engine, it immediately turns to red color and some different host name url is displayed (http://<wronghost>:53000/AdapterFramework/rtc).
So, what could be the problem ?
Kindly clarify, friends.
Thanking you.
Kind regards,
Jegathees P.

Hello Jegathees
Apply the solution in note #804124 HTTP communication with XI Adapter Engine fails. Set the parameters:
SLD.selfregistration.hostName
SLD.selfregistration.httpPort
SLD.selfregistration.httspPort
as described in the note.
Regards
Mark

When i doing cache connectivity test , i am getting below error

When i doing cache connectivity test , i am getting below error, could you please suggest me what action need's to be done
Integration repository, Integration Directory,Integration server ABAP, Integration server java is green, only adapter engine is showing red.
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem
[Fetch Data]: com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:490)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
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.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:175)
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)
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem)
at com.sap.aii.ib.server.sldquery.SLDQuery.dammiIlMioCentralAdapterFramework(SLDQuery.java:70)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:191)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
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.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:175)
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)
[Data Evaluation]:

Check Surya's reply: Cache-Connectivity-Test in RWB
The same procedure in detail manner is given in this How-to guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34
Are you using any Business System? If yes then make sure that you have imported it properly into ID....in this case ID --> Environment --> Clear SLD Cache.
Regards,
Abhishek.

Cache Connectivity Test - RWB

Hello All,
In RWB - Cache Connectivity Test,
Integration Server - JAVA --> Green Status
Central Adapter Engine --> Green Status
But
Integration Sever - ABAP --> RED Status
Error is
http connection to "http://<HOST NAME>:50100/sap/xi/cache?sap-client=100" returns the status code "404" in response
Please can anybody provide suggestion as to why this error persists?
Regards,
Ramesh P

Hi! Ramesh,
Once do cache refesh and use this URL
http://host:port/CPACache/refresh?mode=full
I think you are unable to login right first ssign these roles and then try also please make sure whether you have done all cache refresh or not
J2ee ABAP
xi_af_cpa_monitor = SAP_XI_MONITOR_J2EE, SAP_XI_ADMINISTRATOR_J2EE, SAP_XI_CONFIGURATOR_J2EE, SAP_XI_DISPLAY_USER_J2EE
xi_af_cpa_invalidate = SAP_XI_ID_SERV_USER
okay
Thanks
Amar Srinivas Eli
Reward POints if useful

CPA Cache Connectivity test fails

Hi All,
We are facing the following issues that have to do with the Adapter Engine:
1) In RWB, the Adapter Engine is in error/red status with the following details: Adapter Engine, message: fatal DeleteJob (Default Delete Job) failed.
2) In RWB, the Cache Connectivity Test fails with the following error: Communication with JMS server failed.
3) The CPA Cache refresh gives erros.
Any ideas? There are no Service users locked, SLDCHECK works fine etc.

Hi,
It seems to like problem with your JMS Connector.
For this, login into Visual admin -->cluster >services>JMS connector-->runtime (tab)->check the factories / destinations. Please contact with your basis team, they will might be helpful to you. After that restart your server, it will solve your issue.
Regards,
P.Rajesh
Edited by: Rajesh_1113 on Jun 5, 2011 9:01 AM

Cache Connectivity Test fails for PI on MSCA

Hi all,
I experience the following problem with newly installed PI 7.0 SP12 system on MSCA.
When I go to RWB and press "Cache Connectivity Test" I got the following error for central adapter engine:
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.74.sapxi03, string], target element type: SAP_BusinessSystem)
Tx: SLDCHECK - reports no problems.
Tx:SLDAPICUST - is set to virtual host name and port.
Appreciate your help.

hi,
here u have to clear the delta cache in SXI_CACHE.
Open Tcode SXI_CACHE -
>from menu XI Runtime cache----->start Delta Cache Refresh(F6 or CNTRL + F6 )
reward points if helpful
regards
sreeni

Cache connectivity fails in RWB

Hi Experts,
I have a freshly installed and configured PI 7.0 system.
I tried to run a simple file to file scenario, but the input file was never picked up.
When I went to RWB and did a cache connectivity test I get the following error
Cache notification from Integration Directory failedError when accessing the System Landscape Directory
detailed error
No SLD elements of type SAP_XIAdapterFramework found
In communication channel monitoring, I dont see that communication channel at all...
I also see that in SLD -> TechSystem -> ExchangeInfrastructure
RWB and AdapterEgine are on domain abc.def and IR,ID and IS are on domain uvw.xyz
Is this an error??? how can we correct this?
I have already gone thru and applied note 764176
PLs help m eout
Regards,
Teja

Hello Siddesh,
That note helped, thank you, Im now able to see the adapter engine in RWB.
How ever when i do the cache connectivity test it says
No information available about cache notification from Integration Directory
Also in SLD->TechnicalSystems->ExchangeInfrastructure
AE -> Domain X
Domain X -> Domain X
Domain Y -> Domain Y
IR -> Domain Y
ID -> Domain Y
IS -> Domain Y
RWB -> Domain X
Is it because of this???
I have already applied note 764176...how can i correct it?
Regards,
Teja

Integration directory and cache connectivity test doesn't run correctly

Hi,
In a production system, I can't open any configuration object because of session hangs when i try to see a cc or a receiver determination or any other object.
Moreover, when i try to made a cache connectivity test, it holds and doesn't finish.
What could be the problem
thanks,
Carme.

>
Carme Alentorn Guasch wrote:
> Hi, Abhijit
>
> Testing INTEGRATION_DIRECTORY_HMI connection:
>
> ~response_line               HTTP/1.1 500 Internal Server Error
> ~server_protocol             HTTP/1.1
> ~status_code                 500
> ~status_reason               Internal Server Error
> connection                   close
>
> What does it means?
>
> Shabarish, it's not a problem of my desktop installation.... it's general
>
> thanks,
>
> Carme
confirm if XIISUSER/PIISUSER is locked.... this should be the user provided in that destination

Adapter Engine : Cache Connectivity Test

Hi,
We have recently migrated our PI system's database from one host to the other and as a result there were some duplicate entries for exchange infrastructure components in SLD.
At this besides other problems we have noticed the Adapter Cache Connectivity test is failing.
We have deleted these entries and check that all the required entries are there and they are correct.
After this we did the Adapter Engine Cache connectivity test it still failed. But after some time we noticed that the connectivty test is successfully happening without doing any changes.
We see green bulbs with cache notification from integration server received successfully and cache data fetched successfully and update.
We are just wondering how it happened ? appreciate if anybody can help us understand.
Thanks & regards
Mrutyunjay

hi,
check the below blog....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
check the point 4 (troubleshooting) in the above link
reward points if helpfull
regards
kummari

Cache Connectivity Test

Hi XI Guru's ,
Currently i am working on a scenario JDBC-RFC-JDBC scenario using a BPM.
Issues i am facing....
1. I have made the polling interval from source table to 10 secs, but i can see table is not getting polled in 10 secs.
2. On running Cache Connectivity Test I found that It is not working perfectly : as i can see yellow and red symbols frequently..
3. Sometimes when XI is able to pick the record it is throwing error in Mapping Runtime
"Runtime Exception during application Java mapping com/sap/xi/tf/_MM_REQ_"..
I checked n no of times in Test Mapping it is working fine...
Mapping is between Async Req Object with RFC's import parameters...on drilling down further i figured out that values are not getting passed to this RFC ...as when i passed the constant values to RFC it is working fine...
So i am not sure where the the problem ?
Currently i am working on PI 7.0 and SP 9.0 ...ans also we are not using FQDN now....

Hi ,
 1. I have made the polling interval from source table to 10 secs, but i can see table is not getting polled in 10 secs.
 Yes. It depends on load on XIServer vary .

3. Sometimes when XI is able to pick the record it is throwing error in Mapping Runtime "Runtime Exception during application Java mapping com/sap/xi/tf/_MM_REQ_"..
 Go to sxmb_moni , copy the payload . paste that in Mapping program of design part . Test it . There you can find error .
Assign points if you found helpful
Regards.,
V.Rangarajan

Cache Connectivity Test Issue..:-)

Hi XI Guru's ,
Currently i am working on a scenario JDBC-RFC-JDBC scenario using a BPM.
Issues i am facing....
1. I have made the polling interval from source table to 10 secs, but i can see table is not getting polled in 10 secs.
2. On running Cache Connectivity Test I found that It is not working perfectly : as i can see yellow and red symbols frequently..
3. Sometimes when XI is able to pick the record it is throwing error in Mapping Runtime
"Runtime Exception during application Java mapping com/sap/xi/tf/_MM_REQ_"..
I checked n no of times in Test Mapping it is working fine...
Mapping is between Async Req Object with RFC's import parameters...on drilling down further i figured out that values are not getting passed to this RFC ...as when i passed the constant values to RFC it is working fine...
So i am not sure where the the problem ?
Currently i am working on PI 7.0 and SP 9.0 ...ans also we are not using FQDN now....

Hi Santhosh ,

 on drilling down further i figured out that values are not getting passed to this RFC ...as when i passed the constant values to RFC it is working fine...
On passing the constant values in mapping to RFC the scenario is moving smoothly its only the record being picked by JDBC sender adapter not getting passed to RFC through BPM....
 Yes. You are having issue at Mapping (desing ) side . So, Even if your JDBC Sender picks up the data it won't send to RFC. Obsolutly, your constant value passed to RFC will woks fine .
 So, Have you tested like what i have suggested , like copying the Payload and test the mapping ?
 If you are getting the java.lang.NullPointerException . I am 100% sure your mapping is wrong . Please chek the MAPPING ONCE AGAING !
 Are you getting the Target message structure when you are passing the source etructure ? Executed successfully Message ?
 Please chek the Mapping once again . Test teh Interface Mapping too.
Assing points if you found helpful
Regards.,
V.Rangarajan

Adaptor engine is yellow in cache connectivity test

hi all,
in cache connectivity test the adaptor engine status is yellow.
how can i resolve this.
regards,
KRUSHI

Hi Krushi,
Yellow symbolizes that it is being refreshed or in process to update the cache data....please wait untill it changes to green..try to click on Refresh display button..to see the status of the cache data.
If it changes to red in colour then there is problem in cache connectivity...then u have to do CPA cache refresh...
Regards,
Prasanthi.

Cache-Connectivity-Test in RWB

Similar Messages

Maybe you are looking for