Weave Hub
...
Note that currently Weave Hub is supported on 32 and 64 bit Windows but currently only 32 or 64-bit Weave Hub add-ins can be used at one time, and it requires at least version 4.6.1 of the .Net Framework to be installed (which should be installed by default on Windows 10 or later and installed via a Windows Update for Windows 7 since around January 2016). The choice between the 32 or 64-bit installation depends upon the third-party applications that you use, not the operating system or browser. If you run a 32-bit version of a third-party application, even if it's on a 64-bit operating system with a 64-bit browser, then you'll need to use the 32-bit version of Weave Hub and the associated plugins. Note this can be an issue if you run a mix of 32 and 64-bit third-party desktop applications. There is now only one version of the installer and should work on both 32 or 64 bit operating systems.
The diagram below shows parts required for Weave Hub and how the communication between them occurs.
...
Unless the icon has been hidden, via the right click menu, you should see the following icon in the Windows system tray when the Weave Hub client component is running
...
| Anchor | ||||
|---|---|---|---|---|
|
Here is the latest installers are the time of this update which may be newer than the one in the Weave installer.
| View file | ||
|---|---|---|
|
...
In addition to the Weave Hub add-in, the installer also installs and registers the component required for Pathway to communicate with Weave, Pathway.COMGIS (either Pathway.COMGIS1 or Pathway.COMGIS2). The Pathway.COMGIS component works by sending messages to Weave Hub, which Weave Hub then passes on to the Weave client for processing.
The Pathway integration components must also be installed on the client, this is supplied by Infor and should be located at ...\msc\Pathway.Integration.Setup.exe at your Pathway installation location (which is generally a network share).
Weave Server Components
For the client to utilise the newer Weave Hub integration the com.cohga.weave.pathway bundle must be updated, to at least version 3.0.0. The updated bundle provides the same functionality as the previous version of the Pathway integration but uses the Weave Hub API to perform the communications. To utilise the updated actions in the client, the id of the actions need to be updated. Previously, for example, the action for sending the current selection to Pathway had the id of com.cohga.pathway.Display, and then com.cohga.pathway2.Display (when the actions were updated from using ActiveX to JavaScript). If you wish to utilise Weave Hub, the id will be com.cohga.pathway3.Display. Note that as was the case previously, the Pathway actions can be added directly to a toolbar or added within their own menu.
...