JDrive Plugin 4.6
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.5.
- 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.6 module requires JPlatform 10 SP4
- The JDrive 4.6 module works with the JDrive 4.5 client
- The JDrive 4.5 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 3client
- 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 exchange data 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 service
Clients may 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 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
3. JDrive Plugin Setup
3.1 JPlatform Properties
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
3.2 Plugin 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
NOTE This 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
Adding new documents
You can configure the way JDrive clients upload new documents. 2 modes are defined:
- The transparent mode - This mode allows you to automatically upload 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 upload 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- Upload workspace
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- Upload - 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- Upload - 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.
3.3 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.
4. JDrive client installation
- The JDrive client is digitally signed.
- It is delivered in Windows Installer
4.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.5 Client archive
- Decompress the downloaded archive
- Right click on
jdrive_4.5.4008.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
4.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
5. Configuring the JDrive client
5.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:
(Restricted access media)
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:
(Restricted access media)
- Notification server unavailable
5.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
(Restricted access media)
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
5.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.
6. Using the JDrive
Please check the JDrive functional documentation.
- Changes introduced with plugin 4.6
- Changes introduced with client 4.5
- Changes introduced with client 4.4
- Changes introduced with client 4.3
- Changes introduced with plugin 4.4
- Changes introduced with client 4.2
- Changes introduced with plugin 4.2
- Changes introduced with plugin 4.3
- Changes introduced with client 4.1
- Changes introduced with plugin 4.1
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 choice of the notification server port is free (by default 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
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)
Windows Registry Editor Version 5.00