In this post, we’ll take the DayTrader sample application and look at two ways in which to build and run it using Docker containers: the Eclipse Docker tooling and using Docker Compose.
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?
We haven't provided integration for traditional WebSphere in PaaS environments in the way that we have for Liberty. I am sometimes asked whether it is OK to run traditional WebSphere in a PaaS (Platform-as-a-Service) environment. Here's why Liberty is much better suited to a PaaS environment than most Java application servers.
In this tutorial you will learn how to install OpenShift Origin V3 and deploy multiple instances of WebSphere Liberty that contain your applications. You will use OpenShift to host your Liberty server, which is in the form of a Docker image.
... or how the operations folks can stop servicing configuration tickets and do something more valuable with their time!
WebSphere Liberty has now 'grown-up' to provide the full Java EE 7 platform. Combining that API set with operational capabilities that have been rapidly expanded over the past three years, Liberty is now a great deployment choice for many Java applications. WAS traditional remains fully strategic, however, and will evolve to the Java EE 7 standards itself in time, so how do you choose between the two?
A modern application server for hosting Java EE and OSGi applications during development, test, and production.
- Starts and stops quickly, typically in a few seconds.
- Requires little memory and disk space.
- Simple to configure with an XML file. Include only the capabilities required by your applications.
- Responds dynamically to application updates and server configuration changes.
- Built using IBM technologies and open source software packages from organizations such as Apache, Eclipse, and OW2.