Skip to main content
Version: 4.2.0

Ugrade

Harmony Agent Adpater

  1. Stop the Bucher Suter HarmonyAgentAdapter Windows Service.
  2. Copy BucherSuter_HarmonyAgentAdapter-V_4_2_0-SFX.exe to the target server and execute it to copy the files of the Harmony RoutingAdapter into the following new directory:

C:\Program Files\BucherSuter\ConnectsHarmony

caution

Directory changed!

  1. Add the new configuration values as described in Changes to configuration filie in Harmony Agent Adapter Initialization File into your existing configuration file.
  2. Finally start the newly installed Bucher Suter HarmonyAgentAdapter Windows Service.

Harmony Routing Adapter

  1. Stop the Bucher Suter HarmonyRoutingAdapter Windows Service.
  2. Copy BucherSuter_HarmonyRoutingAdapter-V_4_1_1-SFX.exe to the target server and execute it to copy the files of the Harmony RoutingAdapter into the following new directory:

C:\Program Files\BucherSuter\ConnectsHarmony

caution

Directory changed!

  1. Add the new configuration values as described in Changes to configuration filie in Harmony Routing Adapter Initialization File into your existing configuration file.
  2. Finally start the newly installed Bucher Suter HarmonyRoutingAdapter Windows Service.

Changes to configuration file

This chapter outlines the configuration changes in the Harmony Agent Adapter in release 4.0. Since the component ActiveMQ was removed and Harmony Agent Adapter connects directly to Harmony Integration Server, the configuration values ActiveMQHost and ActiveMQPort were replaced with Host and Port.

Old parameters:

[Gate_harmony]
ActiveMQHost=localhost
ActiveMQPort=61616

New parameters:

[Gate_harmony]
Host=localhost
Port=61616

Additionally, there were configuration changes in the Harmony AgentAdapter in release 3.0. The new configuration parameters define the base configuration required for Harmony Agent Adapter.

In the b+s Connects for Oracle Service Cloud Harmony Agent Adapter, the Section [Gate_fin\MediaRouting] and [Gate_fin\MediaReroute] were introduced for the new MediaRouting solution over FinesseAPI. The values for EmailDomain and ChatDomain are commented out with a semicolon. Enable these values only if you use MediaRouting. They should not be enabled in a voice-only environment.

[Gate_fin\MediaRouting]
;EmailDomain=5001
;ChatDomain=5002

[Gate_fin\MediaReroute]
RoutingHostVarA=pv9
RoutingHostVarB=pv10
;RonaTimeoutEmailInSeconds=30
;RonaTimeoutChatInSeconds=30
;RoutingHostPort=8095
;RoutingHostHttps=false