The cs-rest.properties file contains the information required to configure Shinydrive for all your users.  It contains links to Content Web Services and Profiles for your users.

Web Services Configuration

Typically Tomcat is hosted on port 8080.  Shinydrive will use the same Tomcat port to communicate with OpenText Content Web Services.

Example Web Services Configuration – Content Server 10.5 or 16

LES_SERVICES_AUTHENTICATE=http://localhost:8080/cws/services/Authentication
LES_SERVICES_DOCUMENT_MANAGEMENT=http://localhost:8080/cws/services/DocumentManagement
LES_SERVICES_CONTENT_SERVICE=http://localhost:8080/cws/services/ContentService
LES_SERVICES_MEMBER_SERVICE=http://localhost:8080/cws/services/MemberService
LES_SERVICES_SEARCH_SERVICE=http://localhost:8080/cws/services/SearchService
LES_SERVICES_ADMIN_SERVICE=http://localhost:8080/cws/services/AdminService
LES_URL=http://localhost:8080/livelink/livelink
SHINYDRIVE_SERVICE=http://localhost:8080/shinydrive/services/Shinydrive

 

Example Web Services Configuration – Content Server 10

LES_SERVICES_AUTHENTICATE=http://localhost:8080/les-services/services/Authentication
LES_SERVICES_DOCUMENT_MANAGEMENT=http://localhost:8080/les-services/services/DocumentManagement
LES_SERVICES_CONTENT_SERVICE=http://localhost:8080/les-services/services/ContentService
LES_SERVICES_MEMBER_SERVICE=http://localhost:8080/les-services/services/MemberService
LES_SERVICES_SEARCH_SERVICE=http://localhost:8080/les-services/services/SearchService
LES_SERVICES_ADMIN_SERVICE=http://localhost:8080/les-services/services/AdminService
LES_URL=http://localhost:8080/livelink/livelink
SHINYDRIVE_SERVICE=http://localhost:8080/shinydrive/services/Shinydrive

 

Example Web Services Configuration – Content Server 10, 10.5 or 16 – Outlook Add-In Support

If you are installing the Outlook Add-In for Content Server 10 or 10.5, you will need to install the Enterprise Connect 10.5.2 Module on Content Server (note that this is not necessary with Content Server 16).

You will also need to add the following line to to the Web Services Configuration file, just after LES_URL=http://localhost:8080/livelink/livelink:

LES_EMAIL=true

 

Example DRIVE Profile

The following profile will have two drives.  One is the Enterprise Workspace, with drive letter H on Windows.  The second is the Personal Workspace with the drive letter P on Windows.

DRIVE0=Enterprise Workspace
DRIVE0_LETTER=H
DRIVE0_ROOTID=EnterpriseWS
DRIVE0_ROOTTYPE=EnterpriseWS
DRIVE0_CACHETIMEOUT=30
DRIVE0_CLIENTTHREADS=5
DRIVE0_SIZEAVAILABLE=2048
DRIVE0_SIZETOTAL=10000
DRIVE0_FORBIDDEN=^[A-Fa-f0-9]{8}$|^~.*$|^.*~$|^.*(\\.tmp)$|^.*(\\.temp)$|^.*(\\.bak)$|^\\..*$|^(Backup.of).*$
DRIVE0_ALLOWED=^.*(\\.ai)$|^.*(\\.docx)$|^.*(\\.xlsx)$|^.*(\\.pptx)$|^.*(\\.doc)$|^.*(\\.ppt)$|^.*(\\.xls)$|^.*(\\.pdf)$|^.*(\\.txt)$|^.*(\\.dwg)$|^.*(\\.dwf)$|^.*(\\.psd)$|^.*(\\.png)$|^.*(\\.mov)$|^.*(\\.ods)$|^.*(\\.odt)$
DRIVE0_DELETED_ITEMS_EXPIRY=10
DRIVE1=Personal Workspace
DRIVE1_LETTER=P
DRIVE1_ROOTID=PersonalWS
DRIVE1_ROOTTYPE=PersonalWS
DRIVE1_CACHETIMEOUT=30
DRIVE1_CLIENTTHREADS=5
DRIVE1_SIZEAVAILABLE=2048
DRIVE1_SIZETOTAL=10000
DRIVE1_FORBIDDEN=^[A-Fa-f0-9]{8}$|^~.*$|^.*~$|^.*(\\.tmp)$|^.*(\\.temp)$|^.*(\\.bak)$|^\\..*$
DRIVE1_ALLOWED=^.*(\\.docx)$|^.*(\\.xlsx)$|^.*(\\.pptx)$|^.*(\\.doc)$|^.*(\\.ppt)$|^.*(\\.xls)$|^.*(\\.pdf)$|^.*(\\.txt)$|^.*(\\.dwg)$|^.*(\\.dwf)$|^.*(\\.ods)$|^.*(\\.odt)$
DRIVE1_DELETED_ITEMS_EXPIRY=10

 

Example PROJECTX Profile

The following profile named PROJECTX will have one drive, letter X on Windows.  It is mapped to a folder within Content Server with id 123456.

PROJECTX0=Project X
PROJECTX0_LETTER=X
PROJECTX0_ROOTID=123456
PROJECTX0_ROOTTYPE=Folder
PROJECTX0_CACHETIMEOUT=30
PROJECTX0_CLIENTTHREADS=5
PROJECTX0_SIZEAVAILABLE=2048
PROJECTX0_SIZETOTAL=10000
PROJECTX0_FORBIDDEN=^[A-Fa-f0-9]{8}$|^~.*$|^.*~$|^.*(\\.tmp)$|^.*(\\.temp)$|^.*(\\.bak)$|^\\..*$|^(Backup.of).*$
PROJECTX0_ALLOWED=^.*(\\.ai)$|^.*(\\.docx)$|^.*(\\.xlsx)$|^.*(\\.pptx)$|^.*(\\.doc)$|^.*(\\.ppt)$|^.*(\\.xls)$|^.*(\\.pdf)$|^.*(\\.txt)$|^.*(\\.dwg)$|^.*(\\.dwf)$|^.*(\\.psd)$|^.*(\\.png)$|^.*(\\.mov)$|^.*(\\.ods)$|^.*(\\.odt)$
PROJECTX0_DELETED_ITEMS_EXPIRY=10

 

Properties Explained

Each drive maintains its own properties, these properties are explained in the following table:

(default) This is the "Volume Name" of the drive.  On a Mac, this will appear as the volume name on your Desktop.  On Windows, this will appear next to the drive letter in Explorer.
LETTER This is the drive letter for Windows.  It has no effect on Mac.
ROOTID Can be either a numeric object ID, or one of PersonalWS or EnterpriseWS  This maps the drive root to a specific location within Content Server.
ROOTTYPE Can be Folder if the ROOTID is an object ID, or one of PersonalWS or EnterpriseWS
CACHETIMEOUT Measured in seconds, this is the minimum amount of time the clients will cache folder browse information.
CLIENTTREADS The number of concurrent activities a client can do, such as concurrent file creations, copies, moves, etc.  Some clients are impatient and will fail if a drive is too busy to process its requests immediately, so you may need to tweak this number up if certain file intensive activites start to report insufficient resources.
SIZEAVAILABLE Size in Megabytes to be reported as available within the drive.  Generally it is for cosmetic reasons, but some file activites will actually respect this value, such as bulk copying content into the drive.  Increase it to whatever number you wish.
SIZETOTAL Total size of the drive in Megabytes.  This value is generally cosmetic.
FORBIDDEN This is a regular expression that is intended to identify file patterns we know to be temporary files.  Files that match will never go into Content Server and we will never notify the user when they are stored on the drive.
ALLOWED This is a regular expression that identifies all of the document patterns that are allowed within the system.  If the user tries to save a file that is not in this pattern and the FORBIDDEN pattern they will be notified.
DELETED_ITEMS_EXPIRY  Amount of time, in minutes, and item will stay in the user's local Deleted Items before it is removed from Content Server.  If the file cannot be removed because of permissions or RM policies, it is restored from the Deleted Items and the user is notified.  For a discussion of Deleted Items, please read more here.