<main>
<article class="userContent">
<p>✒️ Access to the license server - The server needs to be able to access the URL https://licensing.svc.frontlineworker.com/app, which resolves to IP 20.76.141.169. You may have to whitelist this IP in their corporate firewalls. An error <em>{"error":"Not found","status":404}</em> is acceptable, a timeout would indicate that the connection is blocked. You will not be able to use the server without a connection to the license server. If you test this using a browser on the server please ensure that either no proxy is required or that our Application Server is configured to use an appropriate proxy. Available options regarding the proxy configuration when invoking the Java VM be found here: <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html." rel="nofollow noreferrer ugc">https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html</a> </p><p>The application server needs to be reachable (from the Frontline Clients and other machines that should access the Web-UI) by a Fully-Qualified Host Name (which could be also an IP-Address that does not change).</p><p>Note: The old license server URL <a href="https://ulm.ubimax.com/app" rel="nofollow noreferrer ugc">https://ulm.ubimax.com/app</a> which resolves to the IP 13.69.62.84 is still operational, however, it shall not be used anymore going forward.</p><h2 data-id="ssl">SSL</h2><p>✒️SSL is required for Frontline 4.0 </p><p>The use of SSL encrypted web-traffic (HTTPS) is a requirement for Frontline since October 2020</p><p>For cloud installations, the needed trust is established by the use of certificates issued by a trusted root CA.</p><p>For an on-premise installation, this trust has to be established by the local infrastructure, e.g. the local server requires a certificate that is trusted by all local users. The local IT needs to issue a certificate for the server that can be used by the Frontline Command Center. We require a standard X509 certificate as used in other web services. There are two common scenarios to obtain this:</p><ul><li><strong>Customer supplied Keystore:</strong> In this scenario, the customer will provide a private key and certificate for the server in form of a password-protected PKCS12 (PFX) Keystore. The password (for the Keystore and the private key) is either given to TeamViewer for setup or configured by the local IT into the configured server.</li><li><strong>Customer signed certificate:</strong> In this scenario TeamViewer will provide a standard X509 certificate signing request (CSR) using the supplied hostname for the server. The local IT will sign this request and provide TeamViewer with the resulting certificate in either DER or PEM format. TeamViewer will then configure the server to use this certificate.</li></ul><p>In both cases, it is the responsibility of the customer to set up the user machines to trust the resulting certificate in the browser.</p><p>Our software requires the following communication interfaces. If needed alternative ports can be configured:</p><div class="embedExternal embedImage display-large float-none">
<div class="embedExternal-content">
<a class="embedImage-link" href="https://us.v-cdn.net/6032394/uploads/Q9NTHHLFNENO/image.png" rel="nofollow noreferrer noopener ugc" target="_blank">
<img class="embedImage-img" src="https://us.v-cdn.net/6032394/uploads/Q9NTHHLFNENO/image.png" alt="image.png" height="127" width="1167" loading="lazy" data-display-size="large" data-float="none"></img></a>
</div>
</div>
<h2 data-id="wi-fi-connectivity">Wi-Fi Connectivity</h2><p>✒️ <strong>DHCP required</strong></p><p><strong> Android does not officially support static IP addresses. Please obtain IP addresses via DHCP</strong></p><h3 data-id="supported-wi-fi-features">Supported Wi-Fi Features</h3><div class="embedExternal embedImage display-large float-none">
<div class="embedExternal-content">
<a class="embedImage-link" href="https://us.v-cdn.net/6032394/uploads/NGAP9S1EHYDH/image.png" rel="nofollow noreferrer noopener ugc" target="_blank">
<img class="embedImage-img" src="https://us.v-cdn.net/6032394/uploads/NGAP9S1EHYDH/image.png" alt="image.png" height="1431" width="2355" loading="lazy" data-display-size="large" data-float="none"></img></a>
</div>
</div>
<div class="embedExternal embedImage display-large float-none">
<div class="embedExternal-content">
<a class="embedImage-link" href="https://us.v-cdn.net/6032394/uploads/YX5QHKX6PIAL/image.png" rel="nofollow noreferrer noopener ugc" target="_blank">
<img class="embedImage-img" src="https://us.v-cdn.net/6032394/uploads/YX5QHKX6PIAL/image.png" alt="image.png" height="1452" width="2349" loading="lazy" data-display-size="large" data-float="none"></img></a>
</div>
</div>
<h3></h3><h2 data-id="openfaas">OpenFaaS</h2><p><strong>Frontline Command Center (FCC)</strong> uses the concept of Function-as-a-Service (<strong>FaaS</strong>) to support functionalities used in various parts of the product. This reduces the individual server maintenance efforts and centralizes processing components. These components do not store any data.</p><p>For Frontline cloud services, we use<strong> OpenFaaS</strong>, which is a serverless framework that can be delivered within <a href="https://docs.openfaas.com/deployment/kubernetes/" rel="nofollow noreferrer ugc">Kubernetes Cluster</a>. There are currently three components in use, <strong>Proglove, PDFMake, </strong>and <strong>Imagemagick</strong>.</p><p><strong>Proglove</strong> is an image generator used to create QR pairing codes and bar codes. These codes can then be used, to connect ProGlove devices to the Frontline Workplace.</p><p><strong>PDFMake </strong>is a JavaScript library used to generate PDF files. An application of this is when creating a Service Report in xAssist.</p><p><strong>ImageMagick </strong>is a software suite used for image manipulation. It is mainly used to scale images from one size to another.</p><p>✒️To use these features by default URL <a href="https://functions.svc.frontlineworker.com/function/" rel="nofollow noreferrer ugc">https://functions.svc.frontlineworker.com/function/</a> should be reachable.</p>
</article>
</main>