Clients
You can operate several independent clients. Certain entries (e.g. profiles) are then only visible on the client on which they were created. You can also specify which resources (e.g. partners) each client has access to.
For each user, you can define which clients they have access to. A logged-in user can switch between the permitted clients in the GUI. This changes the display of the client-specific entries (e.g. profiles). Other areas of the GUI (e.g. certificates) are client-independent and are therefore displayed in the same way for all clients.
Overview
(1) The currently selected client is highlighted in bold.
(2) Context menu.
Creating client
With the standard license, you get one client (default client with ID "-1"). With appropriate licensing, additional clients can be added via the context menu.
(1) Here you can create a configuration subfolder. This is a subfolder in the directory ./conf, in which then all configuration files of this client are. So if you enter value "mysubfolder", for example, the configuration files of the client are in the directory ./conf/mysubfolder. These files are not visible for other clients. Important note: The directory ./conf and subdirectories must not be entered in the file ./etc/admin/datawizard/whiteListPaths.properties!
(2) If this checkbox is set, only the selected resources (set up partners and connected SAP, DB, AMQP, LDAP, MQTT, Kafka systems/resources) in (3) are available for this client. Note: Please note that subsequent changes here may cause problems in profiles that have previously used these resources. Note: See also section "Strict client handling" below.
(4) Here you can specify email addresses, to which notifications are sent in the case of errors in certain phases of the profile processing. See section "Error handling" for details. Especially for phase 1.
(5) Here you can define start directories for channels that use home folders. Example: If your home folder for FTP was "/ftp" and you specify "/folder" here, the path "/folder/ftp" will automatically be entered as home folder for a newly created FTP channel.
(6) If you create a new channel (of one of the types listed here) for this client, the address/ID specified here will be automatically entered in the new channel.
(7) This information is used in the creation of channel datasheets (but can be overwritten there).
Selecting client
The client is displayed in the top right of the GUI. There are areas that are displayed on a client-specific basis and areas that apply to all clients.
Client-specific
Modules entries. If, for example, a profile is created, it is only visible on the client it was created on.
Configuration files can refer to a client-specific subfolder.
Client-specific system information, e.g. profile statistics.
Areas that use client-specific resources, e.g. the SQL console.
You can change the client in client-specific areas. A client change causes all open entries (ASM, profiles, etc.) in the browser session to be closed for security reasons (with a confirmation dialogue before if there are still unsaved open entries).
After you log in, the client that was selected before the last logout is selected.
All clients
It is not possible to select a client here (however, the previously selected client is still active).
In such areas, what applies to all clients is displayed. So if something is changed here, it does not only apply to the current client. This applies in particular when creating resources (e.g. database connections).
Important note: If a resource (partner, SAP, DB, AMQP, LDAP, MQTT, Kafka, MongoDB) is created, it is always valid for all clients in principle. However, this resource is then only displayed and available for clients that either do not have the resource restriction active (→ see section "Creating client" above) or clients that have the resource restriction active and have explicitly released the corresponding resource. Example: You have selected a client with an active resource restriction (only certain partners). You now create a new partner. The new partner is then not visible for this client until you explicitly release it as a resource.
Deleting client
Client can be deleted via the context menu. Important note: If there are active sessions of users who have a specific client assigned, then this client cannot be deleted.
All profiles, DataFlow/Workflow/ASM/ETL entries, test cases and ENGDAT templates of the client are also deleted. In addition, the client is removed in Content Inspectors if it was assigned there. Configuration subfolders (→ see section "Creating client") are not deleted.
Strict client handling
It is possible to restrict the calling of profiles to within the client only (runtime check). This will be valid for all settings and functions. Note: See also option "Restrict resources" in section "Creating client" above.
To do so, enter the following line into the configuration file ./etc/startup.xml.
<Set name="strictClientHandling">true</Set>If the "strictClientHandling" option is set, configuration files can only be accessed via the selection dialog. The field itself is locked for input. The following option can be used to allow manual input again.
<Set name="allowConfigOnStrictHandling">true</Set>