Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: A framework for using metadata to describe user interface elements and for interactions of the user interface elements with an end user and/or with data source(s) that store configuration data. The metadata can be used to generate a settings UI and code that manages the UI such as gathering user input, handling UI events, validating collected data, handling errors and warnings, managing interactions between different UI controls, and the like. A computer-implemented system that facilitates a settings user interface can include a code generation component that employs the stored metadata to automatically generate the settings UI and code that manages the UI. The code generation component provides the generated code to a data source component that interacts with the data source(s). The settings UI is displayed to an end user via a user interface component.

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: A framework for using metadata to describe user interface elements and for interactions of the user interface elements with an end user and/or with data source(s) that store configuration data. The metadata can be used to generate a settings UI and code that manages the UI such as gathering user input, handling UI events, validating collected data, handling errors and warnings, managing interactions between different UI controls, and the like. A computer-implemented system that facilitates a settings user interface can include a code generation component that employs the stored metadata to automatically generate the settings UI and code that manages the UI. The code generation component provides the generated code to a data source component that interacts with the data source(s). The settings UI is displayed to an end user via a user interface component.