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

Similar Messages

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.

Problem with Integration Directory

Hi,
I have problem with Integration Directory while connecting it showing the fallowing Error.any body help me with some solution thanks in advance.
Application cannot be started!
Details: com.sap.engine.services.ejb.exceptions.deployment.EJBConfigurationException: Exception while reading index of JAR file aii_ibdir_sbeans.jar in application sap.com/com.sap.xi.directory from the Configuration.
 at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2322)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:323)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:118)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:219)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4345)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2465)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2338)
 at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:41)
 at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:141)
 at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
 at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:101)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: -9,223,372,036,854,766,508,
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:83)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:60)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:879)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.getCachedConfiguration(ConfigurationHandlerImpl.java:371)
 at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getData(ReadAccessConfiguration.java:84)
 at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:848)
 at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2320)
 ... 15 more
Caused by: java.sql.SQLException: [NWMss][SQLServer JDBC Driver]Connection reset by peer: socket write error
 at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
 at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.sap.nwmss.jdbc.sqlserver.tds.TDSRPCRequest.submitRequest(Unknown Source)
 at com.sap.nwmss.jdbc.sqlserver.tds.TDSRPCNonCursorExecuteRequest.submitExecute(Unknown Source)
 at com.sap.nwmss.jdbc.sqlserver.tds.TDSRPCExecuteRequest.execute(Unknown Source)
 at com.sap.nwmss.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
 at com.sap.nwmss.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at com.sap.nwmss.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
 at com.sap.nwmss.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
 at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:97)
 at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:270)
 at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:241)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getConfiguration(DBAccessDefault.java:604)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:77)
 ... 21 more
Thanks
kiran.B

Kiran,
Start you J2EE engine visual administrator.
Choose Cluster--> server ---> services ---> deploy
Here there will be one application/service named "directory" (dont remember the exact name).Please start that service and your problem should be solved.
Thanks,
Anand

Problem related Integration directory

Hi,
I am sending an IDoc from SAP R/3 to SAP XI . In WE02 IDoc showing Status as 03 (sucess) but in SM58 it showing as Error
1) No service for system SAPBQA, client 300 in Integration Directory
I checked the note 940313 but not able to resolve it.
2) I also found one problem that the software component added to business system but when I imported it to Integration directory then the "other attributes" tab of Business system shows no objects found meaning no software component is mentioned there.
Earlier it was running fine when XI was connceted with development. When we disconnected the Development and connected it to SAPBQA we are getting that problem.
We have also done cache refresh, CPA cache refresh etc.
Can anybody suggest the solution to my problem.

Hi,
"Message interface does not exist in any software components installed on this business system"
1) Open ID-----Double click on Business system that which u are using in the scenario
2) Check whether you are able to see the SWC in the Othere attributes TAB
3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
4) Click on Installed Products TAB
5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
7) Click on Installed products and Check the check box of your Product and then finally save that.
Now you should be able to see the SWC in the Othere attributes TAB in ID
Regards
Seshagiri

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

Problem in Integration directory

I created a new object in integration directory.There is an option called to transfer integration scenario from integration repository.But i am not able to do it because my scenario does not appear in the menu.I activated my namespace in Integration repository.Can you please tell me the procedure to do it?

Hi,
You have to create a scenario by right click on Integration Scenario you have to map the flow source to adapter and adapter to target. After completion of all the things you upload it into ID.
Thanks,
RamuV

Problem restricting Integration Directory object access

Hi All,
We are trying to restrict access to a group of objects in the Integration directory. In the tab "Party" i select the option as follows:
Selection Paths -
Operator - Include, Party - Service without party, Service - BSR_TEST
Objects -
Operator - Include , Type = *, Action - Change
However, this role when assigned to the user allows create and delete option as well. Also, if any other role is assigned to the user and then revoked, the restriction does not work (the role mentioned above gives an Insufficient authorization error even for the objects it is set to permit)
Our XI system version is 7.0 with SP level 17.
Thanks in advance for your inputs
Vijaya

Hi Abhishek,
Thanks again for your response. However any ideas as to why the role would stop working f user settings are changed?
Also, when i select the service using option - single selection and select multiple checkboxes (even 2) it does not work, where as if i add 2 rows with one value it is ok.
Let me know if i am missing something
Thanks
Vijaya

Problem in Integration Directory after transport

Guys,
we did a SLD transport (only LD objects), with DEV and PRD groups. It had some error messages because the SWCV's from the Dev XI were not created into PRD XI, but apparently, despite the errors, the products and SWCV's were created.
After that, we've done IR and ID objects transports, through File System.
Apparently, the IR part was OK.
In the ID, it correctly changed the Business Systems from Dev Configuration to their respective transport targets. However, if we try to open any Adapter, it gives an error message:
Attempt to access the 1 requested objects on 1 failed. Detailed information: com.sap.aii.ib.core.roa.RoaObjectAccessException: Unable to read object Adapter Metadata SOAP | http://sap.com/xi/XI/System (b38bcd00-e471-11d7-afac-de420a1145a5) of type AdapterMetaData from application REPOSITORY on system REPOSITORY. Detailed information: Software component version with GUID b38bcd00-e471-11d7-afac-de420a1145a5 does not exist
And if we try to create a new Adapter, when we go to select adapter type (SOAP, File, RFC etc) it says
Search Result for All Component Versions
No objects found!
So, we can't select any adapter type.
Has anyone had this error before?
What did we do wrong in the transport?
Was it the error from the SLD transport that caused this?
Thanks in advance,
Henrique.

Hi Henrique,
Go and import the SAP BASIS 6.4 or 7.0 Software COmponent Version into Integration Repository.
For this tpz file you can get from -
Copy XI3_0_SAP_BASIS_6.40_09_00.tpz from <Components DVD>/XI /XI_CONTENT to directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
cheers,
Prashanth
P.S Please mark helpful answers

Cache update problem

Hi experts,
I installed sap xi in my system and I finished up with post installation steps also
but I gone to the cache refresh i.e SXI_CACHE transaction code there is showing the error cache not update and it is red color .
Regards,
Srinivas.D

Check out the RFC destination,INTEGRATIONSERVERHMI,(H),
execute the RFC & see.if there is any error with that rfc prob u end up with RED color.
Use Complete cache refresh and check it out.
Or lese use Pull method, http://host:port/CPACache check out the error.
Regards
shekar chandra

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 directory problem while creating business service

HI,
CURRENTLY I AM FACING A PROBLEM IN INTEGRATION DIRECTORY. WHEN I TRY TO CREATE A BUSINESS SERVICE INSIDE THE SERVICE WITHOUT PARTY WHICH I AM TAKING AS A SENDER, I AM UNABLE TO GET THE SOFTWARE COMPONENT VERSIONS IN THE SENDER PARAMETERS.
IF ANYONE CAN GIVE THE COMPLETE CONFIGURATION STEPS FOR SENDER AND RECIEVER SYSTEM THAT WILL BE VERY HELPFUL.
BEST REGARDS,
MONA

Hi Mona,
Let me explain you in detail:-
First, Activate the Change List in the Integration Repository once the design objects are complete. By activating the change list, the object becomes available for Configuration in the Integration Directory.
Secondly, to transfer Integration scenario from Integration Repository - you need your Integration Scenario to be created correctly and when you run this wizard you actually pull the Integration scenario in the Integration directory.
You also have the option of 'Configuration Wizard'.
This tool is a wizard for creating your Recevier Determination, Receiver Agreement, Sender Agreement and Interface Determination. For this tool, you do not need the Integration scenario
It is not mandatory to use any of these tools to configure your scenario.
All you have to do for configuring your scenario is
1. Create Business system/Business service
2. Create Communication Channel
3. Create Receiver Determination
4. Create Interface Determination
5. Sender Agreement
6. Receiver Agreement
I hope this provides you a solution.
Regards.
Praveen

Cache Refresh Problem

Hi,
We updated XI 3.0 to SP4, and started seeing several problems related to Cache Refresh and JCo.
In the SAPGUI in transaction SXI_CACHE, we are unable to refresh the cache, and getting the following error:
Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://NETWEAVER:50000/run/hmi_service_id_fresh_mappings/int?container=any" with user "XIDIRUSER". Response code is 503, response message is "Service Unavailable".
In SM59 for RFC HTTP destinations, the INTEGRATION_DIRECTORY_HMI test gives the HTTP/1.1 500 Internal Server Error. The URL is /dir/CacheRefresh.
On the Runtime Workbench, I am trying to run the self-test for Mapping Runtime. We get the following errors:
Ping Status: HTTP request failed. Error code: "503". Error message: "Service Unavailable"
Self-test status: HTTP request failed. Error code: "503". Error message: "Service Unavailable"
We are on XI3.0 SP4, J2EE SP7 and ABAP SP4.
What can I check on the J2EE server to see if the service is running ? And what can I do to fix the JCo connections ? Thanks,
Manish

Thanks Hart. I have updated the URL and it succeeds on Test.
However, I still have the Cache updation problem.
When I update an object (say, a mapping) in the Integration Builder, and activate it, the XI Server Cache should get updated with this new object.
On running the scenario, I am getting the following error as observed in the monitor (SXMB_MONI):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XICACHE">UPDATE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP status code401 Unauthorized</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>An error occurred when refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
To resolve this problem, I have to manually go to the transaction SXI_CACHE, and do a delta cache refresh. It asks for the user credentials everytime for XIISUSER.
Is there a way to automatically enable this user to enable the cache refresh in the background ?
thanks,
Manish

Cache/Queue Problem while executing scenario

Hi All,
Our server is up and running, but there is a problem every time we try to execute a scenario:
1. The SXI cache and the CPA cache have to be refreshed after making any changes to the objects
2. The queues have to be de-registered, then re-registered in sxmb_adm
Has anyone faced this problem before? Any suggestions as to how to solve this?
Regards,
Puloma.

Hi,
this is not a normal behaviour. Have a look at the cache notifications in the integration directory and check whether you receive some hint. Eventually there might be problems with the connectivity to the adapter engine or user xidiruser. Have a look at the following notes
741214 and 780747 and the HOw To Cache guide which you can find under http://service.sap.com/xi
Hope this helps, Regards, Jaime

Error: - No service for system port, client in Integration Directory

Hi
In Idoc to File scenario, My Idoc 've been successfully send from the sender system.
but its neither getting displayed in the SXMB_PATH nor saved in the specified path.
I checked in SM58 in R3 that RFC user has access to send data to XI. But it showing below Error:_
ERROR:-
No service for system Sender Port (SAPDEV) client sender client (300 ) in Integration Directory
Please do the needful
Thanks,
Anshul

Hi Anshul,
Go to:
TCODE SXMB_ADM -> Integration Engine Configuration
Please change the system rile to be "Application System", then retest if the similar issue happen again after that.
If not helped, follow:
1. Clear SLD Delta Cache Referesh in the Integration Directory
2. Open the Business System in edit mode and select Adapter specific identifiers following the menu path:
Service -> Adapter Specific Identifiers
3. Please click in the button next to "Apply" button to pick up the Logical system from SLD.
Regards,
Caio Cagnani

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 update problem in Integration Directory

Similar Messages

Maybe you are looking for