vasttri.blogg.se - Jabra direct software desktop white box

Jabra direct software desktop white box password#
Jabra direct software desktop white box windows#

Please refer to the section on self-hosting for further information. Jabra makes regular updates of the Jabra Xpress and Jabra SDK backend Docker image on Docker Hub. With this deployment configuration, the Jabra SDK will not access the internet. This makes it possible to host the Jabra SDK backend on-premises using the Docker container technology. The Jabra Integration Service client uses the Jabra SDK as a library for Jabra device detection, firmware update, and device settings configuration.īy default, the Jabra SDK requires internet access to retrieve device metadata and device resources, however, from release 1.4 and onwards, the client supports the configuration of the Jabra SDK backend endpoint. Msiexec.exe /i JabraIntegrationServiceX64Setup.msi TRAYICON="NO" ANALYTICSENDPOINT=" DEVICEMANAGEMENTENDPOINT=" CHECKFORUPDATESINTERVALMINUTES="60" Set the check for updates interval to 1 hour.Set the analytics and device management endpoints to.To clarify deployment further we will use an example where three settings are customized: The client executable is called JabraLoggingClient.exe Deployment example On a 64-bit machine Jabra Integration Service is installed in C:\Program Files (x86)\Jabra\Jabra Integration Service. Installer property: PEOPLECOUNTHEARTBEATINTERVALMINUTES Deployment Location If the interval is zero or negative, the heartbeat function will be disabled. Jabra PanaCast People Count Heartbeat Interval:.Installer property: DEVICECAPABILITIESENDPOINT. Jabra SDK backend configuration option:.

Installer property: BACKENDCONFIGURATION. Partner-specific backend configuration options:.Installer property: CHECKFORUPDATESINTERVALMINUTES.

Jabra direct software desktop white box password#

Installer properties: USERNAME and PASSWORD The Password is excluded from the installation log, and it will be encrypted before it is saved to the configuration file. If Username and Password is specified, they will be used to setup Basic Authentication against both of the above endpoints. Can be either or Installer property: DEVICEMANAGEMENTENDPOINT.

Device management backend endpoint (a URL):ĭefault is empty, i.e.

Can be either or Multiple analytics endpoints can be configured by separating each endpoint with a "|" character. The Jabra Integration Service software component can be mass deployed, mass upgraded, or mass uninstalled using Microsoft SCCM or similar tools.ĭefault is empty, i.e. The endpoints shall provide a RESTful API as described in the following sections. The integration partner should provide the device management backend system and provide the necessary JSON documents (configurations) for the client.īoth endpoint URLs are partner-specific and shall be configured during the installation of the client application using MSI properties. Jabra Integration Service connects to an analytics endpoint where it posts device and system information, it also connects to the device management endpoint where it gets configurations for the managed devices connected to the client PC. NET application, it functions as a client, connecting to integration partner endpoints, see the figure below:

Jabra direct software desktop white box windows#

Jabra Integration Service is a Windows Desktop. When applicable, notes, examples, and tips will be provided. Each section can be read as a stand-alone text, but we encourage you to look through all sections.

This guide is divided into sections, each with a specific topic. The target audience for this document is Jabra integration partners and IT administrators responsible for Jabra device management. The purpose of this document is to provide an overview of the Jabra Integration Service solution.

Setting configuration of Jabra devices.

Event logging of Jabra device and system information.

Jabra Integration Service provides high-level functionality for: