Extensions Web
Profinity can run a second, separate web server that serves custom applications and provides access to the same APIs that Profinity itself uses for all functionality. You configure this second server on the Extensions web tab.
It is disabled by default and needs a Server licence (Server or Enterprise edition). Only with a Server licence is the Extensions web tab shown, and only with a Server licence can the second web server be enabled. With a Server licence, the address options work as they do on the Web tab, so you can use 0.0.0.0 or a specific address.
Saving changes on any System Configuration tab restarts Profinity. Refer to System Configuration for what to expect.
The Extensions Web server hosts custom kiosk applications and custom web applications, such as an in-vehicle display, that call the Profinity API.
The HTTP, HTTPS, and certificate options are the same as on the Web tab, described in Profinity Web and HTTPS certificates. The default ports differ: 19080 for HTTP and 19443 for HTTPS, so that they do not collide with the main Profinity Web ports. The tab has these additional options:
| Parameter | Type | Default | Description |
|---|---|---|---|
Enable Profinity Web Server |
On or off | Off | Starts the second web server, so that extensions can be served on their own ports. |
Enable Profinity API |
On or off | Off | Makes the Profinity API available through the second web server. |
Enable Swagger on API |
On or off | Off | Shows the Swagger UI, an interactive API page on your Profinity instance. It can be enabled only when the Profinity API is enabled. |