cancel
Showing results for 
Search instead for 
Did you mean: 

Integration Proces Kicking off Cache

Former Member
0 Kudos

I am working on a File - > XI(BPM) - > Jdbc scenario. I created an Integration process for the outbound interface and the abstract interface. After I imported the Integration process into the directory, it threw the cache off, and the cache would never get refreshed. Why does this happen? After I delete them , the cache is back to normal. Is this a phenomenon of XI? Any help is appreciated.

AR

Accepted Solutions (1)

Accepted Solutions (1)

moorthy
Active Contributor
0 Kudos

Hi,

You can try out with refreshing the cache in SXI_CACHE.

Many a times it works by refreshing the cache in SXI_CACHE.

And it is not required everytime, and it is required when you change the IbtegratioN process after the first runtime version of the BPM.

For more-

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

Regards,

Moorthy

Former Member
0 Kudos

I have tried many times to refresh the cache but cache wouldn’t come up until and unless I delete the Integration process. And it’s the case even if I try to import the standard integration process supplied by XI. Any setting needs to be done to handle this scenario?

AR

agasthuri_doss
Active Contributor
0 Kudos

Dear Antonio Ramos,

Hi,

a)Start transaction SXI_CACHE.

b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.

c)Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.

If you still face issue try this .

Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.

However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.

To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.

Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.

Regards

Agasthuri Doss

Message was edited by: Agasthuri Doss Baladandapani

Answers (0)