Skip to main content
Jump to: navigation, search

Difference between revisions of "Stardust/Knowledge Base/Deployment/Tomcat/RAD on Tomcat"

 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Rapid Application Development  =
+
The Rapid Application Development approach is the fastest way to get started with Infinity Process Platform. It gives you a runtime at hand that consists of a Tomcat, Derby database and Spring managed process engine runtime. To use the RAD approach you need to at least download and install the Infinity Process Platform Eclipse [[Stardust/Knowledge_Base/Getting_Started/Installation|plug-ins]] and a [http://tomcat.apache.org/download-60.cgi Tomcat 6] server. You will find a detailed documentation about the Rapid Application Development approach of Infintiy Process platform here. This article summarizes the documentation a little bit to allow an even quicker setup of a RAD-based environment. The most important chapters of the documentation are:  
 
+
The Rapid Application Development approach is the fastest way to get started with Infinity Process Platform. It gives you a runtime at hand that consists of a Tomcat, Derby database and Spring managed process engine runtime. To use the RAD approach you need to at least download and install the Infinity Process Platform Eclipse [http://wiki.eclipse.org/STP/Stardust/KnowledgeBase/GettingStarted/Installation plug-ins] and a [http://tomcat.apache.org/download-60.cgi Tomcat 6] server. You will find a detailed documentation about the Rapid Application Development approach of Infintiy Process platform here. This article summarizes the documentation a little bit to allow an even quicker setup of a RAD-based environment. The most important chapters of the documentation are:  
+
 
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/configuration.html#configServer Configuring the Server]
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/configuration.html#configDatabase Configuring an Embedded Audit Trail Database]
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/configuration.html#serverLaunch Setting the Server Launch Configuration]
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/dynamic-web-proj.html Web Application Deployment Descriptor]
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/deployment.html#addProj Deploy the Dynamic Web Project to the Server]
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/deployment.html#startTomcat Start Tomcat]
+
#[https://infinity.sungard.com/documentation/ipp/6.0/topic/ag.carnot.docs.wst/html/wst-integration/deployment.html#deployModel Deployment of the Infinity Model]
+
  
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/configuration.html#configServer Configuring the Server]
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/configuration.html#configDatabase Configuring an Embedded Audit Trail Database]
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/configuration.html#serverLaunch Setting the Server Launch Configuration]
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/dynamic-web-proj.html Web Application Deployment Descriptor]
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/deployment.html#addProj Deploy the Dynamic Web Project to the Server]
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/deployment.html#startTomcat Start Tomcat]
 +
#[http://help.eclipse.org/index.jsp?topic=/org.eclipse.stardust.docs.wst/html/wst-integration/deployment.html#deployModel Deployment of the Infinity Model]
  
 +
<br>
  
 
From the very beginning you should apply some tweaks on server configuration which will make your live much easier.  
 
From the very beginning you should apply some tweaks on server configuration which will make your live much easier.  
  
'''Change Memory Settings'''
+
'''Change Memory Settings'''  
  
Make sure you memory settings for Tomcat runtime are sufficiently high.
+
Make sure you memory settings for Tomcat runtime are sufficiently high.  
  
# Double click on your server configuration
+
#Double click on your server configuration  
# Open launch configuration (upper left corner)
+
#Open launch configuration (upper left corner)  
# Go to Arguments &gt; VM Arguments and apply '''-Xms128m -Xmx512m -XX:MaxPermSize=128m''' at the end
+
#Go to Arguments &gt; VM Arguments and apply '''-Xms128m -Xmx512m -XX:MaxPermSize=128m''' at the end
  
'''Disable Auto Reloading'''
+
'''Disable Auto Reloading'''  
  
Automatic publishing and reloading of your project deployed at the server can be a painful process. It's recommended to turn it off and trigger it manually whenever required.
+
Automatic publishing and reloading of your project deployed at the server can be an anoying feature. It's recommended to turn it off and publishing and reloading of the web application manually when required.  
  
# Double click on your server configuration
+
#Double click on your server configuration  
# Switch tab from Overview to Modules at the bottom
+
#Switch tab from Overview to Modules at the bottom  
# Select your project and press Edit button (this only works if your project has allready been assigned to the server)
+
#Select your project and press Edit button (this only works if your project has allready been assigned to the server)  
# Disable auto reloading
+
#Disable auto reloading
  
'''Disable Auto Publishing'''
+
'''Disable Auto Publishing'''  
  
# Double click on your server configuration
+
#Double click on your server configuration  
# Collapse Publishing menu in the upper right corner
+
#Collapse Publishing menu in the upper right corner  
# Select Never publish automatically
+
#Select Never publish automatically
  
'''Increase Start and Stop Timeouts'''
+
'''Increase Start and Stop Timeouts'''  
  
The default timeouts are sometimes not sufficient to allow the server start completely. This especially happens in situations where you did much changes on your project code that need to be published to the server. To avoid Tomact not coming up, you should increase the start and stop timeouts from the very beginning.
+
The default timeouts are sometimes not sufficient to allow the server start completely. This especially happens in situations where you have many changes in your project that need to be published to the server are when your hard drive is under high load for other reasons. To avoid Tomact not starting within the limit, you should increase the start and stop timeouts.  
  
# Double click on your server configuration
+
#Double click on your server configuration  
# Collapse Timeouts menu in the upper right corner
+
#Collapse Timeouts menu in the upper right corner  
# Set start timeout to '''120 seconds''' and stop timeout to '''30 seconds'''
+
#Set start timeout to '''120 seconds''' and stop timeout to '''30 seconds'''

Latest revision as of 03:44, 25 June 2014

The Rapid Application Development approach is the fastest way to get started with Infinity Process Platform. It gives you a runtime at hand that consists of a Tomcat, Derby database and Spring managed process engine runtime. To use the RAD approach you need to at least download and install the Infinity Process Platform Eclipse plug-ins and a Tomcat 6 server. You will find a detailed documentation about the Rapid Application Development approach of Infintiy Process platform here. This article summarizes the documentation a little bit to allow an even quicker setup of a RAD-based environment. The most important chapters of the documentation are:

  1. Configuring the Server
  2. Configuring an Embedded Audit Trail Database
  3. Setting the Server Launch Configuration
  4. Web Application Deployment Descriptor
  5. Deploy the Dynamic Web Project to the Server
  6. Start Tomcat
  7. Deployment of the Infinity Model


From the very beginning you should apply some tweaks on server configuration which will make your live much easier.

Change Memory Settings

Make sure you memory settings for Tomcat runtime are sufficiently high.

  1. Double click on your server configuration
  2. Open launch configuration (upper left corner)
  3. Go to Arguments > VM Arguments and apply -Xms128m -Xmx512m -XX:MaxPermSize=128m at the end

Disable Auto Reloading

Automatic publishing and reloading of your project deployed at the server can be an anoying feature. It's recommended to turn it off and publishing and reloading of the web application manually when required.

  1. Double click on your server configuration
  2. Switch tab from Overview to Modules at the bottom
  3. Select your project and press Edit button (this only works if your project has allready been assigned to the server)
  4. Disable auto reloading

Disable Auto Publishing

  1. Double click on your server configuration
  2. Collapse Publishing menu in the upper right corner
  3. Select Never publish automatically

Increase Start and Stop Timeouts

The default timeouts are sometimes not sufficient to allow the server start completely. This especially happens in situations where you have many changes in your project that need to be published to the server are when your hard drive is under high load for other reasons. To avoid Tomact not starting within the limit, you should increase the start and stop timeouts.

  1. Double click on your server configuration
  2. Collapse Timeouts menu in the upper right corner
  3. Set start timeout to 120 seconds and stop timeout to 30 seconds

Back to the top