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.
This blog is a follow-up to our WebSphere Liberty API discovery introduction and takes you on the journey of adding Swagger support to your assets, exposing them on-premise, pushing them into the cloud, and finally integrating them with a powerful API management solution.
The key to this decision is whether or not your existing monolithic application is causing you problems. There are a number of well-recognised benefits to a microservices architecture and an equally well-known set of costs. Adam takes a look…
Do you have a Java EE application which is running successfully on your laptop and now you want to run it in a Docker container? Maybe you then want to take that container and deploy it to IBM Containers? What if that application requires access to a database? The following videos can help you in getting started.
Sometimes you have developed a standalone Java application but want to make use of capabilities provided by an application server. For example, you might have a standalone Java application which accesses a DB2 database but you want to make use of the connection pooling provided by WebSphere Liberty. To achieve this, you need to create an application client. This video describes how.
Consolidation of log events, from multiple servers and from servers that are running on different platforms (for example, on dedicated hardware and in the cloud), to a centralized location has always been a challenge. The Logstash and Logmet collector capabilities in the Liberty beta aim to help you do this without needing to install any special agents on your individual servers.