A terminal applications subproject is created automatically when you create a new service flow project (see 1. Choosing a project name and location). You can also create additional terminal applications subprojects (see Adding a subproject to an existing service flow project).
A terminal applications subproject can contain three subfolders: a Hosts subfolder, an Operations subfolder, and a Messages subfolder. None of these subfolders is displayed in the EST Project Explorer unless the subfolder contains at least one artifact.
The following table summarizes key information about the subfolders in a terminal applications subproject. Notice that, in contrast to interface definition subprojects and nonterminal applications subprojects, which contain operations and messages, a terminal applications subproject contains host connections, screen operations and screen operations files, and screen messages:
| Item: | Descriptions: | ||
|---|---|---|---|
| The name of the subfolder: | Hosts subfolder | Operations subfolder | Messages subfolder |
| The type of artifact that the folder contains: | host connection |
|
screen message |
| The extension for this type of artifact: | .host | .wsdl | .sfmxsd |
| How to create an artifact: | Creating a host connection | Creating a screen operations files | Creating a screen message |
| The editor for editing a new or existing artifact of this type: | Host editor | Screen operations editor | Screen message editor |
| Links for more information: | Creating a host connection | Working with screen operations files | Creating a screen message |