Archive for the ‘WebLogic’ Category


In an earlier article, I discussed the creation of a generic Docker Container Image that runs any Node.JS application based on sources for that application on GitHub. When the container is started, the GitHub URL is passed in as a parameter and the container will download the sources and run the application. Using this generic image, you can your Node application everywhere you can run a Docker container. One of the places where you can run a Docker Container is the Oracle Container Cloud Service (OCCS) – a service that offers a platform for managing your container landscape. In this article, I will show how I used OCCS to run my generic Docker image for running Node application and how I configured the service to run a specific Node application from GitHub.

Getting started with OCCS is described very well in an article by my colleague Luc Gorissen on this same blog: Docker, WebLogic Image on Oracle Container Cloud Service. I used his article to get started myself.

The steps are:

  • create OCCS Service instance
  • configure OCCS instance (with Docker container image registry)
  • Create a Service for the desired container image (the generic Node application runner) – this includes configuring the Docker container parameters such as port mapping and environment variables
  • Deploy the Service (run a container instance)
  • Check the deployment (status, logs, assigned public IP)
  • Test the deployment – check if the Node application is indeed available
Create OCCS Service instance

Assuming you have an Oracle Public Cloud account with a subscription to OCCS. Go to the Dashboard for OCCS. Click on Create Service. Read the complete article here.




Two of my favorite Oracle Cloud services are the Exadata Express Cloud Service (Exadata Express) and the Application Container Cloud Service (ACCS). Exadata Express is a fully managed Oracle Database service at an entry-level price point for small to medium sized data and ACCS is an easy way to deploy apps in Docker containers. In this post, I’ll demonstrate how to connect these two services at the most basic level.
What do I mean by “the most basic level”? First, I’m not going to demonstrate how to create an Oracle Cloud account with these two services – I’ll assume you’ve already done that. Also, the demo app in this post will be minimalistic. Normally, I might use the Developer Cloud Service to create a Git repo with an automated build process – not here. This post will focus only on what’s needed to get these two services connected.


Create test app

Create a new directory named connection-test-app and add the following two files. Read the complete article here.


There’s a few examples on the net about how to deploy a JET app to Application Container Cloud. All of these seem to either create an express app and then add oracle code to it later (eliminating the benefit of using grunt serve) or taking the compiled web folder and putting it into a new express application (making your devops or build automation slightly more painful). Let me show you an alternative.

This uses the basic http module in Node to create a very simple http server to serve our JET code from the web directory. If you run this using node server.js you should see your node app running, just like if you used grunt serve. Read the complete article here.


The Oracle Application Container Cloud (ACCS)‘s Application Cache provides (as the name implies) caching for applications! As Mike Lehmann explained in Caching with Oracle Application Container Cloud, you simply specify the amount of memory you want to cache and whether you just need basic non-HA cache for dev/test or reliable caching for production and the appropriate infrastructure is automatically provisioned.

Under the Hood

The ACCS Application Cache is built on the highly performant and scalable Oracle Coherence in-memory data grid that’s been powering trading and other memory and time sensitive applications for years. In the ACCS Application Cache, the underlying Coherence implementation is not exposed but if you need an in-memory data grid cloud service don’t worry, Oracle is working on exactly that. In the meantime, the Coherence team continues to innovate. Read the complete article here.


In previous posts we discussed how Microservice applications can be implemented, combined and monitored in Oracle Application Container Cloud service. So far, we focused on a manual deployment process. However, when aiming to implement a working Microservice strategy DevOps is a key success factor. One area DevOps concentrates on is software delivery automation (CI/CD).

With Developer Cloud Service Oracle provides a full team development and delivery cloud platform. It can be used as a service and is perfectly integrated with other Oracle cloud services, including Application Container Cloud Service. Therefore, it is a valid candidate when evaluating new tool chains for cloud native application development. Nevertheless, many organizations already have existing CI/CD solutions in place and do not want to waste the investment. In these scenarios, an understandable requirement for a solution integrated in the existing tool chain exists. This post will show how one can deploy to Oracle Application Container Cloud using Maven as build tool. As Maven is a tool commonly supported by CI/CD solutions, this approach can be integrated easily in existing development process automations.

Basic Deployment Process

First, let us look at the general deployment process for Oracle’s Application Container Cloud Service. It consists of three basic steps. Within the first step the deployable Application Container Cloud Archive containing all required files must be created. Afterwards this archive is uploaded to Oracle Storage Cloud Service. Finally, one must invoke a deployment procedure on Application Container Cloud service providing application metadata and archive location within Oracle Storage Cloud Service. Even if applications are created using ACC service console this process is followed behind the scenes. To implement our deployment process accordingly, existing Oracle Cloud Service REST APIs can be used. For this blog post we will aim to implement the following steps: Read the complete article here.

imageNew Demos shared by Mike Lehmann Demo 1; Demo 2

Use Wercker step to restart Oracle Container Cloud Service in Wercker Continuous Delivery workflow

About this tutorial

Wercker provides a Docker-Native CI/CD Automation platform for Kubernetes & Microservice Deployments. Wercker is integrated with Docker containers, which package up application code and can be easily moved from server to server. In case when Wercker packaged container deployed to Oracle Container Cloud Service would be useful to restart a container whenever new version of application/Docker container available.

Currently this feature is available using publicly available Wercker Step ([ which allows to restart the container using the specified Docker image.

To enable this step define the oracle-occs-container-util step in the wercker.yml and the application workflow. For further details read the step or follow this tutorial. Get the workshop material here.


Build Spring Boot container packaged application using Wercker and deploy to Oracle Application Container Cloud Service

About this tutorial

Wercker is a Docker-Native CI/CD Automation platform for Kubernetes & Microservice Deployments. Wercker is integrated with Docker containers, which package up application code and can be easily moved from server to server. Each build artifact can be a Docker container. The user can take the container from the Docker Hub or his private registry and build the code before shipping it. Its SaaS platform enables developers to test and deploy code often. They can push software updates incrementally as they are ready, rather than in bundled dumps. It makes it easier for coders to practice continuous integration, a software engineering practice in which each change a developer makes to the codebase is constantly tested in the process so that software doesn’t break when it goes live.

Wercker is based on the concept of pipelines, which are automated workflows. Pipelines take pieces of code and automatically execute a series of steps upon that code. The Wercker API provides programmatic access to information about applications, builds and deploys. There are code snippets available for Golang, Node.js and Python.

Oracle Application Container Cloud Service includes Oracle Java SE Cloud Service and Oracle Node Cloud Service. It provides a lightweight infrastructure so that you can run Java SE, PHP, and Node.js applications in the Oracle Cloud. Get the workshop material here.




Feb 19, 2018 – Mar 16, 2018 or Apr 02, 2018 – Apr 27, 2018

About the Bootcamp

Oracle WebLogic Server 12c Implementation Specialist Boot Camp is a technical enablement program aimed at partner technical consultants who will be implementing Oracle WebLogic Server 12c solutions. The candidates should have hands on experience in installing, administering, and configuring Oracle WebLogic Server 12c and its components, including, Java Enterprise Edition (EE) Applications. It also prepares partners to become OPN Certified WebLogic Server 12c Implementation Specialists.
This boot camp is primarily focused on Oracle WebLogic Server 12c and related features and functionality. It covers topics such as: system architecture, deployment & post-install configurations and implementation best practices.
Learn To:

  • Use new WebLogic Server 12c Features and Functions
  • Configure and Implement WebLogic Server 12c Domains and Templates
  • Deploy Java EE Applications
  • Tune the WebLogic Server 12c Environment including the JVM for performance
  • Design and Implement Environments for High Availability and Disaster Recovery
  • Scale-out solutions with WebLogic Server 12c
  • Utilize Implementation Best Practices

Plan and Implement an upgrade to WebLogic Server 12c

This event is offered FREE of charge to selected
Oracle Partners.

  • Fusion Middleware/Java EE Architects;
  • Technical Consultants;
  • WebLogic Administrators;
  • System Administrators.

For details please visit the registration pages:

Feb 19, 2018 – Mar 16, 2018 or Apr 02, 2018 – Apr 27, 2018

For additional trainings please see the community training calendar (membership required)