Versions Compared

Version Old Version 9 New Version 10
Changes made by

Kenn Pranger-Rasmussen

Kenn Pranger-Rasmussen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

What is the ModuleApiProxy?

...

  1. Install ModuleApiService by running the Setup.exe (available from the ModuleApiProxy SDK). The setup.exe will install the 'ModuleApiService' which creates and updates the certificate used for the https communication between ModuleApiProxyLib and ModuleApiProxy.
    This file can be installed without user interaction using this command line:
    setup.exe /v"/qb"
    The ModuleApiService must be installed before the ModuleApiProxy can be used.

  2. The following step specifies different deployment folders for PIMA 1.0.0 and 1.0.1 vs 1.0.3.
    The files below (available from the ModuleApiProxy SDK) must be included when installing/deploying the module to a computer where Noah 4.9 or later is installed (see image below)

    1. ModuleApiProxyLib.dll

    2. SharedLib.dll

    3. ModuleApiProxy.exe

    4. ModuleApiProxy.Config.json

Note

  1. The ModuleApiService should never be uninstalled when a PIMA module is uninstalled as this service is shared by all PIMA modules on the computer.

.NET 6 Module Deployment files

Deployment Folders

MyDotNet6Module.exe
“Other Module related files“

..\MyModuleFolder\

SharedLib.dll
ModuleApiProxyLib.dll
ModuleApiProxy.exe
ModuleApiProxy.Config.json

..\MyModuleFolder\

Starting with version 1.0.3 of the ModuleApiProxy the component must be deployed like this:
(In the table below the files in cells with green background are provided by HIMSA)

.NET 6 Module Deployment files

Deployment Folders

MyDotNet6Module.exe
“Other Module related files“

..\MyModuleFolder\

ModuleApiProxyLib.dll
SharedLib.dll

..\MyModuleFolder\

ModuleApiProxy.Config.json
ModuleApiProxy.exe

..\MyModuleFolder\.proxy