Deployed Configurations

Contents Hide

  

The management of multiple BEPs on a BrightServer instance is handled by the Deployed Configuration panel, which is available for each server instance registered under the 'Servers' panel of BrightBuilder. This panel allows for server configurations, deployed onto the server as BEP files, to be activated and utilised by users synchronising to the server.

For more information on the concept of activation/deactivation of BEPs for BrightServer instances, along with concepts of default configurations, please refer to the BrightServer Project Deployment chapter of this document.

The panel is organised in two frames; the left displays all projects of the same name, while the right displays all iterations of the deployment. Initially, the right hand side of the panel will be empty until a project is selected.

Deployment Information

Selecting a server configuration name on the right hand panel will populate the deployment table on the left hand side of the panel. This table will detail read-only information regarding the deployment history of the solution selected, including its current activation status.

For each deployment, the information displayed in the columns are as follows:

Deploy Version : The time the deployment was uploaded to the server.

Time Deployed : The time the file was uploaded to the BrightServer instance.

Deployed By : The user name of the system admin who uploaded the control.

Status : 'Active', or no value. '[Default]' is also appended to the string, indicating it's the default BEP used. Active configurations will additionally be highlighted in green, while disabled configurations will display with a white background. If the configuration could not be loaded successfully, the row will be highlighted in red.

Modified : The time the configuration was last made active/inactive, or made default. This field is initially blank if no activations/deactivations have been made on the deployment.

Modified By : The user account which was used to make the last modification.

Description : String value populated on BEP deployment to BrightServer, typically used to identify the server configuration version release. For more information, please refer to BrightServer Project Deployment > Configuration Deployment

All the table fields may be sorted in ascending or descending order, by tapping on the column headers.

Deployment Actions

Deployments may be activated/deactivated or made as default through this panel. Selecting a row in this table will activate available actions which may be performed on the deployment.

Get Selected Version - This button will open a folder picker, which when specified will be written to with the BEP selected.

Activate/Deactivate - Will activate or deactivate the currently selected configuration. When syncing, the server will redirect any deactivated or invalid configurations to the default one. Please refer to BrightServer Project Deployment > Activated Configurations for more information on this state.

Make Default - Sets a deployment across the server. If there is a current default selection, this status will be removed after the confirmation dialog has been confirmed. Please refer to BrightServer Project Deployment > Default Configuration.

Delete Selected Version - Deletes the selected configuration on the server. This may only be performed if the configuration has been deactivated, and is not assigned to any users on BrightServer.

Refresh - Loads the current state of deployments on the server.

Changes to this screen will take effect immediately on BrightServer. If this screen is opened for a BrightServer instance which does not support multiple BEP deployments, an error will occur and the screen will display no data.