CKFinder Installation

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

 
(17 intermediate revisions by the same user not shown)
Line 19: Line 19:
 
== Deployment on a Server ==
 
== Deployment on a Server ==
 
The CKFinder Java connector supports the following servers:
 
The CKFinder Java connector supports the following servers:
−
* Tomcat 5.5-7,
+
* Tomcat 6-8,
−
* Jetty 7-9,  
+
* Jetty 9,
−
* JBoss 6-7,  
+
* WildFly (former JBoss AS) 8-9,
−
* GlassFish 3.0-4.0,
+
* JBoss EAP 6,
 +
* GlassFish 3-4,
 
* Weblogic 11g-12c.
 
* Weblogic 11g-12c.
 
For detailed instructions on how to deploy CKFinder for Java to one of the supported servers, please refer to an appropriate section below.  
 
For detailed instructions on how to deploy CKFinder for Java to one of the supported servers, please refer to an appropriate section below.  
Line 36: Line 37:
 
Please note that the HTTP <code>8080</code> port of the sample URL is the default Tomcat port. If you changed this value while configuring your Tomcat installation, you will need to use a modified port value to run the sample application.
 
Please note that the HTTP <code>8080</code> port of the sample URL is the default Tomcat port. If you changed this value while configuring your Tomcat installation, you will need to use a modified port value to run the sample application.
  
−
Go to the [http://wiki.apache.org/tomcat/FAQ Tomcat FAQ] and [http://tomcat.apache.org/tomcat-5.5-doc/index.html Tomcat 5.5] or [http://tomcat.apache.org/tomcat-6.0-doc/index.html Tomcat 6], or [http://tomcat.apache.org/tomcat-7.0-doc/index.html Tomcat 7] documentation for more information about using this server.
+
If you want to use international files names with CKFinder please see [http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Configuration/URI_Encoding URI Encoding section] which explains how to set UTF-8 in Tomcat.
 +
 
 +
Go to the [http://wiki.apache.org/tomcat/FAQ Tomcat FAQ] and [http://tomcat.apache.org/tomcat-6.0-doc/index.html Tomcat 6], or [http://tomcat.apache.org/tomcat-7.0-doc/index.html Tomcat 7], or [http://tomcat.apache.org/tomcat-8.0-doc/index.html Tomcat 8] documentation for more information about using this server.
  
 
=== Jetty ===
 
=== Jetty ===
Line 46: Line 49:
 
Please note that the HTTP <code>8080</code> port of the sample URL is the default Jetty port. If you changed this value while configuring your Jetty installation, you will need to use a modified port value to run the sample application.
 
Please note that the HTTP <code>8080</code> port of the sample URL is the default Jetty port. If you changed this value while configuring your Jetty installation, you will need to use a modified port value to run the sample application.
  
−
By default Jetty unpacks war files to folders like  <code><nowiki>C:\Users\admin\AppData\Local\Temp\jetty-0.0.0.0-8080-CKFinderJava.war-_CKFinderJava-any-\webapp\</nowiki></code>. Information about this folder is displayed in the output console, when the server is started. <br /> If you wish to change this folder, you can either put the unpacked <code>CKFinderJava.war</code> file in the webapps folder (Jetty will use the unpacked application folder) or go to <code><nowiki>jetty7(8)\etc\jetty-webapps.xml</nowiki></code> or <code><nowiki>jetty9\etc\jetty-deploy.xml</nowiki></code> and set the below parameter to the folder path of your choice:
+
By default Jetty unpacks war files to folders like  <code><nowiki>C:\Users\admin\AppData\Local\Temp\jetty-0.0.0.0-8080-CKFinderJava.war-_CKFinderJava-any-\webapp\</nowiki></code>. Information about this folder is displayed in the output console, when application is deployed. <br /> If you wish to change this folder, you can either put the unpacked <code>CKFinderJava.war</code> file in the webapps folder (Jetty will use the unpacked application folder) or go to <code><nowiki>jetty9\etc\jetty-deploy.xml</nowiki></code> and set the below parameter to the folder path of your choice:
 +
 
 +
<source lang="xml"><Set name="tempDir"><New class="java.io.File"><Arg>C:\tmp</Arg></New></Set></source>
 +
 
 +
Go to the [http://www.eclipse.org/jetty/documentation/current/quick-start.html Jetty 9] Quick Start guide for more information about using this server.
  
−
<source><Set name="tempDir"><New class="java.io.File"><Arg>C:\tmp</Arg></New></Set></source>  
+
=== WildFly ===
 +
The server can be started from the command line. Go to the WildFly <code>bin</code> folder and run the following command:
 +
* Windows: <code>standalone.bat</code> or <code>domain.bat</code>
 +
* Linux: <code>standalone.sh</code> or <code>domain.sh</code>
  
−
Go to the [http://wiki.eclipse.org/Jetty/Starting/Installing_Jetty-7.0.x Jetty 7], [http://wiki.eclipse.org/Jetty/Starting/Quick_Start_Guide Jetty 8], or [http://www.eclipse.org/jetty/documentation/current/quick-start.html Jetty 9] Quick Start guide for more information about using this server.
+
WildFly Application Server can run in two modes: standalone and domain. First one allows running a single standalone Server, while the latter is used to manage multiple physical (or virtual) machines from a single control point. <br />
 +
'''NOTE:''' In this example we are going to work with a standalone server.
  
−
=== JBoss 6===
+
The above two commands start server with its default configurations. If one wishes to start the server with one of alternative configurations, one should pass the <code>--server-config</code> argument with the server configuration file to be used. The example below shows how to run the full profile configuration with high availability:
−
The server can be started from the command line. Go to the JBoss <code>bin</code> folder and run the following command:
+
* Windows: <code>standalone.bat --server-config=standalone-ha.xml</code>
−
* Windows: <code>run.bat</code>
+
* Linux: <code>standalone.sh --server-config=standalone-ha.xml</code>
−
* Linux: <code> run.sh</code>
+
You can read more about available WildFly configurations [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide#GettingStartedGuide-WildFly8Configurations here].
  
−
JBoss Application Server ships with five different server [http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/html/The_JBoss_Server___A_Quick_Tour.html#The_JBoss_Server___A_Quick_Tour-Server_Configurations configurations]: all, default, standard, minimal and jbossweb-standalone. This is because one may want to start server with selected services only.<br /> The Above command will start the server in its default mode. However, if you want to use a different configuration, e.g. start the server with all services available, you would have to pass the <code>–c</code> parameter with an appropriate configuration. In this case use the <code>all</code> value:
+
After the server was started, log into administration console, click '''Deployments''' link, next click the '''Add''' button, select '''Upload a new deployment''' radio button, click '''Next''' and select <code>CKFinderJava.war</code> file. Once CKFinderJava.war upload is finished, verify its runtime name and check the '''Enable''' checkbox. The Application is now ready to use.
−
* Windows: <code>run.bat -c all</code>
 
−
* Linux: <code> run.sh -c all</code>
 
−
'''NOTE:''' In this example we are going to work with a single standalone server.
 
  
−
After the server was started, log into administration console, go to the '''Web Application (WAR)s''' menu and click the '''Add new resource''' button. In the '''Add New Web Application (WAR)''' window specify the path to CKFinder Java <code>.war</code> file, and optionally check one of the following options:
+
Another way of deploying the CKFinderJava application is using WildFly Command Line Interface (CLI). It has to be first launched using the <code>jboss-cli.sh</code> or <code>jboss-cli.bat</code> script located in <code>JBOSS_HOME/bin</code> directory. Once this is done, you can deploy applications as in the example given below:
 +
* '''In standalone mode:''' <code>[standalone@localhost:9999 /] deploy ~/Desktop/CKFinderJava.war</code>
 +
* '''In domain mode:''' <code>[domain@localhost:9999 /] deploy ~/Desktop/ CKFinderJava.war --all-server-groups</code>
 +
'''NOTE:''' Either <code>--all-server-groups</code> or <code>--server-groups</code> with specified server groups must be used.<br />  
  
−
* '''Deploy Exploded''' &ndash; for most usage scenarios,
+
To learn more about CLI please see this [https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-CommandLineInterface link].
−
* '''Deploy Farm''' &ndash; when the server works in a cluster.
 
−
If you don't select any of the options above, JBoss will be instructed to deploy CKFinder for Java as a packed war file. The application will be deployed after you click the '''Continue''' button. <br />
 
  
−
Please bear in mind that JBoss has '''auto-deploy''' mode turned on by default so it is enough to drop the <code>CKFinderJava.war</code> file into an appropriate directory. If you started your server with standard configuration (<code>run –c standard</code>), please drop <code>CKFinderJava.war</code> to the <code><nowiki>JBOSS_HOME/server/standard/deploy</nowiki></code> folder and the server will do the rest.  
+
If your Server is running in the standalone mode, then aside from using the administration console and CLI, WildFly can also work in manual and auto deployment mode (this depends on your settings).<br />
 +
In the '''Auto-Deploy mode''' the scanner directly monitors the deployment content, available in  <code><nowiki>JBOSS_HOME/standalone/deployments</nowiki></code> directory, automatically deploying new content and redeploying content whose timestamp has changed. It means that you can simply drop CKFinderJava.war into deployments folder and the application will be deployed. <br />
 +
To undeploy CKFinderJava in auto mode simply remove war file from deploy directory. <br />
 +
In the '''Manual deploy mode''' the scanner does not directly monitor the deployment content. Instead, the scanner relies on a system of marker files, which the user can add to or remove from deployment directory. These files serve as a sort of command telling the scanner to deploy, undeploy, or redeploy the content. You can learn more about marker files in the "Marker Files" section available under this [https://docs.jboss.org/author/display/WFLY8/Application+deployment link].
  
−
By deafult, the application should be available under the following URL in your browser: <code><nowiki>http://localhost:8080/CKFinderJava/</nowiki></code>.  
+
To deploy <code>CKFinderJava.war</code> in manual mode, copy this file into the <code>JBOSS_HOME/standalone/deployments</code> directory and create the <code>CKFinderJava.war.dodeploy</code> file. CKFinder will be deployed and the <code>CKFinderJava.war.deployed</code> marker file will be created. To undeploy CKFinderJava simply remove <code>CKFinderJava.war.deployed</code> file.
−
The HTTP <code>8080</code> port of the sample URL is the default JBoss port. If you changed this value while configuring your JBoss installation, you will need to use a modified port value to run the sample application.  
 
  
−
Go to the [http://www.jboss.org/jbossas/docs/6-x JBoss AS6 Documentation site] for more information about using this server.
+
Please note that by default WildFly allows auto-deployment of zipped content and prevents auto-deployment of exploded content. This is because exploded content is vulnerable to the scanner trying to auto-deploy partially copied content. However, if you wish to change this behavior, you can go to the <code><nowiki>JBOSS_HOME/standalone/configuration/standalone.xml</nowiki></code> file, look for the '''deployment-scanner'' tag and change the deployment options as you like:
  
−
=== JBoss 7===
+
<source lang="xml">
−
The server can be started from the command line. Go to the JBoss bin folder and run the following command:  
+
<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments"
 +
auto-deploy-zipped="true" auto-deploy-exploded="false"/>
 +
</source>
 +
 
 +
By default, the application should be available under the following URL in your browser: <code><nowiki>http://localhost:8080/CKFinderJava/</nowiki></code>
 +
Please note that the HTTP <code>8080</code> port of the sample URL is the default WildFly port. If you changed this value while configuring your WildFly installation, you will need to use a modified port value to run the sample application.
 +
 
 +
If you want to use international files names with CKFinder please see [http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Configuration/URI_Encoding URI Encoding section] which explains how to set UTF-8 in WildFly.
 +
 
 +
Go to the WildFly [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide Getting Started] and [https://docs.jboss.org/author/display/WFLY9/Admin+Guide Administration Guide] for more information about using this server.
 +
 
 +
=== JBoss EAP 6 ===
 +
The server can be started from the command line. Go to the JBoss Enterprise Application Platform (EAP) <code>bin</code> folder and run the following command:  
 
* Windows: <code>standalone.bat</code> or <code>domain.bat</code>
 
* Windows: <code>standalone.bat</code> or <code>domain.bat</code>
 
* Linux: <code>standalone.sh</code> or <code>domain.sh</code>
 
* Linux: <code>standalone.sh</code> or <code>domain.sh</code>
  
−
JBoss Application Server 7 can run in two modes: standalone and domain. First one allows running a single standalone Server, while the latter is used to manage multiple physical (or virtual) machines from a single control point. <br />  
+
JBoss EAP can run in two modes: standalone and domain. First one allows running a single standalone Server, while the latter is used to manage multiple physical (or virtual) machines from a single control point. <br />  
 
'''NOTE:''' In this example we are going to work with a standalone server.
 
'''NOTE:''' In this example we are going to work with a standalone server.
  
−
The above two commands start servers with their default configurations. If one wishes to start the server with one of alternative configurations, one should pass the <code>--server-config</code> argument with the server configuration file to be used. The example below shows how to run the full profile configuration with high availability:
+
The above two commands start server with its default configurations. If one wishes to start the server with one of alternative configurations, one should pass the <code>--server-config</code> argument with the server configuration file to be used. The example below shows how to run the full profile configuration with high availability:
 
* Windows:  <code>standalone.bat --server-config=standalone-ha.xml</code>
 
* Windows:  <code>standalone.bat --server-config=standalone-ha.xml</code>
 
* Linux:  <code>standalone.sh --server-config=standalone-ha.xml</code>
 
* Linux:  <code>standalone.sh --server-config=standalone-ha.xml</code>
−
You can read more about available JBoss 7 configurations [https://docs.jboss.org/author/display/AS71/Getting+Started+Guide#GettingStartedGuide-JBossApplicationServer7Configurations here].  
+
You can read more about available JBoss configurations [https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/#sect-Configuration_Files here].  
  
−
After the server was started, log into administration console, go to the '''Runtime''' Tab, select '''Managed Deployments''' menu, click the '''Add contents''' button and select <code>CKFinderJava.war</code> file. Once CKFinderJava.war upload is finished, press the '''Enable''' button. The Application is now ready to use.
+
After the server was started, log into administration console, click '''Deployments''' link, next click the '''Add''' button and select <code>CKFinderJava.war</code> file. Once CKFinderJava.war upload is finished, verify its runtime name and check the '''Enable''' checkbox. The Application is now ready to use.
−
Another way of deploying the CKFinderJava application is using JBOSS Command Line Interface (CLI):  
+
 
 +
Another way of deploying the CKFinderJava application is using JBoss Command Line Interface (CLI). It has to be first launched using the <code>jboss-cli.sh</code> or <code>jboss-cli.bat</code> script located in the <code>EAP_HOME/bin</code> directory. Once this is done, you can deploy applications as in the example given below:
 
* '''In standalone mode:''' <code>[standalone@localhost:9999 /] deploy ~/Desktop/CKFinderJava.war</code>
 
* '''In standalone mode:''' <code>[standalone@localhost:9999 /] deploy ~/Desktop/CKFinderJava.war</code>
 
* '''In domain mode:''' <code>[domain@localhost:9999 /] deploy ~/Desktop/ CKFinderJava.war --all-server-groups</code>
 
* '''In domain mode:''' <code>[domain@localhost:9999 /] deploy ~/Desktop/ CKFinderJava.war --all-server-groups</code>
−
'''NOTE:''' Either <code>--all-server-groups</code> or <code>--server-groups must be specified</code>.<br />  
+
'''NOTE:''' Either <code>--all-server-groups</code> or <code>--server-groups</code> with specified server groups must be used.<br />  
  
−
To learn more about CLI please see this [https://community.jboss.org/wiki/CommandLineInterface link].
+
To learn more about CLI please see this [https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/#sect-The_Management_CLI link].
  
−
If your Server is running in the standalone mode, then aside from using the administration console and CLI, JBOSS 7 can also work in manual and auto deployment mode (this depends on your settings).<br />
+
If your Server is running in the standalone mode, then aside from using the administration console and CLI, JBoss can also work in manual and auto deployment mode (this depends on your settings).<br />
−
In the '''Auto-Deploy mode''' the scanner directly monitors the deployment content, available in  <code><nowiki>JBOSS_HOME/standalone/deployments</nowiki></code> directory, automatically deploying new content and redeploying content whose timestamp has changed. It means that you can simply drop CKFinderJava.war into deployments folder and the application will be deployed. <br />
+
In the '''Auto-Deploy mode''' the scanner directly monitors the deployment content, available in  <code><nowiki>EAP_HOME/standalone/deployments</nowiki></code> directory, automatically deploying new content and redeploying content whose timestamp has changed. It means that you can simply drop CKFinderJava.war into deployments folder and the application will be deployed. <br />
 
To undeploy CKFinderJava in auto mode simply remove war file from deploy directory. <br />
 
To undeploy CKFinderJava in auto mode simply remove war file from deploy directory. <br />
−
In the '''Manual deploy mode''' the scanner does not directly monitor the deployment content. Instead, the scanner relies on a system of marker files, which the user can add to or remove from deployment directory. These files serve as a sort of command telling the scanner to deploy, undeploy, or redeploy the content. You can learn more about marker files in the "Marker Files" section available under this [https://docs.jboss.org/author/display/AS7/Application+deploymen link].
+
In the '''Manual deploy mode''' the scanner does not directly monitor the deployment content. Instead, the scanner relies on a system of marker files, which the user can add to or remove from deployment directory. These files serve as a sort of command telling the scanner to deploy, undeploy, or redeploy the content. You can learn more about marker files under this [https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/#Reference_for_Deployment_Scanner_Marker_Files1 link].
  
−
To deploy <code>CKFinderJava.war</code> in manual mode, copy this file into the deployments directory and create the <code>CKFinderJava.war.dodeploy</code> file. CKFinder will be deployed and the <code>CKFinderJava.war.deployed</code> marker file will be created. To undeploy CKFinderJava simply remove <code>CKFinderJava.war.deployed</code> file.
+
To deploy <code>CKFinderJava.war</code> in manual mode, copy this file into the <code>EAP_HOME/standalone/deployments</code> directory and create the <code>CKFinderJava.war.dodeploy</code> file. CKFinder will be deployed and the <code>CKFinderJava.war.deployed</code> marker file will be created. To undeploy CKFinderJava simply remove <code>CKFinderJava.war.deployed</code> file.
  
−
Please note that by default JBOSS7 allows auto-deployment of zipped content and prevents auto-deployment of exploded content. This is because exploded content is vulnerable to the scanner trying to auto-deploy partially copied content. However, if you wish to change this behavior, you can go to the <code><nowiki>JBOSS_HOME/standalone/configuration/standalone.xml</nowiki></code> file, look for the '''deployment-scanner'' tag and change the deployment options as you like:
+
Please note that by default JBoss EAP allows auto-deployment of zipped content and prevents auto-deployment of exploded content. This is because exploded content is vulnerable to the scanner trying to auto-deploy partially copied content. However, if you wish to change this behaviour, you can go to the <code><nowiki>EAP_HOME/standalone/configuration/standalone.xml</nowiki></code> file, look for the '''deployment-scanner'' tag and change the deployment options as you like:
  
−
<source>
+
<source lang="xml">
 
<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments"  
 
<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments"  
 
auto-deploy-zipped="true" auto-deploy-exploded="false"/>
 
auto-deploy-zipped="true" auto-deploy-exploded="false"/>
Line 111: Line 135:
  
 
By default, the application should be available under the following URL in your browser: <code><nowiki>http://localhost:8080/CKFinderJava/</nowiki></code>  
 
By default, the application should be available under the following URL in your browser: <code><nowiki>http://localhost:8080/CKFinderJava/</nowiki></code>  
−
Please note that the HTTP <code>8080</code> port of the sample URL is the default JBoss port. If you changed this value while configuring your JBoss installation, you will need to use a modified port value to run the sample application.
+
Please note that the HTTP <code>8080</code> port of the sample URL is the default JBoss EAP port. If you changed this value while configuring your EAP installation, you will need to use a modified port value to run the sample application.
 +
 
 +
If you want to use international files names with CKFinder please see [http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Configuration/URI_Encoding URI Encoding section] which explains how to set UTF-8 in JBOSS EAP.
  
−
If you want to use international files names with CKFinder please see [http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Configuration/URI_Encoding URI Encoding section] which explains how to set UTF-8 on JBOSS.
+
Go to the JBoss EAP [https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Getting_Started_Guide/ Getting Started] and [https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/ Administration Guide] for more information about using this server.
  
 
=== GlassFish ===
 
=== GlassFish ===
Line 133: Line 159:
 
Please note that the HTTP <code>8080</code> port of the sample URL is the default GlassFish port. If you changed this value while configuring your GlassFish installation, you will need to use a modified port value to run the sample application.
 
Please note that the HTTP <code>8080</code> port of the sample URL is the default GlassFish port. If you changed this value while configuring your GlassFish installation, you will need to use a modified port value to run the sample application.
  
−
By default, Glassfish has ISO parameter-encoding set, which may cause problems if your users want to use filenames with non-ISO characters. If CKFinder in your application is to be used worldwide, it is recommended to set UTF-8 for Glassfish. Please refer to the [http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Configuration/URI_Encodinglink URI Encoding] section for more details.
+
By default, Glassfish has ISO parameter-encoding set, which may cause problems if your users want to use filenames with non-ISO characters. If CKFinder in your application is to be used worldwide, it is recommended to set UTF-8 for Glassfish. Please refer to the [http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Configuration/URI_Encoding URI Encoding] section for more details.
  
−
Go to the Oracle [http://docs.oracle.com/cd/E19798-01/821-1757/index.html GlassFish 3.0] or, [http://docs.oracle.com/cd/E18930_01/html/821-2432/ GlassFish 3.1] or [https://glassfish.java.net/getstarted.html GlassFish 4.0] Server Quick Start Guide for more information about using this server.
+
Go to the Oracle [http://docs.oracle.com/cd/E19798-01/821-1757/index.html GlassFish 3.0] or, [http://docs.oracle.com/cd/E18930_01/html/821-2432/ GlassFish 3.1] or [https://glassfish.java.net/getstarted.html GlassFish 4.x] Server Quick Start Guide for more information about using this server.
  
 
=== Weblogic ===
 
=== Weblogic ===
 
The Weblogic Server (WLS) can be started from the command line. Go to the <code><nowiki>weblogic_main_folder/user_projects/domains/your_domain/bin</nowiki></code> folder and run the following script:  
 
The Weblogic Server (WLS) can be started from the command line. Go to the <code><nowiki>weblogic_main_folder/user_projects/domains/your_domain/bin</nowiki></code> folder and run the following script:  
−
* Windows: <code>startWeblogic.bat</code> or <code>startWeblogicManagedServer.bat</code>
+
* Windows: <code>startWeblogic.cmd</code> or <code>startManagedWebLogic.cmd</code>
−
* Linux: <code>startWeblogic.sh</code> or <code>startWeblogicManagedServer.sh</code>
+
* Linux: <code>startWeblogic.sh</code> or <code>startManagedWebLogic.sh</code>
 
If Weblogic is in production mode then please remember that you need to specify the user name and password in order to run it.  
 
If Weblogic is in production mode then please remember that you need to specify the user name and password in order to run it.  
  

Latest revision as of 15:58, 5 November 2015

This article describes how to install CKFinder for Java.

Installation Procedure

To install CKFinder, download the CKFinder for Java distribution package (a .war file) from the official download site. You will need to deploy this file to your Java server and run as an application. For detailed instructions on how to run CKFinder on one of the most popular Java servers refer to an appropriate section below.

Running the Sample Application

A test application is available in the _samples folder of the distribution package. After the deployment open the _samples/index.html page in your Web browser to see a few usage scenarios for CKFinder.

Basic Configuration

When your application works correctly in the browser, it is time to review its configuration. Go to the config.xml file where you can customize your application. See the Configuration section for more information about the CKFinder configuration.

Please note that due to security reasons by default CKFinder is disabled. When you reviewed the settings and are ready to go, open the configuration file and enable the program. 

<enabled>true</enabled>

Deployment on a Server

The CKFinder Java connector supports the following servers:

  • Tomcat 6-8,
  • Jetty 9,
  • WildFly (former JBoss AS) 8-9,
  • JBoss EAP 6,
  • GlassFish 3-4,
  • Weblogic 11g-12c.

For detailed instructions on how to deploy CKFinder for Java to one of the supported servers, please refer to an appropriate section below.

Tomcat

Place the CKFinder Java .war file in the Tomcat webapps folder. Go to Tomcat bin folder and run the startup script file for your operating system — startup.bat for Windows or startup.sh for Linux. When you are running Tomcat as a service, restart the server.

By default Tomcat has the autoDeploy="true" option enabled (check the Host element in the server.xml file). If this option was not changed, running the application should also be possible after you copy it to the webapps folder without stopping the server.

By deafult, the application should be available under the following URL in your browser: http://localhost:8080/CKFinderJava/

Please note that the HTTP 8080 port of the sample URL is the default Tomcat port. If you changed this value while configuring your Tomcat installation, you will need to use a modified port value to run the sample application.

If you want to use international files names with CKFinder please see URI Encoding section which explains how to set UTF-8 in Tomcat.

Go to the Tomcat FAQ and Tomcat 6, or Tomcat 7, or Tomcat 8 documentation for more information about using this server.

Jetty

Place the CKFinder Java .war file in the Jetty webapps folder. In the command line go to the root of the Jetty server and start it with a java -jar start.jar command.

By deafult, the application should be available under the following URL in your browser: http://localhost:8080/CKFinderJava/

Please note that the HTTP 8080 port of the sample URL is the default Jetty port. If you changed this value while configuring your Jetty installation, you will need to use a modified port value to run the sample application.

By default Jetty unpacks war files to folders like C:\Users\admin\AppData\Local\Temp\jetty-0.0.0.0-8080-CKFinderJava.war-_CKFinderJava-any-\webapp\. Information about this folder is displayed in the output console, when application is deployed.
If you wish to change this folder, you can either put the unpacked CKFinderJava.war file in the webapps folder (Jetty will use the unpacked application folder) or go to jetty9\etc\jetty-deploy.xml and set the below parameter to the folder path of your choice: 

<Set name="tempDir"><New class="java.io.File"><Arg>C:\tmp</Arg></New></Set>

Go to the Jetty 9 Quick Start guide for more information about using this server.

WildFly

The server can be started from the command line. Go to the WildFly bin folder and run the following command:

  • Windows: standalone.bat or domain.bat
  • Linux: standalone.sh or domain.sh

WildFly Application Server can run in two modes: standalone and domain. First one allows running a single standalone Server, while the latter is used to manage multiple physical (or virtual) machines from a single control point.
NOTE: In this example we are going to work with a standalone server.

The above two commands start server with its default configurations. If one wishes to start the server with one of alternative configurations, one should pass the --server-config argument with the server configuration file to be used. The example below shows how to run the full profile configuration with high availability:

  • Windows: standalone.bat --server-config=standalone-ha.xml
  • Linux: standalone.sh --server-config=standalone-ha.xml

You can read more about available WildFly configurations here.

After the server was started, log into administration console, click Deployments link, next click the Add button, select Upload a new deployment radio button, click Next and select CKFinderJava.war file. Once CKFinderJava.war upload is finished, verify its runtime name and check the Enable checkbox. The Application is now ready to use.

Another way of deploying the CKFinderJava application is using WildFly Command Line Interface (CLI). It has to be first launched using the jboss-cli.sh or jboss-cli.bat script located in JBOSS_HOME/bin directory. Once this is done, you can deploy applications as in the example given below:

  • In standalone mode: [standalone@localhost:9999 /] deploy ~/Desktop/CKFinderJava.war
  • In domain mode: [domain@localhost:9999 /] deploy ~/Desktop/ CKFinderJava.war --all-server-groups

NOTE: Either --all-server-groups or --server-groups with specified server groups must be used.

To learn more about CLI please see this link.

If your Server is running in the standalone mode, then aside from using the administration console and CLI, WildFly can also work in manual and auto deployment mode (this depends on your settings).
In the Auto-Deploy mode the scanner directly monitors the deployment content, available in JBOSS_HOME/standalone/deployments directory, automatically deploying new content and redeploying content whose timestamp has changed. It means that you can simply drop CKFinderJava.war into deployments folder and the application will be deployed.
To undeploy CKFinderJava in auto mode simply remove war file from deploy directory.
In the Manual deploy mode the scanner does not directly monitor the deployment content. Instead, the scanner relies on a system of marker files, which the user can add to or remove from deployment directory. These files serve as a sort of command telling the scanner to deploy, undeploy, or redeploy the content. You can learn more about marker files in the "Marker Files" section available under this link.

To deploy CKFinderJava.war in manual mode, copy this file into the JBOSS_HOME/standalone/deployments directory and create the CKFinderJava.war.dodeploy file. CKFinder will be deployed and the CKFinderJava.war.deployed marker file will be created. To undeploy CKFinderJava simply remove CKFinderJava.war.deployed file.

Please note that by default WildFly allows auto-deployment of zipped content and prevents auto-deployment of exploded content. This is because exploded content is vulnerable to the scanner trying to auto-deploy partially copied content. However, if you wish to change this behavior, you can go to the JBOSS_HOME/standalone/configuration/standalone.xml file, look for the 'deployment-scanner tag and change the deployment options as you like: 

<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" 
auto-deploy-zipped="true" auto-deploy-exploded="false"/>

By default, the application should be available under the following URL in your browser: http://localhost:8080/CKFinderJava/ Please note that the HTTP 8080 port of the sample URL is the default WildFly port. If you changed this value while configuring your WildFly installation, you will need to use a modified port value to run the sample application.

If you want to use international files names with CKFinder please see URI Encoding section which explains how to set UTF-8 in WildFly.

Go to the WildFly Getting Started and Administration Guide for more information about using this server.

JBoss EAP 6

The server can be started from the command line. Go to the JBoss Enterprise Application Platform (EAP) bin folder and run the following command:

  • Windows: standalone.bat or domain.bat
  • Linux: standalone.sh or domain.sh

JBoss EAP can run in two modes: standalone and domain. First one allows running a single standalone Server, while the latter is used to manage multiple physical (or virtual) machines from a single control point.
NOTE: In this example we are going to work with a standalone server.

The above two commands start server with its default configurations. If one wishes to start the server with one of alternative configurations, one should pass the --server-config argument with the server configuration file to be used. The example below shows how to run the full profile configuration with high availability:

  • Windows: standalone.bat --server-config=standalone-ha.xml
  • Linux: standalone.sh --server-config=standalone-ha.xml

You can read more about available JBoss configurations here.

After the server was started, log into administration console, click Deployments link, next click the Add button and select CKFinderJava.war file. Once CKFinderJava.war upload is finished, verify its runtime name and check the Enable checkbox. The Application is now ready to use.

Another way of deploying the CKFinderJava application is using JBoss Command Line Interface (CLI). It has to be first launched using the jboss-cli.sh or jboss-cli.bat script located in the EAP_HOME/bin directory. Once this is done, you can deploy applications as in the example given below:

  • In standalone mode: [standalone@localhost:9999 /] deploy ~/Desktop/CKFinderJava.war
  • In domain mode: [domain@localhost:9999 /] deploy ~/Desktop/ CKFinderJava.war --all-server-groups

NOTE: Either --all-server-groups or --server-groups with specified server groups must be used.

To learn more about CLI please see this link.

If your Server is running in the standalone mode, then aside from using the administration console and CLI, JBoss can also work in manual and auto deployment mode (this depends on your settings).
In the Auto-Deploy mode the scanner directly monitors the deployment content, available in EAP_HOME/standalone/deployments directory, automatically deploying new content and redeploying content whose timestamp has changed. It means that you can simply drop CKFinderJava.war into deployments folder and the application will be deployed.
To undeploy CKFinderJava in auto mode simply remove war file from deploy directory.
In the Manual deploy mode the scanner does not directly monitor the deployment content. Instead, the scanner relies on a system of marker files, which the user can add to or remove from deployment directory. These files serve as a sort of command telling the scanner to deploy, undeploy, or redeploy the content. You can learn more about marker files under this link.

To deploy CKFinderJava.war in manual mode, copy this file into the EAP_HOME/standalone/deployments directory and create the CKFinderJava.war.dodeploy file. CKFinder will be deployed and the CKFinderJava.war.deployed marker file will be created. To undeploy CKFinderJava simply remove CKFinderJava.war.deployed file.

Please note that by default JBoss EAP allows auto-deployment of zipped content and prevents auto-deployment of exploded content. This is because exploded content is vulnerable to the scanner trying to auto-deploy partially copied content. However, if you wish to change this behaviour, you can go to the EAP_HOME/standalone/configuration/standalone.xml file, look for the 'deployment-scanner tag and change the deployment options as you like: 

<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" 
auto-deploy-zipped="true" auto-deploy-exploded="false"/>

By default, the application should be available under the following URL in your browser: http://localhost:8080/CKFinderJava/ Please note that the HTTP 8080 port of the sample URL is the default JBoss EAP port. If you changed this value while configuring your EAP installation, you will need to use a modified port value to run the sample application.

If you want to use international files names with CKFinder please see URI Encoding section which explains how to set UTF-8 in JBOSS EAP.

Go to the JBoss EAP Getting Started and Administration Guide for more information about using this server.

GlassFish

The GlassFish server can be started from the command line. Go to the server bin folder and run the asadmin script. Next you need to start the domain which is a pre-requisite to upload the application or use the administrator's console. In this example we are going to use the test domain that is deployed with the servr. Run the start-domain command to start it.

The application can be uploaded to the server by using the command line or the administrator's console.

When using the command line, run the following:

  • deploy relativePath/CKFinderJava.war

Please note that the path to the CKFinder Java .war file is relative to the asadmin script that is located in the bin folder of GlassFish.

When using the administrator's console, log in and go to the Applications tab. Specify the location of the CKFinder Java .war file and set the application type to Web Application.

By deafult, the application should be available under the following URL in your browser: http://localhost:8080/CKFinderJava/

Please note that the HTTP 8080 port of the sample URL is the default GlassFish port. If you changed this value while configuring your GlassFish installation, you will need to use a modified port value to run the sample application.

By default, Glassfish has ISO parameter-encoding set, which may cause problems if your users want to use filenames with non-ISO characters. If CKFinder in your application is to be used worldwide, it is recommended to set UTF-8 for Glassfish. Please refer to the URI Encoding section for more details.

Go to the Oracle GlassFish 3.0 or, GlassFish 3.1 or GlassFish 4.x Server Quick Start Guide for more information about using this server.

Weblogic

The Weblogic Server (WLS) can be started from the command line. Go to the weblogic_main_folder/user_projects/domains/your_domain/bin folder and run the following script:

  • Windows: startWeblogic.cmd or startManagedWebLogic.cmd
  • Linux: startWeblogic.sh or startManagedWebLogic.sh

If Weblogic is in production mode then please remember that you need to specify the user name and password in order to run it.

As you probably know, Weblogic Server uses domains which are logically related groups of server resources. A domain can consist of an Administration Server and one or more Managed Servers, or of a single standalone server that acts as an Administration Server and runs deployed applications. In this example we are going to use a single standalone Administration Server.

After starting Weblogic, log into the Administration Console and click Deployments in the Domain Structure upper left menu. If WLS is in production mode, you need to click Lock&Edit first. In main panel click the Install button, specify the path to CKFinderJava.war, and click the Next button. Select the "Install this deployment as an application" option and press the Next button. In the last panel you can change the name of your deployment, the security model and the source accessibility. Once you are done, click the Finish button and CKFinderJava will be deployed. If WLS works in production mode, you will need to confirm all changes by clicking the Activate Changes button and start the application manually by selecting it and pressing the Start button.

By deafult, the application should be available under the following URL in your browser: http://localhost:7001/CKFinderJava/

The HTTP 7001 port of the sample URL is the default Weblogic Administration Server port. If you changed this value while configuring your Weblogic domain(s), you will need to use a modified port value to run the sample application.

Go to the Weblogic 11g or Weblogic 12c Documentation site for more information about using this server.

Retrieved from "https://docs-old.ckeditor.com/index.php?title=CKFinder_2.x/Developers_Guide/Java/Installation&oldid=7378"
This page was last edited on 5 November 2015, at 15:58.