Deploy & Import Application

Estimated reading: 4 minutes 1222 views

Application deployment in Visual Guard refers to the process of deploying security configurations, such as roles, permissions, and user profiles, to specific applications or systems within an environment. This deployment ensures that security settings are applied effectively to the target applications, enabling consistent access control and enforcing security policies.

Below are the steps of how we can deploy an application

Step 1: Right click on the application and click on Deploy application.

Step 2: Once the setup shows up click on Next

Step 3: Select the option of either Export data in a deployment configuration file or Deploy in an exisiting repository, Click Next after selection

Visual Guard offers two main ways to deploy your security data: through a configuration file or directly to another repository. The configuration file method allows you to export and import security settings, making it ideal for controlled or offline deployments. On the other hand, deploying directly to another repository provides a faster and more seamless transfer, suitable for environments connected within the same network or system.

Export Data in a Deployment Configuration File
Deploy in an Existing repository

Export Data in a Deployment Configuration File enables you to generate a deployment configuration file containing the selected deployment settings and actions. This file can be saved and reused by the Deployment Tool to execute the same deployment configuration at a later time, eliminating the need to manually recreate the deployment settings. It also helps standardize deployment processes, ensuring consistency and reducing the risk of configuration errors across different environments.

Deploy an Existing Repository enables you to apply the selected deployment actions directly to an existing Visual Guard repository. This option executes the configured changes immediately on the target repository, ensuring that security configurations, settings, and other selected objects are deployed efficiently and consistently.

Step 4: Choose the Overwrite option and Deployment mode from the dropdown list provided.

Overwrite Option: Specify the options for deploying the application.

Do not overwrite an existing application: The process do not overwrite the application when it already exists in target repository
Overwrite when deployed version is more recent than existing application: The process overwrites the application only when its version is greater thann eixsting application in target repository
Overwrite when deployed version is equal to the existing application: The process overwrites the application only when its version is equal to the existing application’s version in target repository
Overwrite when deployed version is equal or more than the existing application: The process overwrites the application only when its version is equal to or more recent than the existing application’s version in target repository
Always overwrite an existing application: Always overwrites an application in target repository

Deployment Mode: Select the mode you would like to move forward with.

Refresh
Replace
Merge

Refresh: The process uses the deployed items to replace existing items and add any new deployed items. Existing items that are not included in the deployment remain unchanged, making this mode suitable for applying incremental updates.

Replace: The process removes all existing items from the target application before deploying all items from the deployed application. This mode ensures that the target application is an exact replica of the deployed configuration.

Merge: The process uses the deployed items to replace existing items, add new deployed items, and preserve all other existing items. This mode is ideal for updating specific configurations while retaining any custom or previously configured items in the target application. new deployed items and preserve all other existing items.

Check mark the point: Upgrade the minimum runtime version supported by the repository when needed. This allows the deployment process to upgrade to the minimum supported version of the visul guard runtime.

Click Next after selection

Step 5: Click on the Finish button to complete the deployment.

Note: You will be asked to provide a path to where the configuration file should be saved.

Import Application Configuration Files

Importing deployment configuration files refers to the process of loading external files containing predefined settings and configurations related to the deployment of software or applications. These files typically include details such as environment-specific configurations, deployment targets, versioning information, and other parameters necessary for deploying the software effectively. Importing deployment configuration files streamlines the deployment process by providing a standardized way to configure deployment settings, ensuring consistency and accuracy across different environments and deployment scenarios.

To import the configuration files follow the below steps

Step 1: Login to the repository and click on Import deployment configuration file.

Step 2: Select the path of where your configuration files are saved by clicking on the 3 dots and click OK

Step 3: Once the configuration is successfull you will receive a popup notifying the same

Deploy Via Deployment Tool

Deploy Repository

Deploy & Import Application

Import Application Configuration Files

Recently Viewed articles