Creating path-based web app branding
Path-based branding allows you to host multiple different versions of the web app, each with its own branding and customization, on your Conferencing Nodes.
Users access the web app by entering the IP address or FQDN of a Conferencing Node or reverse proxy, with an optional path (such as /webapp, /webapp2, and /webapp3, or your own self-defined paths such as /sales for example) appended to that root address.
Those URL paths then determine which web app version and branding is served to that user.
This topic describes how to create and configure web app paths to determine which combinations of web apps and branding are offered in your deployment, in addition to the default paths.
Additional parameters can be appended to the path to allow users to join specific meetings and pass in other information specific to the call being placed (see Creating preconfigured links to launch conferences via Connect apps). Note that different users using different paths can still all connect to the same conference.
Prerequisites
You must have already created and uploaded to the Management Node any branding packages to be used.
Note that the branding package content and requirements for each version of the web app are different, so you may need to upload more than one branding package if you want to create web app paths for more than one branded web app version.
Creating a web app path
To create a specific web app path and apply a branding package to it:
- From the Management Node, go to .
- From the bottom of the page, select .
-
Complete the following fields:
Path identifier The string that, when appended to the IP address or domain name of a Conferencing Node or reverse proxy, provides the URL used to access this branded version of the web app.
For example, if users normally access the web app via webapp.pexample.com and you enter sales here, users will be able to access this branding via webapp.pexample.com/sales
Permitted characters are a-z, A-Z, 0-9, - and _
Description An optional description of this path. Webapp Select the version of the web app to use with this path. Web app bundle By default this is set to Use default web app bundle which means that this path will always use the revision of the selected Webapp that is shipped with Pexip Infinity (rather than any other specific revision). Then, when you upgrade to a later version of Pexip Infinity, it will automatically use the default bundle shipped with that later version.
However, if you want this path to use a specific revision of the selected Webapp, then select the associated software bundle to use.
Branding package Select the branding package to use for this path.
The list of options includes the available branding packages for the selected Webapp.
If you don't want to apply a branding package and instead want to use the default Pexip branding for the selected web app version, select Use default branding.
Enabled Determines if the path is enabled or not. Use this setting to test configuration changes, or to temporarily disable specific paths. Set as default Selecting this option sets this path and associated branding as the default path to use for users who enter the address of a Conferencing Node or reverse proxy, either without a path in the URL or with /webapp appended. For more information, see Redirecting "/webapp" (or no path). - Select .
You can now test the branding by entering the path in your browser and using it to join one of your Pexip Infinity services.
Default paths and default branding
Your Pexip Infinity deployment includes default paths and associated branding, described in the following sections.
Redirecting "/webapp" (or no path)
Users access the web app by entering the IP address or FQDN of a Conferencing Node or reverse proxy in your deployment, either on its own or with a path appended. You can configure where to redirect users who either do not enter a path or enter the /webapp path (supported by previous versions of Pexip Infinity).
By default, /webapp (or no path) redirects to /webapp3
To see which path is currently used as the redirect, go to the list of web app paths (via ). The currently selected path is indicated by a tick in the Default path column.
To change the path to use, select the path and then select Set as default.
If none of the paths are set as the default, users who either don't specify a path or use /webapp are presented with a 404 error.
Default path configuration
Every Pexip Infinity deployment is shipped with the following paths and associated branding. You can delete and edit these default paths, as well as creating new paths.
| Path | Web app version | Branding package name |
|---|---|---|
| /webapp3 | Webapp3 | Pexip webapp3 branding |
| /webapp2 | Webapp2 | Pexip webapp2 branding |
| /webapp1 |
Webapp1 (Note that webapp1 is no longer supported from v32 onwards. Please contact your Pexip authorized support representative if you still require access to Webapp1.) |
Pexip webapp1 branding |
Default branding packages
Every Pexip Infinity deployment is shipped with the following branding packages. You can't delete or edit any of these, but you can download them to use as the basis of your own branding packages:
- Pexip webapp3 branding: containing the default folder structure for Webapp3 branding files.
- Pexip webapp2 branding: containing the default branding for Webapp2
- Pexip webapp1 branding: containing the default branding for Webapp1