Integration with Pathway
- Shaun Forbes
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 Pathway.
The following two sections outline the installation and configuration of these components.
Installation
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 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.
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 used if an executable is required.
The WeaveLaunch.exe can be found here WeaveLaunch.exe if 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
And, also removing the PathMap.ocx registration.
Server
Configuration
Server
Entities in Weave must be linked to one of the four levels, PROP, PARC, TITL and/or 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 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 set up to link the pathway levels with the Weave entities
Client
Once the levels have been created the Pathway related actions can be added to the client configuration.
Pathway Configuration
The configuration of Pathway itself must be done via the Pathway application.
Go to the GIS Product Parameter screen
From there edit the Generic COM GIS Interface
You need to set the GIS Layer and GIS Reference Field values for any items you wish to be able to send to Weave.
Also you need to set the window title and startup url in the Parameters. These two values are separated by a verticalbar (|), and the first value, the window title, is the text at the start of the Internet Explorer window title which the link uses to locate a running Weave browser window. The second part is the startup URL for Weave for use when there isn't already a Weave browser running, this is the URL that the link will open in a new Internet Explorer browser window to start Weave.
From there you need to configure the users to use Weave as the GIS link (it may be possible to do this globally rather than having to do it individually for each user)