Basic Settings
Use the menu item Basic Settings to access all of JaniWeb’s general settings.
Changes made here may affect the application itself or its interfaces. Please only make changes here that you have discussed with your contact person.
Tab Clients
This is where you manage different clients in the system. Clients describe the origin of the data and are linked to the objects (e.g. persons, devices, device groups, etc.). The list contains the clients that have already been created. Select an entry to view details.
Press New to create a new client. Enter the required data and press Save.
Detail area
- ID: Enter the 10-digit client ID.
- Description: Enter a meaningful name.
- Visitor Client: Select this option if the client is to be used for visitor management.
- SAP Client: This field is automatically filled when importing data from SAP.
- BS_DIR: Specify the base directory of the application here.
- Folder: Specify the name of the SAP exchange directory here.
- Control Management File Path: In the field Control Management File Path, enter the directory in which parameter files for devices from the manufacturer Dormakaba are to be stored when they are created using control management. - this setting is applied only to devices for the connected client.
- terminal.localfile: Enter the directory for the trigger file that triggers the creation of the terminal.ini file.- this setting is applied only to devices for the connected client.
- terminal.parameter: Enter the directory in which parameter files for devices from the manufacturer Dormakaba are to be stored. - this setting is applied only to devices for the connected client.
Tab License
Here you can see which license you are using.
Tab Configuration
You can import a new license via the License Key field. Enter the new license key and press the Update License button.
The list displays the features that are currently licensed.
Tab Monitoring
Any features whose use is restricted are displayed here together with their level of use.
If required, activate the option Alert for license violation for all users and enter a note.
Tab Pay Per Use
Use the Due Date field to specify the day of the month on which the E-Mail for pay-per-use consumption should be generated. Consumption is always calculated for the previous month.
Enter the recipient's email address in the E-Mail field. You can delete this using the trash can button or add additional E-Mail addresses using the + button.
You can manually trigger the sending of the E-Mail using the Send E-Mail button. Then select the billing period for which you want to generate the email and confirm with the Send E-Mail button.
You can check the status of the last email sendings using the Show Log button.
Tab Password Rules
Specify the strength of the passwords used. Enter the minimum Password length and select the desired options for the composition of passwords.
- Failed attempts: Specify here after how many failed login attempts the user is blocked.
- Password expiration: Specify here after how many days users are prompted to enter a new password. Enter the number 0 if passwords should be valid indefinitely.
Tab GDPR
Specify the number of days after which expired records are automatically deleted. This is also possible for the server log files.
Tab SAP Settings
Specify the number of days for which the backups of the SAP import files should be kept. You can also specify the file name for exported bookings.
- PTEX …: Use these fields to define the file name and the client for deleted bookings.
- Enable API Gateway Data Import: Activate this option to enable importing master data via the API gateway.
- Enable API Gateway Data Export: Activate this option to enable exporting master data via the API gateway.
- Threshold person import (%): Use this field to set the threshold value for the import of persons. If the current import of persons falls below the threshold value (comparison with the number of persons from the last import), the import is rejected. You can use the Import anyway button to import a rejected import anyway. If the number of persons for import remains unchanged for 5 consecutive days, the persons will be imported on the 5th day.
Tabs General / Balance Data
Use these tabs to map the fields of an imported SAP record to the fields in JaniWeb.
Tab Database
Connection and other status information for the databases used is displayed here.
- Press Show function status to display a list of the functions used for all databases in a pop-up window.
- Press Show procedure status to display a list of the procedures used for all databases in a pop-up window.
Information about the version of a function or procedure can be found in the column Comment.
Tab Holiday Calendar
Press New to create a new holiday calendar. Enter an ID and a Description. Use the respective trash icon to delete a holiday calendar.
Tab Event Types
This is where you can specify the event types that should be available at the terminals. The event types are also used for the web terminal. For each booking type, specify whether the booking is triggered by the device itself or by a person (e.g. clock-in, clock-out).
To set the Text for a event type, press Translate. Enter the names for the respective languages and press Save.
With the Booking Type column you can select whether the booking marks the person as present or absent (this is particularly important for calculating working hours in the Overview Bookings menu item).
Use the respective trash icon to delete a event type.
Tab Document Types
This is where you can manage the document types that are available for selection on the tab Documents in the personal master data.
Tab General
This is where you can define which areas and tiles should be preset in the launchpad.
- Background image: Here you can upload a background image that will be displayed in the login screen.
- Logo: Here you can upload a logo that will be displayed in the login screen.
- All Tiles: Select this option to display all menu items as tiles on the launchpad by default.
- Info text / Info mail address: Enter the text and email address that will be displayed in the info area (accessible via the user icon in the top right > Info).
- Image Aspect Ratio: Define the aspect ratio (width:heigth) for images added in the menu items Persons/Visitors (e.g. 4:3, 16:9).
Area Launchpad Areas
Create areas here that will appear by default on the launchpad.
- Press Add to create a new area.
- To set the Text for an area, press Translate. Enter the names for the respective languages and press Save.
- Enter a number in the Sequence column to determine the sequence in which the areas are displayed.
Area Visible Tiles
Create tiles here that are linked to a PDF or link. When the tile is pressed, the PDF or linked page opens.
To set the Text and the Description for a tile, press Translate. Enter the names for the respective languages and press Save.
Tab Login
Specify here how users login.
Area Username and Password
If your system does not use LDAP login, you can assign fields from the HR master record as the Username and Password.
- Username: Select the desired field from the personnel master record (for example, Personnel No.).
- Password: Select the desired field from the personnel master record (e.g. Personal PIN).
Select Own Password if the user should be able to set their own password. The user receives an Initial Password for the first login. Select a field from the personnel master record in the field of the same name.
Forgotten passwords can be reset. To do this, remove the corresponding entry from the list. The user must then login again with their initial password.
Area Login Restrictions
Here you can specify which persons are allowed to login to JaniWeb.
- Criterion: Select the database field that is used to check the login authorization.
- Filter: Enter values separated by semicolons for users who are not allowed to login.
- Whitelist: Press this button to enter IP addresses and DNS names of all clients from which the kiosk application, for example, may be accessed.
Tab Properties
This is where you make settings for the SMTP server, LDAP connection, database backup, and SAP exchange directory. Any changes made here require a restart of the Tomcat server.
Area Device Master Record Calculation
- Enable FTP/SFTP for Master Record Dispatch: Use this option to specify that master data is to be transferred to devices from the manufacturer Dormakaba using FTP/SFTP.
- BPA9 Fallback: Specify an alternative method here for when transmission to a device via FTP/SFTP is not possible (e.g. for older devices).
- Select Server File System if the master data file is to be created in a directory on the server.
- Select Network Directory if the master data file is to be stored in a network directory via SFTP.
- Press Base supply to recalculate all master data and send it to the devices.
- Trigger File Master Record Calculation : Enter the path for the trigger file that is to be created after the master data calculation. If no file is to be created, the field can be left empty.
Area Device Models
Specify the various device types that can be selected in the menu Devices.
Area Login
Specify here the required settings for logging in via LDAP or SSO.
- If Type SSO is selected
- If Type LDAP is selected
- ldap_host: IP address of the LDAP server
- ldap_port: Port of the LDAP server
- ldap_user: Enter the full Distinguished Name (DN) for the LDAP user to search the Active Directory (AD) with.
- ldap_pwd: Password of the LDAP user
- ldap_base_dn: Enter the AD directories to be searched (separate multiple directories with commas).
- ldap_field: Enter the LDAP field that is to be compared with the system field ldap_person_table (hrcc1dnperso01, hrcc1dnbalan01, hrcc1dnperso01_data_relation) and ldap_person_field in order to assign the correct person.
- ldap_object_catergory: Enter the AD field to be searched for the permissions assigned in the roles under LDAP Group.
- using_ssl: Activate this option if SSL is to be used for the connection (LDAPS).
- ignore_leading_0: Activate this option if leading zeros are to be ignored when matching the ldap_field.
Area Email
Here you define the access data for the SMTP server used.
- If Authentication Type Basic Authentication is selected
- smtp_username: Enter the user name.
- smtp_password: Enter the password.
- smtp_server: Enter the server address of the SMTP server.
- smtp_port: Enter the port of the SMTP server.
- If Authentication Type OAuth2 is selected
-
smtp_oauth2_tenant_id: Microsoft tenant ID
-
smtp_oauth2_client_id: client ID of the registered application
-
smtp_oauth2_client_secret: application’s secret key
-
smtp_oauth2_token_endpoint: URL to obtain OAuth 2.0 tokens (https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token)
-
smtp_oauth2_scope: requested permissions (https://graph.microsoft.com/.default)
-
smtp_oauth2_redirect_uri: redirect URL after authentication (optional)
-
- If Authentication Type OAuth2 Delegated gesetzt ist
-
oauth2_delegated_tenant_id: Microsoft tenant ID
-
oauth2_delegated_client_id: client ID of the registered application
-
oauth2_delegated_client_secret: application’s secret key
- oauth2_delegated_auth_endpoint: URL to obtain OAuth 2.0 authorization (https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token)
-
oauth2_delegated_token_endpoint: URL to obtain OAuth 2.0 tokens (https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize)
-
oauth2_delegated_scope: requested permissions (https://graph.microsoft.com/.default)
-
oauth2_delegated_redirect_uri: redirect URL after authentication (https://hostname-janiweb-server/janiweb/oauth2-callback)
-
- admin_mail: Enter the email address that the system uses to send messages.
If the email address in the admin_mail field differs from the one in the smtp_username field, then the user in the smtp_username field needs authorisation to send emails as the user in the admin_mail field.
Area Master Record Lock
Activate the automatic master record lock here. You can specify after how many error attempts (number of failed attempts) within a certain period (time period in seconds) a master record should be locked. In addition, you can use the field event types to specify which booking errors should be taken into account.
Area SAP Settings
Make settings for updating SAP data here.
- sap_refresh_data_dir: Enter the directory from which the SAP import is to be read. Click the plus icon to select multiple directories.
- sap_refresh_archiving: Activate this option if you want to archive the imported data.
- booking_job_archiving: Activate this option if you want to archive the exported booking data.
Area Database Backup
Here you can configure an automatic database backup. The backup is performed once a day at night.
- db_backup_days: Enter the number of days for which the backup is to be stored.
- db_backup_dir: Enter the path where the backup should be saved.
- db_backup_filename: Enter the file name of the backup.
- db_backup_tables: Select the database tables to be backed up.
Area Devices
- terminal.localfile: Enter the directory for the trigger file that triggers the creation of the terminal.ini file.
- terminal.parameter: Enter the directory in which parameter files for devices from the manufacturer Dormakaba are to be stored.
- term.ip.gid: Specify the limit for the GID that can be assigned to a device.
- term.ip.did: Specify the limit for the DID that can be assigned to a device.
- INTUS COM Directory: Enter the directory where INTUSCOM is located.
Area Control Management
In the field control.management.filelocation, enter the directory in which parameter files for devices from the manufacturer Dormakaba are to be stored when they are created using control management.
Area Logging
In this area, you can use the field logs_directory to specify the directory to be sent to the recipients (specified in the field logs_recipients). Press Send logs to start sending.
- log_directory: The directory in which JaniWeb stores log files.
- log_limit: The maximum size of log files.
- log_count: The maximum number of log files.
- log_level: The logging level.
Area License Violation
Specify the threshold from which you would like to be informed about the current license usage.
- license_usage_email_recipient: Enter the email address to which information about license usage should be sent. Press the plus icon to add additional email recipients.
- license_violation_email_recipient: Enter the email address to which license violation information should be sent. Press the plus icon to add additional email recipients.
Area Other
Here you can define various other basic settings.
- inactivity_time: This value defines after how many minutes of inactivity a user will be automatically logged out. This is a global value that applies to all users. It can be overridden for individual users using the Session Timeout (minutes) setting in the Users menu.
- booking_report_limit: Use this option to define the maximum number of results displayed in the booking report.
- Delete archived booking records after (days): Use this option to specify the number of days after which archived bookings are deleted. This does not affect archived bookings themselves.
- badges_limit: Specify here how many people can be loaded at once (e.g. via the menu item Persons).
- disable_cookie_login: Activate this option if you do not want a cookie to be stored when logging in via the mobile application.
- Force Desktop Version: Once this option is activated, the application will be shown always in the desktop version, even if it will be called from a mobile device.
- Extended names search: This option must be activated if the first name and surname are split between the database fields hrcc1dnperso01.edit_name and hrcc1dnperso01.sort_name.
- Old Design: Starting with version 2.0, JaniWeb has a new look. If you want to use the old look, you must enable this option.
Tab Literals
This is where you can edit the terms used in the JaniWeb user interface (tab Literals) and Help texts for various languages.
IMPORTANT: If you change the terms used in the user interface, the operating instructions will no longer match the product. Drakos assumes no liability for the consequences of such changes.
Tab Import
You have the option to initially import personnel master records from a CSV file. The following fields describe a personnel master record. Entries with an X in the column Mandatory must be filled.
| Name | Data type | Table | Mandatory |
| admin_unit_id | char (4) | hrcc1dnperso01 | |
| source_sys | varchar (10) | hrcc1dnperso01 | X |
| timeid_no | char (24) | hrcc1dnperso01 | |
| from_date | date | hrcc1dnperso01 | X |
| to_date | date | hrcc1dnperso01 | X |
| timeid_version | char (1) | hrcc1dnperso01 | |
| perno | varchar (11) | hrcc1dnperso01 | X |
| first_name | varchar (40) | hrcc1dnperso01 | X |
| last_name | varchar (40) | hrcc1dnperso01 | X |
| langu | char (1) | hrcc1dnperso01 | |
| langu_iso | char (2) | hrcc1dnperso01 | |
| subsystem_grouping | char (3) | hrcc1dnperso01 | |
| access_control_group | char (2) | hrcc1dnperso01 | |
| personal_code | char (4) | hrcc1dnperso01 | |
| comp_code | char (4) | hrcc1dnperso01 | |
| costcenter | varchar (10) | hrcc1dnperso01 | |
| customer_field_1 | varchar (20) | hrcc1dnperso01 | |
| customer_field_2 | varchar (40) | hrcc1dnperso01 | |
| company_id | varchar (4) | hrcc1dnperso01_data_relation | |
| prohibition | char (1) | hrcc1dnperso01_data_relation | |
| prohibition_reason | varchar (150) | hrcc1dnperso01_data_relation | |
| ident | varchar (2) | hrcc1dnperso01_data_relation | |
| varchar (100) | hrcc1dnperso01_data_relation |
A sample file for importing persons in CSV format can be found here: Sample Personen CSV Import
Texts for functions
| Field | Values | Description | |
|---|---|---|---|
| gruppe | Terminal group from term_down => htyp. If no match is found, DEFAULT is used. | These 4 columns declare from where to start loading the options for a booking. | |
| sprache | ISO language code from hrcc1dnperso01 => langu_iso. If the language is not available, DE is used. | ||
| hersteller_id | D, K, PCS | Manufacturer from term_down => hersteller_id | |
| satza | Terminal record type of the booking. If not available, the record type falls back to an empty string. | ||
| sapsatza | SAP record type (e.g. P10, P20) to be transferred to SAP. If this field is filled, hrcc1upteven01 is served. | Fields for hrcc1upteven01 | |
| sapinfo | Additional SAP information, which is transmitted in customer_field_1. Mainly for P60 (e.g. }{AM0001). | ||
| security answer | Comma separated Semicolon separated Static response text to the terminal. |
Field antwort 1 / field info 1
zmail = hrcc1dnperso01.mail_indicator imail = hrcc1dnbalan01.time_eval_mail_indicator
Literals for zmail, imail will be configured in following table: imail = (SELECT `text` FROM `mail_texte` WHERE `kennzeichen` = 'I' AND `wert` = iflag); zmail = (SELECT `text` FROM `mail_texte` WHERE `kennzeichen` = 'Z' AND `wert` = zflag); |
|
| info | name, statv, info1, info2, info3, info4, info5, info6, info7, info8, info9, infoa, imail, zmail, lbook | Comma separated Semicolon separated Dynamic response text to the terminal. Is mainly read from hrcc1dnbalan01. |
|
| iform | R, L | Specifies on which side the spaces are output for stretching to the length specified in the field of the dynamic texts. R stands for right-aligned text and thus for the left side. With L, it is exactly the other way around. | |
| ilen | Determines the length with which the fields for info are read, left-aligned. If the field is 0 or empty, the function section is skipped. | ||
| db | Separated by commas Number of seconds searched backwards for a dynamic booking error. |
If a dynamic booking error is triggered, this refers to a new line in the funktion_texte. The original 4 fields (gruppe, sprache, hersteller_id and satza) are queried again, regardless of whether one or more of the criteria could not be found. This means that even if the sentence type, for example, was not available in the language langu_iso, the new check still starts with this. Dynamic booking errors can take the form of double bookings, plausibility checks, booking sequences and replacement bookings. Attention: This function can be used to configure an endless loop that is not intercepted by the dmgr function! |
|
| ppc | Regex field Separated by commas One or more record types that trigger the dynamic posting error. A leading exclamation mark negates the field. |
||
| pps | Regex field Separated by commas Describes all postings that should be held against the check. The triggering posting must also be represented. |
||
| ppe | Separated by commas Reference to the record type in the field satza, with which the program should continue when the trigger occurs. |
||
| statv | Separated by commas Has two fields that provide the text for a clock-in and clock-out response when tracking status. Can only be used in connection with a sapsatza P01 or SNN. With P10, the status is checked for a flat rate of 10 hours in the past, but a P01 booking is also transferred to SAP for this. With SNN, NN indicates the number of hours until the reset. In this case, a P10 or P20 booking is also transferred to SAP. |
||
| anhang | Defines a fixed booking attachment, which is set if the booking does not have its own booking attachment. | ||
| anhang_flag | anab, costc, extwa, saldo | Defines how the booking attachment is to be interpreted. anab Causes the attachment to be written to the att_abs_reason field in hrcc1upteven01. costc Causes the attachment to be written to the costc field in hrcc1upteven01. extwa This is only defined, but does not yet fulfill any function. saldo If this flag is set, an integer is expected as a booking attachment. This number then selects the respective field from the columns antwort and info, separated by semicolons. If the number is larger than answers and infos are defined, the last field is used. |
|
| 24x7 | OBSOLET Overrides the time profile check. | ||
Examples
Terminal replies
|
antwort
|
info
|
iform
|
ilen
|
|
|---|---|---|---|---|
| R1 | 0 | Returns a simple “R1” to the terminal. By setting ilen to 0, the function skips reading hrcc1dnbalan01 and formatting the values, thus saving processing time. | ||
| R1Hello | name | L | 20 | Outputs a booking confirmation, a greeting, and the name from hrcc1dnperso01 left-aligned, limited to 20 characters. It is important to ensure that the correct number of spaces is inserted after the greeting to obtain a line break. The length specified in ilen does not influence the response! |
| R40 | info1,info2,info3 | R | 8 | First outputs an “R40” and then outputs the fields info_1, info_2 and info_3 from hrcc1dnbalan01, fixed to 8 characters, right-aligned. |
| R1Hello,Balance: | name,info_1 | L | 20 | First “R1Hello” is displayed, then the name (20 characters long, left-aligned), the text “Balance: ” and finally the info_1 field from hrcc1dnbalan01. Again, make sure that the number of spaces in the column antwort is correct so that the texts are properly indented on the terminal. |
| R40 | info1,info2,info3;info4,info5,info6 | R | 8 | If the anhang_flag is set to saldo, an integer is expected in the booking attachment. This determines which of the fields separated by semicolons is selected. If the integer is greater than the number of fields, the last field is selected. In this example, if the value is 2, the only available field in antwort and the second (i.e. info4-6) would be used. |
Dynamic booking error
|
satza
|
db
|
ppc
|
pps
|
ppe
|
|
|---|---|---|---|---|---|
| BT | 60 | BT | BT | @ | Checks in the last 60 seconds against itself in a BT and thus triggers a simple double booking block. |
| B1 | 36000 | B1 | B[12] | @ | In the last 10 hours, checks B1 bookings against all B1 and B2 bookings. This is a plausibility check. If the last booking is B1, a double booking block is triggered. |
| A1 | 36000 | !B1 | B[123] | B1 | Checks whether the last booking from B1, B2 and B3 is not B1 and then refers to B1. This is a replacement booking that could be checked at a turnstile entrance. |
| A1 | 36000 | B[23] | B[123] | B1 | Same check as in the example above, only without negation. |
| A1 | 36000,36000 | BS,!B1 | B[ES123],B[123] | BE,B1 | First, BS (break start) is checked against BS, BE (break end), B1, B2 and B3. If a break start was last posted, the system now checks for a break end. It then checks again to see if another absence exists, as in the previous example. If this is the case, the system checks for B1. If none of these apply, it remains an A1 booking. Important: The db field must contain two values, otherwise the other fields in ppc, pps and ppe are not checked. |
| A1 | 84000 | ![AB][023] | X | An A1 booking may only be made if an A0, A2, A3, B0, B2, or B3 booking has been made in advance. If this is not the case, error X will be displayed. |
Status change booking
If the booking sequence is to be used to automatically determine whether the response is issued for an arrival or departure booking, the function checks the last valid booking for the person and derives the next expected booking type from this.
To do this, the corresponding values in the function_texts table must be configured accordingly.
|
satza
|
sapsatza
|
antwort
|
info
|
ilen
|
statv
|
|---|---|---|---|---|---|
| BT | P01 | R1 | statv, name | 20 | Guten Tag , Auf Wiedersehen |