The Documentation that Eduard provided has all of the details for installing cache, but the simple answer, for someone looking for a quick tip is here:
We provide distribution packages available on our distribution page:
Login in with your wrc direct account and download the package that is the correct version you want, and that is correct for your operating system. The packages are named such that their version on os should be clear.
Windows: The package will be an executable like so:
Download this to a location on your system that is not in the pathway where you want to install. Double click and it will start the installation wizard. From there is will prompt with questions you answer about how you want to install cache. If you are not sure of some of those answers the document that Edward pointed out will have lots of answers. When the installation is complete there will be a blue cube on the dashboard from which you can access cache.
Unix and Mac: The package will be a zipped tar file like so:
Download and place in a pathway where you are not installing cache. Unzip this with:
then untar it like so:
#tar -xvf cache-2016.1.0.656.0-ppc64.tar
When done it will expand several files that are part of the distribution. Start the installation script like so:
It will prompt you with answers to questions about the install. If you have questions about this you can refer to the documentation that Edward posted. When done it will tell you the url to use to access the instance with the system management portal. You can use csession <instance name> to get into cache.
vms: This is similar in install to unix, but opening the kit up is a bit different. The package will be a bck file like so:
Set the attributes of the file correctly so that it can be opened:
$ SET FILE/ATTRIB=(RFM:FIX,LRL=32256) cache-2016.1.0.657.0-alphavms.bck
expand the bck file like so:
backup cache-2016.1.0.657.0-alphavms.bck/save DISK:[dir...]
Note, you will have to put the appropriate disk and directory designation. The ... following the directory name is necessary so that it properly expands the directories. You will have to get into the directories that it creates to get to the cinstall executable. There type @cinstall in order to start the installation. Again it will prompt for answers just like with unix.
Hope this helps.