24 If you want another name, you can configure the JNDI resource in the |
24 If you want another name, you can configure the JNDI resource in the |
25 WEB-INF/web.xml and META-INF/context.xml files. It is highly recommended to use |
25 WEB-INF/web.xml and META-INF/context.xml files. It is highly recommended to use |
26 the lightpit_app user which has less privileges to create the data source and |
26 the lightpit_app user which has less privileges to create the data source and |
27 leave the lightpit_dbo user for the database operator. |
27 leave the lightpit_dbo user for the database operator. |
28 |
28 |
29 4. Deploy the WAR file of lightpit |
29 4. Build and Deploy the WAR file of lightpit |
30 |
30 |
31 This is the most straight forward step. Just deploy the WAR file as you usually |
31 Build the WAR file with gradle. If your application server already provides |
32 do in your application server. |
32 the necessary runtime libraries for JSTL and PostgreSQL, leave the variable |
|
33 libsAreProvided = true during the build. Otherwise, set this variable to false |
|
34 and the libraries will be included in the WAR file. But keep in mind that some |
|
35 servlet containers, like Tomcat, are not so happy about this when hot redeploy- |
|
36 ments are performed. If you experience ClassDefNotFound errors after a hot |
|
37 redeployment, you should either provide the libs in your container or always |
|
38 restart the entire container after a redeployment. |
33 |
39 |
34 5. Configuring a web server and authentication |
40 5. Configuring a web server and authentication |
35 |
41 |
36 LightPIT can optionally detect the authenticated user. You may freely decide |
42 LightPIT can optionally detect the authenticated user. You may freely decide |
37 whether to enable authentication in your application server or put a web server |
43 whether to enable authentication in your application server or put a web server |