Modernizing runtimes with Liberty

Analyze existing applications

Summary

• Introduction to IBM Cloud Transformation Advisor
• Install IBM Cloud Transformation Advisor
• Scan a WebSphere Environment or use the pre-provided file
• Download the Data Collector
• Run the Data Collector
• Upload the Data Collector results
• Analyze the Recommendations

Introduction to IBM Cloud Transformation Advisor

• Identify the Java EE programming models in an app
• Determine the complexity of apps by reviewing a high-level inventory of the content and structure of each app
• Highlight the Java EE programming model and WebSphere API differences between the profile types
• Learn any Java EE specification implementation differences that might affect the app

Note

Install IBM Cloud Transformation Advisor

Scan a WebSphere Environment or use the pre-provided file

Download the Data Collector

1. Open IBM Cloud Transformation Advisor in a browser and click the button to create a new Workspace

2. Enter a Workspace name such as CustomerOrderServices and click Next

3. Enter a Collection name such as WAS855_AppSrv01 and click Let’s go

4. When the No recommendations available page is displayed, click the Data Collector button

5. When the Data Collector page is displayed, select the Source Operating System for your environment and click the Download button to download the Data Collector.

   This results in a file with a name similar to transformationadvisor-Linux_CustomerOrderServices_WAS855_AppSrv01.tgz being downloaded.

Run the Data Collector

1. Navigate to the directory you uploaded the transformationadvisor-Linux_CustomerOrderServices_WAS855_AppSrv01.tgz file to and issue the following commands to extract the Data Collector:

   mkdir datacollector
   cd datacollector
   mv transformationadvisor-Linux_CustomerOrderServices_WAS855_AppSrv01.tgz .
   tar -zxvf transformationadvisor-Linux_CustomerOrderServices_WAS855_AppSrv01.tgz
   cd transformationadvisor-*
   Copy to clipboardCopied!

2. It is necessary to modify the scan performed by the Data Collector to include the org.pwte package as the Data Collector doesn’t scan org.* packages by default. Open the conf/customCmd.properties file and modify it as shown below:

   scan_opt=--excludePackages=ch.qos,com.fasterxml,com.ibm,com.informix,com.lowagie,com.mchange,com.meterware,com.microsoft,com.sun,com.sybase,freemarker,groovy,java,javax,net,oracle,sqlj,sun,twitter4j,_ibmjsp --includePackages=org.pwte
   #java_opt=-Xmx2g
   Copy to clipboardCopied!

3. The following command assumes that WebSphere Application Server v855 is installed to /opt/IBM/WebSphere/AppServer855 with a profile named AppSrv01 and that the administration user is wasadmin with a password of wasadmin. Modify and issue the following command as necessary to execute the Data Collector against the WebSphere environment:

   ./bin/transformationadvisor -w /opt/IBM/WebSphere/AppServer855 -p AppSrv01 wasadmin wasadmin
   Copy to clipboardCopied!

4. When prompted, accept the license agreement. The Data Collection process will now start and will analyze all of the applications installed in the WebSphere Application Server environment and will also collect the related Java EE artifacts such as Data Sources and JMS definitions.

5. When the analysis is complete, the Data Collector will attempt to upload the collection results to IBM Cloud Transformation Advisor. If this is successful, you can skip to the Analyze the Recommendations section. If not, you will receive an error at the end of Data Collection and will find a file named AppSrv01.zip in your current directory as shown below.

   ~/datacollector/transformationadvisor-1.9.6# ls -la *.zip
   -rw-r--r-- 1 root root 625493 Jun 12 12:58 AppSrv01.zip
   Copy to clipboardCopied!

   Download this Data Collector Results zip file ready for uploading to IBM Cloud Transformation Advisor in the next section

Upload the Data Collector results

1. In the IBM Cloud Transformation Advisor web browser session, click the Recomendations link in the top left corner and then click the Upload data button as shown below

2. When the Upload data dialog is displayed, use the Drop or Add File button to select the Data Collector Results zip file that was downloaded in the previous section. Click Upload

   After a few moments the upload of the data collector results will be completed.

Analyze the Recommendations

1. The Data Collector analyzed all of the applications running on the traditional WebSphere profile and displays a row in the chart for each application and potential target runtime. In the case of the CustomerOrderServicesApp.ear application, IBM Cloud Transformation Advisor has determined that the application can be modernized to run on either WebSphere Liberty (which supports JEE6, 7 and 8) in 1.5 days or Open Liberty (which supports JEE7 or 8) in 9.5 days. Click on the CustomerOrderServicesApp.ear application name on the WebSphere Liberty row to see more information.

2. Review the analysis results and scroll down to the Complexity Rules section and open the section. Note that IBM Cloud Transformation Advisor has determined that code changes are required before this application will run on WebSphere Liberty.

3. Scroll down to the Issues details section and open the section. Note that IBM Cloud Transformation Advisor has detected that there are issues with lookups for Enterprise JavaBeans and with accessing the Apache Wink APIs.

4. In order to review the IBM Cloud Transformation Advisor results in more detail, scroll to the bottom of the analysis page and click on the Analysis Report link

5. When the warning dialog is displayed, click OK

6. The Detailed Migration Analysis Report will be displayed which show the results of the migration rules that were executed by the Data Collector and returned results. Scroll down to the Severe Rules section and click on the Show rule help link for each of the results. Review the recommendations.

   Behavior change on lookups for Enterprise JavaBeans In Liberty, EJB components are not bound to a server root Java Naming and Directory Interface (JNDI) namespace as they are in WebSphere Application Server traditional. The fix for this is to change the three classes that use ejblocal to use the correct URL for Liberty

   The user of system provided Apache Wink APIs requires configuration To use system-provided third-party APIs in Liberty applications, you must configure the applications to include the APIs. In WebSphere Application Server traditional, these APIs are available without configuration. This is a configuration only change and can be achieved by using a classloader definition in the Liberty server.xml file.

Final Analysis