Posts

Showing posts from 2022

Flows for APEX 22.2

With Flows for APEX 22.2, there are many new features to explore. We have planned several sessions to give you an overview of these and to engage with the Flows for APEX team. 29-SEP 2022 16:00-17:00 CET APEX Office Hours https://apex.oracle.com/officehours This session will be recorded and made available publicly on YouTube 04-OCT 2022 15:00-16:30 SGT / 08:00-09:30 CET https://us06web.zoom.us/meeting/register/tZcpdOmrqzMuG9WUsQZ8CuVX3Z3g4gqXYTOu More interactive session without recording for EMEA & Asia Pacific area 04-OCT 2022 10:00-11:30 EST / 16:00-17:30 CET https://us06web.zoom.us/meeting/register/tZUkcuyoqzooE9AgXlfHYwtZfmyG7nFwK9fe More interactive session without recording for EMEA & America area Yours truly, The Flows for APEX team https://flowsforapex.org

Out now: Flows for APEX 22.1!

We are proud to announce the general availability of Flows for APEX 22.1. You can download a free copy of this open source software at https://flowsforapex.org. Major new features of 22.1 include: - declaratively sending an e-mail using the service task in BPMN - support for repeating timers for non-interrupting boundary events - timers supporting the Oracle date/interval format during modeling - to prevent lost updates, we have introduced a "step key" - the modeler having the Monaco text editor integrated - APEX metadata being leveraged by the properties panel in the modeler - support for a business rule task in BPMN - an enhanced sample app "Expense Claims" to reflect most features of Flows for APEX 22.1 Have a look at the readme file in the software distribution to see a complete list of all enhancements. To give you an overview of what is new in Flows for APEX 22.1 and how the upgrade path looks like, we invite everybody to join one of the following online sessi

Protect your public server!

During the week, a DDoS attack with over 384 IP addresses from all over the world was started on our public Oracle APEX server. As we do like people (and proper bots) to make use of our free services to provide information about Oracle APEX, the bots managed to request an APEX page around 1.000 times a minute! With that many page views, the connection pool of Oracle REST Data Services (ORDS) with maximum 30 DB connections got full and people were starting to see an error message from ORDS. Of course we could scale up the connection pool with the database, but that would mean we had to scale up our hardware too, as ORDS was already taking up 100% CPU. Instead, my colleague Moritz Klein quickly found a way to throttle-down the requests in our proxy server installed in front of ORDS. We used a module called "event MPM". The configuration looks like this: # event MPM # StartServers: initial number of server processes to start # MinSpareThreads: minimum number of worker threads wh