The goal of the Blueriq Publisher is to simplify the distribution of applications over environments.

Typical setup

Components

The Publisher consists of the following components:

1. The Publisher Application application, used to publish applications from one environment to another.
2. The Publisher Client component, used to execute published applications on an environment.
3. The Publisher API, which has the same capabilities as the Publisher application. This API can be used to integrate the publishing process with other tools.

The following picture provides a graphical representation of the different components and their interaction. In this picture the Publisher can be replaced by another tool that uses the Publisher API. Also note that an application from Studio can be executed directly on the Runtime (in case of a Development environment), or needs the Publisher and the Publisher Client to be executed on the Runtime (in case of a Test/Acceptance/Production environment).

Usage

The publication of applications from one environment to another can be managed by restricting publishing actions to specific users. Additionally, the Publisher can be configured to enforce the "two-man rule," requiring that any publish action performed by a user must be approved by another user.

When an application is published from Studio, an export is created from the Studio repository and stored in the Publisher database of the target environment (e.g., the Test environment). When the application is subsequently published from Test to Acceptance, a copy of the application is transferred from the Publisher database in the Test environment to the Publisher database in the Acceptance environment. It's important to note that the application resides in each environment to which it is published.

To remove an application from an environment, it must be unpublished. This action deletes the application's corresponding database entry in that environment. However, this does not apply to the Studio (Development) environment, as the application will always remain in the Studio repository.