arrow_back_ios

Main Menu

See All Software See All Aufnehmer See All Elektroakustisch See All Akustische End-of-Line-Testsysteme See All Vibration Testing Equipment See All Systeme und Datenerfassung See All Akademie See All Anwendungen See All Industrien See All Services See All Support See All Sustainability See All Our Business See All Our History See All Careers See All Globale Präsenz
arrow_back_ios

Main Menu

See All DAQ See All Drivers API See All nCode - Durability and Fatigue Analysis See All ReliaSoft - Reliability Analysis and Management See All Test Data Management See All Utility See All Vibration Control See All Inertial Sensor Software See All Acoustic See All Current / voltage See All Displacement See All Schwingungserreger See All Force See All Inertialsensoren See All Wägezellen See All Pressure See All Smarte Sensoren mit IO-Link-Schnittstelle See All Strain See All Torque See All Vibration See All Testlösungen See All Aktoren See All Verbrennungsmotoren See All Betriebsfestigkeit See All eDrive See All Sensoren für Produktionstests See All Getriebe See All Turbolader See All LDS-Shaker-Systeme See All Leistungsverstärker See All Schwingungsregler See All DAQ Systeme für die mechanische und Struktur-Analyse See All DAQ-Systeme für Sound & Vibration&V See All Industrie-Elektroniken See All Leistungsanalysator See All Handgehaltene Geräte für Schall und Schwingung See All Drahtloses Datenerfassungssystem See All DAQ Systeme für die mechanische und Struktur-Analyse See All Schulungskurse See All Akustik See All Anlagen- und Prozessüberwachung See All Elektrische Energie See All Kundenspezifische Sensoren See All NVH See All Zuverlässigkeit See All Smarte Sensoren See All Schwingbelastung See All Strukturelle Integrität See All Automobil & Bodentransport See All Calibration See All Installation, Maintenance & Repair See All Support Brüel & Kjær See All Release Notes See All Our People See All Compliance
arrow_back_ios

Main Menu

See All BK Connect / PULSE See All API See All Microphone sets See All Cartridges See All Spezialmikrofone See All Akustische Kalibratoren See All Mikrofon-Vorverstärker See All Schallquellen See All Zubehör für akustische Sensoren See All Accessories See All Leistungsverstärker See All Zubehör für Schwingprüfsysteme See All Accessories See All Bending / beam See All Zubehör für Wägezellen See All DMS für die Experimentelle Spannungsanalyse See All DMS für den Aufnehmerbau (OEM) See All Zubehör für Dehnungsmessstreifen See All Nicht rotierend (Kalibrierung) See All Rotierend See All CCLD (IEPE)-Beschleunigungssensor See All Ladungs-Beschleunigungssensor See All Impulse hammers / impedance heads See All Drehzahlsensoren See All Kabel See All Accessories See All QuantumX See All SomatXR See All MGCplus See All Optische Interrogatoren See All CANHEAD See All LAN-XI See All Fusion-LN See All Zubehör für Industrieelektroniken See All GenHS See All Zubehör für GenHS See All Software für handgehaltene Geräte See All Zubehör für handgehaltene Geräte für Schall und Schwingung See All Drahtlose DAQ Gateways See All Drahtlose DAQ-Knoten See All Elektroakustik See All Schallquellenortung See All Umgebungslärm See All Produkt-Lärm See All Schallleistung und Schalldruck See All Vorbeifahrgeräusche See All Strukturüberwachung See All Produktionsprüfung und Qualitätssicherung See All Maschinenanalyse und -diagnose See All Strukturüberwachung See All Batterieprüfung See All Einführung in die Messung elektrischer Leistung bei transienten Vorgängen See All Transformator-Ersatzschaltbild | HBM See All Strukturelle Dynamik See All Prüfung der Materialeigenschaften See All Sicherstellung der strukturellen Integrität von Leichtbaustrukturen See All Elektrifizierung von Fahrzeugen See All Calibration Services for Transducers See All Calibration Services for Handheld Instruments See All Calibration Services for Instruments & DAQ See All On-Site Calibration See All Resources See All Software License Management

ReliaSoft API Ante Service

 

The ReliaSoft API is installed with your ReliaSoft desktop applications. If you plan to run the API on a Windows desktop environment, no additional setup is required. However, if you plan to run the API on a Windows server, you must use locally hosted licensing and you'll need to install the ReliaSoft API Ante Service on the server. The service acts as a bridge between your license server and API clients, allowing the implementation to scale up.

There are three architectural components to making the server-based API calls work: the license server, the API Ante service, and your API client program. All of these components may run on the same machine or on separate networked machines.

 

Prerequisites

The API Ante service is based on WCF technology and requires .NET Framework 4.6.1 or greater to run. Communication between the service and clients is done over TCP and is secured point-to-point via Windows authentication; therefore, the service and any clients must have domain user credentials to run successfully. Also, your server OS and .NET Framework 4.6.1 must be 64-bit.

Before installing the API Ante service, be sure to have configured your license server according to these instructions.

 

Installing the ReliaSoft API Ante Service

 

You may need assistance from a system administrator to complete the installation.

 

  1. Run ReliaSoftAPIAnteService64Pack_1.0.0.0.exe and extract the Ante service files to a location of your choice.

  2. On the computer where the API Ante service will run, create or configure a domain user that has permission to log on as a service and to access the network.

    For this user, set the environment variable HBMUK_LICENSE_PATH to the value PORT@HOST where PORT and HOST are the port and hostname for the license server. (See DistributionFiles\set-license-path.bat for an example of setting this environment variable.)

  3. In the DistributionFiles\ directory, right-click the install-service64.bat file and choose Run as administrator[1]

    You will be prompted for a login name and password. Provide the credentials of the user configured in step 2. Prepend the domain name like so: DOMAIN\USER.

    To check whether the installation was successful, look for the following output:

     

    ...
    Beginning the Install phase of the installation.
    ...
    Service RSAPIAnteService has been successfully installed.
    ...
    The Install phase completed successfully, and the Commit phase is beginning.
    ...
    The Commit phase completed successfully.

    The transacted install has completed.

  4. Start the service. The following case-sensitive arguments may also be provided:

    • /P - The port on which the service will listen for API clients. Default is 64132.

    • /V - Verbose logging. Some messages will not be published to the Windows event log without this flag.

    An example usage: /P 8532 /V

  5. Make a firewall rule to open the port used in step 4.

  6. Optional admin settings:

    • To create a simple filter for capturing messages from the service, open the Windows Event Viewer, then choose Action > Import Custom View and select RSAPIAnteService_CustomView.xml from the provided distribution files.

    • To configure automatic restart upon error/failure, open the Windows Services tool. Find the ReliaSoft API Ante Service in the list and view its properties. On the Recovery tab, choose Restart the Service in the First failureSecond failure and Subsequent failures fields, and select the Enable actions for stops with errors check box.

    • Consider configuring the service to automatically launch at startup.

  7. On the computer where the API client will run, two environment variables must be set:

    • The API client must be able to find the license server. Set the HBMUK_LICENSE_PATH variable to the same value used in step 2 for the API user. (See DistributionFiles\set-license-path.bat for an example of setting this environment variable.)

    • The RS_ANTESERV_PATH variable tells the API client where to find the Ante service. Use the PORT@HOST format where PORT is the value from step 4 and HOST is the hostname of the computer where the service was installed in step 3. (See DistributionFiles\set-anteserv-path.bat for an example of setting this environment variable.)

       

[1] The install scripts assume that the installer program (InstallUtil.exe) is located at the default .NET Framework install location. If the install fails, first open the script and make sure the supplied path is correct for your .NET Framework installation. If the path is incorrect, find the location of InstallUtil.exe and copy its full path into the script. Then save and try running again.