This class defines Ignite startup based on servlet context listener.
This startup can be used to start Ignite inside any web container.
This startup must be defined in web.xml
file.
<listener>
<listener-class>org.apache.ignite.startup.servlet.ServletContextListenerStartup</listener-class>
</listener>
<context-param>
<param-name>IgniteConfigurationFilePath</param-name>
<param-value>config/default-config.xml</param-value>
</context-param>
Servlet context listener based startup may be used in any web container like Tomcat, Jetty and etc.
Depending on the way this startup is deployed the Ignite instance can be accessed
by either all web applications or by only one.
Please consult class loading architecture documentation of your web container.
There are two ways to start Ignite on Tomcat.
- Ignite started when web container starts and Ignite instance is accessible only to all web applications.
- Add Ignite libraries in Tomcat common loader.
Add in file
$TOMCAT_HOME/conf/catalina.properties
for property common.loader
the following $IGNITE_HOME/*.jar,$IGNITE_HOME/libs/*.jar
(replace $IGNITE_HOME
with absolute path).
- Configure this startup in
$TOMCAT_HOME/conf/web.xml
<listener>
<listener-class>org.apache.ignite.startup.servlet.ServletContextListenerStartup</listener-class>
</listener>
<context-param>
<param-name>IgniteConfigurationFilePath</param-name>
<param-value>config/default-config.xml</param-value>
</context-param>
-
Ignite started from WAR-file and Ignite instance is accessible only to that web application.
Difference with approach described above is that
web.xml
file and all libraries should
be added in WAR file without changes in Tomcat configuration files.