(r13) LibertyVersusWASFullProfileForCLM < Deployment

Engineering Lifecycle Management Wiki - Deployment
Community information and contribution guidelines
~~EditAttach~~Printable
TWiki > Deployment Web > DeploymentMigratingAndEvolving > LibertyVersusWASFullProfileForCLM
Revision 13 - 2019-07-05 - 09:45:15 - DineshKumar
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Liberty Vs Websphere Full Profile for CLM <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: Main.DineshKumar <br>
Build basis: CLM 6.0.6.1
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky> 
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 experience share from our internal hosting and from Customer deployments.. 
<br><br>
---++ What IBM Websphere Team says about Liberty 
One of the frequent asks from Websphere deployments was the start times.  Websphere Team says that "<i>Application start is generally faster on Liberty.</i>"  
<br><br>
Next common concern when comparing the two is performance, on which the Websphere Team says "<i>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).</i>"
<br><br>
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 : <br>
    [[https://developer.ibm.com/wasdev/docs/was-classic-or-was-liberty-how-to-choose/][ Traditional WebSphere or Liberty: how to choose? ]]
<br><br>
---++ Why Liberty, a word from CLM Development Team
 

*CLM applications* are typical *J2EE applications* and *only require* standard *J2EE application server container*.  *WebSphere Liberty* is a standard *J2EE application container*.  

Liberty is much lighter (200mb) than traditional <noautolink>WebSphere</noautolink> (1gb+) (as an example, we do not require EJB support, which is one of several features that make TWAS heavy). 
This makes Liberty more suitable for many of the modern use cases. 

For example Clustering... RTC nodes should be light and fast... starting up a Liberty node takes two - four minutes, this could be much longer with the heavier Traditional Websphere.

With Cluster use cases, Liberty is much simpler to handle.. in terms of starting, stopping, upgrading, monitoring, and overall resource footprint.

Clustering requires Jazz Authorization Server (JAS) and *JAS is supported only on Liberty*.
If you are looking *to Scale your Deployments*, its important to *migrate to Liberty*. 
<br><br>
---++ What we see in our Internal Hosting


*Jazz.net, <noautolink>ClearObject</noautolink>* runs on Liberty and haven't witnessed any performance degradation.
<br><br>
By Migrating to Liberty, *Jazz.net Team* found that it was much easier to administer and maintain due to : <br>   
   * Relieved of the Thread Pool management.  For more details, refer to [[https://developer.ibm.com/wasdev/docs/was-liberty-threading-and-why-you-probably-dont-need-to-tune-it/][Why you probably don’t need to tune Liberty Thread Pool]]
   * Easier to stage the deployment for any testing purposes.  
   * Startup times are noticeably faster, which makes it easier for incorporating quick changes.  

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 : [[MigrateFromTWAStoLiberty][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 
   * <noautolink>HttpSessionIdReuse</noautolink> to idReuse 
Properties that are valid for Liberty can be found [[https://www.ibm.com/support/knowledgecenter/SSRTLW_8.5.5/com.ibm.websphere.wlp.nd.multiplatform.doc/autodita/rwlp_metatype_4ic.html][here]]

<br>
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.  
<br><br>

*<noautolink>ClearObject</noautolink> Team* see that, with Liberty Performance is better with startup as well as during runtime.  Like Jazz.net Team, even the <noautolink>ClearObject</noautolink> Team opines that Migration is simple, could be accounted for in man-hours rather than in man-days.  For some CLM Instances, only few applications were migrated to Liberty while others continued to be on WAS Full Profile.  Even with such mix, the interop between applications remains unaffected.  

Admin/IT Team was well-versed with Full Profile and were skeptic of the learning curve involved in moving over to Liberty.  However, they found that learning curve was short and post migration, Admin/IT Team is happy since they find it easier to administer and maintain a Liberty setup, a few examples mentioned include : 
   * editing User Roles to Group mappings, visiting each profile through the admin console is avoided
   * [[https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_enable_tls1.2_liberty.html][enforcing TLS v1.2]] is simpler

Some things to *be cautious* about before switching to Liberty though : 
   * verify if your integrations are covered
   * any war file that is not CLM, needs to be investigated before
   * test authentications before planning the migration

Overall experience with and/or post Migration has been positive and now, mostly the CLM instances that are older (v5.x and pre v6.0.1), continue to be on WAS Full Profile and they are looking forward to moving more and more instances to Liberty sooner.
<br><br>

---++ 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.
<br><br>

<hr>
---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]], [[MigrateTomcatToLiberty][Migrate from Apache Tomcat to WebSphere Liberty]], [[https://developer.ibm.com/wasdev/docs/was-liberty-threading-and-why-you-probably-dont-need-to-tune-it/][WebSphere Liberty threading (and why you probably don’t need to tune it)]]

---+++++!! External links:          

   * [[https://www.ibm.com][IBM]]

<sticky></div></sticky>
Copyright © 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.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.