| At line 39 removed one line |
| !!!Installation |
| At line 41 removed one line |
| !!J2EE Install |
| At line 43 removed 39 lines |
| the latest stable version of JSPWiki is now available as a Web Start Application Installer at the following URL: [JSPWiki on magpie|http://www.javaeestore.org/appstore/wiki/jspwiki.html]. Simply click on the 'launch' button to install JSPWiki on a new tomcat or an already existing tomcat on your system. |
|
| !!Easy Install |
| JSPWiki is designed to "drop in" to your favorite servlet container and will run without much customization. |
|
| To install JSPWiki, just drop the {{JSPWiki.war}} file into your servlet container's web application directory. For example, on Tomcat this folder is {{''$CATALINA_HOME''/webapps}}. |
|
| Next, point your browser to {{http://''myhost''/JSPWiki/Install.jsp}} and follow the on-screen directions. The installer will ask you where you'd like to store wiki pages, put log files, and a few other things. It will also set up a privileged user account that you will use to manage the wiki. After that, you should restart the JSPWiki webapp (or the container) and you should be ready to start using your new wiki. |
|
| By design, the JSPWiki installer page offers only a limited number of configuration options, JSPWiki's other default settings should be sufficient to get you started. By default: |
| * the default login configuration and security policy is loaded automatically |
| * anonymous users can edit pages and create user profiles |
| * users log in with a login name and password |
| * user identities are stored in an XML file inside WEB-INF |
| * wiki groups are stored in an XML file inside WEB-INF |
| * JSPWiki relies on its own authentication and authorization system to manage security, and does not rely on container-managed security |
|
| The default settings allow users to create profiles, create pages and groups, and create page ACLs. It's good for a workgroup or small intranet that needs only a single wiki, and it requires no container configuration. If you want to use JSPWiki in a real production environment, you will want to read the ''Advanced Installation'' section (next). |
|
| In some cases, particular web containers require a small amount of configuration to work properly. See the ''Container Notes'' section of this page for details. |
|
| Security is the most common configuration issue first-time JSPWiki deployments. JSPWiki has a built-in diagnostic page, at {{http://''myhost''/JSPWiki/admin/SecurityConfig.jsp}} that can help troubleshoot typical problems. For more installation help, see [Troubleshooting]. |
|
| !!Easy Windows Installation |
| [Simple JSPWiki] |
|
| !!Advanced Installation |
| !Configuring container authentication |
| As described in the [security documentation|Wiki.Admin.Security] JSPWiki authenticates users in via either of these methods: |
| * __Custom authentication__, which looks up and validates the user's id and password against those stored in JSPWiki's UserDatabase |
| * __Container authentication__, which relies on the servlet container to perform the authentication and supply credentials |
|
| In many corporate environments, container authentication is the preferred method. Depending on the container's realm configuration, this sharply expands the range of authentication mechanisms available to JSPWiki. Many containers support LDAP, database, Kerberos, SecurID, Shibboleth, SAML and NT domain controller authentication among others. JSPWiki is smart enough to detect whether you are using container authentication. To set up container authentication, you must: |
| 1. Configure your container's authentication realm |
| 2. Uncomment the {{<security-constraint>}} block in JSPWiki's {{web.xml}} file. |
| See the [security documentation|Wiki.Admin.Security#IntegratingJSPWikiWithContainerManagedAuthentication] for more details on how to do this. |
|
| !Locking down your wiki |
|
. Use this wiki only for improving the documentation.