AppClarity has a Windows service component which hosts multiple network services. These services listen on specific ports and the clients that use the services need to know which ports to communicate with. The ports are set during installation and can only be modified post-installation.

It is conceivable that you may have to change the default port (8334) AppClarity uses for communications between the console and its service because some other application is already using it. You will know if this is the case because the 1E AppClarity service fails to start, and the following message appears multiple times in the AppClarity.ServiceHost.<servername>.log file.

There is already a listener on IP endpoint This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations.

You can review which ports are being used by starting an admin command prompt and typing netstat -anb.  Each port number appears above its application name.  For example.

  TCP               LISTENING

Modify the AppClarity Console service port as follows: 

After installing AppClarity

ActiveEfficiency Server will have been installed as a prerequisite.

  1. Choose a new port number that you know is not already in use, for example 9334.
  2. Stop the 1E AppClarity service
  3. Edit each of the following files for <INSTALLDIR>\AppClarity\Coordinator\AMP.Coordinator.ServiceHost.exe.config, changing each and every instance of the port value from 8334 to the new port number
    • <INSTALLDIR>\AppClarity\Coordinator\AMP.Coordinator.ServiceHost.exe.config
    • <INSTALLDIR>\AppClarity\Coordinator\AMP.Coordinator.Synchronizer.exe.config
    • <INSTALLDIR>\AppClarity\CatalogUpdateService\CatalogUpdateService.exe.config
    • <INSTALLDIR>\AppClarity\CatalogUpdateService\AppClarity.Catalog.UpdateService.dll.config
    • <INSTALLDIR>\AppClarity\ConsoleInstaller\Default.htm
  4. Start the 1E AppClarity service and confirm it remains started.
  5. Install a new AppClarity Console
    • browse to http://<AppClarityServer>/1eAppClarity and begin installation
    • confirm installation completes and the Console starts (the logged on user will need to be an AppClarity administrator)
  6. Examine each of the logs in C:\ProgramData\1E\AppClarity folder
    • AppClarity.ServiceHost.<servername>$.log - to confirm the AppClarity Service is running without issue
    • AppClarity.ServiceHost.log - ignore
    • AppClarity.ServiceHost.ConsoleService.log - to confirm AppClarity Console activity is being audited
    • AppClarity.Catalog.UpdateService.log - to confirm AppClarity has sent a subscription request to ActiveEfficiency (there may also be catalog updates if the request was successful)

After installing ActiveEfficiency Scout

Installation of the Scout includes the ActiveEfficiency Synchronisation Manager (1E AE Sync Manager).

  1. Edit the following file for the 1E AE Sync Manager, changing the port value from 8334 to the new port number
    • <INSTALLDIR>\ActiveEfficiency\Scout\tools\AppClarity.Synchronizer\AppClarity.Coordinator.Synchronizer.exe.config
  2. At the appropriate time, start the 1E AE Sync Manager and configure a daily schedule according to Get ActiveEfficiency to talk to AppClarity
  3. Examine the logs in C:\ProgramData\1E\ActiveEfficiency folder
    • DailyScheduledTask.log - to confirm the Scout and AppClarity syncs started and completed
    • Scout.log - to confirm the scout has collected data from ConfigMgr into the ActiveEfficiency database
    • AppClarity.Coordinator.Synchroniser.log - to confirm AppClarity has collected data from ActiveEfficiency

For example, to change a port from 8334 to 9334: