When viewing endpoints, the example response may not actually match the response when you use the ‘Try it Out’ button.
Also, some attributes may specify it returns a string but instead it returns an integer. It is recommended to utilize the ‘Try it Out’ button for the API you wish to use as how that API will actually behave.
<br>
Even though you are able to attempt to filter on NULL or a date, it does not work on any endpoint that provides a date field attribute.
<br>
When using the ESM API to retrieve servers or cameras, sometimes a field may come back as an integer when the attribute does not say ID.
There is usually no way to know what the integer represents. It should show a string.
<br>
ESM-API-may-not-provide-strings-for-all-attributes.pdfIn some versions of IE, the slide in module will not show up correctly.
Also, in IE and Firefox, the calendar selection will not display.
Using chrome will allow this functionality to display correctly. In the case of no slide in module for actions like scheduled updates, there is no choice but to use Firefox or Chrome as it will not work in IE.
For calendar, you can manually update the date fields on the bar.
3.9.19.90492
All
<br>
Browser-compatibility-issues-in-ESM.pdfThere are two ways to modify the ports used by the Web Service:
It is recommended to use the configuration interface, whenever possible. However, it is possible that you must hand edit the configuration in cases where the Web Service cannot start (for example, if there is a port conflict). This article provides instructions for both methods.
Important: The structure and location of the Web Service config has changed over the life of the web service. Please pay close attention to the section headers in this article, as they indicate the versions to which particular instructions apply.
While various versions are mentioned in this article, it is recommend to keep your Web Service updated to the latest version to help prevent exposure to vulnerabilities and take advantage of the latest performance improvements.
<br>
Log into Web Service Configuration using your Web Service administrator account. Using the provided Web Service configuration interface navigate to Configuration > Ports.
Update the fields to change to your selected port number, then click ‘Apply’ to save your changes. The Web Service will need to restart to reflect your changes.
Web Service version 7.2 introduced Web Sockets for video streaming. Version 9.4 was the last version to feature Web Sockets, as it was replaced by other improvements.
When logging into Web Service Configuration, navigate to Configuration > Ports. Update the fields shown to your selected port numbers then click ‘Apply’ to save your changes. The Web Service will need to restart to reflect your changes.
Web Service version 7.2 introduced Web Sockets for video streaming. Version 9.4 was the last version to feature Web Sockets, as it was replaced by other improvements.
When logging into Web Service Configuration, navigate to Basic Service Configuration. You have the ability to update the Web Service Port and WebSocket Ports through the configuration page.
To change the HTTPS (SSL) or Secure WebSocket (SSL) ports requires manually editing the configuration file. See the section in this article titled ‘Manual Configuration‘ for more on these steps.
The Web Service will need to restart to reflect your changes.
These versions are quite dated and as mentioned earlier, we recommend keeping your Web Services updated to help avoid vulnerabilities and take advantage of new features and performance enhancements.
<br>
Note: Changing the SSL ports (https/wss) DOES NOT enable SSL. This merely allows you to easily modify those ports, but you still need to manually configure SSL support for both Apache and WebSockets. See the following article on configuring a certificate for HTTPS.
Note: Be sure to forward the new port in your router. Exacq Technical Support does not provide assistance with port forwarding, but see the following links if necessary:
<br>
The steps here will change depending on the type of port (HTTP vs. WebSockets) you wish to edit.
The first step to manual editing is to find the location of the config file where the port numbers are held. This depends on both the platform (operating system) and version of the Web Service you have installed.
Windows:
C:\ProgramData\Webservice\conf\wfe.jsonC:\Program Files[(x86)]\exacqVision\WebService\Apache\conf\httpd.confC:\Program Files[(x86)]\exacqVision\WebService\Apache\conf\extra\httpd-ssl.confLinux:
/etc/webservice/wfe.json/etc/evapache/httpd.conf /etc/evapache/extra/httpd-ssl.confDetermine where this file is for your install before continuing.
Once you have found the file, open it using your editor of choice (be sure to do so with administrative privileges) and perform either of the following depending on its name:
httpd.conf (HTTP port) and httpd-ssl.conf (HTTPS port):
Listen directive in the file
Listen 80wfe.json:
webserver sectionlisten key, nested one level within the webserver sectiontls key, nested one level within the webserver sectiontls section, find the listen key one level below<br>
Both the standard and SSL WebSocket ports are changed from the Web Service ini/conf file. The location and name of this file depends on the platform (operating system) and web service version:
Windows:
C:\Program Files[(x86)]\exacqVision\WebService\WebService.iniLinux:
/etc/webservice.conf/etc/webservice/webservice.confDetermine where this file is for your install before continuing.
Once you have found the file, open it using your editor of choice (be sure to do so with administrative privileges) and perform the following:
[Broker] section. websocket_port = 8082, while the secure websocket port (wss) is ssl_port = 8083. Modify the port numbers as desired.[Broker] section is missing, the defaults are being used. You may manually add the section/settings with desired values should this be the case. The resulting section of the file should appear similar to the below example, with your custom port numbers.[Broker]websocket_port = 8082ssl_port = 8083<br>