Contact usRequest a demo

This document describes version 6 of Unblu. If you’re using the latest major version of Unblu, go to the documentation of the latest version.

The support period for version 6 ended on 29 August 2023. We no longer provide support or updates for this version. You should upgrade to the latest version of Unblu.

Order of deployment — no cluster

A complete list of all requirements is a handy thing to have before embarking on a major integration.

For clarity’s sake the examples herein assume an installation with Apache 2 and Tomcat but you may use any web and application server of choice.

Before you start you should have Apache 2, apxs and your application server already deployed.

To install Unblu in one of the configurations outlined in this guide you need to deploy the following components:

  • The collaboration server

  • The database; see Database configuration

  • An optional filter (SecureFlow Manager) on the reverse proxy server which identifies co-browsing requests and forwards them to the collaboration server; see SecureFlow Manager

The three items above should be deployed first. The remaining features can be deployed according to the most convenient path for your particular system. Although it may make sense to deploy the Agent Desk as soon as possible after the steps above in order that you can get Unblu up and running.

To complete the installation so that your agents can start engaging with visitors, you must set up the [Agent Desk.

After these steps are completed you must configure the collaboration server. Note that configuration is outside of the scope of this concise setup guide. See Configuration and Configuration Properties.

After initial setup and configuration you can change the Agent Desk configuration at any time using configuration files or by setting values on-the-fly through the Agent Desk GUI.

See also

  • For information on deploying Unblu in a cluster environment, refer to Cluster deployment.