The iteraplan .WAR file contains the following important configuration files:
- [iteraplan Server Context]/WEB-INF/applicationContext-spring-security.xml
This file configures authentication with the Spring Security component. The last section is of particular interest: this section describes calling of user and role data from a JNDI-connected database. With the factory settings, access is configured to a database schema corresponding to the iTURM schema (see Chapter 6.2). You need not change this file if you are using the accompanying iTURM implementation for authentication.
If you would like to connect iteraplan to your own identity management (e.g. LDAP), please contact iteratec GmbH via e-mail at firstname.lastname@example.org.
- [iteraplan Server Context]/META-INF/context.xml
The configuration file for the iteraplan context contains information such as the connection details for a JNDI-connected iTURM database which the Spring Security component uses for authentication (see previous section). If you use LDAP or another mechanism for authentication, you can skip this paragraph. The database schema is expected to be as described in section 6.2.
The first time the application is deployed, the file is copied to the directory conf/Catalina/localhost in the Tomcat installation folder under the name of the application (e.g. iteraplan.xml). Please bear in mind that only the settings in this file will be used, and those in context.xml will be ignored. Moreover, this file is not overwritten upon redeployment of the application, and therefore has to be edited manually or be deleted before redeployment.
- [iteraplan Server Context]/WEB-INF/web.xml
The configuration file for the iteraplan web application contains entries such as the session timeout value and the security settings. As a rule, there is no need to make changes to this file.
- [iteraplan Server Context]/WEB-INF/classes/iteraplan.properties
The iteraplan general configuration file contains the settings for "last modification logging", "audit logging" and reporting.
Most graphical reports as well as the mass update functionality have upper limits on the number of building blocks they process at once. This is intented to prevent overly large memory consumption or long processing times. In this file, you may increase these limits if your server has the necessary hardware resources available.
- [iteraplan Server Context]/WEB-INF/classes/iteraplan-db.properties
This configuration file contains connection information for the database used for loading business data records. It must have the schema defined by iteraplan. Please note that different versions of iteraplan will generally have different database schemas, though exceptions are possible. Be aware that some of the settings require a syntax specific to the database product you are using. Before changing these settings, make sure you understand their syntax.
- [iteraplan Server Context]/WEB-INF/classes/iteraplan-gui.properties
The configuration file contains the colour values which are offered during graphical report configuration. For all five digram types that iteraplan can generate, you can specify seven colour values (in hexadecimal RGB notation, like in HTML).
- [iteraplan Server Context]/WEB-INF/classes/log4j.properties
The Log4j Framework configuration file contains the settings for technical logging and for audit logging. Log file names and paths are configured here.