The following sections discuss prerequisites that must be performed before Infinity Process Platform can be deployed within a Tomcat servlet engine.
Before any activities can be done, download Tomcat from the Apache Tomcat Site . Once downloaded, install TOMCAT by unpacking the ZIP/TAR file onto the host server. The Tomcat installation directory referred to as %TOMCAT_HOME% from this point forward.
A basic understanding of Tomcat Administration and Web Application Archive (WAR) files is required from this point forward.
Infinity Process Platform provides predefined deployment configurations to prepare a deployment with Tomcat. You can achieve these Maven archetype templates matching your requirements by downloading from the Infinity Process Platform artifactory. The following deployment configuration for Tomcat is provided to prepare a Infinity Process Platform Portal WAR deployment for Tomcat 7:
Please refer to chapter Creating a Runtime Environment with Apache Maven in the Installation Guide section Stardust Archetypes of our Infinity Process Platform Wiki Maven/Basic Setup page for details on how to retrieve this configuration.
For DB2 you need to set up the data source configuration in the following way:
db2 catalog tcpip node <node_name> remote localhost server <db2 port number> remote_instance db2inst1
db2 catalog database <database> as <db_name> at node <node_name> authentication server db2 terminate
db2 list node directory db2 list database directory db2 connect to <db_name> user <username> using <password> db2 list tables db2 connect reset
db2 uncatalog database <db_name> db2 uncatalog node <node_name> db2 terminate
For information on the general setup of a DB2 audit trail database please refer to the chapter DB2 Audit Trail Database Setup.
To set up additional Jackrabbit VFS repositories, perform the following steps depending on whether transaction integration is required or not:
... <bean id="jackrabbitRepositoryStartupBean2" class="org.eclipse.stardust.vfs.jcr.spring.JackrabbitRepositoryStartupBean"> <property name="jndiName" value="jackrabbit.repository2" /> <property name="repositoryConfig" value="/WEB-INF/jackrabbit/repository.xml" /> <property name="repositoryHome" value="c:/tmp/repository2" /> </bean> ...
You can use Hazelcast for tuning via retrieving entities from in-memory cache. Hazelcast is a clustering and scalable data distribution platform. For detailed information on Hazelcast refer to http://www.hazelcast.com/product.jsp.
For details on tuning via an in-memory cache in Infinity refer to chapter Retrieving Entities from In-Memory Cache in the Developer Handbook.
The in-memory cache is turned on by default with the property below in your server-side carnot.properties file.
Infinity.Engine.Caching = true
If not, set this property explicitly.
To enable Hazelcast caching, add the following entries to your server-side carnot.properties file:
Infinity.Engine.Caching = true Infinity.Engine.Caching.CacheFactory = org.eclipse.stardust.engine.core.cache.hazelcast.HazelcastCacheFactory Infinity.Engine.Caching.Hazelcast.TxMode = rw Infinity.Engine.Caching.Hazelcast.ConnectionFactoryJndiName = HazelcastCF Infinity.Engine.Caching.Hazelcast.GlobalCacheName = ipp-2nd-level-cache
Refer to chapter Hazelcast Integration for Spring Environments for details on the required Spring configuration to setup Hazelcast in-memory cache in Spring-managed environments.
You have the following options to deploy Infinity on Tomcat:
Chapter How To deploy a IPP Portal Project created via Tomcat Archetype describes different variants on how to deploy a IPP Portal project, which was created via the Tomcat Archetype.