Jump to: navigation, search

Installing and Deploying Genesys Co-browse

Important
Genesys recommends that you first install Co-browse in a test environment. This will allow you to customize and test Co-browse before moving it to your production environment.
Objective Related procedures and actions
1. Prepare your deployment.

Review Related Components and Sizing Information.

2. Install Genesys Co-browse Server. See Install Genesys Co-browse Server for details.
3. Install the related plug-in for Interaction Workspace.

Install the Genesys Co-browse Plug-in for Interaction Workspace to enable co-browsing features in Interaction Workspace. See Install the Genesys Co-browse Plug-in for Interaction Workspace for installation details.

4. If you are using Genesys Workspace Web Edition, configure it to work with Co-browse.

See Configure Genesys Workspace Web Edition to Work with Co-browse for configuration details.

5. Load the certificate and private keys into the Java and Jetty keystores.

See Loading Certificate for SSL for details.

6. Configure a Cluster of Chat Servers.

Complete the procedures on the Configure a Cluster of Chat Servers if your solution includes more than one Chat Server.

7. Add the Co-browse JavaScript snippet to your website.

See Website Instrumentation for details.

8. Configure a cluster of Co-browse servers.

See Configure a Cluster of Co-browse Servers for details.

9. Start and stop Genesys Co-browse Server.

See Start and Stop Genesys Co-browse Server for details.

10. Import the reporting templates. You can use the provided Genesys Co-browse Sample Reporting Templates for real-time and historical reporting. See Genesys Co-browse Reporting Templates for details.
11. Test and troubleshoot. Complete the procedures on the Testing and Troubleshooting the Co-browse Solution page to ensure that your Co-browse solution is properly configured. This page also provides solutions to common problems that you might encounter while testing the Co-browse solution.
This page was last edited on May 24, 2016, at 20:56.
Comments or questions about this documentation? Contact us for support!