EditAttachPrintable
r8 - 2019-06-14 - 14:50:24 - DineshKumarYou are here: TWiki >  Deployment Web > DeploymentMigratingAndEvolving > LibertyVersusWASFullProfileForCLM

Liberty Vs Websphere Full Profile for CLM uc.png

Authors: DineshKumar
Build basis: Products, editions, or versions that apply to the content. If no build basis applies to this content, set the build basis to None.

This article focuses on answering the curious question on if Liberty is the right choice for CLM Deployment. The article is a one-stop place for comparative study on Websphere vs Liberty for CLM. Read on for the results from our own Testing as well experiences from Customer Deployments..

What IBM Websphere Team says about Liberty

One of the frequent asks from Websphere deployments was the start times. Websphere Team says that "Application start is generally faster on Liberty."

Next common concern when comparing the two is performance, on which the Websphere Team says "The performance of request processing is very similar on the two profiles in most scenarios, because the application request paths are mostly common code (channels, transports, containers etc)."

The differences between the two profiles is touched upon at high-level in the below article, a whitepaper is referred inside gives in-depth details :
Traditional WebSphere or Liberty: how to choose?



What we have seen with our Customers

Several large Customers have migrated to Liberty. Some of them were further able to Cluster RTC and were able to support over 900 concurrent user base on a single RTC instance, running as a 3-Node Cluster.

What we find in our Testing for 6061



What we see in our Internal Hosting

Jazz.net, Clear Object runs on Liberty and haven't witnessed any performance degradation.

By Migrating to Liberty, Jazz.net Team found that it was much easier to administer and maintain due to :

Jazz.net Team migrated to Liberty mid 2017, and now some of RTC instances have further been clustered, making them more scalable. During migration, some key things to take care of were Certificates, LDAP config and custom properties.

A link that helps with Certificates is here : Migrate from Traditional WebSphere to WebSphere Liberty

Some Websphere custom properties that had to be mapped are listed below :

  • com.ibm.ws.webcontainer.channelwritetype to channelwritetype
  • com.ibm.ws.webcontainer.extractHostHeaderPort to extractHostHeaderPort
  • trusthostheaderport to trustHostHeaderPort
  • HttpSessionIdReuse to idReuse
Properties that are valid for Liberty can be found here


A word of caution from them though, about changing the XML files. Liberty loads the files automatically, without necessitating a restart and that might catch you off-guard, test your changes well before updating anything on the XML configuration files.

Why Move to Liberty, what's in store!

Ability to Scale CLM Applications - Clustering requires JAS and JAS is supported only on Liberty. If you are looking to scale your Deployments, its important to migrate to Liberty.



Related topics: Deployment web home, Migrate from Apache Tomcat to WebSphere Liberty, WebSphere Liberty threading (and why you probably don’t need to tune it)

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r20 | r10 < r9 < r8 < r7 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.