cancel
Showing results for 
Search instead for 
Did you mean: 

sxi_cache is not working

former_member220077
Participant
0 Kudos

We did a system copy and I'm trying to get PI work, Everything seems to be working now except the SXI_CACHE. The error is LCR_GET_BUSINESS_SYSTEM-NO_BUSINESS_SYSTEM. I have looked at the SLD, the XI Adapter Framework has 1 entry under it and 19 associations. Does anybody know how I can fix this?

Accepted Solutions (1)

Accepted Solutions (1)

dharamveer_gaur2
Active Contributor
0 Kudos

There are 3 caches,

1) SLD Cache - Used to cache the objects you created in SLD to runtime.You can check if SLD cache is updated or not in Integration repostory or Integration Directory.

2) CPA cache - Used to cache , adapter or communication channels as well as changes to adapter fraemwrok to runtime.You can check the status of this cache in http://<host><port>/CPACache

3) Repository cache - Used to cache Development obejcts from IR and ID e.g Message Type , Interface, Receiver determination etc .You can track this in SAP Transaction cose SXI_CACHE.

Hope this help you.

Refer below link for Cache monitoring

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Properties for Service SAP XI AF CPA Cache (SAP Library - Configuration of Usage Type Process Integration (PI))

http://help.sap.com/saphelp_nw04s/helpdata/en/a8/22ee41c334c717e10000000a155106/frameset.htm

How to Handle XPI Caches in SAP NetWeaver 2004s (NW7.0)

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01...

Check this note 764176, & below links.

Check this guide for how to handle the cache:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a7930...

Answers (4)

Answers (4)

former_member220077
Participant
0 Kudos

When i run the Cache Connectivity test, all them get a HTTP 401? Where do I set the passwords and what users are they.

Central Adapter Engine

Integration Server - Java

Integration Server ABAP

Former Member
0 Kudos

The passwords used in

SM59, Exchange profile & NWDS

Need to chane in particular places

RFC Destination--> SM59

Exchange profile --.

http://xi-server:50100/webdynpro/dispatcher/sap.com/tcxiexprofui/XIProfileApp

NWDS --where the RFC destination is configured.

( these are very sensitive configuration , becareful while changing)

Former Member
0 Kudos

user is PIISUSER

Former Member
0 Kudos

Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized

Description: The request requires user authentication

Possible Tips:

u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER

u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>

u2022 If the error is in Adapter Engine

u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.

u2022 May be wrong password for user XIISUSER

u2022 May be wrong password for user XIAFUSER

u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message

Former Member
0 Kudos

Check the RFC Destination type H

INTEGRATION_DIRECTORY_HMI in u r XI server. it should return 200/500 response.

If there is response like 401 there there is login credential error.

Check

Regards,

Jayasimha jangam

Former Member
0 Kudos

hi david

run the report SAI_CACHE_REFRESH

check this doc

https://websmp202.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf

regards

kummari

former_member183906
Active Contributor
0 Kudos

Alternatively, you can try refreshing cache by using this url

http://<host>:<Java-Port>/CPACache/refresh?mode=full

where host is your xi host and port is java port. You can set the mode to either full or delta

In transaction sm59, check the connection INTEGRATION_DIRECTORY_HMI.

See if you can test that connection successfully. If you cannot, check the user, pwd and connection details for that.

In transaction SICF, choose default_host->sap->xi. Check that all the services are active. In particular, the ones that relate to caches are cache and cache_ssl.

Check whether all the service users are okay and are not locked. Also check the current SLD cache (table LCRT_CLNTCACHE). This can be cleared via function module LCR_CLEAR_CACHE.

I would recommend you read the guide 'How to Handle Caches in SAP XI 3.0' available on SDN at the following URL.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a7930...