Configuring the Portal Server
Call up
INUBIT Workbench > Administration > General Settings >Portal > Portal Server
|
Virtimo recommends to use HTTPS everywhere, at least on productive systems/environments. On test systems/environments HTTP can also be used. |
| Option | Description | ||
|---|---|---|---|
Portal server |
For selecting and activating a portal server. Additionally, you must configure a respective process user server, refer to Configuring the Process User Server.
|
||
URL of the portal server |
URL of the portal server. If the portal server does not run on the same computer as the INUBIT Process Engine or if the portal server is not reachable using port 8080, you need to adjust the URL. |
||
Login for portal server |
Name of the portal user that the INUBIT process engine needs for connection. On delivery the username is |
||
Password for portal server |
Password of the user, who is given at the option On delivery the password is |
||
URL of the Process Engine |
URL (hostname and port) of the INUBIT Process Engine. To ensure proper deployment hostname and port are mandatory. |
||
Log files of the portlets |
Directory for storing portlets log files. The path refers to the installation directory of the INUBIT Process Engine.
Refer to Trace Level |
Configuring Business Process Center Portal Server
If you have chosen the Business Process Center option in Portal Server, the Business Process Center is used as portal server. The prerequisite is that the Business Process Center is installed and started and that it can be accessed from the system on which INUBIT is installed. For this purpose, there are the following additional settings.
Option |
Description |
||
API-Key for the BPC connection |
The API key is required to authenticate at BPC. All BPC calls must use the API key. If the API key is not valid to authenticate, an error message is displayed. The response will come from the BPC service. Click the icon Enter the API key or click the New button to create one. |
||
Backend Connections for bpc portal server |
Click the icon If there is no Backend Connection, click the New button to create one. Afterward, two instances are created. One instance with the module name inubit Connection of http_proxy type. One instance with the module name inubit idp of identity_provider type. In the core services in BPC*., the *IdentityProvider_BackendConnection is set to: idp_inubit |
||
BPC Identity Provider |
Choose the identity provider that should be used in the Business Process Center for user authorization. This option can be used to configure INUBIT as identity provider instead of BPC (default).
|
||
Test connection to BPC |
Click the icon If there is no API key, the connection test is validated against the provided user name and password. If an API key is set, connection test happens based on the API key. |
Configuring Liferay Portal Server
If you have chosen the Liferay option in Portal Server, Liferay is used as portal server. For this purpose, there is the following additional setting.
| Option | Description |
|---|---|
Liferay portal version |
Version of the Liferay portal, for example: |
