Apache Tomcat 9.0

This topic describes how LumisXP should be installed on the Apache Tomcat 9.0 server.

Initially, you need to edit the server.xml file, located in the "%CATALINA_HOME%/conf" folder, including or changing the following configurations in the Connector elements that are used for accessing the application:

1. maxPostSize: By default, Tomcat only accepts 2MB of POST in forms. To increase this limit, this attribute should be included with the desired limit in bytes.
2. bindOnInit: By default, Tomcat starts listening for new connections while it is starting, blocking them until the application boot is complete. This creates unnecessary queuing of connections in it, and is especially detrimental in environments with multiple servers, where another Tomcat could be serving the queued connection if Tomcat did not accept the connection and thus the Load Balancer directed the connection to another Tomcat. To prevent Tomcat from accepting connections while the application is still starting, include this attribute with a value of false.

<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443" maxThreads="60" enableLookups="false" maxPostSize="2097152" bindOnInit="false" > </Connector>

Shared Libraries

Some libraries (files . JAR) need to be installed in the shared library area on the application server.

On Tomcat, simply copy the JAR files that are in the %LUMIS_HOME%/lib/shared folder to the %CATALINA_HOME%/lib folder.

Deployment

1. Change the file "setup/Tomcat/portal.xml" to indicate the correct path of the product installation: <Context path="/portal" docBase="C:/LumisPortal/www" crossContext="true">

   Where:

   • Path: context name. The name of the file also defines the context name (portal.xml);
   • docBase: path where the "www" folder is installed;
   • crossContext: allows the use of standard JSR-168 portlets in LumisXP. These are installed on the application server in separate contexts.
2. Place it in the Tomcat configuration directory: "conf/Catalina/localhost".

DataSource Configuration

It is possible to configure the Data Source to delegate to the application server the management of the connection pool with the database.

In the server.xml or portal.xml, the following configuration must be made:

<!-- For enabling the datasource in the Tomcat, add a tag similar to the example below inside the application's Context tag and put the jdbc driver JAR file inside tomcat/common/lib. If your JDBC driver does not support Connection.isValid method, must also be included in Resource the attribute validationQuery with a value that is a query that may be used to validate the connection. For example, for MS SQL Server could be used: validationQuery="select 1" More details and examples in http://tomcat.apache.org/tomcat-8.0-doc/jndi-datasource-examples-howto.html --> <Resource name="jdbc/portal" type="javax.sql.DataSource" maxTotal="100" maxIdle="30" maxWaitMillis="10000" auth="Container" driverClassName="my.database.Driver" url="jdbc:my:database:url" username="username" password="password" ></Resource>

Then, in the web.xml file, the following fragment should be added:

<resource-ref> <description>Portal DataSource</description> <res-ref-name>jdbc/portal</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref>

Remote IP Valve Configuration

This valve of Apache Tomcat serves to enable the correct integration of it with proxy servers (whether webservers or other proxies).
The valve is configured inside the Host definition in the server.xml.
Below is an example of how a Remote IP Valve can be configured.