Oracle WebLogic Server and Oracle AI Database 26ai

Oracle WebLogic Server provides an enterprise Java application runtime and is a foundation for many Oracle Fusion Middleware products. It manages application execution, transactions, messaging, security, and database connection pools. Oracle AI Database 26ai provides the database services used by those applications. The application server and database are separate products with their own releases, configuration requirements, and maintenance schedules.

WebLogic applications can connect to Oracle databases through JDBC on premises or on Oracle Cloud Infrastructure (OCI). Oracle REST Data Services (ORDS) provides another integration option for applications that need HTTP APIs. Choosing between these approaches depends on the application, its interfaces, and its operational requirements.

1. Modernizing Legacy Middleware

Applications originally developed for Oracle Internet Application Server require an assessment before migration. Identify their Java version, frameworks, deployment descriptors, authentication mechanisms, and database dependencies. Then select a supported upgrade or redevelopment path for the specific application and middleware product.

Moving a server to OCI does not update its application code or make an unsupported software combination supported. Likewise, adopting a Fusion Cloud SaaS application is a business application replacement project, rather than a routine WebLogic upgrade.

WebLogic release selection also affects application compatibility:

Check Oracle's certification information for the complete configuration, including Oracle AI Database 26ai connectivity. A newer JDBC driver alone does not establish certification for every middleware product or application.

2. Running Applications on WebLogic Server

A WebLogic domain groups the configuration and runtime resources for an application environment. Its Administration Server manages the domain, while Managed Servers typically run deployed applications. Clusters support scalability and availability when application state, networking, and recovery are designed appropriately.

• JDBC data sources: Applications obtain database connections from a configured connection pool, commonly through a JNDI name. Pool sizes and timeouts must match application demand and database capacity.
• Transaction management: WebLogic coordinates application transactions, including distributed transactions when appropriately configured.
• Messaging: JMS resources support asynchronous communication and decouple application components.
• Security: Authentication providers, application roles, and transport security control access to applications and server resources.

For WebLogic 14.1.2 and later, use WebLogic Remote Console for supported graphical administration tasks. The earlier WebLogic Administration Console was removed in 14.1.2. WLST scripting and management APIs also support administration and automation. Fusion Middleware Control is available in applicable Fusion Middleware installations.

Oracle Forms, Oracle SOA Suite, and other middleware products have their own installation and certification requirements. Do not assume that every product runs on every WebLogic release. Modernizing the database tier also does not automatically expose every Oracle AI Database 26ai feature through an existing Forms application.

3. Deploying WebLogic Applications on OCI

OCI offers several ways to host an application tier. WebLogic can run on OCI Compute, and Oracle WebLogic Server for OCI provides tooling for provisioning and managing supported deployments. Container deployments can use Oracle Kubernetes Engine (OKE) with the WebLogic Kubernetes Operator where the selected workload and configuration are supported.

The database tier is a separate choice:

• Oracle Base Database Service: Provides database systems with customer administration responsibilities and supported single-instance or RAC configurations.
• Oracle Autonomous AI Database: Automates many database maintenance tasks. Applications still require suitable credentials, connectivity, schema privileges, and connection pool settings.
• Oracle Exadata Database Service: Provides a distinct Exadata-based deployment option. Exadata is not a feature included in every Base Database Service deployment.

Configure network routing, security rules, and encrypted connections for the chosen services. Restrict administration endpoints and database access to authorized systems. Cloud infrastructure IAM policies, WebLogic application authorization, and database privileges protect different resources and must be configured accordingly.

Provisioning automation does not remove operational responsibilities. Establish ownership for application updates, WebLogic and JDK patches, secrets, monitoring, backups, and recovery testing. Kubernetes scaling also needs coordinated database connection limits; adding application instances can otherwise create more connections than the database can accommodate.

4. Providing REST APIs with ORDS

ORDS is a Java middleware service that exposes selected Oracle database resources through HTTP and HTTPS. It supports REST interfaces for database operations and can provide JSON document access to JSON Relational Duality Views. Applications can consume these interfaces without using JDBC directly.

ORDS can run in its standalone configuration or in a supported application server, including supported WebLogic configurations. Autonomous database services also provide managed ORDS capabilities. Consult the ORDS installation requirements before selecting a container and Java version.

WebLogic and ORDS can coexist. For example, a WebLogic application might use JDBC for transactional business operations, while mobile clients use secured ORDS endpoints for selected services. Exposing those endpoints requires deliberate API design, authentication, authorization, and appropriate database privileges.

ORDS does not automatically convert Oracle Forms screens or replace an application's business logic. Introducing REST APIs is an application integration decision. JSON Relational Duality Views can simplify document access to relational data, but their definitions, permitted updates, and application concurrency handling still require design.

Choosing an Integration Approach

Use WebLogic when an application requires its enterprise Java runtime and services, or when a supported Oracle middleware product requires it. Use ORDS when clients need database-backed REST APIs. Deploy either or both on infrastructure that meets the application's availability, security, and maintenance needs. Oracle AI Database 26ai can serve the database tier without requiring every application to use the same middleware architecture.

Oracle Documentation

• WebLogic Server 15.1.1: platform changes and upgrade considerations
• WebLogic Remote Console support information
• Components of Oracle WebLogic Server for OCI
• Introduction to Oracle REST Data Services

Java Web - Exercise