...

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

Installation

The ProClaim components are installed on the server as part of the Interop installer. When the Interop installer is run and ProClaim chosen as one of the components to install this will install the server side components and also copy the client components to the server in the weave\interop\proclaim directory, these components, along with the WeaveLink components must be registered on any client PC that will be linking between Weave and ProClaim.

Registration of the ProClaim components should be performed using the regsvr32.exe application provided with Windows, e.g.

regsvr32 WeaveProclaimLink.dll
regsvr32 WeaveMapLink.dll

Un-installation

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

...

latest version of the ProClaim integration requires Weave Hub to be installed on the client PC, see this page for information on installing Weave Hub.

Once Weave Hub is installed on each client PC you need to install the ProClaim add-in for Weave Hub to add support for ProClaim to Weave Hub.

The Proclaim Weave Hub add-in is installed via a .msi file and only provides the option to change the installation directory, which defaults to C:\Program Files\Cohga\WeaveHub\Proclaim\. The installer also creates some registry entries, to register the add-in with Weave Hub.

In addition to the Weave Hub add-in, the installer also installs and registers a COM object that can be used by Proclaim to communicate with Weave. The name of the COM object is WeaveHubProclaim.MapAutomation and must be registered within Proclaim as the component to call when communicating with a GIS, which is outlined at the bottom of this page. Like the Pathway and Trim integrations, the COM object just sends messages to Weave Hub which will then forward them on to the browser.

Server

Configuration

Server

...

The 'entity' tags setup sources for data to send to ProClaim and targets for data sent from ProClaim.
When setting up a linkage in ProClaim to go from Weave to ProClaim the source entity should be set to the 'id' attribute of the entity tag.
When setting up a linkage in ProClaim to go from ProClaim to Weave the destination entity should be set to the 'id' attribute of the entity tag.

Client

Once the server have has been configured the ProClaim action can be added to a toolbar in the client configuration. Note the change to "proclaim2" below, it was previously just "proclaim".

<item action="com.cohga.proclaimproclaim2.Send" version="production"/>

...

When registering the Weave application with ProClaim the Automation Component for Weave is WeaveMapLink and WeaveHubProclaim and the Automation Class is WeaveMapAutomation MapAutomation.

There are two properties for the Weave application that should be set:

...

Only Direct Relation criteria type are currently supported.

Client Test Script

The following script can be saved to a file on a client PC as "proclaim.vbs" and run from a command prompt using "cscript proclaim.vbs" to test if the required components are installed and available

on error resume next

dim o

set o = CreateObject("Weave.Link")
if o is nothing then
	WScript.Echo("Don't have Weave.Link")
else
	WScript.Echo("Have Weave.Link")
end if
set o = Nothing

set o = CreateObject("WeaveMapLink.WeaveMapAutomation")
if o is nothing then
	WScript.Echo("Don't have WeaveMapLink.WeaveMapAutomation")
else
	WScript.Echo("Have WeaveMapLink.WeaveMapAutomation")
end if
set o = Nothing

set o = CreateObject("WeaveProclaimLink.ProclaimFactory")
if o is nothing then
	WScript.Echo("Don't have WeaveProclaimLink.ProclaimFactory")
else
	WScript.Echo("Have WeaveProclaimLink.ProclaimFactory")
end if
set o = Nothing

set o = CreateObject("ProAppLink.Linkages")
if o is nothing then
	WScript.Echo("Don't have ProAppLink.Linkages")
else
	WScript.Echo("Have ProAppLink.Linkages")
end if
set o = Nothing

...

...