Did you know that you can integrate the Oracle Container Registry and Container Cloud to rapidly deliver a WebLogic environment?
In this post, I will show you how it is done in 3 easy steps.
1. Integrate the Registry with Oracle Container Cloud
2. Spin up a WebLogic Stack on the Cloud
3. Access your Cloud-based instance
Once you have accepted the terms, you will have 8 hours to download the images you need from within your Oracle Container Cloud Service instance.
Step 1: Integrate the Registry and Container Cloud
From the Oracle Container Cloud Service:
1. Go to Registries then New Registry.
2. Enter your account details for Oracle Container Registry.
3. To test your credentials, you can click Validate.
4. When you are ready, click Save.
Once we have added the Registry to the Oracle Container Cloud, we can now easily spin up Oracle WebLogic instances.
Step 2: Spin up a WebLogic Stack on Cloud
Before we can spin up our stack, we need to tell Oracle Container Cloud which Docker image we want to create our containers from so that it starts the correct version of WebLogic.
To find the appropriate image, from the Oracle Container Registry:
1. Click on Middleware under Business Area.
2. Then, click on weblogic under Explore Official Repositories.
3. The default image name is shown in the top right hand corner. For WebLogic it is
If you want to download the latest version of WebLogic, you can simply use the default image name. However, if you want to download a specific image version you will need to specify a tag in the image name you provide to the Oracle Container Cloud. Tags are appended to the image name with colon (
:). For example, if we wanted Oracle WebLogic 22.214.171.124 we would specify the image as
The full list of available tags are shown under the Tags tab.
If you omit the tag in the image name it defaults to
latest which is why
container-registry.oracle.com/middleware/weblogic will give you the latest version. You should not use
latest for production as it may lead to unpredictable behaviour such as unintended upgrades.
Let's get our instance up and running.
- Go to Stack then Quick Start Wizard.
- Choose your Resource Pool. If you are evaluating the Container Cloud, I would recommend sticking to the default Resource Pool. Click Next.
- Copy and paste your
docker runsnippet and click Add. In our example, we will use
docker run -d -p 7001:7001 container-registry.oracle.com/middleware/weblogic:126.96.36.199which says to map 7001 in the container to 7001 in the host and to use WebLogic 188.8.131.52. If you do not add a port mapping you will not be able to access your instance from a public IP address.
- Click Next.
- Enter a name for your stack and click Launch.
Your Docker image will be downloaded and booted in a few minutes.
Step 3: Access your WebLogic Stack
To access your stack, click on the Hostname for your container.
Next, copy the public IP address to your clipboard.
With this public IP address you can access your WebLogic Admin Console from a web browser at
To login as the default
weblogic admin user, you will first need to obtain the randomly generated password.
Click on Container then select the Name of the container.
Then click to View Logs
At the top of the logs, on the second line, it will show what the randomly generated password is.
Bonus Points: Port your container anywhere!
As Docker containers are infinitely portable, you can port your instance anywhere that Docker is installed; including your local machine. To do this, copy your Stack YAML and paste in into a file called
Now, on any machine where
docker-compose is installed you can simply do this:
docker login. Enter your Registry account details.
docker-compose up -d
3. Access the WebLogic Admin Console from a web browser at
Good luck and Happy Shipping!