Deployment involves manual configuration of your Tomcat context and the copying of the application resources into the target directory. Developers should be aware that the build process (using the developer profile) will create a local deployment target accessible from within Eclipse.

Configuration of Tomcat requires an application context be configured pointing to the directory where you have deployed your application assets. Practices vary with some administrators preferring to put this context into the server.xml file and others preferring to place it separately under the Catalina engine directory tree. Either way your context should resemble something of the form:

			<Context path="/olat" 
				docBase="/path/to/olat"
					debug="4" reloadable="false" />

You may now deploy your application from either the administrative or the manager consoles within Tomcat, or by restating your Tomcat instance (which is often the preferred approach if you are using the CATALINA_BASE methodology).

You can access your deployed application by visiting http://tomcat_host:tomcat_port/olat in your browser (if you are accessing the instance from behind a reverse proxy then your should use your virtual host name.) By default you can either login as administrator (password olat) or as author (password test). The former has full administrative rights and we strongly recommend that you change the password immediately by navigating to 'Home', 'Settings' and 'Password'. See the tab 'User Management' for a list of all test users (all with password 'test').

Be aware that OLAT does not yet work deployed as an unpacked war file due to some issues with servletcontext methods we use. Tomcat comes with unpack war files set to true as default.