The Weave/Pathway integration provides a two-way link between Weave and Pathway. That is Pathway can call out to Weave to display information and Weave can call out to Pathway to display information.

For additional information about using the newer Weave Hub integration please see this page Weave Hub - Third-party Application Integration.

Client Workstation

The link between Weave and Pathway requires the installation of components on each client computer that will be requiring communication between Weave and ConfirmPathway.

The following two section sections outline the installation and configuration of these components.

...

Two Pathway specific .dll files, pathway.dll and weavepathway.dll, must be copied and registered on each client PC, along with the weave link components.

This should be performed using the regsvr32.exe application provided with Windows, e.g.

        regsvr32 pathway.dll
      
 regsvr32 weavepathway.dll

The Pathway map component, PathMap.ocx, integration components must also be installed on the client, this components is supplied with Pathway. PathMap.ocx by Infor and should be located at ...\Pathway\Prod\msc\PathMap.ocx in Pathway.Integration.Setup.exe at your Pathway installation location.

Configuration

The Pathway GIS integration must be configured to use Pathway.COMGIS1 as it's mapping component (weavepathway.dll implements Pathway.COMGIS1 ProgId)

Some versions of Pathway require an executable file to be entered as one of the configuration parameters, a dummy executable, WeaveLaunch.exe, can be use used if an executable is required.

Un-installation

The installation can be undone by using regsvr32 with the "/u" parameter, e.g.

        regsvr32 /u pathway.dll
   
    regsvr32 /u weavepathway.dll

...

Entities in Weave must be linked to one of the four levels, prop PROP, parc PARC, titl TITL and/or strt STRT, in Pathway.

Firstly the pathway namespace must be added to the config.xml file header (or a separate pathway.xml file can be created and included into in config.xml)

<?xml version="1.0" encoding="UTF-8"?>

<config xmlns="urn:com.cohga.server.config#1.0" xmlns:pathway="urn:com.cohga.pathway#1.0">
...
</config>

then the pathway configuration must be setup set up to link the pathway levels with the Weave entities

<?xml version="1.0" encoding="UTF-8"?>

<config xmlns="urn:com.cohga.server.config#1.0" xmlns:pathway="urn:com.cohga.pathway#1.0">

  <pathway:config>
    <link level="propPARC" entity="property"/>
    <link level="strtSTRT" entity="roads"/>

    <!-- Set the name of the Pathway database to launch if it's not already running -->
    <!-- this is the newer way of setting what Pathway has to be launched -->
    <database>Pathway</database>

    <!-- Optionally set the name of the Pathway application to launch if it's not already running -->
    <!-- this is the older way of setting what Pathway has to be launched, you should probably use database above -->
    <launch>C:\\Infor\\Pathway\\Demo\\msc\\Pathway.exe</launch>
  </pathway:config>

</config>

Client

Once the levels have been created the Pathway related actions can be added to the client configuration.

   <item action="com.cohga.client.actions.menuAction">
    <iconCls>icon-pathway_pathway</iconCls>
    <item action="com.cohga.pathway.Display" text="Display"/>
    <item action="com.cohga.pathway.SendQuery" text="Send Query"/>
    <item action="com.cohga.pathway.DisplayOther" text="Display Other"/>
    <item action="com.cohga.pathway.SendQueryOther" text="Send Query Other"/>
    <item action="com.cohga.pathway.CreateLink" text="Create Link"/>
    <item action="com.cohga.pathway.Return" text="Return"/>
  </item>

...