...

• Unlike TR-69, which polls wide-and-deep across a device landscape, on a less frequent basis, WebPA can precision-poll for the most useful data, much more quickly. That’s mainly because it’s lightweight, and because the load can be redistributed into all the apps needing to access the data.
• Specifically, WebPA is a lightweight connectivity socket, with lower-level protocol connectivity between devices, and the cloud — much like a websocket. It works by each client registering with the cloud, so that it maintains a socket connection to the cloud. On the cloud side, APIs enable polls through which other cloud components could receive events, or translate them in to a TR-181 device data model for further analysis.
• And, because WebPA is an “always on” connection (Websocket), asynchronous notifications for a change in device data are a straightforward exercise, where the application “listens” for webhook web hook events.

Setting up a single node

...

WebPA cluster

System Requirement

...

Building from the Source

If pre-built prebuilt packages are already installed as explained in previous section & we want to use the same, skip to configuration section

...

• • Records dependency information in a glide.yaml file. This includes a name, version or version range, version control information for private repos repo or when the type cannot be detected, and more.
  • Tracks the specific revision each package is locked to in a glide.lock file. This enables reproducibly recursively fetching the dependency tree.
  • Utilizes vendor/ directories, known as the Vendor Experiment, so that different projects can have differing versions of the same dependencies.

...

WebPA server components as well as requesting application has to use a autorization authorization token for bearer authentication. We can either use a basic authorization token or make use of a key server for obtaining a bearer token.

For example, a UI application needs to invoke some Preference setting or to obtain some diagnostics information on behalf of a MSO partner, deviceId, serviceAccountId or combination of the three. It will first obtain or use a pre-defined auth predefined AUTH token, set it as a HTTP header and then invoke the GET/SET operation.

...

However in the standalone setup, we have used basic base64 encoded autherization authorization token because SAT requires access to operator specific key servers. This auth token will be used when configuring different webPA components as well while performing GET/SET requests to the CPE from a 3rd party application.

...

Add the "aws" section with following values for supressing suppressing few error messages 

...