The Frontline Connector is primarily used to integrate customer data into workflows and allows for easy communication with mobile devices running Frontline Workplace. It serves as a connector between the Frontline suite and the customer IT. To facilitate backend integrations with Frontline, a Frontline Connector project template is offered as a basis for development.
The Frontline Connector template is a Java + Spring Boot project, using Angular for the frontend portion. The template comes with a full implementation of the Frontline Command Center API and contains classes for device communication.
For xPick, which is Frontline's warehouse logistics solution, it additionally comes with a full implementation of the Vision Pick Interface (an interface specification the customer can develop against). Finally, it also contains a file upload interface for picking orders (CSV or Excel files) and article images providing the distinct advantage of requiring no customer-side development for quick and easy proof-of-concept.
The following steps allow the user to run the Frontline Connector template from an Integrated Development Environment (IDE):
swagger-codegen-cli
library.install
lifecycle phase.compile
lifecycle phase. IntegrationService
class and configure the following environment variable: UBIMAX_HOME
= <Path to a HD Folder where the Application will store logs, configuration files etc.>
.https://192.168.133.45:444
.https://192.168.133.45:445
.https://192.168.133.45:445
This property is required whenever the Frontline Command Center runs on Port 443.jdbc:mysql://<DB Hostname/IP>/<Database name>
\webapp
and run npm install
and npm run build
The most relevant package for development is the com.teamviewer.connector.service package. In order to communicate with devices running Frontline Workplace the RequestHandler classes will be used, for example for xInspect or xMake the class: service.inspection.implemention.DefaultInspectionRequestHandler
For the Picking use case there are two fully implemented RequestHandlers. The class service.picking.implementation.FileBasedPickOrderRequestHandler
contains the ready-to-use implementation of the picking logic when using the CSV or Excel order upload, while the service.picking.implementation.RestBasedPickOrderRequestHandler
contains the implementation of the Vision Pick Interface.
Which RequestHandler receives which message from the devices is handled by the ServiceController classes, for example: service.picking.PickOrderServiceController
For sending HTTP requests to the customer's backend the TemplateHttpConnector can be used.
In order, to have a good starting point you can take a look at our Hello Machine example, consisting of a small workflow, a modified DefaultInspectionHandler, and a simple Node-Red endpoint. In this example, the Frontline Worker inspects a machine in the field. They scan a barcode from the machine using a smart glass. The barcode gets passed on to the Frontline Connector which in turn sends a REST request to the Node-Red endpoint containing machine diagnostics data. This data finally is displayed on the smart glass.
Note: In the example, irrespective of which QR code is scanned, the resulting data received is the same.