For a deployment inside Eclipse with Rapid Application Development, you proceed with the following operations:

The section Exporting the Web Project as WAR explains how to export your dynamic Web project as WAR file.

Deploy the Dynamic Web Project to the Server

To add your dynamic Web project to the server proceed as follows:

Select Add Project

Add Project

Added project to Tomcat

Start Tomcat

Setting the Default Web Browser

The usage of Stardust Portal via the internal Web browser is currently not supported. Set the browser to be used to your default Web browser:

  1. Select Window > Preferences in the main menu
  2. Select General > Web Browser
  3. Enable Use external Web browser
  4. Click Apply

Figure: Set to external Web Browser.

Starting the Server

To start the Tomcat server:

Start Tomcat
Figure: Start Tomcat

The Tomcat Status should now be Started.

Location of your published Web Application

You might like to browse to the folder where your Web application is published for troubleshooting and seeing what Eclipse actually published to the server. The Stardust dynamic Web project is not published to the server's webapps folder. Eclipse leaves your Tomcat installation unmodified. The Web application is published to a temporary folder. If you do not change the configuration, it is created inside your workspace under:

<your workspace>/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps

Starting the Server without valid License

In case you have not set the license for Stardust as described in section Setting the Stardust License of chapter Post-Installation Tasks in the Installation Guide, an according warning dialog opens.

No License Warning
Figure: No License Warning Dialog

To add a valid license in the preferences dialog, click Yes. The Process Manager preferences dialog opens, where you can browse to your valid license file.

Browse to your valid License File
Figure: Browse to your valid License File

In case you choose No, the server starts without valid license. Note that no model deployment is possible in that case.

Deploying the Process Model

Process execution requires prior deployment of the process model to the audit trail database. In Rapid Application Development environment you don't have to configure the connection parameters in the Also the Stardust environment settings, like CARNOT_HOME and CARNOT_WORK, are set automatically.

Start Tomcat as described in the previous section. Now your process model can be deployed:

Deploying a Model to the Stardust
    Runtime Environment
Figure: Deploying a Model to the Stardust Runtime Environment

The model deployment dialog prompts. Choose, if you like to create a new model version or to overwrite the last version of the model. Please refer to the chapter Working with Multiple Versions of the Operation Guide for details on multiple model versions in the runtime environment.

Deploy Dialog
Figure: Deployment of Model Version

If the following confirmation dialog appears, the deployment of the process model was successful and it is ready for use:

Deployment Confirmation
Figure: Deployment Confirmation

After a successful deployment of the process model in the dynamic Web project:

in the Stardust Portal.

Exporting the Web Project as WAR

After completing the development of a dynamic Web project, you have the option to export it as a WAR file for further usage in your production environment.

To export your dynamic Web project:

Export as WAR
Figure: Export Web Project as WAR File

Browse to Destination
Figure: Browse to Export Destination