This chapter describes optional installation steps for items not specified in the previous sections.
Since version 4.7.0 M2, we support the SMB 2.x and 3.x protocol. It utilizes the smbj library dependent on Bouncy Castle.
Below, you can find Bouncy Castle installation instructions for CloverDX Designer and CloverDX Server.
Before you start, you have to download a required .jar
file:
Go to the official Latest Bouncy Castle Java Releases page.
Locate the section "SIGNED JAR FILES" and download the latest release.
The filename consists of the name bcprov-jdk15on
, followed by a version number, for example:
bcprov-jdk15on-158.jar
After you download the .jar
file,
add it to CloverDX Designer or CloverDX Server by following these instructions:
There are two ways of adding Bouncy Castle to CloverDX Designer:
Recommended:
Rename the .jar
file to bcprov-jdk15on.jar
and copy the renamed file into the CloverDX Designer's installation directory
(e.g. C:\Program Files\CloverDX Designer\
on MS Windows or
CloverDX Designer.app/Contents/Eclipse
on Mac OS).
Alternative:
Edit the CloverDXDesigner.ini
file and specify the path to
the .jar
file using the parameter:
-Dcloveretl.smb2.bouncycastle.jar.file=/path/to/bcprov-jdk15on-XYZ.jar
Now restart CloverDX Designer for the changes to take effect.
There are two ways of adding Bouncy Castle to CloverDX Server, as well:
Recommended:
Set the system property cloveretl.smb2.bouncycastle.jar.file
pointing
to the location of the .jar
file.
Example for Apache Tomcat:
Edit the setenv.bat
file located in the \Apache_Tomcat\bin\
directory.
Set the system property by adding the following line:
set JAVA_OPTS=%JAVA_OPTS% "-Dcloveretl.smb2.bouncycastle.jar.file=path/to/bcprov-jdk15on-XYZ.jar"
![]() | Note |
---|---|
The instructions for setting up the system property may differ depending on the application container. |
Alternative:
Put the .jar
file on the application container's classpath
(e.g. C:\CloverDXServer.5.0.0.Tomcat-9.0.10\lib\
).
![]() | Warning |
---|---|
This option may noticeably slow down the server startup; therefore, it is not recommended. |
Now restart CloverDX Server for the changes to take effect.