CKFinder 2.x/Developers Guide/Java/Installation - Revision history

J.swiderski at 14:58, 5 November 2015

2015-11-05T14:58:54Z

J.swiderski at 08:30, 4 November 2015

2015-11-04T08:30:25Z

J.swiderski at 17:17, 3 November 2015

2015-11-03T17:17:29Z

J.swiderski at 15:46, 3 November 2015

2015-11-03T15:46:44Z

J.swiderski at 15:33, 3 November 2015

2015-11-03T15:33:43Z

J.swiderski at 22:43, 2 November 2015

2015-11-02T22:43:59Z

J.swiderski at 22:37, 2 November 2015

2015-11-02T22:37:01Z

J.swiderski at 22:32, 2 November 2015

2015-11-02T22:32:35Z

J.swiderski at 21:22, 2 November 2015

2015-11-02T21:22:30Z

J.swiderski at 16:22, 2 November 2015

2015-11-02T16:22:24Z

@@ Line 36: / Line 36: @@
 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-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.
@@ Line 92: / Line 94: @@
 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 on WildFly.
+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.
@@ Line 135: / Line 137: @@
 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 on 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 in JBOSS EAP.
 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.

@@ Line 94: / Line 94: @@
 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 WildFly.
-Go to the JBoss EAP [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.
+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 ===

@@ Line 54: / Line 54: @@
 === WildFly ===
-The server can be started from the command line. Go to the WildFly bin folder and run the following command:
+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>
@@ Line 66: / Line 66: @@
 You can read more about available WildFly configurations [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide#GettingStartedGuide-WildFly8Configurations 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 <code>CKFinderJava.war</code> file. Once CKFinderJava.war upload is finished, verify its runtime name, check the '''Enable''' checkbox. The Application is now ready to use.
+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.
-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 the WildFly <code>bin</code> directory. Once this is done, you can deploy applications as in the example given below:
+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>
@@ Line 80: / Line 80: @@
 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].
-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>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.
 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:
@@ Line 94: / Line 94: @@
 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 WildFly.
-Go to the WildFly [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide Documentation] site for more information about using this server.
+Go to the JBoss EAP [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 ===
@@ Line 109: / Line 109: @@
 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, 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, check the '''Enable''' checkbox. 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). It has to be first launched using the <code>jboss-cli.sh</code> or <code>jboss-cli.bat</code> script located in the JBoss EAP <code>bin</code> directory. Once this is done, you can deploy applications as in the example given below:
+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 domain mode:''' <code>[domain@localhost:9999 /] deploy ~/Desktop/ CKFinderJava.war --all-server-groups</code>
@@ Line 123: / Line 123: @@
 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 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:
@@ Line 133: / Line 133: @@
 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 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.
+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 on JBOSS EAP.
-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] sites for more information about using this server.
+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 ===

← Older revision		Revision as of 15:46, 3 November 2015
Line 95:		Line 95:

	Go to the WildFly [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide Documentation] site for more information about using this server.		Go to the WildFly [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide Documentation] site 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>
		+	* Linux: <code>standalone.sh</code> or <code>domain.sh</code>
		+
		+	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.
		+
		+	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>
		+	* Linux: <code>standalone.sh --server-config=standalone-ha.xml</code>
		+	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, 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, 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 <code>jboss-cli.sh</code> or <code>jboss-cli.bat</code> script located in the JBoss EAP <code>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 />
		+
		+	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 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>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 />
		+	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.
		+
		+	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 lang="xml">
		+	<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 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 on JBOSS EAP.
		+
		+	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] sites for more information about using this server.

	=== GlassFish ===		=== GlassFish ===

@@ Line 71: / Line 71: @@
 * '''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> must be specified.<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://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-CommandLineInterface link].

@@ Line 53: / Line 53: @@
 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.
-=== JBoss 7===
+=== WildFly (former JBoss AS)===
-The server can be started from the command line. Go to the JBoss bin folder and run the following command:
+The server can be started from the command line. Go to the WildFly bin 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>
-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 />
+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.
-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>
 * 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 WildFly configurations [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide#GettingStartedGuide-WildFly8Configurations 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, select '''Upload a new deployment''' checkbox and select <code>CKFinderJava.war</code> file. Once CKFinderJava.war upload is finished, verify its runtime name, 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 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 the WildFly <code>bin</code> directory. Next you can deply 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 must be specified</code>.<br />
+'''NOTE:''' Either <code>--all-server-groups</code> or <code>--server-groups</code> must be specified.<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://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-CommandLineInterface 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, 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/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 in the "Marker Files" section available under this [https://docs.jboss.org/author/display/WFLY8/Application+deployment 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.
-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 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:
 <source lang="xml">
@@ Line 89: / Line 89: @@
 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 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 on JBOSS.
+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 WildFly.
-Go to the JBoss AS7 [https://docs.jboss.org/author/display/AS7/Getting+Started+Guide Documentation] site for more information about using this server.
+Go to the WildFly [https://docs.jboss.org/author/display/WFLY9/Getting+Started+Guide Documentation] site for more information about using this server.
 === GlassFish ===

@@ Line 22: / Line 22: @@
 * Jetty 9,
 * WildFly (former JBoss AS) 8-9,
-* JBoss EAP 6.4.0,
+* JBoss EAP 6,
-* GlassFish 3.0-4.1,
+* 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.

@@ Line 47: / Line 47: @@
 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>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>
@@ Line 113: / Line 113: @@
 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 ===