Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Stardust/Knowledge Base/Deployment/Tomcat/RAD on Tomcat"
m (→Publishing & Auto Reloading) |
m (→Rapid Application Development) |
||
| Line 22: | Line 22: | ||
# Open launch configuration (upper left corner) | # Open launch configuration (upper left corner) | ||
# Go to Arguments > VM Arguments and apply '''-Xms128m -Xmx512m -XX:MaxPermSize=128m''' at the end | # Go to Arguments > 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. | ||
# Double click on your server configuration | # Double click on your server configuration | ||
| Line 37: | Line 37: | ||
# 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''' | ||
| + | |||
| + | 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. | ||
| + | |||
| + | # Double click on your server configuration | ||
| + | # Collapse Timeouts menu in the upper right corner | ||
| + | # Set start timeout to '''120 seconds''' and stop timeout to '''30 seconds''' | ||
Revision as of 05:40, 11 November 2011
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 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:
- Configuring the Server
- Configuring an Embedded Audit Trail Database
- Setting the Server Launch Configuration
- Web Application Deployment Descriptor
- Deploy the Dynamic Web Project to the Server
- Start Tomcat
- 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.
- Double click on your server configuration
- Open launch configuration (upper left corner)
- 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 a painful process. It's recommended to turn it off and trigger it manually whenever required.
- Double click on your server configuration
- 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)
- Disable auto reloading
Disable Auto Publishing
- Double click on your server configuration
- Collapse Publishing menu in the upper right corner
- 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 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.
- Double click on your server configuration
- Collapse Timeouts menu in the upper right corner
- Set start timeout to 120 seconds and stop timeout to 30 seconds