WebSphere Application Server V8.5 Migration Guide

Chapter 9. Migrating from Apache Tomcat 275

The three applications we selected for migration are:

򐂰 IBM Redbooks Publications Sample Application

򐂰 MvnForum

򐂰 Easy JSP Forum

9.1.1 Comparison of Apache Tomcat 7.0.27 and WebSphere Application

Server V8.5 Liberty profile terminology

Here we present some of the similarities and differences in terminology between Apache

Tomcat 7.0.27 and WebSphere Application Server V8.5 Liberty profile. The full profile and

Liberty profile share common terminology.

Table 9-1 Terminology comparison

9.2 Application Migration Tool - Apache Tomcat to WebSphere

Application Migration Tool - Apache Tomcat to WebSphere (Application Migration Tool) is

part of the Migration Toolkit, which is described in detail in Chapter 4, “Installation and

configuration of the Application Migration Tools” on page 89. Application Migration Tool can

help you in the following areas when migrating Java web applications from Apache Tomcat

(starting with Version 6.x) to WebSphere Application Server V7, V8, or V8.5 or a WebSphere

Application Server V8.5 Liberty profile.

򐂰 Apache Tomcat proprietary Java package references: Detect proprietary

package references.

򐂰 Apache Tomcat JSP issues: Detect nonstandard JSP.

򐂰 Apache Tomcat context.xml file: Detect and migrate context.xml file entries.

򐂰 Preferred practices for Spring: Detect and migrate Spring preferred practice issues.

9.3 Prerequisites and assumptions

There are a number of prerequisites and assumptions you must consider before you begin

the migration examples. You should be familiar with the Application Migration Tool as

described in Chapter 4, “Installation and configuration of the Application Migration Tools” on

page 89.

Description WebSphere Application

Server V8.5 Liberty profile

Apache Tomcat 7.0.27

Configure a file of users and

roles for security.

Creates users in a server.xml

file using a BasicUserRegistry

or LdapUserRegistry element.

Creates users in a

tomcat-users.xml file using

role and user elements.

Mapping of JNDI naming to

database drivers.

Creates JNDI mappings in a

server.xml file using jdbcDriver

and DataSource elements.

Creates JNDI mappings either

in a META-INF/context.xml file

in the application’s WAR file, or

in the server.xml file.

File Monitoring. Configures file monitoring in a

server.xml file using an

applicationMonitor element.

Configures file monitoring in a

context.xml file using a

WatchedResource element.