With a drive to improve system performance and deliver a smaller footprint, OpenText Documentum 7.3 moves to go above and beyond customer expectations for continuous delivery by introducing application container support with Docker.
What is Docker?
Docker is a software containerization platform that allows user to package an application into a standardized unit for software development. Docker containers wrap a piece of software in a complete filesystem that contains everything needed to run: code, runtime, system tools, system libraries – anything that can be installed on a server. This guarantees that the software will always run the same, regardless of its environment. Containers running on a single machine share the same operating system kernel, starting instantly and use less RAM.
With Docker, images are constructed from layered filesystems and share common files, making disk usage and image downloads much more efficient. Docker containers are based on open standards, enabling containers to run on all major Linux distributions and on Microsoft Windows – and on top of any infrastructure.
What’s the Docker Appeal?
Docker containers enjoy small footprints that reduce the number of physical or virtual servers required to run an application.
As a result, system performance benefits from the smaller footprint and shared resources are better utilized, resulting in reduced hardware and operating costs.
OpenText Documentum 7.3 offers customers potential time savings of up to 75% with continuous deployment and integration functionality. These features include backwards-compatible, binary-only version updates through Stateless Documentum that can be applied to existing Documentum repositories without forced changes.
Documentum 7.3 and compatible components are also optionally packaged within portable, lightweight, production-ready reference images compatible with Docker runtime engines at no cost to customers. Regardless of repository size, this support provides significant upgrade and patch performance, as well as reduced downtime.
Documentum administrators may wish to start with development servers, then deploy to application servers or content servers as needed. The scaling and high availability capabilities are much easier using Docker, especially as infrastructure teams mature to move to the cloud, using Docker in production environments, and using Docker Swarm for autoscaling.
As 2017 moves forward, watch how OpenText Documentum will continue to support the trend toward the software-defined datacenter, enabling customers to take a cloud-first approach, or more easily migrate from on-premises solutions with continuous deployment.