Note
	The server already has to be set up and running. Server and client have to be compatible, but not necessarily of the exact same service pack or patch level. [80]

In V12, the access to CADENAS_DATA, CADENAS_SETUP and CADENAS_SITESETUP via AppServer has been improved. The access to CADENAS_SETUP and CADENAS_SITESETUP via AppServer has been accelerated.

Another new feature is that all client applications now use the RemoteFileSystem if it is enabled on the client. Previously it was only PARTdataManager and Seamless.

If PARTsolutions Client and AppServer are running on the same computer, no RemoteFileSystem and no Remote-Index is used. In this case access to CADENAS_DATA happens via FileSystem. _DATA

Access via RemoteFileSystem is ReadOnly. If PARTadmin or PARTlinkManger should be used on the client, then RemoteFileSystem should not be enabled on the client.

Access should only be used to change config files, for example. Then the user needs appropriate rights.

For catalog/classification updates and index administration this access is not suited. On this see below.

Whether the remote file system should be activated on the client can be decided during the installation.

Example: Software, Data and Setup local (in other words the RemoteFileSystem is not used)

If Software local, Data and Setup from Appserver is selected, the RemoteFileSystem is used.

Note

If data, setup and sitesetup are accessed via the AppServer, a local pappclient.cfg is no longer needed in V12. Instead there is the environment variable CADENAS_APPSERVER. CADENAS_APPSERVER=https://<servername.domain>?<param1>=<value1>&<param2>=<value2>... The following parameters are possible: (name,default value if not specified, meaning) port=9020 => http port of the server sslport=9022 => ssl port of the server mzcomport=9021 => mzcom service port mzcomsport=9023 => ssl mzcom service port noproxy=1 => do not use proxy for access to the server proxyAddr= => if specified, proxy address to use if noproxy=0 remoteFileSystem=1 => mount CADENAS_DATA via rfs from server remoteSetup=0 (Default) => local CADENAS_SETUP | 1 => mount CADENAS_SETUP via rfs from server remoteSiteSetup=1 => mount CADENAS_SITESETUP via rfs from server remoteDB=1 => use db connection remoting via appserver remotepool=1 => mount $CADENAS_DATA/pool and $CADENAS_DATA/shared from appserver (if =0, they are placed in the local data directory) writeable=1 => mount rfs in writable mode and let the server determine if writing is allowed... (if =0, all mounts are readonly...) httpCacheSize=5000 => size of the rfs cache in Mb ... default is a max of 5GB in $CADENAS_USER/rfs

Under Appserver URL, enter the https string with exact Server name and HTTPS-Port which you entered on the Server under AppServer Service > tabbed page Port configuration > HTTPS-Port.

Example: Software local, Data and Setup from Appserver (in other words the RemoteFileSystem is used)

Once the client is successfully connected, in the task bar, right below, the icon File system service connected / Index service connected is shown in green.

A detailed documentation about the different installation types can be found under Section 3.4.1, “Different installation scenarios” in Installation Manual.

Please also see Section 3.7, “ Automatic login ”.