Integration Directory - Cache Notifications

I just installed QA box. I am trying to move my Integration Directory objects. When I do cache notifications in ID I get an error in the cache notifications Integration Server (ABAP Cache).
Any help is appreciated.

Hi Michael,
What type of error are you getting ?
Anyway if you did not go thru this document, then please have a look into this-
https://websmp101.sap-ag.de/~sapidb/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Hope this helps,
Regards,
Moorthy

Similar Messages

  • Integration Directory - Cache Notifications Error!!

    Hi ,
    When i try to select "Cache Notifications" in directory i am facing this error below.
    <b>Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server></b>
    I can see in SLD -> technical system -> exchange infrastructure, the entry for Integration Directory is missing. I ve applied note 764176 , but it is not helping. Similarly the entry for RWB is also missing here.
    ve checked in SLD -> Admin -> Content Manitenance and the assocations are missing for IR & RWB. I beleive these errors are closely related. ve chked exchange profile XIDIRUSER & XIRWBUSER pwds , chked the roles , they are the same as our DEV / QA envionments.
    Can anyone pls point what am i missing here
    Thanks
    Saravana

    Hi Saravana,
    About the roles for XIRWBUSER...you can check the same in the ABAP stack...go to transaction SU01 and check the Roles attached...it should have the following entries...
    SAP_SLD_CONFIGURATOR
    SAP_XI_RWB_SERV_USER
    SAP_XI_RWB_SERV_USER_MAIN
    These should be sufficient as it is working for us...also...the roles gets passed along from the abap stack to the J2ee stack....
    Now to your original issue...we had to change our sld in our system to a new box and had to re-configure....we got the same error that you were getting...
    we corrected it by doing the following...
    Corrected the entries in the Visual Admin under SLD data supplier service... for the HTTP tab as well as the CIM tab.
    Did the SLDCHECK(TCODE on abap stack) and made sure everything was ok....
    Did a CPACache refresh full...and of course a restart....
    that solved the issue for us...
    Thanks,
    Renjith

  • Integration Directory, Cache Notifications with error

    Guys,
    In Integration Directory, I create one Comunication Channel, but, when i actived one, it dosnt appears in RWB Comunication Channel Monitoring.
    In Integration Directory -> Environment -> Cache Notifications, show the following error:
    Integration Server (Central Adapter Engine) | Directory Change List | pisuper | Standard Change List
    With "Standard Change List" as: Not Yet Started
    Details: Never change Status.
    Can anybody help me?

    Also check in SLD technical system for Exchange Infraustructure.
    Check weather Adapter enginer is registered or not.
    Your XI domain should contains 6 entries
    1.Adapter engine
    2.Domain
    3.Integration Directory
    4.Integration Repository
    5.Integration Server
    6.RWB

  • SXI_CACHE - Integration Directory Cache problem

    hi
    im getting this on 001 but not xxx client.
    I id post installation also. i switch client 001 to another.
    while SXI_CACHE - Integration Directory Cache TC i can't see cache also manu option that adpter engine.
    Thanks
    Sachin

    Check if the right client has been identifies as integration server in SLD and check right URL has been mentioned in SXMB_ADM.
    VJ

  • Cache Notifications Error in Integration Directory

    Hello,
    I'm having an interesting problem at my client's PI 7.0 system. When I update my changelist, I can see problems in Integration Directory - cache notifications. Integration Builder works fine. When I retry the cache refresh manually, I turns to green.
    But, Communication Channels with adapter type XI are not created even when I activate my changelist and manually fix the cache refresh if there are errors. All other adapters can be seen in Component Monitoring - Adapter Engine - CC Monitoring, but XI type adapters are not there.
    How can we resolve this problem?
    Thank you,
    Gökhan

    Hi,
    Check all steps in this doc (Especially from Page 20 to 24): [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34]
    Thanks,
    - Gujjeti.

  • Error in Directory Cache Update

    Hi,
    because we changed from two SLDs (PROD & DEV) to one (DEV) we did all changes like given in note 720717.
    Everything seems to run fine except the Adapter Engine - ok parts of it.
    When checking the Cache-Infos in Integration Directory we get following error in Integration Server (Central Adapter Engine). What do we need to do?!
    br
    com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.px1.sapru03, string], target element type: SAP_XIIntegrationServer)
         at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:483)
         at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:154)
         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.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:259)
         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: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(AccessController.java:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Hi,
    Hereu2019s a list of common errors/problems in SAP XI and their possible resolutions. This Guide will help you troubleshoot your integration scenarios in SAP XI/PI. This is in no way an exhaustive list. You can add your points/ideas to this list. Please feel free to post your inputs using the comments form at the end of this article.
    Cache Update Problems
    Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
    For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full
    For delta cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta
    If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
    Now in the Integration Repository go to Environment u2192 Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment u2192 Clear SLD Data Cache.
    Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
    If you are facing cache update problems in your BPM (say you have modified the BPM, but when executed old version of the BPM is picked up instead of the new one), run the transaction SWF_XI_CUSTOMIZING and press F9 carry out automatic BPM/Workflow Customizing.
    Routing Errors
    NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
    This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
    TOO_MANY_RECEIVERS_CASE_BE
    More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
    Mapping Errors
    JCO_COMMUNICATION_FAILURE
    Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
    NO_MAPPINGPROGRAM_FOUND
    Ensure that mapping program exists and is activated. If it exists then update the cache.
    EXCEPTION_DURING_EXECUTE
    This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
    Messages stuck in queues
    Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
    Conversion Errors
    Unable to convert the sender service XXXX to an ALE logical system
    This error occurs in case of scenarios with IDoc adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
    Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service u2192 Adapter Specific Identifiers. Click the button that says u2018Compare with System Landscape Directoryu2019 and chose Apply. Save and activate your change list.
    In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP systemu2019s partner profiles.
    Errors on the outbound side
    Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the outbound side. It may not be possible to restart them from using RWB or the transactions like SXI_MONITOR/SXMB_MONI. In such cases, you can follow the procedure outlined in the following article - Dealing with errors on the outbound side.
    Refer this article:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/content.htm
    Refer this portal
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/pointers%2bfor%2btroubleshooting%2bportal%2bruntime%2berrors
    Regards,
    Suryanarayana

  • Integration Builder Directory cache access problem

    Hi All, 
    I am learning SAP XI. I am trying to follow the example explained at https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1312. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] I did al the steps in the Integration Builder Repository. Then I opened the Integration Builder Directory to continue with the next steps.
    in the Cache Notifications Panel I get some errors, all of the same kind:
        Unable to notify integration runtime (ABAP) of data changes
    http connection to "http://p4p800d-6:8000/sap/xi/cache?sap-client=000" returns the status code "403" in response
    Am I doing something wrong?
    Thanks
    Juan Manuel

    The Java Web Start cannot accept unsigned jars. If the jars are signed, it will ask in a dialog box if it should allow unrestricted access to this jar.
    In my case, I upgraded XI SP0 to SP4, which included updating the Adapter Core, Adapter Framework, and the XI TOOLS to SP4.
    On launching the Web start, it seemed that the jars were not getting signed. JWS cannot allow unsigned jars to the client.
    These jars are maintained in:
    \usr\sap\<SID>\SYS\global\xi\directory_server\javaws\directory
    I am having problems with my XI upgrade to SP4, and it is probably not signing the jars.
    Do you know why this may be happening ...
    thanks,
    Manish

  • Attempt to fetch cache data from Integration Directory failed

    HI,
    while checking cache connectivity testing: status is
         green:   Integration Repository     
         green:    Integration Directory     
              green: Integration Server - JAVA     
                  red:Adapter Engine af.axd.aipid     
               yello:Integration Server - ABAP
    Jun 30, 2007 1:16:08 PM - Cache notification from Integration Directory received successfully
    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.00.aipid, string], target element type: SAP_BusinessSystem)
    [Data Evaluation]: GlobalError
    what to do?
    and there is nothing under integration server and integration engine but there is an green status under Non-Central Adapter Engines > from this i am doing send messeage testing fro xi to bi ,
    send message to: http://aibid:8000/sap/xi/engine?type=entry
    payload:
    <?xml version="1.0" encoding="utf-8"?>
    <ns1:MI_VCNdatatoBI
    xmlns:ns1="http://bi.sap.com"
    xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance">
    <DATA>
    <item>
    </BIC/ZG_CWW010>1000<//BIC/ZG_CWW010>
    </BIC/ZVKY_CHK>1<//BIC/ZVKY_CHK>
    </item>
    </DATA>
    </ns1:MI_VCNdatatoBI>
    i can sent message from there (component monitoring > Non-Central Adapter Engines) but unable to get it at message monitoring and at BI side.
    dushyant.

    thanks,
    but i have adepter type XI
    and i am folowing step of this lonk and there is no need to create fild adepter type according to that and almost done but while sending message through config. monitor in RWB it goes but not coming in mess monitoring and at bi side
    see 4.5 > 3 and 4 topic and 4.6 > 3,4,5
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f027dde5-e16e-2910-97a4-f231046429f2
    now what to do?
    dushyant,

  • Adapter Status Grey and Cache Error in acessing Integration Directory

    Dear All
    While going through the following path
    RWB-->Component Monitoring->Adapter Engine->Cache Connectivity Test
    i got the following result
    " Cache notification from Integration Repository failedError when accessing the Integration Directory "
    RWB-->Component Monitoring->Adapter Engine->Adapter Monitoring
    I am able to see the list of all adapters but all the adapters have Gery light status instead of having a red or green light status
    Kindly tell me what to do...how to change the grey light status to green light and how to set the Cache right
    and going by the following path
    Thanks in anticipation
    Chakra and Somnath

    Hi Somnath,
    Check out this link for cache Connectivity:
    How To handle Caches in SAP XI 3.0
    https://websmp206.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
    Cheers,
    Vijay Raheja

  • No value mapping in Integration Directory, but they are in the cache

    Hi,
    I recently got acquainted with the fabulous world of value mappings in PI. Until now, FixValues did the trick for me, but now I have to modify the errors in someone else's work.
    I read this article:
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00ee347e-aabb-2a10-b298-d15a1ebf43c5&overridelayout=true
    and a bunch of other help.sap.com stuff and I still don't get a very specific thing in our system. When I check the cache from the runtime workbench, the values, agencies and what have you are all ok. However, when I go to Integration Directory, disregarding the fact that I don't have any values on the search helps for Agency and Scheme, which is quite weird, when I put the correct Agencies and Schemes, I don't get any value displayed, just blanks.
    Why does this happen? Is it something wrong in the PI configuration or something that I don't see any value mapping there, altough they are in the cache?
    Thanks in advance and best regards,
    George

    Hi ,
    1. Create Value Mapping directly in ID (this cannot be seen in RWB, it can be only seen in ID)  
        *Just a corection we can see the value mappings created in Integration directory in RWB in cache monitoring.*
    Just follow these steps to refresh your cache. you will no longer be able to see deleted Val mappings and newly created entries will also shown immediately.
    1) Go to integration builder -- > Administration  --> click on Runtime tab --> cache overview
    You will find 2 things over there :
    Value Mapping Group Cache
    Value Mapping Value Cache
    Refresh both of them. I hope it will work as it always work for me :).
    Thanks
    Inder

  • Integration Builder (Design) - Cache notification

    Friends,
    When we save the objects in Design (Integration Builder), the objects goes to status "Notification Not Yet Started" or "Red" in the cache notification screen. The developer has to manually execute the repeat cache notification to make it successful. Is there any settings or configuration missing? can you please guide me?
    Thanks,
    Peter

    Hi,
    Since your cache in getting update automatically, therefore you should check the RFC in SM59 as mentioned in this document.
    First check this one...
    http://help.sap.com/saphelp_nw04s/helpdata/en/8f/770f41218ff023e10000000a155106/content.htm
    Also go through this thread:
    Cache Error
    Regards,
    Sarvesh

  • Cache update problem in Integration Directory

    Hi all,
    We have a cache update problem in our PI development server.
    If we try to edit, save and activate any of the ID objects, under Cache notifications>Central Adapter Engine> all these objects are displayed as gray items.
    We have tried:
    1. Clearing the SLD Data Cache.
    2. Did SXI_CACHE complete refresh.
    3. Did CPA cache refresh.
    4. Did a complete cache refresh of the server.
    5. Restarted the server.
    But still the problem has not bee resolved. Could you pls provide your inputs and resolution points.
    Thank you very much.
    regards,
    Jack Nuson

    HI Jack ,
    first try to manually update the cache from ID select on your cache notifiaction and click on delta cache refresh button and refresh button .IF it does not yied any result then
    Perform a full cache refresh using the URL
    http://<host>:<port>/CPACache/refresh?mode=full . If the cache refresh happens properly then your problem will get resolved other wise you have to see the cache log to view why it failed there it will show you the exact reason . You might need to restart your java server also if the problem persist .
    Regards,
    Saurabh

  • CACHE NOTIFICATIONS

    Hi,
      Whenever i activate the change list, i could see some errors in the cache notifications(Environment->Cache Notifications).
    The errors are
    1) Unable to contact Adapter Engine "af.mtx.bw" that is   affected by the data changes
    2)http connection to "http://bw:8200/CPACache/invalidate" returns the status code "401" in response
    How do i resolve this?
    I have plain J2SE Adapter Engine installed on my m/c. In my Adapter Configuration, i have only one entry under the Adapter Engine Drop down box(instance is Integration Server). Is it correct or should i get my decentral adapter engine in that drop down box?
    My configuration changes are not getting reflected in the SXI_CACHE tcode.For ex. i have a sender agreement in my ID. But its not present under the SXI_CACHE TCODE.similarly communication channel is missing in XI Runtime Cache.
    Thanks in advance
    Regards
    Amith

    Hi,
      MY SLD is connected to the AE. Bcoz i could see my AE Entries in the sld and my SLDACCESSOR is working properly in AE.
    When i try to refresh the cache in Integration Directory for the cache instance CENTRAL INTEGRATION SERVER, i am getting a message that
         "http connection to "http://bwxi:8200/CPACache/invalidate" returns the status code "401" in response"
    Sometimes i am getting a message saying that SAP_XIADAPTER FRAMEWORK is not found in SLD.
    what do i need to do?
    Regards

  • Cache Notifications unable to determine name of Central Adapter Engine

    Hi All,
      When I tried Tools -> Cache Notifications in the integration directory, im getting
    Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time.
    Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine.
    This is usually structured as follows: af.<SAP System ID>.<Name of application server>
      Once i click the OK on the pop up dialog which has this message, it has given the Notifications and Problems Tab.
      In the Problems Tab, its has given an error message
    'Unable to find an associated SLD element (source element: SAP_XIIntegrationServer"
    Any suggestion of what to look for to modify ??
      Thanks
      Sourav

    Hi Kedar,
      Check this Blog. it should probabaly solve your problem.
      /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
      Thanks
       Sourav

  • Error in Integration Directory

    Hi Experts,
    In ID When I Go for Environment-->>Cache Notifications
    I Got the Following Error
    <b>
    Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server></b>
    I Checked With All PI* Users, None of them are Locked.
    In The Runtime Workbench Component Monitoring-->> All Components AE, SLD,IR , ID, RTW, Are in the Green State Only.
    Here If I Clicked on the Cache Connectivity Test Means It's Giving Error.
    <b>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.01.epnwsrv, string], target element type: SAP_BusinessSystem)</b>
    Please Resolve this Issue.
    10 Points If Problem is Solved
    Regards
    Khanna

    HI Khanna
    <i>Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server></i>
    did you try to clear the SLD cache in Integration Directory? After that SLD information is newly read and so your biz system will appear.
    To clear SLD cache go to menu "Environment" --> "Clear SLD Data Cache".
    Have a look at these threads ?
    Unable to determine name of central adapter engine
    Wrong Adapter engine in RFC Adapter after export/import
    <i>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.01.epnwsrv, string], target element type: SAP_BusinessSystem)</i>
    Same kind of problem discussed here.. have a look at this thread.. might be helps to you....
    Attempt to fetch cache data from Integration Directory failed
    Cheers...
    Vasu
    <b>** REward Points if found useful **</b>

Maybe you are looking for