FlexNet Edge Server Setup
The FlexNet Edge Server installer is available for download from the Product and License Center. FlexNet Edge is Linux based only. This section lists steps required to run FlexNet Edge.
For information about installing and configuring FlexNet Edge, see the FlexNet Edge Server User and Installation Guide that is available on docs.revenera.com.
Authorizing FlexNet Edge Server
The following steps are essential for FlexNet Edge to be able to communicate with the Notifications Server:
|
1.
|
Request a public key for checking signed update responses. While the device might not request signed updates, FlexNet Edge will always use the /signed-updates API, and requesting the public key will create the private key in FlexNet Operations. |
The public key must be made available to any devices requesting signed updates, but FlexNet Edge does not need the key to be loaded in its UI or install directories.
|
2.
|
Create a JWT (see Documentation about JSON Web Tokens) and install it in FlexNet Edge. All requests to the Notification Server, from devices or from FlexNet Edge, must be authorized using a JWT and so FlexNet Edge must be provided with this token. There are three ways to provide FlexNet Edge with the token: |
|
•
|
Place it in the file /opt/edge/conf/authorization-token in the FlexNet Edge server's operating system. |
|
•
|
Upload the JWT in the FlexNet Edge settings UI. |
|
•
|
Upload the JWT using its /authorization-token REST API. (For more information about the FlexNet Edge REST API, see the FlexNet Edge Server API Reference Guide on docs.revenera.com.) |
FlexNet Edge User Interface
The FlexNet Edge User Interface (UI) is located on port 8888. The primary purpose of this UI is to provide information to the end user, about devices in the network and the version the devices have updated to. In addition, controls are provided to the end user with which to clear and view the cache, and to pause or restart FlexNet Edge communication with the Notification Server.