Candy setup can be divided into four parts.
· User settings
· User data folders
Requirements for Candy QTO are not detailed here.
Candy can be updated from inside Candy (SUPPORT\UPDATE CANDY). Administrator mode is required.
Alternatively, the install file can be downloaded from the CCS website www.ccssa.com.
Administrators can use the following URL. This page will offer two systems one of which is regarded as a previous good system that is recommended for network environments.
To install on a local workstation simply run setup.exe.
To install Candy at a particular path (no interface) use the following: …\setup.exe SILENT=[install path]
Note that entire Candy folder can be copied to any other machine and will run without the install program being used. No third party installs are done by the setup program and no required registry settings are changed.
The application is a WIN32 .EXE file that runs in a folder structure similar to the following:
C:\Program Files (x86)\CCSWIN
A desktop shortcut will run the loader program C:\Program Files (x86)\CCSWIN\SYSTEM\CCSVFX.EXE. No parameters or “start in” path is required.
If Candy is run from a server then install the application in a sharable folder i.e. C:\APPS\CCSWIN. C:\APPS can be shared . A shortcut needs to be created on each user’s desktop with the following target path: \\App_Server\AppsShare\CCSWIN\SYSTEM\CCSVFX.EXE.
Candy runs in the memory space provided by the workstation, virtual machine or remote desktop.
.Net 4.0 is not required to run Candy but is required for many operations in Candy.
The Candy licence is a file that has knowledge of the environment in which it is installed. It can be installed in any static folder. It can’t be synchronised, replicated or recovered from backup.
In a simple local setup the licence file will automatically install in the user’s local APP DATA folder.
The licence must be created by a Candy Support person.
The licence requires validation every few months which can be done online or by telephone. This can be done from any Candy installation that is making use of the licence as long as the user has READ/WRITE/MODIFY permissions to the licence folder.
A concurrent licence is a normal Candy licence that allows an agreed number of users in a local area to use the licence concurrently. The licence must be in a sharable folder on a static file server. For example: C:\CCSLICENCE
Once the licence is set the folder will look as follows:
C:\CCSLICENCE can be shared. Each user will need to set Candy to use the licence in this folder: \\File_Server\LicenceShare
Note that the licence must be created from a user’s workstation that represents how all users will access the licence. In other words, if a user is going to access the licence as \\File_Server\LicenceShare then the licence can’t be set from the server where the licence is accessed using the path C:\CCSLICENCE.
Candy stores user settings in a folder called MY CCS. It will automatically be created in the DOCUMENTS folder of the local profile.
Here reports, document positions, settings, paths etc are stored. Most importantly this folder stores the list of DATA PATHS that Candy has access to. In the ‘first time’ case the MY CCS folder will be created in the local profile DOCUMENTS folder and a default data folder called ..DOCUMENTS\CCSDATA will also be created.
It is critical that each user has a his or her own MY CCS folder.
Any synchronising of this folder will cause Candy to slow down (ie setting the DOCUMENTS folder to ‘work off line’).
Each Candy user can have many DATA FOLDERS. The user must have full READ/WRITE/MODIFY permissions to a data folder. Candy will create folders and files inside each data folder.
Candy will always make a default data area in the local profile DOCUMENTS folder and it will be called ..\CCSDATA.
If a server is to host a Candy data folder then it must be a dedicated file server. Any application such as MS SQL or a virtual machine server that is running on the same server will make Candy unusable. The connection between the Candy application and the user’s data must be consistent and efficient (LAN quality and speed).
Many users can access the same data folder. However, only one user can access a ‘job’ at a time. See ‘multi user’ below for concurrent access to a job.
Candy data folders must not be synchronised or marked as ‘work off line’. This can cause performance problems and data integrity problems (multiple versions or out of date files). Any specialised cache settings or software could cause data corruption. Virus checker programs that hold Candy data files open for long periods will cause Candy to fail when trying to open files.
Master Job folder: This is a normal Candy data folder. Most users will only need READ ONLY permissions to access it. Some users can have full permissions so that the master data can be managed. The jobs in this folder can be used as a company library and data can be dragged from it into a live job.
Common folder: A shared folder where data can be placed by one user and retrieved by another. Can also be used as a quick backup.
Archive folder: A folder away from the user’s workstation that data can be backed up to either for actual backup or for progress backups.
Multi User folder: A ‘multi user’ path can be set up to allow many users to access the same ‘job’ at the same time.