JDrive Plugin 4.5 (English)
With Jalios JDrive, access and work on your documents from your PC, tablet or mobile phone with complete peace of mind : documents are automatically saved and shared on your Jalios Digital Workplace.
When to use this plugin?
With version 4.4 of the JDrive plugin, you can now configure the JDrive synchronization folder's name associated with the JPlatform site that will be used for all users.
And for newly synchronized documents, you can now enable read-only directly from the JDrive client popup window.
What does this plugin do?
- The first feature allows you to keep on your computer an automatically synchronized copy of documents that are added to the JDrive.
- The second feature is called "live edition" and allows you to open and modify documents directly from the platform.
The use of JDrive requires the JDrive plugin on the server and the JDrive client on the user's workstation. The latest version of the client is JDrive Client 4.4.
- Automatically synchronize the document both ways
- Detect potential updating conflicts
- Display JDrive status icons of the file (synchronized, locked, private, new document, etc.)
When a category (folder) is added, JDrive performs these operations for all the documents associated to this category.
- Directly display of the document on the site
- Editing of metadata associated to the document
- Lock taking on the document
- Sharing of the document through recommendation
- Indicating a major update of the document
- Read-only mode to avoid taking the lock when opening the document
- Either in the document space associated with the local path of the created file
- Either in the user's private JDrive
JDrive's app view gives fulll access to manage all documents added to the JDrive.
Editing and updating documents
- creates a local copy and opens it with the appropriate associated editing software on the computer
- updates changes that have been saved locally to the remote document when the user closes the document
- deletes the local copy (unless the document has been added to the user's JDrive)
Other JDrive client features
- JDrive popup always accessible from the taskbar
- JDrive explorer and search in the JDrive
- JDrive capacity/quota indicator
- JDrive connection status indicator (Disconnected, Authenticated, Synchronized, etc.)
- JDrive actions history
- Choice of JDrive root location
- Management of Jalios sites and connection identifiers
The JDrive client is also available on the AppStorefor iPhone and iPad.
What our customers like about it
The ease of use
Organized documents without duplication
Compatibility with several editing software
- The JDrive 4.2 module requires JPlatform 10 SP1
- The JDrive 4.2 module works with the JDrive 4.4 client
- The JDrive 4.4 client requires the installation of the .Net 4.6.1 framework on Windows workstations
- The JDrive client can be installed on Windows Vista, Windows 7, Windows 8 and Windows 10
- The JDrive client is no longer compatible with Windows XP
- For the Jcms 9 version, use the JDrive 3 client
- To use Windows authentication, it is necessary to configure the Waffle module beforehand
- If you have configured the SAML or TOTP module, then you can select the browser authentication mode.
JDrive client dialogs with the JDrive module through the JPlatform Open API.
The JDrive module on the JPlatform server can interact with JDrive clients through one of two services: Tcp or Push. This is configurable from the JDrive module properties on the JPlatform server.
2.1 Tcp notification serviceJDrive
clients can connect to the Tcp notification server that is started by the JDrive module (by default on port 37480). This port must therefore be accessible to JDrive users. If users need to be able to connect from outside your local network, contact your system administrator to open this port.
2.2 Push Notification Service - Beta
The push notification service is based on the Web Push protocol. It doesn't need to open a port unlike the Tcp notification service.
This feature sets up a long connection to JPlatform.
So assuming that 150 people have a jDrive connected (or 50 people have 3 jDrives connected, it's the same thing), you will have to configure 150 more connections (so also on the apache workers side).
To do this, you have to add to tomcat an AJP connector on another port (here with 50 threads of margin) :
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8019 -->
<Connector port="8019" minProcessors="25" maxProcessors="200" connectionTimeout="600000" disableUploadTimeout="true"
enableLookups="false" protocol="AJP/1.3" URIEncoding="UTF-8" />
You now have to add a new corresponding ajp configuration in the existing configuration :
in the workers.properties :
worker.list=jkstatus, ..., pushTomcat
In the apache configuration
JkMount /push/provider pushTomcat
JkMount /push/provider/ pushTomcat
JkMount /push/provider/* pushTomcat
JkMount /push/event-stream pushTomcat
JkMount /push/event-stream/ pushTomcat
JkMount /push/event-stream/* pushTomcat
Finally, you will have to configure on the JPlatform side the number of simultaneous connections to 150
3. using the
com.jalios.jcms.push.maximumServletInstanceCount property (by default 100)
- This property defines the maximum number of simultaneous calls to the push servlet (whatever its URI is)
- It allows to return an error https://httpstatuses.com/429 code if this number is exceeded
4. Configuration du module JDrive
4.1 Properties of JPlatform
To use JDrive you need to enable JPlatform Open API.
Go to the JPlatform Property Editor, on the Web Services tab, enable Open API and allow reading and operations as shown below:
When a document is updated from the JDrive, you can configure whether to replace the existing file on the server or create a new version of the file.
To do this, edit the WEB-INF/data/custom.prop file and configure the
true: replacement of the existing file
false: new file
4.2 Module properties
You can enable or disable the notification server.
NOTE: If you choose to disable the Notification Server, JDrive clients will need to manually synchronize their contents. To do this, click "Synchronize" from the JDrive client menu.
1- Notification service - Host name
Specify the IP address of the server or its host name. By default, the value used is the IP address of the notification server.
2- Notification service - Server port
Specify the port used to communicate with customers. By default this is the port
NOTEThis port must be accessible to JDrive users. If users need to be able to connect from outside your local network, contact your system administrator to open this port.
3- Notification service - Waiting time
Specify the time after which JDrive clients reconnect to the notification server. The default value is
Filing of new documents
You can configure the way JDrive clients deposit new documents. 2 modes are defined:
- The transparent mode - This mode allows you to automatically drop private documents
- Only users who have uploaded the document can access it. It is then possible to share it with other users
- Documents are automatically dropped in a workspace defined via the module property
Espace de dépôt
- The non-transparent mode - This mode allows you to deposit documents via a drop interface
- To use this mode, leave the property
Espace de dépôtblank
- The repository interface allows users to configure the metadata of new documents to be deposited (workspace, categories, workflow, comments, etc...)
- To use this mode, leave the property
1- Drop-off space
You can specify a workspace identifier for the personal document repository.
NOTE: If this property is set then the transparent mode is enabled. Otherwise the non-transparent mode is activated.
2- Deposit - Default document type
You need to specify the type of document that will be created in the JPlatform when you upload via the JDrive. The default is
NOTE: The configured type must be enabled in the spaces accessible to different users
3- Deposit - Extension to be ignored
You can specify file extensions to be ignored. These files will then not be uploaded to the site.
By default the unauthorized extensions are:
You can specify a download URL for the JDrive client. If so, the client download will be offered to users from the 'My JDrive' interface on the JPlatform.
Live Edition - Allowed Applications
You can specify the list of allowed document types for triggering Live Editing. Specify the complete mime-type of the document (example for a PDF file:
application/pdf). 4 short mime-types are also supported:
You can specify category identifiers containing documents that will be used as templates for creating a new document
Quota per member
This property allows you to limit the number of documents a member can have in his JDrive.
- By default the limit is
1000documents per member.
- To remove any limitation, set the
Choosing the name of the synchronization directory
From version 4.4 of the JDrive plugin and version 4.3 of the JDrive client, you can choose the name of the synchronization directory that will be used to synchronize the site documents.
If this property is not filled in, the name of the site (as declared in the custom.prop file) will be used.
Using JDrive ACLs
Utiliser le JDrive and
Utiliser l'édition Live allow you to configure the JDrive usage modes:
Utiliser le JDriveThis ACL allows to define the members benefiting from the document synchronization service
Utiliser l'édition Livethis ACL allows to define the members benefiting from the Live editing service of the documents
1- Using the JDrive
By default, any JPlatform member can add documents to his JDrive. It is possible to limit the use of the JDrive by activating the Module > JDrive > Use JDrive ACL. In this case, only members belonging to a group with this ACL will have access to the JDrive functions.
2- Using Live Edition
By default, any member of JPlatform can use Live editing. It is possible to limit the use of this feature by activating the Module > JDrive > Use Live Edition ACL. In this case, only members belonging to a group with this ACL will have access to this function.
3- Using category synchronization
By default, any member of JPlatform can use category synchronization. It is possible to limit the use of this feature by enabling the Module > JDrive > Use category synchronization ACL. In this case, only members belonging to a group with this ACL will have access to this function.
5. JDrive client installation
- The JDrive client is digitally signed.
- It is delivered in Windows Installer
5.1 Manual installation
- For manual installation, make sure that the .Net Framework 4.6.1 is installed.
- If a version of the JDrive client is already installed on the computer, quit if it is running
- Download jdrive 4.4 Client archive
- Decompress the downloaded archive
- Right click on
jdrive_4.4.3736.exeand execute as administrator (otherwise the installation will not succeed)
- Authorize the application to make changes on the client workstation
If this is the case, be sure to exit JDrive if it is running, and avoid closing these applications automatically as they may not restart automatically
5.2 Installation by group strategy (GPO)
For the IT manager JDrive can be deployed by GPO
- - machine configuration
- - per-machine configuration
- - configuration by user
- - per-user configuration
- In this case, an administration template is provided that allows you to install JDrive and apply settings for using JDrive to an entire fleet of clients.
- They modèles d'administrationcan be used from the Group Policy Object Editor for GPO deployments to set up Windows authentication and certificate validation.
- The administration template files that come with JDrive enable/disable certain features of the JDrive client
- Disable client certificate validation
- Disable checking against the CA revocation list
- Disable access to Windows Session Authentication Mode
- Disable access to the authentication mode by delegation to Jcms
- Setting the path to the synchronization directory
- Configuring default site properties
- Authentication mode (classic, Windows, delegated)
- Configuring JDrive in a Citrix environment
- Enable JDrive to stop after closing all edited live documents
- Enable JDrive to shut down when the Citrix user logs off
Deployment on an OU (Organisational Unit) of computers
There are several methods to apply a GPO to an entity, people or computers. For this example, we will choose to apply a GPO to a particular OR:
- Create an OR in "Computers" called "JDrive"
- Create a new GPO, named "JDrive deployment"
- Enter the following characteristics for this GPO :
- Computer Configuration / Software Settings / Assigned Applications: Right-click and click on "New package" ;
- Then go and find the file
.msicorresponding to the software to be installed
- As a deployment method, select "Assigned"
- Once the policy has been created on the OU, move the computers on which the software is to be deployed to that OU
- Make sure that the GPO is active ("Enabled")
- Ask users to restart their workstation, or launch, locally or remotely, one
gpupdate /forcefor the computer to update its policies.
- In the case of a
gpupdate /force, it is necessary to reboot the computer in order to finalize the installation of the JDrive client
Options for deployment by group strategy (GPO)
|Registry key (path relative to HKLM or HKCU depending on the templates used)||Value name||Default value||Possible values||Description|
|Software\Policies\Jalios\Jalios JDrive||SynchronizationFolder||%userprofile%\JDrive||Windows Path||Allows you to specify a synchronization directory|
|Software\Policies\Jalios\Jalios JDrive||DisableCertificateValidation||0||0/1||Disables certificate validation|
|Software\Policies\Jalios\Jalios JDrive||DisableCheckCertificateRevocationList||0||0/1||Disables checking against the CA revocation list|
|Software\Policies\Jalios\Jalios JDrive||DisableWindowsAuth||0||0/1||Disable the choice of Windows authentication in the login window|
|Software\Policies\Jalios\Jalios JDrive||DisableDelegateAuth||0||0/1||Disables the choice of delegated authentication in the login window|
|Software\Policies\Jalios\Jalios JDrive\Citrix||StopWhenEditionCompleted||0||0/1||Enables JDrive to stop when no more documents are being edited|
|Software\Policies\Jalios\Jalios JDrive\Citrix||StopWhenCitrixSessionClosed||0||0/1||Enables JDrive to stop when the web browser from which you requested editing is closed|
|Software\Policies\Jalios\Jalios JDrive\Default Site||Url||NULL||Jcms site URL||Allows you to define the Url of the site to which the default site is connected|
|Software\Policies\Jalios\Jalios JDrive\Default Site||Authentication||NULL||
Allows you to set the preferred authentication mode used to authenticate to the default site
BasicAuthentication = login/password
NegotiateAuthentication = Session Windows
CookieAuthentication = delegated to JPlatform
6. Configuring the JDrive client
6.1 Configuration after manual installation
When the JDrive client starts for the first time, the configuration window appears.
- Enter the URL of your JPlatform site
- Select the authentication mode
- If you select the login and password authentication, enter your login and password
- click on the "Save" button
The JDrive icon in the notification bar will indicate that the JDrive is currently authenticating.
- As soon as the icon appears, your JDrive is operational:
The JDrive icon in the Windows notification bar indicates the status of the JDrive :
- Synchronisation in progress
- Server unavailable
In case of unavailability (network or site) the tooltip indicates the time remaining before the next connection attempt:
- Notification server unavailable
6.2 JDrive client menu
The JDrive client menu is accessible in 2 places:
- From the context menu of the JDrive icon in the Windows notification bar:
- From the change history button
This menu allows you to
- Synchronize your entire JDrive
- Login/Logout to the site
- Go to Preferences,
- Drop off pending documents, ...
- Exit JDrive
- The JDrive popup presents a list of synchronized files, a history of the last actions performed on the documents, and a view dedicated to conflicts when they occur
- On each element, a contextual menu is proposed, accessible from the arrow on the flyover of each document in the history
- The button allows you to filter the displayed view, a click on enter triggers a classic Windows search
6.3 JDrive preferences menu
It is accessible from the context menu of the JDrive client.
You can :
- Set up new sync sites,
- Change user or delete a site
- Select the site you wish to be synchronized with.
- Report a problem to support by providing the archive created on your desktop.
- Change the level of event logging (by default set to
- Open the current los file.
- Open the current log directory.
In this tab you will find information about the version of the client, as well as the deployed plugin.
7. Using the JDrive
Adding a document to the JDrive from JPlatform
To add a new document to your JDrive from the JPlatform, view a document and click 'Add to my JDrive'.
You can also add a document via the context menu.
The document is then automatically copied to your JDrive and a notification balloon tells you when the document arrives.
Access to the JDrive folder
To access the document in your JDrive, right-click on the JDrive menu and select 'Open JDrive folder'. You can also open the JDrive folder by double-clicking the JDrive icon.
The JDrive folder contains all your documents.
A small icon in the lower left corner indicates the status of the :
- Updated document
- Document being synchronized or to be synchronized (e.g. if you are logged off)
- Document locked by another user
- Document not yet filed in the JDrive
- Private document visible only to the user who deposited it.
ATTENTION : the file names correspond to the titles of the documents in JPlatform
Removing a document from the JDrive
You can remove a document from your JDrive from the JPlatform web interface (in the same interfaces as for adding) or simply by deleting it from your JDrive folder. This does not delete the document on the JPlatform server.
Restoring JDrive content from the client
In previous versions of the JDrive client, when you deleted the synchronization
%userprofile%\JDrive\mysite\directory, this had the effect of purging your JDrive: All documents were removed from your JDrive on the server side.
Since version 3.1 of the client:
- Deleting the synchronization directory restores the contents of your JDrive: All documents on the server are downloaded back to the local directory.
- From now on, to purge your JDrive, you need to go into the directory
%userprofile%\JDrive\mysite\and delete all its contents.
View JDrive content on JPlatform
JPlatform provides an interface to view the documents in your JDrive. To access it, click on your photo in the topbar and select "My JDrive" from the menu.
By default, the display uses the Folder view. By clicking a folder, you see the contents of the folder (documents and subfolders).
You can choose the list view to get an overview of all the documents on your JDrive in one view:
When the JDrive is connected and the notification server is accessible, synchronization is automatic. The client triggers synchronization in the following cases:
- Every time you connect to the JPlatform server
- When a local document is modified AND released
- Under MS-Office and Open/Libre-Office you have to close the document
- When a local document is deleted
- Via the JDrive "Synchronize" menu
- On receipt of a synchronization message from the notification server
JPlatform, through the notification server, sends a synchronization command :
- When a document is added to or removed from the JDrive
- When a document is updated or deleted
At each synchronization, a small bubble appears indicating that changes have taken place if there are several changes, or specifying the name of the modified document if there is only one:
Offline Synchronization - For low-speed or frequently interrupted networks (available only from JDrive Plugin version 4.2 and later)
Starting with version 4.1 of the JDrive client and version 4.2 of the JDrive plugin, it is now possible to do "partial synchronizations" in offline mode:
- The user, once his JDrive is disconnected, can synchronize a document or a directory from the context menu of Windows Explorer:
- JDrive automatically returns to the disconnected state
Quota management (as of Release 3.2)
Quota Management is configurable property from the back-office site =>
plugin manager =>
JDrive Plugin =>
Quota par membre- Default value: 1000
Quota par membre= 0 => no limit set - users can upload as many documents as the Jcms/Windows quotas allow
Organization of JDrive files
JDrive organizes the contents of the JDrive folder and synchronizes this organization with the server. You can create as many folders and sub-folders as you like, both from the Windows workstation and from the "My JDrive" view of the website
When you add a document to your JDrive from the website, you can select the folder where you want to add it.
The organization on file is unique to you and is known only to your JDrive. JDrive synchronizes folders on the server. If you use your JDrive on two machines, the folder organization will be the same from machine to machine.
Dropping a document from the JDrive client with the drop window in simplified/detailed form
You can drop off pending documents by selecting 'Drop Pending Documents' from the JDrive menu. The drop window will appear with a list of documents to drop. You can drop them one by one or more at a time.
When the deposit window appears, you can postpone the deposit to a later date. Documents that have not been deposited will be displayed with a blue dot with a question mark.
Once deposited, you will be notified that the deposit has gone smoothly:
Transparent and personal repository
To further simplify the use of the JDrive, it is possible to activate the personal drop mode. To do this, you need to activate the drop space in the properties. Any document placed in the JDrive directory is then automatically dropped into the InfoSpace with the default type and with limited access to its author. On the document's web page, the user is reminded that his document is private and a button prompts him to share it.
It is possible to make the use of the private deposit conditional. To do so, simply limit the people who can publish in the repository space. A member who does not have access to the transparent repository will have to fill in the repository window.
Discover this new feature in this video Jalios JDrive 3 - Dépôt de document privé
One of the goals of JDrive 3 is to replace and extend the functionality of the MS-Office add-in. Thus, JDrive 3 introduces the "live edition" which allows you to edit any type of document from its web page. This applies not only to MS Office documents (like the function provided by the add-in), but also to OpenOffice / LibreOffice documents, Adobe documents (Photoshop, Illustrator and InDesign), and any type of document for which editing makes sense (e.g. by default we do not offer video or ZIP editing). The choice of editable formats is made in the module's parameterization.
Discover this new feature in this video Jalios JDrive 3 - Live Edition
Other new features from the MS Office add-in: document templates. With JDrive 3, it is now possible to define document templates not only for MS-Office but for all types of documents (Libre Office, Open Office, Visio, Illustrator, In Design, ...). Templates are documents like any other documents that are categorized under one of the template categories (defined in the module properties). To create a new document from a template, simply go to either the Add menu of the topbar (Add > Documents > From template...) or the Actions menu of the Explorer portlet. The new document is created by duplicating the model and is directly opened for editing thanks to Live Edition.
Discover this new feature in this video Jalios JDrive 3 - Création d'un document à partir d'un modèle
With JDrive 3, document classification trees are now synchronized between the clients and the server. Thus, the user will find the same filing organization on all JDrive clients and also on the JDrive content management web interface. The risk of conflicts is much less than with document updates because the classification is user-specific, so the user can only produce a conflict with himself. If this happens, the customer's ranking always takes precedence.
As a corollary to folder synchronization, documents added to the JDrive from the web interface are automatically placed in a folder with the name of their workspace. So, if the user adds a document from the Marketing Area, it will automatically be placed in a 'Marketing Area' folder in their JDrive. But this is only a suggested filing suggestion. The user always has the option to move the document to another folder
Another new feature on folders, from the web page of a document it is possible to open the Windows folder containing this document.
Discover this new feature in this video Jalios JDrive 3 - Synchronisation des dossiers
Synchronization from a category
Several customers have told us about the need to automatically synchronize documents located in certain category trees with the JDrive. This feature has been added in JDrive 3. From the context menu of a category, a member can request to synchronize a category. Any document created with this category will be added to its JDrive; as well as any document moved to this category. However, a document removed from the category will not be removed from the JDrive. When added to the JDrive, the document is placed in a folder corresponding to the name of its space and in a tree structure corresponding to the synchronized category. However, the user can choose to rearrange the folders for these documents. Finally, from the interface of his JDrive, a member can view all the categories he synchronizes.
This feature is to be used with awareness of its effects. If many members synchronize the same category, any addition of document in this category will trigger the synchronization of the JDrive of these members; and thus as many downloads of the document. This will result in bandwidth consumption. For example, if 1000 members were to download a 1 GB video at the same time, this would represent a bandwidth of 1 TB!
Also, it is possible to limit the use of category synchronization to a certain population by activating the Category Synchronization ACL. If the ACL is not enabled everyone has access to this feature.
Discover this new feature in this video Jalios JDrive 3 - Synchronisation de catégories
Document repository with automatic workspace and category detection
When you drop a document into your JDrive client, JDrive can automatically detect in which workspaces and categories to apply to that document:
Let's suppose that you can participate in the
espace commercial and that in this space is the category
- If you create a directory
espace commercial, then all the documents you put in this subdirectory will be automatically moved to
- If you create a directory
espace commercialin which you create a subdirectory
- Then, all documents that you drop into this subdirectory will be automatically moved to
l'espace commercial, with the category
- In non-transparent deposit mode,
- The drop window opens with the workspace and category automatically selected.
- In case of a multi-document repository the setting will be applied to all selected documents in the repository
- If your JDrive synchronizes from categories, then directories are automatically created. This makes it easier for you and avoids typos when creating directories.
- For a category to be automatically selected, the directory whose name corresponds to a category must be a subdirectory of a workspace
JPlatform propagates document locking information to the JDrive.
A locked document automatically becomes read-only in all JDrive drives that contain it.
By right-clicking on a file on your JDrive, the Windows menu offers you a "Jalios JDrive" submenu. This has two entries :
- Synchronize - Accessible from a file or a directory (Requires JDrive 4.2 plugin)
- Display on the site
- Edit on the site
- Lock the document (or Unlock the document)
- Enable/disable read-only
As its name implies, the "Lock Document" menu locks the document on JCMS provided you have the rights to do so.
Self-locking of MS Office and Libre Office documents
To avoid conflicts, the JDrive automatically locks MS Office and Libre Office documents as soon as you open them. The document is then unlocked when it is closed.
This feature is only available on MS Office and Libre Office documents, as these are the only documents for which the JDrive is able to detect opening.
If you have added a document solely for consultation purposes, it is possible to activate read-only so as not to disturb other contributors:
Adding a set of documents from Explorer
The JDrive 2 provides a new icon in the JPlatform Explorer portlet. This icon allows you to add all documents of the current category to your JDrive in one click. This icon only appears if the Explorer portlet is configured to display only documents.
JDrive automatically detects and resolves conflicts at each synchronization. A conflict occurs in one of the following 3 cases:
- The document has been updated on the user's workstation and on the server
- The document has been updated on the workstation and removed from the JDrive on the server
- The document was removed on the workstation and updated on the server.
When a conflict occurs, the JDrive client moves the files in question to the "Conflicts" folder, within a sub-folder corresponding to the synchronization date, and to a sub-folder corresponding to the document. This folder contains the local and server version of the file.
The JDrive client applies a specific resolution procedure for each type of conflict:
- Conflicts Update / Update (UU)
- Moving the local document to a conflict directory
- Retrieving the server version
- Copying the server version to the conflict directory
- Moving the local document to a conflict directory
- Deleting the JDrive document
- Deleting the JDrive document
In case of conflict, the user is notified in the notification window. If the automatic resolution does not suit the user, he can use the files copied to the conflict folder to produce a new version of the file and replace the one in the JDrive folder.
The history makes it possible to quickly find out whether conflicts have occurred. The "Conflicts" tab shows you the list of detected conflicts. By clicking on it, a menu appears through which the resolution actions are proposed according to the type of conflict:
JDrive controls the access rights of documents. The check is done at each synchronization. Only the documents accessible by the user are kept in the JDrive.
JDrive also monitors the deposit rights. If the update is protected (e.g. by a DataController), an update attempt will only take place during explicit synchronizations. The document then remains in the "To be synchronized" state.
View currently connected JDrive
If you have the monitoring ACLs, you can view the list of JDrive clients currently connected to the notification server.
To do this, go to Administration > JDrive Status.
See the uses of the JDrive
The JDrive module brings a new tab in the usage analysis interface. The JDrive tab only appears for global analyses.
Several measures are presented:
- The number of users who have installed and configured their JDrive.
- The number of JDrive clients that logged in at least once during the day.
- The average number of documents contained in each JDrive.
- JDrive activity. This represents the exchanges between the server and all JDrive clients. An exchange corresponds to an addition, modification or removal of a document from a JDrive.
Connecting to multiple sites
The JDrive client can be configured with multiple JPlatform sites. It manages the documents of each site in a dedicated directory.
However, the JDrive client can only be connected with one site at a time. Document synchronization is therefore only active with the site with which it is connected.
In a JSync cluster, the notification server must be configured and started on each replica. When a JDrive Client requests the Notification Server from a replica, the replica returns the Notification Server to the JDrive Client.
On each replica, the port of the Notification Server is free to choose (default is 37480).
Antivirus software can induce unexpected behaviors with the JDrive client (false conflicts detected, data loss, unusable live edition, etc.)
As security is ensured on the JPlatform side, it is therefore strongly recommended to deactivate the antivirus in the synchronization directory of the user station (by default it is %userprofile%\JDrive)
Since version 77 of Chrome, it is no longer possible by default to memorize the choice of protocol handler.
To recover the behavior of previous versions, it is necessary to modify the register (via the Chrome gpo)