The following terms describe various components that apply to AppServer support in Progress Developer Studio for OpenEdge:
| Server | An instance of a server runtime. You can define many servers for a given runtime. For AppServer support in Progress Developer Studio for OpenEdge, a server is used to connect to OpenEdge Explorer and provides connection information, broker name, and publishing options for a particular AppServer. |
| Server configuration | A collection of files used to configure a running server. Typically, the configuration consists of a set of port numbers and other properties. |
| Server Runtimes (or runtimes) | The software application that executes as a server platform. For OpenEdge, this refers to the location of the OpenEdge installation that is used to communicate with OpenEdge Explorer and provide AppServer functionality |
| Modules | A collection of files used to organize content that is being
developed for a server. A module usually consists of a hierarchy of files that reside in the Eclipse workspace. Modules also have a many-to-many relationship with other modules, and the file hierarchy for modules does not indicate any specific module containment. An OpenEdge AppServer project is allowed one module, and an AppServer module is required for publishing code to a server. |
| Facets | A mechanism used to add project functionality that you can turn on or off. Within OpenEdge, you can use facets to add a specific module type to a project. When you add a facet to a project, the facet is used as a marker for performing certain setup requirements or for simply marking the project as a specific project type. |
For more information, see the details in overview to the Web Tools Platform Guide.