Configuring the application migration tool for analysis

You can configure the tool to define a set of rules to run and define the scope of analysis within the workspace. The scope can be a project, a working set, or the entire workspace. After you define the scope, you can save the analysis configuration to use or modify later. With an application migration tool installed, you have new analysis options to configure and run an analysis.

To configure the analysis, complete the following steps:

  1. Open the analysis configuration options.
    You can access the configuration options in the following locations within Eclipse:
    • In the main Eclipse menu bar, go to Run > Analysis.
    • In the Launch toolbar, click the Software Analyzer icon ( Software Analyzer icon ) and select Software Analyzer Configurations.
    • In the Explorer view, right-click your project and select Software Analyzer > Software Analyzer Configurations.

    If you do not see Software Analyzer options, see Software Analyzer options not shown.

    You can add or remove analysis configurations by using the icons in the window.

    Figure 1. Creating a Software Analyzer configuration
    Configuration window
  2. In the configurations list, select Software Analyzer. Then, click New New icon . The basic configuration interface is shown in the window.
    Figure 2. Setting up the configuration
    Configuration setup
  3. In the Software Analyzer Configurations window, enter a name for the configuration, such as AppMigration.
  4. On the Scope tab, select Analyze entire workspace to scan all projects in the workspace.

    You can limit the scope of an analysis by using the other options to analyze a working set or a selection of projects.

    Tip: When you run your analysis from the Explorer view, the scope of the analysis is limited to the node in the project where the menu item was selected. This allows you to perform a quick analysis on a limited set of code.
  5. On the Rules tab, select the type of analysis to perform using the Rule Sets list. You can also select individual rules to run.
    Tip: To obtain additional information about a rule, highlight the rule and press Help icon . Help for the rule is shown in the configuration window. The initial help page includes a short description and a link to more information.
    Figure 3. Selecting rules
    Rule selection window

    Depending on which features you installed, you see one or more migration-related rule sets:

    • Cloud Application Migration
    • WebSphere Application Server Version Migration
    • WebLogic Application Migration
    • JBoss Application Migration
    • Oracle Application Migration
    • Apache Tomcat Application Migration
    • Other third-party servers

    The application migration tools have rules under the following analysis providers:

    • File Review
    • Java Code Review
    • JSP Code Review
    • XML File Review

    After you select a rule set, click Set to select the applicable application migration rules.

    Figure 4. Configuring a rule set
    Rule set configuration window

    Select the source and target settings for your environment:

    Source application server
    The source application server indicates the application server that you are migrating your application from. The source application server, either WebSphere Application Server or a third-party application server, affects the rules selected.

    When using the WebSphere version-to-version rule set or the cloud migration rule set, you can choose the source application server. For rule sets for third-party application servers, the source application server is preselected and cannot be changed.

    Target application server
    The target application server indicates the application server that you are migrating to. You can migrate to a specific version of WebSphere Application Server traditional, Liberty, or Liberty Core.
    Target Java EE version
    When migrating to WebSphere Application Server Liberty, you can also select the target Java Platform, Enterprise Edition (Java EE) version that you plan to use for the application.

    If you move to the latest Java EE level on Liberty or traditional WebSphere Application Server V9.0, you might experience different behaviors. The Java EE rules help you understand these differences and how they will affect your application. The rules can help you move from Java EE 6 to Java EE 7 on either WebSphere Application Server traditional or Liberty. It can also help you move from Java EE 6 or Java EE 7 to Java EE 8 on WebSphere Liberty. If you are already on Liberty Java EE 6 or Java EE 7, you can stay on your current Java EE level with zero migration.

    For Liberty, choose only the technologies that you are using. For example, if you do not use the CDI feature, do not select CDI. For both Liberty and traditional WebSphere, choose only the technologies that you must migrate. Some technologies, such as JPA and JAX-RS, do not require moving to the latest Java EE level. Consider keeping existing JPA applications running on the Java EE 6 JPA 2.0 feature based on OpenJPA, and use JPA 2.1 based on EclipseLink for new applications.

    Target cloud runtime
    The target cloud runtime indicates the cloud platform that you are migrating to. You can choose a cloud runtime environment to evaluate if your target application server is WebSphere Application Server traditional V8.5.5 or V9.0, Liberty, or Liberty Core.
    Source Java version
    The source Java version indicates the Java Platform, Standard Edition (Java SE) version that your application server currently uses.
    Target Java version
    The target Java version indicates the Java SE version that your target application server will use. If the source and target Java versions are different, migration rules are automatically selected.
    Note: The number of rules in the analysis configuration options varies depending on the platform on which the tool is installed. Analysis rules are available in several Rational products such as Rational Application Developer; therefore, the included rule sets might be different.
  6. To save the rule configuration, click Apply.
  7. In the Software Analysis Configurations window, you can select or clear any rule or group of rules to use in the analysis. For example, if you find after analysis that you do not need to make changes pointed out by a particular rule from the selected rule set, you can clear its selection to turn it off.
    1. To find the rule, the navigation in the configuration window is similar to the folders shown in the results tree view. Use the folder names to locate the rule.
    2. Clear the rule selection.
    3. Click Apply.
    The deselected rule will not be included in the next analysis.

Some rules have additional configuration options. When a rule with configuration options is selected, the rule properties are shown in the Properties tab under the list of rules. The following figure shows the rule properties for a web services rule. If you do not update the properties, the rule uses the default values.

Figure 5. Rule properties
Rule properties window