After a successful installation open your Eclipse and configure your workspace to be able to use the Rapid Application Development. Therefore you need to define the server and audit trail database as described in the following sections.
Eclipse provides integration for the Apache Tomcat Web environment and this can be used for rapid Infinity Process Platform deployments within Eclipse. Install Apache Tomcat, e.g. from http://tomcat.apache.org/download-70.cgi. Please refer to the Infinity Release Notes for details on the supported Tomcat version.
To establish Tomcat integration in Eclipse:
Figure: Define a New Server
Figure: Choose Tomcat version
Figure: Browse to Installation Folder
Open the Servers view to see the server listed:
Figure: The Server View
This server configuration can be used for multiple Web projects.
The database can be (re)used for multiple Web projects. When you have more than one active process model, each one needs its own audit trail database. The Database to be used drop-down box is used to select the audit trail matching the active project. The Manage existing Audit trail databases link allows you to add or delete databases as needed.
To create a new audit trail database:
Figure: Create a New Audit Trail Database
Figure: Enter Database Name
Note, that there will be a pause as Infinity Process Platform creates the database!
A database schema for the audit trail is created automatically with the default name carnot. You find the new audit trail displayed in the Package Explorer:
Figure: Audit Trail in Package Explorer
If you use an audit trail database in RAD that has been created with IPP
version earlier than 9.0, you have to deselect and select the database from the server
configuration page. Republishing the server updates the Tomcat
file with the new resource definition entry for embedded database usage.
server.xml file, you should then see the following entry in the
<Resource name="AuditTrail.DataSource" description="Embedded Derby database for IPP" factory="org.apache.tomcat.jdbc.naming.GenericNamingResourcesFactory" type="org.apache.derby.jdbc.EmbeddedXADataSource" databaseName="carnot" user="carnot" password="ag" />
In some cases it might happen that your database created in the Rapid Application environment is incomplete. In this case try one of the following or a combination:
To avoid running out of PermGenSpace, increase the size of the permanent generation memory by setting the -XX:MaxPermSize argument in the run configuration for the server.
To set the server configuration:
Figure: Setting Server Arguments for Tomcat
Please note that you might increase the maximum perm size according to your requirements.