search results

(...) ended) Storage for system files (RAID1) 140G Storage for SOLR Search indexes (200GB)   Notes: All WEBCON BPS components will be installed on WINDOWS IIS server (except database). 2.2.3.Recommended installation – setup for over 10 000 users The system can be scaled-up to support over 10 000 users by allotting additional resources to the followi (...)

Applies to version 2020.1.3; author: Tomasz Słuszniak   SSL Offloading (SSL Termination) is the process that allows you to transfer the encryption and decryption of the SSL connection through Reverse Proxy Server that is located “in front of” the application server. It is mainly used to relieve Web Server from performing these costly operations for the processor. &nbs

(...) ended) Storage for system files (RAID1) 140G Storage for SOLR Search indexes (200GB)   Notes: All WEBCON BPS components will be installed on WINDOWS IIS server (except database).   2.2.3.Recommended installation – setup for over 10 000 users   The system can be scaled-up to support over 10 000 users by allotting additional reso (...)

Applies to version: 2021.1.x and above; author: Michał Bednarz Introduction The article presents how to expand the WEBCON BPS installation with new application servers to easily support the higher load and increase the availability and reliability of WEBCON BPS applications. Important: Each subsequent WEBCON BPS application server requires an appropriate license. The WEBCON BPS Search Se

(...) globally for all applications/processes and all places where you can add an attachment – forms, HotFolders, HotMailBoxes, API. When specifying the attachment size – remember that the IIS server setting is the overriding limitation on the size of the added file. NOTE: from WEBCON BPS 2022 R1 version onwards it is possible to upload files bigger than 128 MB. The files are now sent in (...)

(...) Applies to version: 2021.1.x and above; author: Michał Bednarz  Introduction As of 2019.1.1 version the application pool and  WEBCONBPS  IIS server is set by default. Default settings are not recommended for production environments. In the production installations, a change of default settings is recommended to  minimalize the Portal response time to the first HTTP request after (...)

  Applies to version: 2021.x.x.xxx and above; author: Mateusz Syrek Introduction This article describes 3 variants for transferring WEBCON BPS databases to a different SQL server: new server has the same name as the old one, new server has a different name – applying SQL aliases, new server has a different name – no SQL aliases applied, changing configuration

Applies to version: 2023 R1 and above; author: Łukasz Maciaszkiewicz   Introduction In the present-day dynamic and distributed application environments data monitoring and analysis are key to ensure high efficiency, reliability, and optimization of an application. To address those challenges, the 2023 R1 WEBCON BPS version has introduced support for OpenTelemetry – a powerful

External content by Daniel Krüger; July 06, 2024 ;  The original post has appeared on daniels-notes.de   It should be obvious, that you should secure any website with an SSL certificate. There's neither an excuse nor a valid reason for it. Ok, there's one theoretical exception I would accept. You are run a single server environment. Use only local accounts.

Applies to version: 2023 R1 and above; author: Krystyna Gawryał   Introduction Version 2023 R1 of WEBCON BPS introduced the functionality to invalidate all active user sessions with the Global logout button. When the button is pressed, the user is logged out of all environments and platforms that use cookie-based authentication, including web browser tabs and windows, the mobile app

Applies to version: 2022 R1 and above; author: Konrad Keppert   Related documentation License Activation Service WEBCON BPS License activation Configuration of Portal-Service communication and selection of Nettops protocol   Introduction In the standard platform configuration, the name of the machine on which the WEBCON BPS components are installed is stored i

Applies to version: 2024 R1 and above; author: Łukasz Chechelski   Introduction   The Public Forms mechanism is an interesting solution that allows you to create external forms whose main advantage is anonymity. The site built in this way communicates with WEBCON BPS via the REST standard, creating new instances in specific processes. It is important to note that the mechani

(...) e is in place. The most convenient solution is to use a wildcard certificate that covers both the main domain and all its subdomains (e.g., *.yourdomain.com). After installing this certificate on the IIS server , both the Portal and all configured hub subdomains will be secured automatically, without the need to issue additional certificates. The final step is to ensure that network traffic directed to th (...)

Problem with launching the WEBCON portal after a new installation according to the instructions "WEBCON BPS standalone installation" (windows 2019 and updates, .net 4.7 installed automatically with the system, .net core hosting bundle 2.0.9, MSSQL 2019 express, Ms Sql Server Management Studio 18, IIS with Windows Authentication) -in the browser error http 500.19 - internal server error. Additiona

(...) More Information: This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose query string is greater than a specified value. If the request's query string is greater than the configured value, this error is returned. If the allowed length of the query (...)

I installed a new instance of webcon. In IIS I have new site with 3 bindings webcon-test.domain:.com 80 webcon-test.domain.com : 443 empty :80 Auth provider AD I'm not able to login to portal from the machine where webcon is installed via https/http://webcon-test.domain.com But link http://localhost works fine When I change a server and try to login via https/http://webcon-test.domai

Hello, we have a production- and a dev-environment. The production environment was installed in 10/2024 (R 2024 version.. and updated to the latest R2025), the dev-environment was installed a few days ago (R 2025). For each stage we have 2 system accounts: Prod: service_webcon service_webcon_iis Dev: service_webcon_dev service_webcon_iis_dev In the production environment the user