# SWS Caching

> Advanced Topic - Caching Responses - Read Carefully!

---

LLMS index: [llms.txt](/llms.txt)

---

<div class="alert alert-warning" role="alert"><div class="h4 alert-heading" role="heading">Warning</div>


The PeopleSoft REST caching has some limitations. I would read the <a href="https://ib.books.cedarhillsgroup.com/rest/restcaching/">PeopleSoft REST Caching integration broker book section</a> before using this.
</div>


- **Minutes to Cache Response**: You can optionally configure to have the integration broker cache the response. This can be done for performance reasons if the SQL is very "expensive".

SWS can tell the `RESTListeningConnector` servlet to cache the response. This caching is provided by the built-in caching mechanism in PeopleTools REST functionality. It can speed up requests for expensive SQL where the result is not expected to change often. There are some known caveats — see the [PeopleSoft REST Caching integration broker book section](https://ib.books.cedarhillsgroup.com/rest/restcaching/) before using this.

<div class="alert alert-warning" role="alert"><div class="h4 alert-heading" role="heading">Warning</div>


If your SWS setup uses `%EMPLOYEEID` or `%OPERATOR` then do NOT use caching if you have multiple clients.
</div>