If not already done, download the Stardust features as described in the Installation Guide.
Apart from the Stardust installation, you only need a Tomcat installation to go through this tutorial. Refer to the Stardust Release Notes for details on the Tomcat version supported with the current release.
As a start some names of the product are described here. For an overview on the provided packages provided by Stardust, refer to the Installation Guide.
This is the general product name.
This name is used for the runtime component of Stardust.
To open the Stardust Process Workbench, start your Eclipse environment, where you installed the Stardust Process Workbench Eclipse plugins and features.
We will now add the following views to the desktop:
So, now we are ready to start the tutorial.
Before your business process can be executed, you must model its elements (activities to be performed, variable definitions, applications and resources) as well as the relationships between these elements. For this purpose Stardust provides the Stardust Process Workbench where you can define your processes by drawing diagrams. Diagrams in Stardust contain process definitions, on the basis of which other components of Stardust, e.g. the Stardust Portal, can control the enactment of your processes. The Process Workbench and the Stardust Portal will be introduced in the following sections.
In our ACME example we will use applications and data implemented in Java, which have to be integrated in the business model. We have prepared the applications and data classes so that you can proceed with this tutorial without having to implement the model-specific components yourself. To get the example resources, download the following ZIP file:
You find the resources in folder support-case.
In the following figure you see a screenshot of the complete ACME Workflow example model:
Figure: The ACME Workflow Model
Eclipse provides integration for the Apache Tomcat Web environment and this can be used for rapid Stardust deployments within Eclipse.
To establish Tomcat integration in Eclipse (this only needs to be done once for all successive deployments. It is not required for each Stardust deployment):
! Tip: If your Eclipse installation does not have Server in the list of available objects to create, you will need to update your environment with the necessary plug ins of the Eclipse Web Tools Project, or use the Eclipse installation which comes with the normal Stardust distribution.



If your Eclipse desktop does not yet have a view for Servers as shown below, select Window > Show View in the main menu (or select the Show View button in the left lower corner of your Eclipse window) and choose Other... > Server > Servers to open it.

For this tutorial we will use a Dynamic Web Project (from the Eclipse Web Tools Project). To create a new Dynamic Web Project, follow these steps in Eclipse:
Figure: Creating a Dynamic Web Project - Step 1
2.5,
as 3.0 is currently not supported by Stardust.
Figure: Set the dynamic web module version
Figure: Select the Stardust Portal
Figure: Set Build Path.


Figure: Change the perspective
A dialog opens to inform you to set a location for the repository path:

Figure: Repository Path Warning
Please set a repository path as described in the section Setting the Repository Path of the Document Service Integration Guide.
After Eclipse created the project, you see a new project folder in the Package Explorer view:
Figure: New Dynamic Web Project in the Package Explorer
! Tip: You can use different explorer in eclipse. If you like to see all files under your project open the Navigator view.
The next step is either to open an existing model or to create a new one. Both can be done in the Stardust Process Workbench. Since no model exists in our introductory scenario, we will proceed with creating a new model.
Three aspects are essential for a proper understanding of the notion and the function of a model:
To create a new model:
Figure: Creating a New Model
Figure: Fill in Model Name
An open (editable) version of the ACME Workflow Model has now been created.
If you wish to omit the modeling phase and just set up this scenario in a
minimum of time, you can import an existing model instead of creating one
manually. In the main menu use the option File > Import...
> Process Manager > Process Model. In the appearing
dialog, choose Stardust XML as Model Type and
select the file ACMEWorkflowModel.xpdl residing in your Stardust
installation in the directory examples/support-case/dat.
Now you are ready to start building diagrams. In the Process Workbench window you will find the Outline view area, organizing the processes in your model and the components used in or by these processes. The Package Explorer area will display your projects and the created model files.
Figure: Initial State of a Model in the Stardust Process
Workbench
Diagrams are principally bound to a single process definition and contain a series of activities with the information connected to these activities (activity performers, data and applications). With each newly created process definition, a default diagram for this definition is created. You can add an arbitrary number of diagrams to a process definition. To get more detailed information on diagrams please refer to the chapter Working with Diagrams of the Stardust Modeling guide.
The diagrams which you can see in the Outline view tree
under the model element (which is the Stardust icon root element) are intended
to visualize the hierarchies of participants in your model and the dependencies
among process definitions, e.g. a graph of a process with its sub-processes. In
this tutorial we want to direct your attention to diagrams bound to a single
process definition, so we will focus on the diagrams which appear in the tree
view after a process definition has been created.