Choosing between WAS Classic and WAS Liberty

  • 09 Mar, 2016

“There are a number of aspects to consider when choosing between the traditional WebSphere Application Server (WAS full profile, or WAS Classic) and WAS Liberty for deployment. If you

have a hard requirement which is only available on one or the other (such as a particular API) then the choice is easy, but as the Liberty function has grown, it has become more common to

need to weigh the pros and cons of each more closely; to consider topology choices, operational capabilities and security options. Over one hundred and fifty IBM products have shipped with

Liberty as their internal application server and an ever-growing number of IBM SaaS offerings, such as BPM Workflow and Watson Analytics, are running on Liberty.“

See this document from IBM

Next

Related Posts

WebSphere Application Server Configuration Comparison Tool

  • 06 Sep, 2019

The Configuration Comparison Tool (CCT) is a lightweight wsadmin script and Python report generation script which will produce HTML reports on configuration settings for the following types of resourc

WebSphere Application Server Configuration Comparison ToolRead More

Configuring Cross Origin Resource Sharing on a Liberty server

  • 08 Mar, 2018

You can enable Cross Origin Resource Sharing (CORS) for your web applications on a Liberty server. Enabling CORS will allow JavaScript clients to make requests against your application on the Liberty

Configuring Cross Origin Resource Sharing on a Liberty serverRead More

Recommended values for web server plug-in config

  • 26 Sep, 2017

In the web server plug-in, what do the LoadBalanceWeight, MaxConnections, ConnectTimeout, ServerIOTimeout, RetryInterval, IgnoreAffinityRequests, and GetDWLMTable options mean and what are the recomme

Recommended values for web server plug-in configRead More