<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Malek M.Edresi on Medium]]></title>
        <description><![CDATA[Stories by Malek M.Edresi on Medium]]></description>
        <link>https://medium.com/@malek.m.edresi?source=rss-e8b29f4ee50f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AW2fceG6Mz5YVUyDb3jUHA.jpeg</url>
            <title>Stories by Malek M.Edresi on Medium</title>
            <link>https://medium.com/@malek.m.edresi?source=rss-e8b29f4ee50f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:59:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@malek.m.edresi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Oracle Backend for Firebase APIs: Oracle’s Modern Alternative to Firebase for Enterprise…]]></title>
            <link>https://medium.com/@malek.m.edresi/oracle-backend-for-firebase-apis-oracles-modern-alternative-to-firebase-for-enterprise-40ae60702662?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/40ae60702662</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[oracle-database]]></category>
            <category><![CDATA[oracle-cloud]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 12:49:44 GMT</pubDate>
            <atom:updated>2026-07-29T00:42:36.911Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpd7ngbh81yeDJoiB7m3-w.png" /></figure><h3><strong>Oracle Backend for Firebase APIs: Oracle’s Modern Alternative to Firebase for Enterprise Applications</strong></h3><h4>Oracle is redefining backend development by bringing Firebase-style APIs directly to Oracle AI Database.</h4><p>For years, developers building Flutter, Android, iOS, and web applications have relied on Firebase because it provides a complete backend platform with authentication, storage, SDKs, and APIs without building everything from scratch.</p><p>Now Oracle has introduced Oracle Backend for Firebase, a self-managed Backend-as-a-Service (BaaS) toolkit that brings a familiar Firebase development experience while keeping Oracle AI Database at the core.</p><h4><strong>Why This Matters</strong></h4><p>Many enterprise teams love Oracle Database but prefer Firebase&#39;s simple client SDKs.</p><p><strong>Previously, developers typically built:</strong></p><p>· REST APIs with ORDS<br>· Authentication services<br>· File management<br>· Security layers<br>· Client SDK integrations</p><blockquote>Now Oracle packages these capabilities into a unified platform, dramatically simplifying backend development while preserving enterprise-grade Oracle features.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rymmKnG-lvtNOyQTnFQ4xA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_72L8d1JX09iVRx1EDYdRA.png" /></figure><h4><strong>What Oracle Backend for Firebase Provides</strong></h4><p><strong>Oracle Backend for Firebase includes:</strong></p><p>· Authentication<br>· Database APIs<br>· Object Storage<br>· Security Rules<br>· JavaScript SDK<br>· Flutter SDK<br>· Android SDK<br>· iOS SDK<br>· REST APIs<br>· Web Management Console<br>· Command Line Interface (CLI)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpd7ngbh81yeDJoiB7m3-w.png" /></figure><p>Unlike <strong>Google&#39;s managed Firebase service</strong>, Oracle&#39;s solution is self-managed, meaning you deploy it wherever your Oracle AI Database runs—on-premises, Docker, OCI, or another cloud provider.</p><h4><strong>Getting Started with Oracle Backend for Firebase</strong></h4><p>Let&#39;s look at how simple it is to connect a Flutter application to Oracle Backend for Firebase.</p><ol><li>Initialize the SDK</li></ol><pre>import &#39;package:oracle_backend_firebase/oracle_backend_firebase.dart&#39;;<br>await OracleBackend.initialize(<br>  projectId: &quot;medical-center&quot;,<br>  apiKey: &quot;YOUR_API_KEY&quot;,<br>);</pre><p>Once initialized, your application can securely communicate with Oracle AI Database through the backend services.</p><p>2. User Authentication</p><p>Creating a new user is straightforward.</p><pre>await OracleAuth.instance.signUp(<br>  email: &quot;doctor@example.com&quot;,<br>  password: &quot;SecurePassword123&quot;,<br>);</pre><p>Logging in:</p><pre>await OracleAuth.instance.signIn(<br>  email: &quot;doctor@example.com&quot;,<br>  password: &quot;SecurePassword123&quot;,<br>);</pre><p>This eliminates the need to build your own authentication API.</p><p>3. Reading Data</p><p>Suppose we have a Patients collection.</p><pre>final patients = await OracleDatabase.instance<br>    .collection(&quot;patients&quot;)<br>    .get();<br>    for (var patient in patients) {<br>      print(patient[&quot;full_name&quot;]);<br>}</pre><p>Instead of writing SQL endpoints manually, developers can work with simple SDK methods.</p><p>4. Inserting Data</p><p>Adding a new patient becomes just as easy.</p><pre>await OracleDatabase.instance<br>    .collection(&quot;patients&quot;)<br>    .add({<br>      &quot;full_name&quot;: &quot;John Smith&quot;,<br>      &quot;phone&quot;: &quot;+1 555 123456&quot;,<br>      &quot;blood_type&quot;: &quot;A+&quot;<br>    });</pre><p>Behind the scenes, Oracle AI Database stores and manages the data securely.</p><p>5. Flutter Healthcare Example</p><p>Imagine a healthcare application.</p><p>A doctor opens the mobile app.<br>The application authenticates the user.</p><pre>await OracleAuth.instance.signIn(...);</pre><p>The dashboard loads appointments.</p><pre>final appointments =<br>    await OracleDatabase.instance<br>        .collection(&quot;appointments&quot;)<br>        .get();</pre><p>Selecting a patient retrieves the medical history.</p><pre>final history =<br>    await OracleDatabase.instance<br>        .collection(&quot;medical_history&quot;)<br>        .where(&quot;patient_id&quot;, equals: patientId)<br>        .get();</pre><blockquote>No custom REST endpoint is required for these common operations.</blockquote><h4><strong>My Perspective</strong></h4><p>As an Oracle APEX and Oracle Database developer working on enterprise healthcare systems, I find this announcement particularly exciting.</p><p>In my projects, I normally expose business logic through ORDS REST APIs and consume them from Flutter applications. Oracle Backend for Firebase introduces another option for projects where developers want a Firebase-like experience while still using Oracle AI Database. For greenfield mobile applications, it can reduce the amount of backend code needed and speed up development, while ORDS remains an excellent choice for complex, highly customized business APIs.</p><p>This new toolkit fits naturally into architectures built around Oracle APEX, ORDS, Flutter, and Docker, allowing enterprise teams to maintain their Oracle ecosystem while simplifying mobile backend development.</p><h4><strong>Final Thoughts</strong></h4><p>Oracle Backend for Firebase isn&#39;t trying to replace Firebase feature-for-feature.</p><p>Instead, it delivers a Firebase-like developer experience while leveraging Oracle AI Database as the foundation. For organizations already invested in Oracle, this offers a compelling path to modern mobile and web application development without leaving the Oracle ecosystem.</p><p>I&#39;m looking forward to exploring it further and seeing how it evolves alongside Oracle APEX, ORDS, and Oracle AI Database.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40ae60702662" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Enterprise RAG Systems the Smart Way with Oracle 26ai]]></title>
            <link>https://medium.com/@malek.m.edresi/building-enterprise-rag-systems-the-smart-way-with-oracle-26ai-36752633245f?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/36752633245f</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[vector-database]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 22:31:13 GMT</pubDate>
            <atom:updated>2026-07-14T22:31:13.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-dNAniknipZYd4WOpedJLQ.jpeg" /></figure><h3>A no-nonsense guide to the Oracle Vector Search RAG Toolkit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ipPbgbFDmeDahYCXFur1BA.png" /><figcaption>Architecture Diagram</figcaption></figure><h3>The Problem: RAG Is Hard</h3><p>Let’s be honest — building a production-ready RAG (Retrieval-Augmented Generation) system is complicated.</p><p>You need to:</p><ul><li>Ingest documents (PDFs, Word files, emails)</li><li>Chunk them intelligently</li><li>Generate vector embeddings</li><li>Store and index those vectors</li><li>Build a hybrid search that combines semantic similarity with metadata filters</li><li>Keep everything in sync when data changes</li></ul><p>Most solutions today involve stitching together multiple tools: one for ingestion, one for vector storage (Pinecone, Weaviate, Milvus), one for the LLM, and a traditional database for metadata. It works, but it’s fragile, complex, and expensive to maintain.</p><p><strong>What if you could do it all inside your existing Oracle Database?</strong></p><h3>The Solution: Oracle 26ai Hybrid RAG Framework</h3><p>Meet the <strong>Oracle Vector Search RAG Toolkit</strong> — a complete, modular framework for building hybrid RAG systems natively on Oracle Database 26ai.</p><p>Built for Oracle developers, APEX developers, and database architects, this toolkit is both an <strong>educational resource</strong> and a <strong>production-grade template</strong>.</p><p>Here’s what makes it special:</p><h4>1. Native Vector Search</h4><p>Oracle 26ai supports native vector data types (VECTOR(384, FLOAT32)) and HNSW vector indexes. No external vector database required. Your vectors live right next to your relational data — with all the ACID guarantees you expect from Oracle.</p><h4>2. Intelligent Chunking</h4><p>The framework uses DBMS_VECTOR_CHAIN.UTL_TO_CHUNKS to automatically chunk large documents. It handles CLOBs and BLOBs (PDFs, Word docs) out of the box.</p><h4>3. Automated Embeddings</h4><p>Vector embeddings are generated seamlessly via DBMS_VECTOR.UTL_TO_EMBEDDING using the E5_SMALL model. You don&#39;t need to call external embedding APIs — everything runs inside the database.</p><h4>4. Event-Driven Synchronization</h4><p>An asynchronous event queue (AI_SEC_RAG_SYSTEM_L_EVENT) handles background synchronization. When your source data changes, the system updates the vector index automatically — without blocking your primary transactions.</p><h4>5. Hybrid Retrieval Engine</h4><p>The search pipeline combines <strong>semantic vector similarity</strong> (Cosine distance) with <strong>structured metadata filters</strong>. This means you get the best of both worlds: AI-powered semantic search with the precision of SQL filtering.</p><h4>6. Pluggable Architecture</h4><p>Everything is built with modular PL/SQL packages — separated DAO, Search, Embedding, and Admin layers. You can extend or replace any component without breaking the whole system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QjFHYmDC2P5l17Vq0d9NMw.png" /><figcaption><strong>Example AI RAG Documents with Vector Embeddings</strong></figcaption></figure><h3>How It Works (In 3 Steps)</h3><p><strong>Step 1: Ingest</strong><br>Data flows from your source tables into the system.</p><p><strong>Step 2: Process</strong><br>A background sync process extracts text, generates overlapping chunks, and computes semantic embeddings.</p><p><strong>Step 3: Search</strong><br>All processed data is stored in vector-indexed tables for lightning-fast retrieval.</p><p>That’s it. A complete RAG pipeline, running entirely inside Oracle Database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O5EcgEiMQJp8AmdP_0lpHA.png" /><figcaption><strong>Example Search All Documents Using AI Vector Search</strong></figcaption></figure><h3>Getting Started</h3><p>Deploying the toolkit is straightforward:</p><ol><li><strong>Check prerequisites</strong> — Oracle Database 23ai/26ai with Vector Search enabled</li><li><strong>Run the automated </strong><strong>install.sql script</strong></li><li><strong>Start indexing</strong> your first document using the API</li></ol><p>The project includes detailed documentation:</p><ul><li><a href="https://github.com/malek-al-edresi/oracle-26ai-hybrid-rag-framework/blob/main/docs/architecture.md">Architecture Details</a> — System design, chunking strategy, and vector indexes</li><li><a href="https://github.com/malek-al-edresi/oracle-26ai-hybrid-rag-framework/blob/main/docs/data_flow.md">Data Flow Diagrams</a> — Visual guides to the ingestion and search pipelines</li><li><a href="https://github.com/malek-al-edresi/oracle-26ai-hybrid-rag-framework/blob/main/docs/developer_guide.md">Developer Guide</a> — Onboarding and extensibility patterns</li><li><a href="https://github.com/malek-al-edresi/oracle-26ai-hybrid-rag-framework/blob/main/docs/api_documentation.md">API Documentation</a> — PL/SQL package specs and usage examples</li><li><a href="https://github.com/malek-al-edresi/oracle-26ai-hybrid-rag-framework/blob/main/docs/installation_guide.md">Installation Guide</a> — Step-by-step setup instructions</li></ul><h3>Why This Matters for Your Organization</h3><p>Most RAG implementations today are <strong>Frankenstein architectures</strong> — a patchwork of external services that are hard to secure, hard to scale, and hard to maintain.</p><p>This framework offers a different path:</p><p><strong>Lower latency</strong> — No network hops to external vector databases<br><strong>Simpler architecture</strong> — One database does it all<br><strong>Enterprise security</strong> — Your data never leaves Oracle<br><strong>ACID compliance</strong> — Transactions work the way they should<br><strong>Cost savings</strong> — No need for additional vector database licenses</p><h3>The Bottom Line</h3><p>If you’re already an Oracle shop — or even if you’re just exploring enterprise RAG — the Oracle Vector Search RAG Toolkit is worth your time. It proves that you don’t need a dozen different tools to build a production-ready RAG system. Sometimes, the best solution is already in your database.</p><p><strong>Check it out on GitHub</strong>: <a href="https://github.com/malek-al-edresi/oracle-26ai-hybrid-rag-framework">malek-al-edresi/oracle-26ai-hybrid-rag-framework</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36752633245f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle APEX 26.1]]></title>
            <link>https://medium.com/@malek.m.edresi/oracle-apex-26-1-2f6c1bde4bd8?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f6c1bde4bd8</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[oracle-apex]]></category>
            <category><![CDATA[oracle]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 06:25:53 GMT</pubDate>
            <atom:updated>2026-06-22T06:25:53.294Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U80quSAGDnrE7TsBgWWEqg.jpeg" /></figure><h3>Oracle APEX 26.1 and Antigravity AI: A Modern Approach to Understanding and Maintaining Large APEX Applications</h3><p>As Oracle APEX applications continue to grow in size and complexity, developers need better tools for version control, documentation, code reviews, and application maintenance.</p><p>With Oracle APEX 26.1, exporting applications into structured source files opens the door to modern development workflows. Combining this capability with the Antigravity AI IDE creates a powerful environment for managing, understanding, and improving APEX applications.</p><h3>Why This Combination Matters</h3><p>Oracle APEX is one of the fastest ways to build enterprise applications. However, large applications often contain hundreds of pages, regions, processes, and shared components.</p><p>By exporting an APEX application into files and opening it inside Antigravity AI, developers gain:</p><ul><li>Better visibility into application structure.</li><li>AI-assisted code understanding.</li><li>Easier documentation generation.</li><li>Faster code reviews.</li><li>Improved Git integration.</li><li>Simplified maintenance of large applications.</li></ul><h3>Application Export Structure</h3><p>Oracle APEX 26.1 allows applications to be exported into multiple files instead of a single SQL export.</p><p>The result is a clean project structure:</p><pre>f105/<br>├── application.apx<br>├── page-groups.apx<br>├── pages/<br>├── shared-components/<br>├── supporting-objects/<br>└── workspace-components/</pre><p>This makes Oracle APEX projects behave much more like modern software projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*4YUKesdFh8P461-b" /><figcaption>Figure 1. Oracle APEX application inside SQL Developer VSCode.</figcaption></figure><h3>Reviewing Individual Pages</h3><p>Each page is stored as an individual file.</p><p>For example:</p><pre>p09999-SYS_P_LOGIN.apx</pre><p>The page definition contains:</p><ul><li>Page settings</li><li>Authentication configuration</li><li>Regions</li><li>Items</li><li>Processes</li><li>Dynamic Actions</li><li>Template settings</li></ul><p>Developers can inspect page behavior without opening App Builder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZnmTSWmR6TeX3q-N" /><figcaption>Figure 2. Reviewing the exported Login page definition directly inside Antigravity AI without opening Oracle APEX App Builder.</figcaption></figure><h3>Exporting from SQL Developer on VS Code</h3><p>The export process is straightforward:</p><ol><li>Open the APEX application.</li><li>Right-click the application.</li><li>Select <strong>Export</strong>.</li><li>Choose the destination folder.</li><li>Open the exported files in Antigravity AI.</li></ol><p>The entire application becomes accessible as source file :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/0*lrotF41ug8Z0uoeM" /><figcaption>Figure 3. Exporting an Oracle APEX application from SQL Developer for VS Code.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BRRuvKOi-WTjBT5P" /><figcaption>Figure 4. Configuring the export destination and generating the APEX application source files.</figcaption></figure><h3>Applying Changes with AI Assistance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lfeztShAGJPjFfnE" /><figcaption>Figure 5. Using Antigravity AI to analyze Oracle APEX page files and apply AI-assisted improvements.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HaVDvSe1wGqG2TAf" /><figcaption>Figure 5. Applying Oracle APEX page changes directly from VS Code.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m9XOqaVJKNsE3MAc" /><figcaption>Figure 8. Final customized Oracle APEX login page implemented in the Medical Center System.</figcaption></figure><h3>Final Thoughts</h3><p>Oracle APEX 26.1 already provides an excellent low-code development platform. Pairing it with an AI-powered IDE such as Antigravity introduces a new way to explore, document, review, and maintain applications.</p><p>For teams managing large Oracle APEX applications, exporting source files and leveraging AI tools can significantly improve productivity and application quality.</p><p>#OracleAPEX #OracleDatabase #OracleAPEX26 #ArtificialIntelligence #AI #LowCode #SoftwareDevelopment #OracleDevelopers #SQLDeveloper #Git #DeveloperTools #OracleCloud #EnterpriseApplications #AntigravityAI #APEXDevelopment #DevTools #OracleCommunity #DatabaseDevelopment #AIIDE #OpenSource</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f6c1bde4bd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating Oracle Database 26ai with JasperReports Server Using Docker]]></title>
            <link>https://medium.com/@malek.m.edresi/integrating-oracle-database-26ai-with-jasperreports-server-using-docker-8711a318fb4e?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8711a318fb4e</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[jasper-reports]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[oracle-database]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Sat, 13 Jun 2026 01:52:21 GMT</pubDate>
            <atom:updated>2026-06-17T07:05:18.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fhCrqTH75ey2FVZtncHwJw.jpeg" /></figure><p><strong>Enterprise applications </strong>often require powerful <strong>reporting capabilities </strong>alongside modern database technologies. To simplify this process, I created an open-source project that demonstrates how to integrate Oracle Database 26ai with <strong>JasperReports</strong> Server using <strong>Docker containers.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXCPLdXUq11BR5C_q0nJ4w.png" /></figure><h3>What the Project Provides</h3><p>This project delivers a ready-to-use environment that combines:</p><ul><li>Oracle Database 26ai</li><li>JasperReports Server</li><li>Docker-based deployment</li><li>JDBC connectivity between Oracle and JasperReports</li><li>Enterprise reporting capabilities</li></ul><p>The objective is to help developers quickly build reporting solutions without spending hours on manual configuration.</p><h3>Architecture Overview</h3><p>The architecture is straightforward:</p><p>Oracle Database 26ai → JDBC Connection → JasperReports Server → Reports &amp; Dashboards</p><p>JasperReports retrieves data directly from Oracle and generates professional reports in formats such as PDF and Excel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBdZ9_-QDSUz198UlRVPFg.png" /></figure><h3>Why Use Docker?</h3><p>Docker simplifies deployment by packaging all required components into isolated containers.</p><p>Benefits include:</p><ul><li>Fast setup</li><li>Consistent environments</li><li>Easy maintenance</li><li>Simplified upgrades</li><li>Portable deployments</li></ul><h3>Getting Started</h3><p>Clone the repository:</p><pre>git clone https://github.com/malek-al-edresi/Oracle-Database-AI-26ai-Integration-for-Jasper-Report-Server.git<br>cd Oracle-Database-AI-26ai-Integration-for-Jasper-Report-Server</pre><p>Start the environment:</p><pre>docker compose up -d</pre><p>After startup, JasperReports Server can connect directly to Oracle Database and begin generating reports.</p><h3>Use Cases</h3><p>This setup is useful for:</p><ul><li>Enterprise reporting systems</li><li>Healthcare applications</li><li>Financial reporting</li><li>Business intelligence dashboards</li><li>Operational analytics</li></ul><h3>Repository</h3><p>GitHub Repository:</p><blockquote><a href="https://github.com/malek-al-edresi/Oracle-Database-AI-26ai-Integration-for-Jasper-Report-Server">https://github.com/malek-al-edresi/Oracle-Database-AI-26ai-Integration-for-Jasper-Report-Server</a></blockquote><h3>Conclusion</h3><p>Combining Oracle Database 26ai with JasperReports Server creates a powerful reporting platform. By using Docker, deployment becomes faster, easier, and more reliable, allowing developers to focus on building reports instead of configuring infrastructure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8711a318fb4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Oracle Database Free 26ai, ORDS, and APEX 26 with Docker]]></title>
            <link>https://medium.com/@malek.m.edresi/running-oracle-database-free-26ai-ords-and-apex-26-with-docker-5f571dd95cb9?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f571dd95cb9</guid>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[oracle-database]]></category>
            <category><![CDATA[oracle-apex]]></category>
            <category><![CDATA[oracle-cloud]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 20:53:39 GMT</pubDate>
            <atom:updated>2026-06-10T20:53:39.665Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUTbfSWZj3hg8B6dZn9vSw.jpeg" /></figure><p>Setting up a <strong>complete Oracle development environment</strong> can take time, especially when working with <strong>Oracle Database</strong>, <strong>ORDS</strong>, and Oracle APEX. To simplify the process, I created an open-source project that provides a ready-to-use Docker-based environment for <strong>Oracle Database Free 26ai</strong>, <strong>Oracle REST Data Services (ORDS)</strong>, and Oracle APEX 26.</p><p>The goal is simple: start a modern Oracle development stack in minutes with minimal manual configuration.</p><h3>What’s Included</h3><ul><li>Oracle Database Free 26ai</li><li>Oracle REST Data Services (ORDS)</li><li>Oracle APEX 26</li><li>Docker Compose configuration</li><li>Persistent storage for database data</li><li>Easy startup and deployment process</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r2MvXiLlw4R3ilI8INwJjA.png" /></figure><h3>Why Use This Project?</h3><p>Developers often spend valuable time installing and configuring Oracle components before they can begin building applications. This project removes much of that complexity and provides a clean environment for:</p><ul><li>Oracle APEX development</li><li>PL/SQL testing</li><li>Learning Oracle Database 26ai</li><li>Rapid prototyping</li><li>Local development environments</li></ul><h3>Getting Started</h3><p>Clone the repository:</p><pre>git clone https://github.com/malek-al-edresi/oracle-free-26ai-ords-apex-26.git<br>cd oracle-free-26ai-ords-apex-26</pre><p>Start the environment:</p><pre>docker compose up -d</pre><p>After the containers are running, Oracle Database, ORDS, and APEX will be available and ready for development.</p><h3>Project Highlights</h3><ul><li>Containerized architecture</li><li>Fast deployment</li><li>Easy maintenance</li><li>Reproducible environments</li><li>Suitable for development and testing</li></ul><h3>Open Source Repository</h3><p>The complete source code is available on GitHub:</p><blockquote><a href="https://github.com/malek-al-edresi/oracle-free-26ai-ords-apex-26">https://github.com/malek-al-edresi/oracle-free-26ai-ords-apex-26</a></blockquote><h3>Conclusion</h3><p>Docker makes Oracle development significantly easier. By combining Oracle Database Free 26ai, ORDS, and APEX into a single containerized solution, developers can focus on building applications instead of spending time on installation and configuration.</p><p>I hope this project helps Oracle developers get started faster and explore the latest Oracle technologies with less effort.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f571dd95cb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an Oracle Vector Health Toolkit for AI Vector Search and RAG Systems]]></title>
            <link>https://medium.com/@malek.m.edresi/building-an-oracle-vector-health-toolkit-for-ai-vector-search-and-rag-systems-a221314af735?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a221314af735</guid>
            <category><![CDATA[vector-database]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[solutions]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 01:49:50 GMT</pubDate>
            <atom:updated>2026-06-13T02:08:27.060Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Zraz8Furrr-4JgUwgZttHw.jpeg" /></figure><p>As <strong>Oracle AI Vector Search</strong> becomes a core component of modern AI and <strong>Retrieval-Augmented Generation (RAG) applications,</strong> maintaining vector quality is becoming just as important as building the search functionality itself.</p><p>While working on Oracle Database 23ai and 26ai environments, I noticed a recurring challenge: vector search environments often fail silently.</p><p><strong>A system may contain:</strong></p><ul><li>Missing embeddings</li><li>Invalid vector dimensions</li><li>Missing vector indexes</li><li>Inconsistent vector configurations</li><li>Degraded RAG quality</li></ul><p>These issues are <strong>difficult</strong> to detect before they start impacting application accuracy and search quality.</p><p>To address this problem, I created Oracle Vector Health Toolkit, an open-source PL/SQL toolkit designed to help Oracle developers monitor and validate AI Vector Search environments.</p><h3>What the Toolkit Does</h3><p>The toolkit provides several validation and administration capabilities:</p><ul><li>Vector health diagnostics</li><li>Embedding validation</li><li>Vector dimension verification</li><li>Vector index validation</li><li>Missing embedding detection</li><li>Automated embedding refresh operations</li><li>Human-readable health reports</li></ul><p>The goal is to provide a simple way to evaluate whether an Oracle AI Vector Search environment is healthy and ready for production workloads.</p><h3>Health Report Example</h3><p>The toolkit generates a diagnostic report that summarizes the current status of the vector environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80FSbmjAC3Lwy-lHNzK29w.png" /></figure><p>The report validates:</p><ul><li>Total documents</li><li>Embedding generation status</li><li>Vector dimensions</li><li>Vector index availability</li><li>Overall environment status</li></ul><h3>Refreshing Missing Embeddings</h3><p>One common operational issue is the presence of records that do not have embeddings.</p><p>The toolkit can automatically identify missing vectors and execute the configured embedding generation function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVCAo1HAV0XmPd3AJWnYMQ.png" /></figure><p>This helps maintain vector consistency without requiring manual intervention.</p><h3>Why This Matters</h3><p>Oracle AI Vector Search enables developers to store vectors directly inside Oracle Database and build semantic search and RAG applications using standard SQL and database features. Oracle positions AI Vector Search as a core capability for semantic search, vector indexes, and enterprise RAG architectures.</p><p>As AI systems grow, operational monitoring becomes increasingly important. Vector quality issues can reduce retrieval accuracy and negatively impact downstream LLM responses.</p><p>Oracle Vector Health Toolkit aims to provide a lightweight operational layer for monitoring vector environments and identifying issues early.</p><h3>Project Repository</h3><p>GitHub Repository:</p><blockquote><a href="https://github.com/malek-al-edresi/oracle-vector-health-toolkit">https://github.com/malek-al-edresi/oracle-vector-health-toolkit</a></blockquote><p>Contributions, feedback, and ideas are always welcome.</p><h3>Conclusion</h3><p>Building AI applications is only part of the challenge. Maintaining healthy vector environments is equally important.</p><p>Oracle Vector Health Toolkit was created to help Oracle developers monitor, validate, and manage AI Vector Search environments more effectively while building production-ready RAG systems on Oracle Database 23ai and 26ai.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a221314af735" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing OTP MFA in Oracle APEX: A Simple Step-by-Step Guide]]></title>
            <link>https://medium.com/@malek.m.edresi/implementing-otp-mfa-in-oracle-apex-a-simple-step-by-step-guide-51d49bb809a5?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/51d49bb809a5</guid>
            <category><![CDATA[mfa]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[oracle-aepx]]></category>
            <category><![CDATA[otp-verification]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Tue, 12 May 2026 02:43:04 GMT</pubDate>
            <atom:updated>2026-05-12T02:43:04.526Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5o2QXSP0IEgArFVm2qvMdA.jpeg" /></figure><p>Two-factor authentication with OTP is one of the easiest ways to strengthen an Oracle APEX login flow. In the solution shown in your package, the system generates a one-time password, stores it temporarily, sends it to the user, verifies it on a separate page, and then marks the login as trusted for a limited time. The package also keeps a history record for generated and verified OTP attempts, which makes the flow easier to track and control.</p><h3>1. What this solution does</h3><p>The login process is split into two stages. First, the user enters the normal username and password. If the user already has a recent verified OTP entry, the system allows direct login. If not, the system creates a new OTP, sends it to the user, and redirects them to an OTP verification page. After the OTP is confirmed, the user is logged in and the OTP is moved into history as verified.</p><h3>2. Main objects used in the flow</h3><p>This implementation depends on two tables. The first table stores the active OTP temporarily, and the second table stores the OTP history for auditing and verification tracking. The temp OTP row is time-limited, while the history row keeps the generated and verified status.</p><p>Here is the idea in a simple form:</p><pre>-- Temporary OTP storage<br>OTP_TEMP_TABLE (<br>    username,<br>    otp_code,<br>    expires_at,<br>    created_at<br>);<br>-- OTP history<br>OTP_HISTORY_TABLE (<br>    username,<br>    otp_code,<br>    status,<br>    created_at,<br>    verified_at<br>);</pre><h3>3. Step 1: Generate the OTP</h3><p>The OTP in your package is a 6-digit random number. The general logic is simple: create a random value, convert it to a string, and pad it with zeroes when needed. Your package does this through a dedicated function.</p><pre>FUNCTION generate_otp RETURN VARCHAR2 IS<br>BEGIN<br>    RETURN LPAD(TRUNC(DBMS_RANDOM.VALUE(0, 999999)), 6, &#39;0&#39;);<br>END;</pre><h3>4. Step 2: Clear the old OTP and save the new one</h3><p>Before inserting a fresh OTP, the system deletes any previous temporary OTP for the same user. Then it inserts the new code into the temp table with a short expiry time, and writes a GENERATED record into the history table. In your package, the expiry is 5 minutes.</p><pre>PROCEDURE generate_and_store_otp(p_username IN VARCHAR2, p_otp OUT VARCHAR2)IS<br>BEGIN<br>    DELETE FROM otp_temp_table<br>     WHERE UPPER(username) = UPPER(p_username);<br>p_otp := generate_otp;<br>    INSERT INTO otp_temp_table (<br>        username, otp_code, expires_at, created_at<br>    ) VALUES (<br>        p_username,<br>        p_otp,<br>        SYSDATE + (5 / 1440),<br>        CURRENT_TIMESTAMP<br>    );<br>    INSERT INTO otp_history_table (<br>        username, otp_code, status, created_at<br>    ) VALUES (<br>        p_username,<br>        p_otp,<br>        &#39;GENERATED&#39;,<br>        SYSDATE<br>    );<br>END;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SL_E0AHSHFovbw-cT3MQg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JgiH1QxcfFfdDDjv7TuR6g.png" /></figure><h3>5. Step 3: Send the OTP to the user</h3><p>After the OTP is created, it is sent to the user’s email address. In your code, the email lookup is handled separately, and the actual sending is done by an email procedure. This keeps the OTP logic clean and reusable.</p><pre>v_email := get_user_email(p_username);<br>IF v_email IS NOT NULL THEN<br>    send_otp_email(<br>        p_email =&gt; v_email,<br>        p_code  =&gt; v_otp<br>    );<br>END IF;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQBWVQyUcOkOcdQbE0J0-w.png" /></figure><h3>6. Step 4: Redirect the user to the OTP page</h3><p>Once the OTP is generated and delivered, the login process redirects the user to the OTP page. In your package, this is done with an APEX page URL and the APEX engine is stopped so the normal login does not continue before verification.</p><pre>l_url := apex_page.get_url(https://medium.com/p_page%20=&gt;%20156);<br>apex_util.redirect_url(https://medium.com/l_url);<br>apex_application.stop_apex_engine;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*83fe07ZLpdKjP9_1VGINAA.png" /></figure><h3>7. Step 5: Verify the entered OTP</h3><p>On the OTP page, the system checks whether the entered code matches the stored active OTP and whether it is still valid. Your package performs this check against the temp table and also checks the expiration time.</p><pre>FUNCTION check_otp_match(p_username IN VARCHAR2, p_otp IN VARCHAR2)<br>RETURN BOOLEAN IS<br>    v_count NUMBER;<br>BEGIN<br>    SELECT COUNT(*)<br>      INTO v_count<br>      FROM otp_temp_table<br>     WHERE UPPER(username) = UPPER(p_username)<br>       AND otp_code = p_otp<br>       AND expires_at &gt; SYSDATE;<br>RETURN v_count &gt; 0;<br>END;</pre><h3>8. Step 6: Log the user in after valid OTP</h3><p>If the OTP is correct, the system logs the user in using the normal APEX authentication process, then redirects them to the home page. After that, the OTP is recorded as verified and removed from the temp table. This makes the OTP single-use and prevents reuse.</p><pre>PROCEDURE login_after_valid_otp(<br>    p_username IN VARCHAR2,<br>    p_password IN VARCHAR2,<br>    p_otp      IN VARCHAR2<br>) IS<br>BEGIN<br>    IF check_otp_match(p_username, p_otp) THEN<br>        apex_authentication.login(<br>            p_username           =&gt; p_username,<br>            p_password           =&gt; p_password,<br>            p_uppercase_username =&gt; TRUE<br>        );<br>  apex_util.redirect_url(https://medium.com/apex_page.get_url(p_page%20=&gt;%201));<br>        update_otp_history_as_verified(p_username);<br>    ELSE<br>        raise_application_error(-20001, &#39;Invalid OTP&#39;);<br>    END IF;<br>END;</pre><h3>9. Step 7: Mark the OTP as verified</h3><p>The final OTP step is the history update. The system reads the temporary OTP, finds the matching history record, changes its status to VERIFIED, and then deletes the temp row. Your package does exactly this to keep the flow clean and auditable.</p><pre>PROCEDURE update_otp_history_as_verified(p_username IN VARCHAR2) IS<br>    v_otp_code  VARCHAR2(6);<br>BEGIN<br>    SELECT otp_code<br>      INTO v_otp_code<br>      FROM otp_temp_table<br>     WHERE UPPER(username) = UPPER(p_username);<br>UPDATE otp_history_table<br>       SET status = &#39;VERIFIED&#39;,<br>           verified_at = SYSDATE<br>     WHERE UPPER(username) = UPPER(p_username)<br>       AND otp_code = v_otp_code;<br>    DELETE FROM otp_temp_table<br>     WHERE UPPER(username) = UPPER(p_username);<br>END;</pre><h3>10. Step 8: Allow trusted users to skip OTP for a short period</h3><p>Your package also supports a trusted-login shortcut. If the user already has a verified OTP within the last 24 hours, the system skips the OTP step and lets the user log in directly. That check is handled through the history table and a time-based validity window.</p><pre>IF has_history(p_username)<br>   AND has_recent_verified_otp(p_username) THEN<br>    apex_authentication.login(<br>        p_username           =&gt; p_username,<br>        p_password           =&gt; p_password,<br>        p_uppercase_username =&gt; TRUE<br>    );<br>  apex_util.redirect_url(https://medium.com/apex_page.get_url(p_page%20=&gt;%201));<br>END IF;</pre><h3>11. General flow summary</h3><p>The complete flow is straightforward: login with username and password, generate OTP, send OTP, verify OTP, log in, and save the OTP as verified. The temporary OTP lasts only a few minutes, while the verified history can be reused for a short trust period. That is the core design behind your package.</p><h3>12. Final article text</h3><p><strong>Step-by-Step OTP MFA Implementation in Oracle APEX</strong></p><p>OTP-based multi-factor authentication adds a second security layer to the standard login process. In Oracle APEX, the best approach is to split the login into two phases. The user first enters the normal credentials, then receives a one-time code, and finally confirms that code before access is granted. The implementation in this package uses a temporary OTP table, a history table, and a small set of reusable procedures and functions to manage the entire flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JgiH1QxcfFfdDDjv7TuR6g.png" /></figure><p>The first step is OTP generation. A 6-digit code is created using random number logic and padded to keep a consistent format. The system then removes any previous OTP for the same user, stores the new code in a temporary table, and writes a history entry with the status GENERATED. This makes sure only the latest code is active.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*CEj6RHg1HDZYRg88UUg8Xg.png" /></figure><p>The second step is delivery. The system looks up the user’s email address and sends the OTP through an email routine. This keeps the OTP process separated from the mail implementation, which makes the package easier to maintain and extend. After sending the code, the user is redirected to a dedicated OTP verification page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vts33V48oY1YUdGw0B1Q1A.png" /></figure><p>The third step is verification. When the user enters the code, the system checks whether the value exists in the temporary table and whether it is still valid. If the code matches and has not expired, the user is authenticated through the standard APEX login method. The verified OTP is then written to history and removed from the temporary table so it cannot be reused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*1ninxOT1h9WreUiAeZApPg.png" /></figure><p>The fourth step is trusted reuse. To improve usability, the package checks whether the user has a recently verified OTP record. If such a record exists within the allowed time window, the system can skip the OTP request and allow direct login. This creates a balanced design between security and user convenience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*0NS0COeFRm9LpgDc8PjEDQ.png" /></figure><p>This approach is practical, clean, and easy to explain. It uses a clear separation between OTP generation, OTP delivery, OTP validation, and OTP history tracking. That makes it suitable for Oracle APEX applications that need a simple but effective MFA flow</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51d49bb809a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Dynamic Lookup Lists in Flutter Using Oracle APEX ORDS APIs]]></title>
            <link>https://medium.com/@malek.m.edresi/building-dynamic-lookup-lists-in-flutter-using-oracle-apex-ords-apis-fd1394c053a6?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd1394c053a6</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 17:26:25 GMT</pubDate>
            <atom:updated>2026-04-24T17:26:25.455Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1w-6WL8APK97YXE49hatqQ.png" /></figure><p>Modern applications require dynamic data integration instead of hardcoded values. One common example is dropdown lists that fetch data from a backend system in real time.</p><p>This project demonstrates how to integrate a Flutter application with Oracle APEX ORDS APIs to dynamically populate a lookup list, using a blood type dropdown as a practical example.</p><h3>Overview</h3><p>The idea is simple: instead of storing static values inside the mobile app, the data is fetched directly from Oracle Database through ORDS (Oracle REST Data Services).</p><p>This allows:</p><ul><li>Centralized data management</li><li>Real-time updates</li><li>Clean separation between frontend and backend</li></ul><h3>Database and ORDS Setup</h3><p>The process starts at the database level. A lookup table (e.g., blood types) is exposed through ORDS as a REST endpoint.</p><p>Example query:</p><pre>SELECT BLOODID, BLOODNAME<br>FROM l_bloodtypes;</pre><p>This query is published as a REST-enabled service (GET method), making it accessible externally.</p><h3>REST API Endpoint</h3><p>Once the service is published, ORDS generates an endpoint like:</p><pre>https://&lt;server&gt;/ords/&lt;schema&gt;/l_bloodtypes/</pre><p>This endpoint becomes the data source for the Flutter application.</p><h3>Flutter Architecture</h3><p>The application follows Clean Architecture, which separates responsibilities into clear layers:</p><ul><li><strong>Entities</strong> → Defines the data structure</li><li><strong>Models</strong> → Maps JSON to objects</li><li><strong>Repositories</strong> → Abstracts data access</li><li><strong>Services</strong> → Handles API calls</li><li><strong>Use Cases</strong> → Business logic execution</li><li><strong>Provider</strong> → State management</li></ul><p>This structure improves scalability and maintainability.</p><h3>Data Flow</h3><p>The data flow inside the app is structured and predictable:</p><ol><li>The app starts and loads data</li><li>Provider triggers the use case</li><li>Repository calls the service</li><li>Service sends HTTP request to ORDS</li><li>JSON response is parsed</li><li>UI updates dynamically</li></ol><p>This flow ensures a clean separation between UI and data logic.</p><h3>Dynamic Dropdown Implementation</h3><p>The dropdown is populated dynamically using state management:</p><pre>DropdownButtonFormField(<br> items: bloodProvider.bloodTypes.map((bloodType) {<br>   return DropdownMenuItem(<br>     value: bloodType.bloodId,<br>     child: Text(bloodType.bloodName),<br>   );<br> }).toList(),<br>)</pre><p>This approach removes hardcoded values and ensures the dropdown always reflects the latest data from the database.</p><h3>Error Handling</h3><p>The system handles common runtime issues:</p><ul><li>Network failures</li><li>Unauthorized access</li><li>Missing data</li><li>Timeout errors</li></ul><p>These are converted into user-friendly messages inside the UI instead of raw system errors.</p><h3>Why This Matters</h3><p>This pattern solves a fundamental problem in application design:</p><ul><li>No duplicated data between frontend and backend</li><li>Centralized control from database</li><li>Easier updates without redeploying the app</li><li>Scalable architecture for enterprise systems</li></ul><h3>Conclusion</h3><p>This project demonstrates how Oracle APEX ORDS can act as a powerful backend for modern Flutter applications.</p><p>By exposing database tables as REST APIs and consuming them dynamically, you get:</p><ul><li>Real-time data</li><li>Clean architecture</li><li>Flexible integration</li><li>Maintainable systems</li></ul><p>This is not just a dropdown example — it is a reusable pattern for building dynamic, data-driven applications</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd1394c053a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle APEX WhatsApp Integration: Building an Enterprise Messaging System with UltraMsg API]]></title>
            <link>https://medium.com/@malek.m.edresi/oracle-apex-whatsapp-integration-building-an-enterprise-messaging-system-with-ultramsg-api-3f4a4461fba6?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f4a4461fba6</guid>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[otp-verification]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[plsql]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 15:02:08 GMT</pubDate>
            <atom:updated>2026-04-23T15:02:08.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5pNIzq3sOVZeTjkRiC-uQ.jpeg" /></figure><h4>Modern enterprise systems require real-time communication with users. Whether it’s notifications, alerts, or transactional messages, WhatsApp has become one of the most effective channels.</h4><p>This project demonstrates how to integrate Oracle APEX with the UltraMsg WhatsApp API to build a production-ready messaging system using pure PL/SQL, without external middleware.</p><h3>Architecture Overview</h3><p>The system is designed as a queue-based messaging platform:</p><p><strong>Oracle APEX → PL/SQL Queue → Processing Engine → UltraMsg API → WhatsApp User</strong></p><p>Instead of sending messages directly from the UI, requests are placed into a queue and processed asynchronously. This ensures reliability and scalability.</p><h3>Core Design Concept</h3><p>At the heart of the system is a decoupled architecture using a message queue:</p><ul><li>WA_MESSAGE_QUEUE stores outgoing messages</li><li>Processing engine handles delivery</li><li>Scheduler runs jobs automatically</li><li>Logs capture every operation</li></ul><p>This design separates user interaction from API execution, improving performance and stability.</p><h3>Key Features</h3><p>The system includes enterprise-level capabilities:</p><ul><li>Asynchronous message queue</li><li>Priority-based message routing (OTP vs normal messages)</li><li>Retry mechanism (up to 3 attempts)</li><li>Full API logging (request, response, status, latency)</li><li>Centralized error logging</li><li>Secure credential storage (no hardcoded tokens)</li></ul><p>These features transform a simple API integration into a robust messaging platform.</p><h3>Implementation Flow</h3><p>The message lifecycle follows a structured flow:</p><ol><li>APEX inserts message into queue</li><li>Scheduler triggers processing job</li><li>Engine reads pending messages</li><li>API request sent via APEX_WEB_SERVICE</li><li>Response is logged</li><li>Status updated (success / retry / failed)</li></ol><p>This ensures that no message is lost and failures are handled properly.</p><h3>Database Components</h3><p>The system is built using modular database objects:</p><ul><li>Configuration table for API credentials</li><li>Queue table for messages</li><li>Logging tables for API calls and errors</li><li>PL/SQL packages for sending and processing</li><li>Scheduler job for automation</li></ul><p>This modular design makes the system easy to maintain and extend.</p><h3>Security Design</h3><p>Security is handled at multiple levels:</p><ul><li>API tokens stored in database (not in code)</li><li>Network ACL restricts outbound API access</li><li>Controlled execution privileges</li><li>Optional encryption for sensitive data</li></ul><p>This ensures the system is safe for production environments.</p><h3>Setup and Execution</h3><p>The setup process is straightforward:</p><ol><li>Enable network access to UltraMsg API (api.ultramsg.com)</li><li>Run SQL scripts in order:</li></ol><pre>@config/api_config.sql<br>@logging/logs.sql<br>@src/send_whatsapp.sql<br>@src/process_queue.sql<br>@scheduler/job.sql</pre><p>3. Configure API credentials:</p><pre>UPDATE WA_API_CONFIG<br>SET INSTANCE_ID = &#39;your_instance&#39;,<br>    API_TOKEN   = &#39;your_token&#39;;</pre><p>4. Insert message into queue:</p><pre>WA_MSG_PKG.ENQUEUE(...)</pre><p>5. Run or monitor scheduler job</p><h3>Monitoring and Observability</h3><p>The system provides built-in monitoring:</p><ul><li>Queue status dashboard</li><li>API call logs</li><li>Error logs</li><li>Scheduler controls</li></ul><p>This allows tracking system health and debugging issues.</p><h3>Use Cases</h3><p>This integration supports real-world scenarios:</p><ul><li>OTP and authentication messages</li><li>Appointment reminders</li><li>Billing notifications</li><li>System alerts</li><li>Customer communication</li></ul><p>It fits perfectly in healthcare, banking, and enterprise systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vS99WU11-5KBFo-QP1HsOQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UW6X0TEXUVyN4HrGViilVg.jpeg" /></figure><h3>Why This Matters</h3><p>Traditional APEX applications are limited to internal workflows.</p><p>This project extends APEX into:</p><ul><li>External communication systems</li><li>Real-time messaging platforms</li><li>Event-driven architectures</li></ul><p>It transforms Oracle APEX from a UI tool into a full communication backend.</p><h3>Conclusion</h3><p>This project demonstrates how to build a complete WhatsApp messaging system using Oracle APEX and PL/SQL.</p><p>Without external services or middleware, it delivers:</p><ul><li>Scalable architecture</li><li>Reliable message delivery</li><li>Secure configuration</li><li>Full observability</li></ul><p>This is a practical example of enterprise integration using Oracle technologies.</p><blockquote>Repository</blockquote><blockquote>GitHub Repository:<br> <a href="https://github.com/malek-al-edresi/oracle-apex-ultar-message-whatsapp-integration?utm_source=chatgpt.com">https://github.com/malek-al-edresi/oracle-apex-ultar-message-whatsapp-integration</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f4a4461fba6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle APEX Twilio SMS Integration: Building Real-Time Messaging with PL/SQL]]></title>
            <link>https://medium.com/@malek.m.edresi/oracle-apex-twilio-sms-integration-building-real-time-messaging-with-pl-sql-fa254281b556?source=rss-e8b29f4ee50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa254281b556</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[oracle-apex]]></category>
            <category><![CDATA[plsql]]></category>
            <dc:creator><![CDATA[Malek M.Edresi]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 15:01:19 GMT</pubDate>
            <atom:updated>2026-04-23T15:01:19.120Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FHILPbz8MJmzOwJJCOX9fA.jpeg" /></figure><p>Modern applications require instant communication with users. Whether it’s sending OTP codes, alerts, or transactional messages, SMS remains one of the most reliable channels.</p><p>This project demonstrates how to integrate Oracle APEX with Twilio SMS API using PL/SQL, enabling real-time messaging directly from the database without external middleware.</p><h3>Architecture Overview</h3><p>The system follows a simple and effective integration model:</p><p><strong>Oracle APEX → PL/SQL → Twilio REST API → SMS Delivery</strong></p><p>Instead of relying on third-party services or external backends, the integration is handled entirely inside Oracle using REST calls.</p><p>[Insert Screenshot — API Flow or APEX Process]</p><h3>Core Concept</h3><p>Twilio provides a cloud-based communication platform that allows applications to send SMS through APIs.</p><p>In this project:</p><ul><li>APEX triggers a PL/SQL procedure</li><li>The procedure calls Twilio REST API</li><li>SMS is sent to the target phone number</li></ul><p>This approach keeps everything centralized within the Oracle environment.</p><h3>Implementation Approach</h3><p>The integration is based on REST API calls using APEX_WEB_SERVICE.</p><p>The typical flow:</p><ol><li>Prepare SMS parameters (To, From, Body)</li><li>Authenticate using:</li></ol><ul><li>Account SID</li><li>Auth Token</li></ul><p>3. Send HTTP POST request to Twilio endpoint</p><p>Example endpoint:</p><pre>https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json</pre><p>This is the core entry point for sending SMS via Twilio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKJ2NK8BgkOJ3U2hNa35tA.png" /></figure><h3>Key Features</h3><p>The project provides a clean and practical implementation:</p><ul><li>Direct SMS sending from PL/SQL</li><li>REST-based integration (no middleware)</li><li>Secure authentication using Twilio credentials</li><li>Easy integration into APEX processes</li><li>Reusable procedure for multiple use cases</li></ul><p>This makes it suitable for both simple and enterprise-level applications.</p><h3>Security Considerations</h3><p>Security is handled through:</p><ul><li>Secure storage of Account SID and Auth Token</li><li>Avoiding hardcoded credentials</li><li>Controlled API access via HTTPS</li><li>Optional use of API Keys for production environments</li></ul><p>These practices ensure the integration is safe for real deployments.</p><h3>Setup and Execution</h3><p>The setup process is straightforward:</p><ol><li>Create Twilio account</li><li>Get:</li></ol><ul><li>Account SID</li><li>Auth Token</li><li>Twilio phone number</li></ul><p>3. Configure credentials inside Oracle</p><p>4. Use PL/SQL procedure to send SMS</p><p>Example execution:</p><pre>BEGIN<br>  SEND_SMS_PROC(<br>    p_to   =&gt; &#39;+123456789&#39;,<br>    p_body =&gt; &#39;Hello from Oracle APEX&#39;<br>  );<br>END;</pre><h3>Use Cases</h3><p>This integration supports many real-world scenarios:</p><ul><li>OTP / 2FA authentication</li><li>Appointment reminders</li><li>Transaction notifications</li><li>System alerts</li><li>Customer communication</li></ul><p>Twilio is widely used for real-time messaging in enterprise systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*RCnW7HVx-QVAHMooRxiusg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*nxwNoZAhlLdR_Ziu2fMS0w.jpeg" /></figure><h3>Why This Matters</h3><p>Oracle APEX applications are traditionally focused on internal workflows.</p><p>By integrating Twilio, you extend APEX into:</p><ul><li>Real-time communication systems</li><li>Event-driven applications</li><li>Customer-facing notification platforms</li></ul><p>This significantly increases the value of APEX applications.</p><h3>Conclusion</h3><p>This project shows how to integrate Oracle APEX with Twilio SMS using a clean and direct PL/SQL approach.</p><p>The result is:</p><ul><li>Simple architecture</li><li>Fast integration</li><li>Reliable SMS delivery</li><li>Scalable communication layer</li></ul><p>It is a practical example of connecting Oracle systems with modern communication APIs.</p><blockquote>Repository</blockquote><blockquote>GitHub Repository:<br> <a href="https://github.com/malek-al-edresi/oracle-apex-twilio-sms-integration">https://github.com/malek-al-edresi/oracle-apex-twilio-sms-integration</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa254281b556" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>