1.3.9.9.2.3. Caching on client side or at secondary locations

1.3.9.9.2. AppServer client: Configuration 1.3.9.9.2.3. Caching on client side or at secondary locations
Prev	Next

If the performance at secondary locations should be improved (especially with large assemblies/ZJVs) you can use RFS or SQUID.^[14]

Caching with SQUID
For external access from PARTsolutions to the PARTapplicationServer from secondary locations SQUID can be optionally installed. Squid is free software, which is installed at customer site.
Squid is a proxy for caching, which supports HTTP, among others. Squid optimizes the data flow between client and server and caches often used data (especially project and ZJV files). At large assemblies (also at native parts) the use of SQUID can improve the performance. Everything which has ever been loaded is in the local cache. In order to make sure that all files are always up-to-date, Squid checks this at each access.
Caching with RFS
If caching is activated (CacheActive=1) in the determined CacheDir a local http(s) cache is created and used. All queries to remote file system will use this cache then.
If using Squid would mean a disproportionate effort or is not necessary for performance reasons, RFS Caching can be an alternative. RFS works with UNC and therefore is a bit slower than HTTP+Squid.
Activation: Under %CADENAS_SETUP%/partsol.cfg -> block [RemoteFileSystem] -> key CacheActive set the value to 1.

Tip
Filtering with "RemoteFileSystem" will immediately find the desired setting.
```
[RemoteFileSystem]
CacheActive= 0 oder 1
CacheDir=$CADENAS_USER/rfs
CacheSize=50
```
CacheSize is given in MB.
CacheDir can be an UNC path wherewith you can realize a common caching.

	Note
	The cache can be initially filled via VBS scripting for certain catalogs. And via VBS command the files are nightly grabbed and copied in a temp-directory. Thereby the cache is filled.

	Note
Caching only works, when the headquarter is online. This is not a real restriction, because the headquarter has to be online for LinkDB calls anyway. Also using earlier versions, PARTsolutions cannot be used remotely without access to the headquarter server.

Note

Caching only works, when the headquarter is online.

This is not a real restriction, because the headquarter has to be online for LinkDB calls anyway. Also using earlier versions, PARTsolutions cannot be used remotely without access to the headquarter server.

	Note
	A diagram for distinction of different caching methods can be found under Section 1.3.9.5, “Caching methods for data storage and operation ”.

^[14]In case of doubt contact CADENAS consulting.

Prev	Up	Next
1.3.9.9.2.2. Key combinations and values of the single GUI options	Home	1.3.9.9.2.4. Precondition for Single Sign-on