Installation

Browsium Catalyst is simple to install — administrators need both Browsium Catalyst Configuration Manager and Browsium Client, while end users only need Browsium Client installed. This section provides details on the specific components of Catalyst, as well as information on how to manage Browsium Client installation in an enterprise environment.

Browsium Client is a lightweight, unified client agent that works with all modules in the Browsium browser management suite. Install Browsium Client once and enable Ion, Proton, and Catalyst services as required for your organization.

Catalyst Components

Browsium Catalyst is comprised of two main parts: a configuration manager tool for defining rules and settings, and a client for interpreting the configurations for end users. The client includes a Controller process and browser extensions for Microsoft Internet Explorer, Microsoft Edge, Google Chrome, and Mozilla Firefox.

• Catalyst Configuration Manager (Catalyst-Setup.exe)

Catalyst Configuration Manager (BrowsiumCatalystManager.exe) is used to create and manage Catalyst configurations (browsers, rules, and settings), which will ultimately be deployed to end user PCs. This application is not intended to be run by end users, so Catalyst-Setup.exe should not be installed broadly — installation of this package should be limited to system administrators, web application owners, or business unit managers.

• Browsium Client (Browsium-ClientSetup.exe)

Browsium Client is responsible for loading Catalyst configuration data and redirecting browser traffic based on that configuration. The client package should be installed on all Catalyst-licensed PCs in your organization. The package consists of two components:

• Browsium Controller

The Browsium Controller (BrowsiumController.exe) is the main component of the client infrastructure used by Catalyst to handle rules implementation and redirection. The Client consists of a background process/listener service that must be running for Catalyst to operate. Without this component, the browser extensions cannot communicate properly and redirection will fail to function properly. Browsium Management Service (BrowsiumService.exe) runs as a Windows service with System privileges to handle content loading for projects that require elevated permissions. Browsium Monitor (BrowsiumMonitor.exe) is responsible for ensuring that Controller is running reliably.

• Browsium Client Extensions for Microsoft Internet Explorer, Microsoft Edge (Legacy and Chromium), Google Chrome, and Mozilla Firefox

Browsium Client installs extensions to each browser to enable communication between the browsers and the Browsium Controller.

System Requirements

The following system specifications are required to run Catalyst.

• Microsoft Windows

  • Windows 10 (1607) or later

  • Windows Server 2008 R2 or later (for multi-user terminal servers)

• Microsoft Internet Explorer 8, 9, 10, or 11

• Google Chrome 39 or later

• Mozilla Firefox 52 or later (41 or later using Browsium legacy extension)

• Microsoft Edge (Legacy) 42 or later (machine must be domain joined)

• Microsoft Edge (Chromium) 80 or later (machine must be domain joined)

• Microsoft .NET Framework Version 3.5 SP1 or later (full version only)

• 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor

• 1MB or more system memory; 2GB when used on multi-user terminal servers

While Browsium Client can be installed on systems with less than 1GB of memory, users may experience performance issues.

Installing Browsium Catalyst Configuration Manager

This section covers the installation process for the Browsium Catalyst Configuration Manager. The Browsium Catalyst Configuration Manager is only required, and should only be installed, on systems for Administrator use and building deployment configurations. End users SHOULD NOT have the Configuration Manager installed. End users should only have the Browsium Client installed. Administrators will need the Browsium Catalyst Configuration Manager and the Browsium Client be installed on their systems for project development and testing.

The steps for installing Catalyst Configuration Manager are as follows:

1. Locate the Catalyst Configuration Manager Installation file (Catalyst-Setup.exe) and double click to run the program.

{width=“3.5712346894138234in” height=“2.7730479002624673in”}

2. Confirm you have read and agreed to the End-User License Agreement (EULA) by clicking ‘I agree to the terms in the License Agreement’ and Next to continue with installation.

{width=“3.5497987751531057in” height=“2.7564041994750657in”}

3. By default, the installer places the required files in
   C:\Program Files\Browsium\Catalyst Manager (32-bit systems) or
   C:\Program Files (x86)\Browsium\Catalyst Manager (64-bit systems) on the system drive.

{width=“3.515690069991251in” height=“2.7299179790026247in”}

Select an installation location and click Next.

4. Now you’re ready to install Catalyst Configuration Manager. Click Install.

{width=“3.4852876202974628in” height=“2.706311242344707in”}

Catalyst Configuration Manager installation requires Administrator rights so the installer may generate a UAC prompt before installing.

5. This screen will be displayed when the installation is complete and all necessary files have been configured. Click Finish and you are ready to begin working with Catalyst.

{width=“3.5290977690288714in” height=“2.7403291776027996in”}

Installing Browsium Client

Detailed information on installation and deployment of the Browsium Client package can be found in the Browsium Client Installation and Deployment Guide.

Upgrading from Evaluation to Licensed Version

If you have chosen to trial Catalyst in a proof of concept using the 30-day evaluation period, or simply started your deployment without a Browsium Client Management Server (BCMS) in place and now want to ensure all Catalyst clients function properly, you will need to have a BCMS in place.

Clients must contact the BCMS server to obtain authorization and continue functioning as licensed software. Failure to regularly connect to the BCMS server (at least once every 30 days) will result in the client machine becoming ‘unauthorized’ and the software will no longer function.

Upgrading clients to licensed status is simply a matter of configuring them to contact the BCMS server. If the BCMS server includes a valid license file, provided by Browsium, client communication with the BCMS will ensure registration and authorization happen automatically. Clients DO NOT need the license file deployed to any systems.

For more information about BCMS please see the Browsium Client Management System Administration Guide.

{width=“1.222069116360455in” height=“1.222069116360455in”}

Section Three

Introduction to the

Catalyst Configuration Manager

In this section, you will learn:

• More about Catalyst Configuration Manager

• How to manage browsers, rules, and settings in Catalyst Configuration Manager