Update Manager Installation

Provides orchestrator server-based updates. 
You can update libraries/DLLs such as pre-built templates and custom libraries deployed on the server through the update manager.
The update manager can be run from a designer or a bot and helps users update each program.

1. After logging in the designer, click Menu > Help > Update Manager . This feature is not available in Stand Alone Designer.

Update manager on a bot, click About > Update Manager. This feature is not available in Attended Bot.
 If the status is Connected to the server, a user message window will pop up asking you to disconnect.

2. Click on the list of packages deployed to the server in the Update Manager pop-up window.

At the top of the screen, you will see the version information of the currently installed client. If a newer version of the client installation package is available on the server, a button will appear to start the installation of that client.

At the bottom, you'll find an 'Installable' tab, which shows a list of packages that can be installed, and an 'Install History' tab, which shows information about packages you've installed in the past. The "Installable" tab shows the number of packages that a user can install by a number of badges.

3. A checkbox is displayed at the beginning of the list of packages that are not installed; click on the check box; details of the DLLs included in the update package are displayed at the bottom of the line. 

 4. Check that the Install button at the bottom is activated.

5. Click the Install button. A confirmation message pop-up window is displayed.

6. Click OK. The selected package will start downloading.

7. The designer exits and starts updating when the download is complete.

8. When the update is finished, the designer will be restarted.

Generating Update Package Files

Creating Generic Update Package Files

You can create an update package file to deploy to the orchestrator server.

1. Run the BrityRPA_UpdatePackageGenerator.exe file with administrator privileges, the path where the designer is installed.

2. Specify the package name, type, version, application target, and files to be installed, which are required input values. If any required input values ​​are missing, the 'Create' button will not be activated.

3. You can create a subfolder structure by selecting New Folder from the right-click menu of the [Bot/Designer installation folder] item.

4. You can select Add Files from the right-click menu; you can add files to be included in the package.

5. Select the Create button to designate the package file name
and save it when the file addition is complete.

6. When the package is created successfully, the Create button changes to a Save button, you can save the currently edited content to the package file through Save. You can also create a new package file by changing the Create button if necessary.

Click the New button to initialize all package creation input values. Please note that all the content currently being edited will be lost.

7. Click the Load button. You can import the contents of the previously created package file. Please note that all the content currently being edited will be lost. When loading is complete, the Create Package button automatically changes to Always Save.

8. Deploy the update package you created to the server to make it available to the update manager.

See, Managing Client Installations for distributing the package files.

Generating Execution Engine Package Files

Real-time bot engine updates. Describe how to create update packages in the form of 'execution engines' to be utilized by features. The 'Execution Engine' update package is a package that can only be used by Bots. The version of the 'execution engine' package used for the real-time bot engine update function must be v2.1.1 or higher.

1. Uninstall the previously installed bot, and proceed with the next step.

2. Later, a normal verified bot is newly installed on the PC. At this time, remember whether you installed 32-bit or 64-bit. After the bot installation is complete, do not run the bot.

3. If required, also install via the installer any AddIns to be included in the bot execution engine. BrityRPA_AddIn_Installer_v 0.0.000.00000 This is a file in the .exe format. Like the bot installation file, this installer file must be a normal installation file that has been verified and officially distributed.

4. Run the update package creation program in the path where the 3.1.0 designer is installed and change the type to Execution Engine. This is the BrityRPA_UpdatePackageGenerator.exe file. Do not run the BrityRPA_UpdatePackageGenerator.exe file from the path where the bot is installed.

5. Open the pop-up menu by right-clicking on the first node in the Files to be Installed area, and click the Add Folder Sub-File button.

6. Select the installation path of the newly cleaned bot on your PC in step 2, and wait until all files are added to the Files to Install area.

7. Enter 1.0 for the protocol version; the value is fixed.

8. In Executable Version, enter the range of designer versions of processes or projects to run with this execution engine package. When the real-time bot engine update function works, this execution engine package will be utilized to run the projects created in the designer belonging to the version range. Projects created by designers outside of this version range cannot be executed in this execution engine package.

• A version range can specify a start and end version with ~.

• You can specify a specific version by typing a single version without ~.

• You can specify multiple such versions and version ranges.

• Each version range must be separated by , .

For example, the following version range represents a project created in the designer 2.0.000.00101 or a project created in the designer version between 2.5.000.00202~2.6.000.00303.

  . 2.0.000.00101, 2.5.000.00202~2.6.000.00303

9. For # version, enter the product version of the BrityRPA_BOT.exe file from the bot folder you installed in Step 1. You can find this value by checking the properties information of the file in File Explorer.

10. Enter the name of the appropriate execution engine package in the Package name if you include the previously installed 32-bit or 64-bit version and the version of the bot executable file.

The following is an example of the name of the recommended execution engine package: For the version part, enter the version of the actual execution engine package.

BrityRPA_BOT_Engine_x32_v3.0.600.00607

11. Click the Save New button to complete the creation of the 'Execution Engine' package.

12. Go back to step 1 and create the execution engine for 64-bit. Execution Engine packages for 32-bit and 64-bit, respectively, are required for proper distribution and management of the Execution Engine package. When creating a 64-bit execution engine, change the fields entered when creating a 32-bit package in the previous steps to 64-bit.