Oracle 23ai Internet and Cloud Integration (Module 6 Conclusion)

This module examined how Oracle's approach to internet connectivity, multimedia management, Java integration, and identity services has evolved from the Oracle 8i and 9i era through Oracle Database 23ai running on Oracle Cloud Infrastructure. The lessons covered the retirement of legacy components — including Oracle interMedia, Oracle Internet Directory, and Oracle Internet Application Server — and the modern tools and architectural patterns that replace them.

Internet and Cloud Connectivity

Lesson 1 established the foundational shift in Oracle's connectivity model. Where Oracle 9i relied on SOAP-based web services and the Oracle Internet File System, Oracle 23ai builds on REST, JSON, and cloud-native infrastructure. Oracle REST Data Services exposes SQL queries and PL/SQL procedures as secure HTTP endpoints, JSON Relational Duality Views bridge relational and document models, and Autonomous Database manages connection pooling and network optimization automatically. Two-tier and three-tier architectural patterns remain relevant, but the application tier now communicates with Oracle through HTTPS and REST rather than proprietary Oracle Net protocols wherever possible.

Within OCI, databases deploy into Virtual Cloud Networks with private endpoints, FastConnect or VPN for hybrid connectivity, and Oracle Connection Manager for multi-tenant environments. TLS 1.3 and certificate-based authentication secure all client-to-server communication across public and private networks.

Multimedia Management

Lesson 2 covered Oracle 23ai's treatment of multimedia as semantic data rather than specialized file storage. The VECTOR data type and AI Vector Search enable similarity-based retrieval of images, audio, and video based on content meaning rather than filename or metadata. Traditional LOB storage — BLOB, CLOB, and BFILE — continues to serve as the binary storage layer, with SecureFiles providing automatic space reclamation, inline storage for small objects, and Transparent Data Encryption for data at rest.

Lesson 4 documented the complete lifecycle of Oracle interMedia: introduced in Oracle 8i as a unified content management framework, renamed Oracle Multimedia in Oracle 11g, deprecated in Oracle 18c, and desupported in Oracle 19c. There is no single drop-in replacement. Full-text indexing moved to Oracle Text, binary storage moved to SecureFiles BLOBs or OCI Object Storage, and in-database media processing moved to application-tier services. Organizations maintaining legacy schemas that reference ORDImage, ORDVideo, or ORDAudio types should follow a structured migration — inventorying usage, separating storage from processing, and replacing in-database transforms with external service calls.

Java Integration

Lesson 3 confirmed that JDBC-based Java applications are the standard for Oracle database connectivity on OCI. The recommended configuration uses the JDBC thin driver with TLS and wallet credentials, Universal Connection Pool or HikariCP for application-tier pooling, and Database Resident Connection Pooling for high-concurrency serverless and microservices workloads. PL/SQL remains the preferred language for set-based data logic, constraints, auditing, and transactional business rules. Java in the application tier handles web and API layers, orchestration, and CPU-bound processing. Stored Java inside the database is a niche tool appropriate only when a Java library must execute adjacent to data and cannot be moved to an external service.

Oracle 23ai's JDBC 23ai drivers expose JSON Relational Duality, AI Vector Search, and native Boolean datatype support directly to Java applications. Microservices built on Micronaut, Quarkus, or Spring Boot deploy to Oracle Kubernetes Engine and connect to Autonomous Database using UCP and DRCP, providing the combination of application-tier elasticity and database-tier connection efficiency required for high-traffic internet workloads.

Identity and Directory Services

Lessons 5 and 6 addressed Oracle's identity management evolution. Oracle Unified Directory is Oracle's current LDAP v3-compliant directory service, serving on-premises Oracle Identity Management deployments as a system directory, proxy directory, and identity store backend for Oracle Access Manager and Oracle Identity Governance. OUD supports multi-master replication and virtual directory capabilities that allow it to aggregate identity data from Active Directory and other enterprise LDAP sources without requiring full migration.

For new Oracle 23ai deployments on OCI, Oracle Identity Cloud Service and OCI IAM replace LDAP-based directory services with OAuth 2.0, OpenID Connect, and SAML. Token-based authentication eliminates the directory lookup pattern in favor of JWT consumption at the API layer. ORDS integrates with OCI IAM for role-based access control, and Autonomous Database enforces authorization policies at the cloud infrastructure level. Organizations evaluating new deployments on OCI should determine whether LDAP-based directory services are required at all before provisioning OUD, since IDCS and OCI IAM handle the majority of identity use cases natively.

Middleware Modernization

Lesson 7 completed the module by addressing the application server tier. Legacy Oracle Internet Application Server versions — iAS 1.0.2, 9g, and 10g — are unsupported and no longer viable for production use. Oracle WebLogic Server 14.1.2 and 15.1.1 are the current Oracle Fusion Middleware releases, both certified with Oracle Database 23ai and supporting Jakarta EE 8 with Java SE 17 and 21. WebLogic provides the runtime for Oracle Forms 14.1.2, Oracle SOA Suite, Oracle Service Bus, and Oracle WebCenter, with centralized management through the WebLogic Admin Console and Fusion Middleware Control.

On OCI, WebLogic integrates with Oracle Base Database Service for RAC and Exadata deployments and with Autonomous Database for self-healing, self-patching environments. Oracle WebLogic Server for OCI automates provisioning, scaling, and patching. Containerized WebLogic on Oracle Kubernetes Engine extends these capabilities to cloud-native workloads. For organizations that do not require complex Java EE application server capabilities, Oracle APEX provides a practical alternative — building internet-facing applications directly on the database without a separate middleware tier.

Module Summary