Want to run an application on WAS traditional in a Docker container but wondering how you can upgrade your WAS instance without losing your profile configuration?

Best practice for Docker containers is to make them immutable, persisting any data outside of the volume. This means that failed containers can be disposed of and replaced with new instances without losing any data. As long as those new instances expect the data in the same format, they don’t have to be running from the same image as the original failed container was using.

We can make use of this pattern where the data in question is a WAS profile configuration. If this is stored outside of the container, we can replace a container running one version of WAS with a container running a newer fix pack, all whilst retaining the same profile configuration. If some manual updates to the profile configuration are required, like removing temporary files, it is also possible to attach the volume to, for example, an Ubuntu container running bash.

The following video demonstrates how using separate data volume containers for profile configuration you can upgrade to the latest fix pack.

2 comments on"Upgrading WAS traditional Docker containers"

  1. Ernani Joppert March 01, 2017

    2 questions here:

    1) Why is there a custom node on the docker example? Is it really needed? I want to have 1 dmgr and 2 separate servers only, which each one already has a node themselves..

    2) Can this profile be used back and forth between earlier releases like v8.5.5.8 and then latest releases such as v8.5.5.11?

    Best Regards!

    • Kavitha Suresh Kumar March 01, 2017

      1) Custom node can be create and used when you want to create servers on nodes during cluster creation
      2) Yes, it can be used.

Join The Discussion

Your email address will not be published. Required fields are marked *