Rational Developer for System z

About service flow projects

A service flow project provides an organizational framework for the source files and the generated files associated with a service flow.

A service flow project contains a diverse group of artifacts that are organized within a predefined set of three folders and four subprojects, each folder or subproject dedicated to a particular class of artifact. (Within each subproject are subfolders, each dedicated to a particular subclass of artifact.)

The distinction between a folder and a subproject is as follows: All of the artifacts contained in the three folders and the four subprojects are available for use throughout the service flow project to which they belong.

A service flow project and its folders and subprojects are displayed in the EST Project Explorer view (see The EST Project Explorer) of the Enterprise Service Tools perspective (see The Enterprise Service Tools perspective).

The EST Project Explorer does not display a folder if the folder is empty (for example, the Flows folder is not displayed if you have not created a flow). When the first artifact is created for a folder, then the EST Project Explorer automatically displays the folder.

You can create multiple service flow projects within the EST Project Explorer. However, each service flow project is self-contained and cannot reference resources in another service flow project.

Although the hierarchical appearance of the service flow project, folders, subfolders, and subprojects displayed in the EST Project Explorer is reminiscent of the hierarchical appearance of a file system, you should realize that the EST Project Explorer presents an abstract view of the data in your service flow project, not the actual file structure.

To see the actual file structure of your workspace, look in the Navigator view (see Opening or reopening a view). You may sometimes wish to use the workspace to store a file so that you can later import the file into the Enterprise Service Tools.


Feedback