External Content

The "External Content" Service integrates applications from the Internet or the respective network via IFrame.

It also offers the option of loading applications through the internal BPC proxy, therefore logging in via BasicAuth or taking into account upstream proxy servers and adapting set HTTP headers. The prerequisite for these further options is a created backend connection component of type http_proxy, see Backend Connections.

In addition, the integrated websites can also be integrated in full or in part via a widget in BPC dashboards.

Access rights

In order for a user to access the module and view the content, the right loadModule_externalContent is required.

Create and configure external content module

The module type of the external content module is "proxy". The creation and configuration is carried out via the administration area of the BPC.

Configuration of the External Content module

Configuration parameters

The following configuration parameters can be set:

Setting (Key) Type Description

Setting (Key)	Type	Description
Group: target
Target_Path (`target_path`)	text	URL to be called. A relative URL must begin with "/", even if the base URL of the External Content and/or http_proxy already ends with "/".
Target_BaseURL (`url`)	text	This base URL to the target system is prefixed each time it is used. Dominates and is optional if a base URL is specified here as well as in the http_proxy used. Placeholders can also be used. Placeholders are set using curly brackets. The brackets and the content are then replaced accordingly. Example: `Sprache: {language}` Possible values for the placeholder: `userSession.data.loginName`: User name of the currently logged in user `language`: Active language of the BPC
Group: widget
ExternalContent_WidgetURL (`widget_url`)	text
ExternalContent_WidgetTitle (`widget_title`)	text
ExternalContent_WidgetEnabled (`widget_enable`)	bool
Group: proxy
ExternalContent_ProxyID (`proxy_id`)	text	ID of the Backend Connection to be used
ExternalContent_ProxyEnabled (`proxy_enable`)	bool	true, if the connection is not to be established directly, but a Backend Connection of type http_proxy

Group: target

Target_Path
(target_path)

text

URL to be called. A relative URL must begin with "/", even if the base URL of the External Content and/or http_proxy already ends with "/".

Target_BaseURL
(url)

text

This base URL to the target system is prefixed each time it is used. Dominates and is optional if a base URL is specified here as well as in the http_proxy used. Placeholders can also be used. Placeholders are set using curly brackets. The brackets and the content are then replaced accordingly. Example: Sprache: {language}

Possible values for the placeholder:

userSession.data.loginName: User name of the currently logged in user
language: Active language of the BPC

Group: widget

ExternalContent_WidgetURL
(widget_url)

text

ExternalContent_WidgetTitle
(widget_title)

text

ExternalContent_WidgetEnabled
(widget_enable)

bool

Group: proxy

ExternalContent_ProxyID
(proxy_id)

text

ID of the Backend Connection to be used

ExternalContent_ProxyEnabled
(proxy_enable)

bool

true, if the connection is not to be established directly, but a Backend Connection of type http_proxy

Example

Example with the following URL: https://www.virtimo.de

Keywords: