Providing this WebLogic Server images facilitates the configuration, and environment setup. This project includes the installation and the creation of an empty WebLogic Server domain (only an Admin Server). These WebLogic Server 12.2.1.4, 14.1.1, and 14.1.2 images are based on Oracle Linux and Oracle JDK (Server JRE).

NOTE: The WebLogic installation in these images do not contain any WebLogic Server Patches, these are GA images of WebLogic Server. If you need patched images of WebLogic Server with the latest CPU patches please go to the middleware/weblogic_cpu repository.

WebLogic Server 12.2.1.4, 14.1.1.0, and 14.1.2.0 images on Oracle Linux 8 and 9, JDK 8, 11, 17, and 21 are available for amd64 and arch64 systems. Calling docker pull without specifying an architecture will download images for the architecture that matches your docker client. You can also specify the desired architecture with the --platform option.

The container images for Oracle WebLogic Server, facilitate the creation of a WebLogic Server multi-server domain or a single server domain running in Containers or Kubernetes. This makes it simple to deploy applications and any resources the application might need.

Note: New released WebLogic Server 14.1.2 GA images

For more information on WebLogic Server certification please check the Oracle WebLogic Server on Docker Certification Whitepaper and WebLogic Server Blog for updates.

Get Started

Available Tags

Oracle WebLogic Server 14.1.2.0 Container Images

These images are created using the WebLogic Image Tool and have a pre-installed Oracle Home with the Oracle WebLogic Server and Coherence 14.1.2.0 Generic distributions, JDK 17 or JDK 21, and are based on Oracle Linux 8 or 9 slim. Samples are not installed with the WebLogic Server Generic installation, nor is Automatic Diagnostic Repository (ADR) included. Patches for any of these components will not be applied.

Oracle WebLogic Server 14.1.1.0 Container Images

These images are created using the WebLogic Image Tool and have a pre-installed Oracle Home with the Oracle WebLogic Server and Coherence 14.1.1.0 Generic, Slim, or Developer distributions, JDK 8 or JDK 11, and are based on Oracle Linux 8 or 9 slim. Samples are not installed with the WebLogic Server Generic and Slim installations, nor is Automatic Diagnostic Repository (ADR) included. Use of ADR is no longer required with WebLogic Server. Patches for any of these components will not be applied.

Oracle WebLogic Server 12.2.1.4 Container Images

These images are created using the WebLogic Image Tool and have a pre-installed Oracle Home with the Oracle WebLogic Server and Coherence 12.2.1.4 Generic or Slim distributions, JDK 8 (8u231), and are based on Oracle Linux 7 or 8 slim. Samples are not installed with the WebLogic Server Generic and Slim installations, nor is Automatic Diagnostic Repository (ADR) included. Use of ADR is no longer required with WebLogic Server. Patches for any of these components will not be applied.

Note: Tags that are republished on a schedule should not be used for development and production because it is difficult to ensure that all compute nodes have the same binaries. Use tags like 12.2.1.4, 14.1.1.0-8, and 14.1.1.0-11 for samples, proof-of-concepts, and workshops, but change to using one of the date-stamped tags after you are in development. These date-stamped tags will never be republished.

Note: The WebLogic images above are not patched with the latest security patches. After pulling these images you can secure them by using the WebLogic Image Tool to patch the WebLogic binaries inside the image.

The following documentation uses 12.2.1.4 (Generic distribution); you may choose to modify the commands to use the other 12.2.1.4, 14.1.1.0-8, or 14.1.1.0-11 tags instead.

Login into Oracle Container Registry (OCR) using the OCR credentials.

$ docker login container-registry.oracle.com

To pull a WebLogic Server image, run the docker command with the specific tag:

$ docker pull container-registry.oracle.com/middleware/weblogic:<tag>

Different WebLogic Images

1. The WebLogic generic image is supported for development and production deployment of WebLogic configurations using Docker. It contains the same binaries as those installed by the WebLogic generic installer.

2. The WebLogic slim image is supported for development and production deployment of WebLogic configurations using Docker. In order to reduce image size, it contains a subset of the binaries included in the WebLogic generic image. The WebLogic Console, WebLogic examples, WebLogic clients, Maven plug-ins, and Java DB have been removed - all binaries that remain included are the same as those in the WebLogic generic image. If there are requirements to monitor the WebLogic configuration, they should be addressed using Prometheus and Grafana, or other alternatives.

3. The WebLogic developer image is supported for development of WebLogic applications in Docker containers. In order to reduce image size, it contains a subset of the binaries included in the WebLogic generic image. WebLogic examples and Console help files have been removed - all binaries that remain included are the same as those in the WebLogic generic image. The WebLogic developer image is primarily intended to provide a Docker image that is consistent with the WebLogic “quick installers” intended for development only. Production WebLogic domains should use the WebLogic generic or WebLogic slim images.

Providing Administration Server User Name and Password

The user name and password must be supplied in a domain.properties file located in a local directory that you will map at Docker run time with the -v option. The properties file enables the scripts to configure the correct authentication for the WebLogic Administration Server. Please refer to documentation for the criteria of valid administration passwords.

The format of the domain.properties file is key value pair:

    username=myadminusername
    password=myadminpassword

Note: Oracle recommends that the domain.properties file be deleted or secured after the container and WebLogic Server are started so the user name and password are not inadvertently exposed.

To create an empty domain with a running Administration Server:

$ docker run -d -p 7001:7001 -p 9002:9002 \
      -v $PWD:/u01/oracle/properties container-registry.oracle.com/middleware/weblogic:12.2.1.4

Ensure that you create a domain.properties file in the current directory before running this command. The WebLogic Server image will invoke createAndStartEmptyDomain.sh as the default command, and the Administration Server will be running on port 9002. When running multiple containers, map port 7001 and 9002 to different ports on the host.

To run a second container on port 7002:

$ docker run -d -p 7002:7001 -p 9004:9002 \
      -v $PWD:/u01/oracle/properties container-registry.oracle.com/middleware/weblogic:12.2.1.4

Ensure that you create a domain.properties file in the current directory before running this command. Now you can access the WebLogic Server Administration Console at https://localhost:9002/console. Your browser will request that you accept the Security Exception. To avoid the Security Exception, you must update the WebLogic Server SSL configuration with a custom identity certificate.

Customize your WebLogic Server Domain

You might want to customize your WebLogic Server domain by extending this image. The best way to create your domain is by writing your own Dockerfiles and using WebLogic Scripting Tool (WLST) to create clusters, data sources, JMS servers, security realms, and deploy applications.

In your Dockerfile, you will extend the WebLogic Server image with the FROM container-registry.oracle.com/middleware/weblogic:12.2.1.4 directive.

We provide a variety of examples (Dockerfiles, shell scripts, and WLST scripts) to create domains, configure resources, deploy applications, and use load balancers in GitHub.

Customer Support

We support WebLogic Server in certified Docker containers; please read our Support Statement. For additional details on the most current WebLogic Server supported configurations, please refer to the Oracle Fusion Middleware Certification Pages.

Copyright

Copyright (c) 2024, Oracle and/or its affiliates.