eCMS Setup

Use this article to install the ToolWatch Integration Connector for eCMS. First, you install the connector and check its network connection. Then you send your eCMS API details to ToolWatch, and our team confirms that everything is working. If needed, you can also change the connector region.

Depending on your ToolWatch region, you may have to change what server the ToolWatch Integration Connector communicates with. By default the Integration Connector communicates with the East region. ToolWatch will inform you during integration setup if this needs to be changed. To change this region on the Windows machine with the connector:

Region API URLs

Networking rules where the ToolWatch Connector is installed might block traffic to these API endpoints.

Note: The Check connection link runs a series of connection tests for the current API endpoint. If the first test is successful, you will see "Success!". Otherwise, you will see the response code and error message for the connection request, the DNS name resolution for the API endpoint, and whether you were able to connect to the API endpoint through a TCP connection on port 443. You can run as many connection checks as needed. If the connection check fails, contact ToolWatch Support.

Please let us know when the connector has been installed and we will have our team check to confirm everything is working properly. When you reply, please be ready to provide the following information, some of which will be derived from following the install instructions:

If you would prefer not to send this information via email, then please call our support team at 720-856-3441 and they will be happy to capture the information over the phone.

If the integration run error log shows this error for one of the endpoints: "Content": "ERROR: Requested service is not available.", ask your eCMS administrator whether that endpoint is configured for the integration.

A: The ToolWatch Connector is a Windows Service that allows the ToolWatch Cloud to integrate with on-premise systems.

A: For Vista, Spectrum, and CMiC integration customers, the connector can be installed on any host that has network access to the database or the APIs exposed by the application server. This can be the database server itself, the application server, or a completely separate host.

For Sage 100 Contractor or Sage 300 CRE integrations, the connector must be installed on a host that has filesystem access to the application database. This can be either via the local filesystem, or via a network share.

A: For all integrations the host must be able to make outbound HTTPS calls to:

If you need to whitelist these destinations, you must whitelist the domain, and not the IP address, as the IP address will change frequently as our cloud platform elastically scales up and down.

No inbound network access is required.

A: The host only needs to be running Windows with a recent version of the .NET framework. There are no other external requirements such as SQL Management Studio. CPU, memory, and disk requirements are negligible.

A: The load caused by the integration should be negligible relative to a normal workload, but as with all things appropriate testing is advised. A simple approach would be to initially try the integration after hours for load testing. Using a ToolWatch sandbox account would further allow for testing different configurations without worrying about affecting production data.

A: Use the Windows Add/Remove Programs in Windows Settings. The connector will be listed as "ToolWatch Connector" and can be uninstalled using the remove option.