Usually the APEX images reside in a directory on your server called /i/, which can be changed on instance or application level.
In 95% of all cases I saw, the image prefix is /i/, sometimes it is extended by a version number like /i501/ or /i181/. Continue reading
Oracle APEX offers a declarative setting for Text and Textarea items to “Trim Spaces”, which would remove leading/trailing spaces from the user input before saving the value to the database.
On a recent installation we had problems serving APEX static files (application and workspace), they would always report a 404 not found back from ORDS.
When installing Oracle APEX you also get a wealth of additional resources to explore: Packaged Applications.
For the Analyse Webserver Logfile Application (AWL) I wanted to show better information instead of just the Useragent String, because they are a mess and contain confusing information.
As an example look at this Useragent String: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.109 Safari/537.36
I rather would want to show it like this: Chrome (59) OS X
For my little Webserver Logfile Analysis project I had to solve the problem of how to stream data from a flat file into a relational datamodel in my target database.
Since I used NodeJS in several projects over the past years, it came to my mind at first. On a second thought and by consulting some friends another, easier, solution materialized:
Recently I wanted to set up better monitoring for our several FOEX webservers and decided not to use an off-the-shelf solution, since I wanted to have the analysis results in my Oracle Database, ready to be used by whatever internal tools we have.
This requirement pops up every now and then, time to put it in a blogpost so I can find it myself again when needed :-)
In various integration scenarios it is required to have users swiftly move between applications written in various technologies. This is very common for legacy Forms applications where some functionality is moved to APEX. From the Forms menu one entry could open a Form, another one an APEX page.
We recently upgraded a Web server from Oracle REST Data Services 2.10 to the latest version 17.4.1 . This might sound like jumping from the stone age to spaceships, but there have been only roughly 3 years between those two versions.
The good news is, ORDS ran fantastically stable for so long, and would have continued to do so even longer, but we wanted to use the latest and greatest features, hence the decision to upgrade.
Recently I had to investigate a requirement, where a translated application to Serbian language was showing Cyrillic characters, whereas the customer wanted to see Latin characters.
