Weave Hub

...

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

...

Here is the latest installers are the time of this update which may be newer than the one in the Weave installer

Weave Server Components

To provide support to the rest of the Weave client, an updated version of the com.cohga.client.interop bundle, at least version 3.0.0, must be installed in the Weave server. This updated bundle provides code that the third-party components within the client will use to communicate with the Weave Hub. Additionally, the Weave Hub integration must be enabled via a plugin to the client configuration. This can be done by adding the weave.hub plugin to the client as shown below. 

...

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.

...

To help provide suitable log output for a Support ticket, please follow this process:

1. Kill the WeaveHub.Core.exe process via Task Manager.

2. Stop the Weave Hub Service.

3. Ensure that the WeaveHub.Core.exe and WeaveHub.Service.exe processes are not running in Task Manager.

4. Start DebugView or clear the display if it's already running.

5. Run the WeaveHub.Service.exe program in the C:\Program Files\Cohga\WeaveHub\Core directory, it will open a new window.

6. Run the WeaveHub.Core.exe program in the C:\Program Files\Cohga\WeaveHub\Core directory, it will show the icon in the task bar.

7. Start a new browser session and open a Weave client that has the Weave Hub plugin enabled and wait for it to complete its startup.

8. Use the File|Save menu in DebugView to export the log file and send that to the Support team.

9. Stop Debug View.

10. Press any key inside the window that opened when you ran WeaveHub.Service.exe to shut it down.

11. Restart the Weave Hub service.

Microsoft Edge

Because of security restrictions Microsoft has implemented for Edge Weave Hub will not work unless the following command is run as an administrator on each client PC:

...