You are on page 1of 37

WebSphere Application Server

Application Migration Tool
Built on Rational Software Analyzer technology

Version 1.0.0
December 4, 2009

A combined effort:
IBM Software Group, Application and Integration Middleware Software
IBM Software Group, Rational Software

© Copyright IBM Corp. 2009

This page intentionally left blank.
(So the table of contents prints right side when duplexed)

Application Migration Tool

Table of Contents
Overview ..................................................................................................................................................4
Support ....................................................................................................................................................5
Installing and updating the migration tool ...........................................................................................6
Importing applications in Eclipse..........................................................................................................9
Configuring the tool for analysis.........................................................................................................15
Running the analysis............................................................................................................................21
Completing the process .......................................................................................................................24
WebLogic to WebSphere Application Server rules and quick fixes ................................................25
Java code review rules .........................................................................................................................25
JSP code review...................................................................................................................................28
XML file review .....................................................................................................................................28
Class path review .................................................................................................................................30
Troubleshooting....................................................................................................................................31
Software Analyzer options not shown ..................................................................................................31
Java EE constructs or JSP not read correctly ......................................................................................31
Logging and trace.................................................................................................................................32
Reports and history ..............................................................................................................................32
Known Issues .......................................................................................................................................32
Copyrights and trademarks .................................................................................................................36
Document change history....................................................................................................................37

© 2009, IBM SWG -3- Version 1.0.0 Date: Friday, December 04, 2009

2009 . The conversion process can involve modifying Java source code. Enterprise Edition (Java EE) applications from one third-party application server to another platform can be costly and time consuming. and use the tooling to assist in the conversion process. In many cases. which provides a single solution to identify.0 Date: Friday. December 04.Overview Converting Java™ Platform. The Application Migration Tool can assist you in performing these types of migrations. analyze. The tool flags a number of known differences between applications hosted on Oracle WebLogic and WebSphere Application Server. and optimize the application health. Version 1. it flags the file in question to provide insight to where design changes are needed. The tool then provides a way to review and change that data so that the application can run on IBM WebSphere Application Server. IBM SWG -4. the tool can automatically convert these key differences. The migration toolkit uses the scanning capabilities of Rational Software Analyzer to look for specific constructs unique to the Oracle® WebLogic application server. JavaServer™ Pages (JSP). The Application Migration Tool is part of the IBM® WebSphere® Application Server Migration Toolkit. The tooling is based on IBM Rational® Software Analyzer. If the tool is unable to perform the fix. The migration tool is compatible with:  WebSphere Application Server Version 7.0.4 and prior versions © 2009. This toolkit is part of the overall strategy and plan for assisting customers in migrating from one application server to the IBM WebSphere Application Server. This document explains how to install.0  Java EE 1. and deployment descriptors. configure.

The tool highlights these problem areas but does not provide a quick fix. IBM SWG -5.ibm. the tool detects areas that require design changes and code rewrites. You can use the quick fix preview support in the migration tool to decide if you want to accept the suggested code change.jspa?forumID=2106).com/developerworks/forums/forum.Support The Application Migration Tool scans for a number of known issues in applications being migrated from WebLogic to WebSphere Application Server. Supported rules and quick fixes are documented in WebLogic to WebSphere Application Server rules and quick fixes on page 25.0.com/developerworks/rational/products/rsar/. Other users can use the forum to report issues or suggestions and ask questions. a quick fix is provided to change your code to a more portable solution. we want to hear your feedback. If you have access to IBM Passport Advantage®. Always make a backup copy of your source code before starting a migration. For more information on the Rational Software Analyzer product. Also. (http://www. During the scanning process. The tool will be updated on developerWorks® as new rules and quick fixes are available. Version 1.0 Date: Friday. The tool does not catch all problems. Where possible. view the help information provided with the rules to decide if you want to run the quick fix. you can open a customer defect.ibm. © 2009. 2009 . December 04. go to http://www. The Application Migration Tool forum is available to provide input and get questions answered. As you encounter patterns that the tool does not flag.

eclipse. and Java EE Development.org/releases/ganymede). Development.ibm. Download the latest version of the migration toolkit from developerWorks site http://www.4.Installing and updating the migration tool The Application Migration Tool is a plug-in that you install into an existing Eclipse IDE. install (http://download. perform the following steps: 1. IBM SWG -6.4. install the prerequisite plug-ins from either the Galileo or Ganymede site depending on your Eclipse version. Rational Application Developer is configured with the required plug-ins.4 (3. To install or update the Application Migration Tool. Start the Eclipse IDE. version 3.0 Date: Friday. the tool works with a basic Eclipse IDE. If this is not a Rational Application Developer environment. select Help > Install New From the Eclipse menu bar.5 and higher For Eclipse 3. Use the appropriate example.eclipse. If an Eclipse IDE is not already installed. 2. then download and install Eclipse 3.com/developerworks/websphere/downloads/migration_toolkit. install Business Intelligence.eclipse. depending on your version of Eclipse: For Eclipse 3. XML. The preferred environments are Rational Application Developer or Rational Application Developer for Assembly and Deploy so that you have all the tools for application development and deployment.2 or higher.2 or higher from http://www. Reporting and Charting and Charting and Reporting and Web and Java EE Web. 2009 .2 and higher) From the Eclipse menu bar. December 04.html and save it locally.0.org. However. Version 1.4. 3. select Help > Software Software… updates… Using the Galileo update site Using the Ganymede update site (http://download.org/releases/galileo). Figure 1: Eclipse plug-in installation © 2009.

4. Click Next on the Install Details panel. Select the checkbox for Application Migration Tool. Use the previous installation dialog to install or update the Application Migration Toolkit. The install status window shows the installation progress. 9. b. 2009 . Click Finish. Click Add… in Eclipse 3. Figure 2: Tool installation 6. Click OK. Complete the following actions in the Install window: (Figure 3: Select Plug-in) a. 5. 8.5 or click Add Site… in Eclipse 3. 7.0 Date: Friday. 4.0. Name: Application Migration Tool Location: Use the Archive… button to find the compressed file you downloaded. © 2009. IBM SWG -7. December 04. enter the following information: (Figure 2: Tool installation). read the terms and accept the license agreements. On the Review Licenses panel. Version 1. Select the checkbox to Contact all update sites during install to find required software and click Next. if any are presented. In the Add Site window.

IBM SWG -8.0. Figure 3: Select Plug-in 10. Restart the Eclipse environment when the Software Updates window is displayed.0 Date: Friday. December 04. 2009 . Version 1. Figure 4: Restart dialog © 2009.

Shared Java projects In some cases Java source files belong in a separate project rather than in the Web project. belong in the src folder of the project. Review the following guidelines for structuring projects:  Java source code for a WAR file (for example. There are two options for referencing those Java classes from a Web project: 1. servlet. For example. or utility classes). it can be placed in the EarContent folder. The src folder is defined and can be changed in the Java Build Path properties for the project. Create a copy of the JAR file in each WAR file. and each EJB module should be created as an EJB project. December 04. Create a single copy of the Java project’s JAR file in the EAR file. since it reduces the size of the EAR file. Create a new Java project and add the Java source into the project’s src folder. organize files in this manner when multiple WAR files within the same Web application reference common classes or to improve the organization of the Web application. Select the Java EE Module Dependencies item from the left pane. If the Java source code needs to be referenced by more than one WAR. The preferred approach for doing this is to create new projects in the workspace for each EAR. If your project contains an APP-INF/lib folder. Each WAR file references the JAR file. The EAR file should be created as an enterprise application project.  EAR-level JAR libraries can be placed in the EarContent folder of the enterprise application project.  Java source code for an EJB module can be placed in the ejbModule folder of the EJB project. model. you must import the application enterprise archive (EAR) file or modules with source code into Eclipse before performing analysis.0 Date: Friday.0. and on the right pane select the checkbox next to the Java projects you want to reference. see the Shared Java Projects section of this document. You must install Java EE Developer Tools for Eclipse to create these projects. Complete the following steps to place Java source files in a separate project: 1. Web archive (WAR). © 2009. Go to the Properties dialog of the EAR project (right-click the project in the Project view and select Properties).  Precompiled Java archive (JAR) libraries for a WAR file belong in the WebContent/WEB-INF/lib folder. Each WAR file within the EAR file should be created as a dynamic Web project. you must run the class path rule and its quick fix to update the class paths correctly. This approach works well if only one WAR file references the JAR file. Version 1. 2009 . and Enterprise JavaBeans™ (EJB) module. This approach is preferable.Importing applications in Eclipse If the application to migrate is not already in Eclipse. 2. however. 2. IBM SWG -9.

10 . and ensure that the J2EE Modules tab is selected. Version 1. 2009 . December 04. Select the Java EE Module Dependencies item from the left pane.Figure 5: Java EE EAR module dependencies 3. Select the checkbox beside the JAR files to reference. © 2009. Open the Properties dialog for each Web project that needs to reference a JAR file.0. IBM SWG .0 Date: Friday.

Figure 6: Java EE Module Dependencies For the second approach.0. Version 1. Select the Java EE Module Dependencies item from the left pane. which creates a copy of the JAR file in each WAR file. IBM SWG . The table contains every Java project available.0 Date: Friday. and then click on the Web Libraries tab in the right pane.11 . complete the following steps: 1. © 2009. 2009 . December 04. Right-click on the project in the Project view and select Properties. Open the Properties dialog of the Web project.

Figure 7: Web Libraries Module Dependencies 2. Follow these steps to configure the Java EE Runtime Library: 1.0 Date: Friday. Configuring a Java EE Runtime Library When using Eclipse with the Java EE tooling installed. December 04.0. Version 1. Select the checkbox beside the project to add it to the WAR file. Open the Eclipse preferences by choosing Preferences under the Eclipse Window menu. 2. Navigate to the Server > Runtime Environments item on the left pane. the Java compiler will not be able to resolve references to the Java EE APIs unless a target runtime environment is configured. © 2009. IBM SWG . 2009 .12 .

December 04. Version 1. On the next wizard page. click Browse to choose the library location. Click Add and choose Basic > J2EE Runtime Library.13 . Figure 9: Targeted Runtimes © 2009.jar file with the Java EE APIs.Figure 8: Server Runtime Environments 3. That folder contains the j2ee. go to the project properties dialog. 2009 . Right-click on the project in the Project view and select Properties. and choose the Targeted Runtimes item. and locate the dev/JavaEE folder of your WebSphere Application Server installation and select the appropriate Java EE version.0. IBM SWG . 4. To use this runtime library in a Web or EJB project.0 Date: Friday.

0.Under the runtime listing. select the checkbox next to the recently configured Java EE runtime library. © 2009.0 Date: Friday. 2009 .14 . December 04. IBM SWG . Version 1. and click OK.

© 2009.0.Configuring the 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. a working set. in the Launch toolbar. Once defined. Version 1. With the migration toolkit installed. The scope can be a project. Software Analyzer options not shown. on page 31. you can save the analysis configuration to use or modify later. you have new analysis options to configure and run an analysis. or the entire workspace. see the troubleshooting section. From the Eclipse menu: From the Launch Eclipse toolbar: From the explorer context menu: Figure 10: Options for running the tool If you do not see Software Analyzer options. You can access the options in the Eclipse Run menu.15 .0 Date: Friday. December 04. and in the explorer context menus. IBM SWG . The following figure demonstrates the different ways you can run the analysis using the Application Migration Toolkit. 2009 .

16 . December 04. select Software Analyzer ( ) > Software Analyzer Configurations… to display the main configuration dialog. complete the following steps: 1. On the toolbar. In the configurations list. Figure 11: Configuration dialog 2. 2009 . The right side of the dialog changes to show the basic configuration interface. You can add or remove analysis configurations by using the icons in the dialog. © 2009. select Software Analyzer then click New . Version 1.0. IBM SWG .To configure the analysis using the toolbar.0 Date: Friday.

Version 1. This allows you to perform a quick analysis on a limited set of code. Figure 12: Configuration Setup 3. The migration toolkit has rules under the following analysis providers: © 2009. 2009 . You can limit the scope of an analysis by using the other options on this dialog to analyze a working set or a selection of projects. select WebLogic Application Migration from the Rule Sets menu list. On the Scope tab. Tip: When you use the explorer context menu to run your analysis. December 04. On the Rules tab. select the type of analysis to perform (see Figure 13) To automatically select all of the WebLogic conversion rules. select Analyze entire workspace to scan all projects in the workspace.17 . such as AppMigration as shown in Figure 12: Configuration Setup. 4. enter a name for the configuration. IBM SWG .0 Date: Friday. In the Software Analyzer Configuration dialog.0. 5. and click Set. the scope of the analysis is limited to the node in the project where the context menu was selected.

Analysis rules are available in several Rational products such as Rational Application Developer. Help for the rule is shown in the configuration dialog. 2009 . December 04. The nodes at the beginning of the domain tree are analysis providers. Note: The number of rules in the analysis configuration dialog varies depending on the platform on which the toolkit is installed. This tab also includes additional buttons for importing and exporting rule selections.0 Date: Friday. therefore. See Figure 13 for an example of selected rules. highlight the rule and press F1. Providers contain categories which organize the rules. which represent the types of analysis tools that are recognized by the analysis framework. where you can select or deselect analysis elements.  Class-Path Review  Java Code Review  JSP Code Review  XML File Review The Rules tab displays a directory tree. IBM SWG .0. Version 1. Tip: To obtain additional information about a rule. The initial help page includes a short description and a link to more information. © 2009. the included rule sets might be different.18 .

Some rules have additional configuration options. click Apply. To save the rule configuration.0 Date: Friday. When a rule with configuration options is selected. If you do not update the properties. the rule properties are shown in the Properties tab under the list of rules.19 . © 2009. Figure 13: Rule selection 6.0. the rule uses the default values. Figure 14 shows the rule properties for a Web services rule. IBM SWG . Version 1. 2009 . December 04.

0 Date: Friday. 2009 . IBM SWG . Figure 14: Rule Properties © 2009.0. December 04.20 . Version 1.

such as Java Code Review. the results view might vary. 1. Figure 15: Java Code Review results view If no results are shown in the panel. December 04. Right-clicking on individual results gives access to options such as viewing the source code where the problem occurred or correcting the problem with a provided fix.21 . support viewing results in more than one format.0. IBM SWG . The results are displayed in the Software Analysis Results view (Figure 15: Java Code Review results view). no issues were identified while scanning. For example. 2009 . © 2009.0 Date: Friday. To start the analysis. click Analyze on the Configuration dialog. results can be viewed in a table or a tree format. The results generated by the migration toolkit are displayed in one of four tabs:  Class-Path Review  JSP Code Review  XML File Review  Java Code Review Some results views. 2.Running the analysis Run the analysis and display the results. Depending on which rules you are running. Version 1.

 Quick Fix Preview – This option is available for the rules that support showing a side-by-side comparison of the original code and the code after the quick fix is applied.xml file. The cause of the problem is highlighted and a rule violation icon is shown in the left margin of the editor.22 . XML file. IBM SWG . Figure 16: Result options with Quick Fix Preview and Help shows an example of the quick fix preview. Figure 16: Result options with Quick Fix Preview and Help Not all rules have all actions available. JSP or manifest file. but the possible actions include:  View Result – Opens an editor showing the source file that triggered the rule. the files are shown in the Structure Compare portion of the Compare view.  Quick Fix – The light bulb overlay on the result list icon ( ) indicates this rule has a quick fix. The quick fix might change the code directly or it might present the steps needed to complete the fix. Some quick fixes modify more than one file. Selecting this option runs the conversion that modifies the affected Java code. When you select Quick Fix Preview for a fix affecting multiple files. For example. © 2009. This option allows you to see the changes before they are made. Version 1.0. 2009 . Figure 17 shows the changes that will be made to a web. Double-click each file to view the differences. allowing it to run in WebSphere Application Server.0 Date: Friday. December 04.

0 Date: Friday. For Java files.23 . The first panel is a short description. Version 1. a comment annotation is added to the file so that the rule is not triggered on future analysis runs. Press F1 to open the Help view. 2009 . IBM SWG . Click Detailed Help to get more information. Context sensitive help is displayed in the Help view as you select each result.  Quick Fix All – This option resolves all issues identified for a given rule. Figure 17: Quick Fix Preview with multiple files  Ignore Result – This option removes the rule from the list without making a code change. December 04.0. © 2009.

the updated application must be exported and tested on WebSphere Application Server. Version 1. there are a number of additional rules provided by the Rational Software Analyzer product that can help improve the quality of your code. there are tools available to create deployments and test the application within the Eclipse environment.0 Date: Friday. When the selected rules run and necessary changes are made. Figure 18: Other architectural and Java rules Access these rules by creating a new analysis configuration or modifying an existing one. These rules are not automatically selected as part of the WebLogic Application Migration rule set. 2009 . IBM SWG . December 04.0. Figure 18: Other architectural and Java rules shows examples of the additional rules.24 . If using Rational Application Developer.Completing the process After correcting the issues highlighted by the migration toolkit by running quick fixes or by making manual code changes. © 2009. These rules are not required for conversion.

provider.jndi.lookup(“javax. References to the UserTransaction object are not allowed from CMT beans.0 Date: Friday.url= t3://localhost:7001 If found. press F1 when viewing the rule in the configuration dialog or in the results viewer.rmi to use the Java provided classes. Version 1.WebLogic to WebSphere Application Server rules and quick fixes The Application Migration Tool evaluates Java code. This section provides specific details on the rules and quick fixes provided.naming. 2009 . IBM SWG . JSP code.WLI nitialContextFactory  java. These references are flagged so that you can remove this Java EE violation.rmi to java.transaction. WebSphere Application Server conversion rules are included in the following analysis domains: Figure 19: Analysis domains Java code review rules Under the Java Code Review set of rules.25 . and Web services deployment descriptors as part of its analysis set. deployment descriptors.rmi packages. Do not use WebLogic-specific JNDI Yes Scans Java files detecting the usage of the JNDI name values name values:  java. users are given the option to change the © 2009. December 04. the WebLogic to WebSphere code migration category contains multiple rules. Rule Name Quick Action Taken Fix Do not use UserTransaction No This rule detects references to interface from CMT beans ctx. For more information. Do not use WebLogic RMI API calls Yes This rule detects the use of references to the proprietary weblogic.0. The quick fix changes weblogic.initial=weblogic.factory.UserTransaction”) within container managed transaction enterprise beans.naming.

lookup(“java:comp/UserTransaction”) Use matching throws clause in EJB Yes This rule looks for mismatches between the bean class enterprise bean implementation and the method definitions in the home and remote interfaces.InitialContext(Hashtable) constructor.ServletContextListener interface and registers it in the application's web.apache Yes This rule flags import and code references to classes packages where the class package starts with weblogic. The quick fix adds any missing exceptions and removes any extra exceptions. JNDI names to default portable JNDI Name values:  java. IBM SWG .apache and the class does not map to an open source Apache class.url=corbaloc:iiop:local host:2809 Note: the JNDI Name values must be in the same java source file where the context is initialized with the javax.0 Date: Friday. You must modify the code to use different classes. December 04. Use compliant UserTransaction Yes This rule looks for references to lookup name ctx.transaction. Do not use weblogic.provider.WsnInitialContextFactory  java. Within servlets.servlet. The quick fix converts these classes to use the javax.initial=com. Within bean managed transaction (BMT) beans.apache packages where the class package starts with weblogic. the quick fix converts the flagged line to ctx.0.naming.factory.lookup(“javax.naming.InitialContext(Hashtable). Do not use WebLogic startup or Yes This rule looks for classes that implement the shutdown classes WebLogic startup and shutdown interfaces.apache class.websph ere. Use portable JNDI Names No Detects the usage of the constructor: javax.26 . See the rule help for more information. The interfaces are not changed.ibm. The quick fix changes the code to org. Web applications and client code.apache. informing not to put any proprietary WebLogic JNDI name values into the Hashtable. 2009 . Do not use non-mapping No This rule flags import and code references to classes weblogic.getUserTransaction(). Version 1.UserTransaction”). the flagged line is converted to the JNDI lookup: ctx.xml file.naming.apache and the class maps directly to an org.naming. © 2009.naming.

Download the appropriate Apache open source . Version 1.jar file. Do not use WebLogic-specific No This rule flags imported classes that begin with packages weblogic but not including the weblogic. © 2009.0.apache classes. and include it with your application. IBM SWG .0 Date: Friday. December 04. 2009 .27 . The flagged server specific APIs must be migrated.

Use standard deployment Yes WebLogic-specific deployment descriptors descriptors for resource reference (weblogic. If the JSP fragment file has the .jsp extension for Yes This rule looks for JSP fragments included in another JSP fragments JSP.xml). For the references to work on WebSphere Application Server. press F1 when viewing the rule in the results viewer. December 04. For more information.28 .xml or ejb-jar. XML file review The XML File Review provides a number of rules to detect deployment descriptors.xml) might contain names EJB references.0.jspf extension. For the references to work on WebSphere Application Server.JSP code review Under the JSP Code Review set. they must be moved to the standard Java EE deployment descriptors (web.xml or weblogic-ejb-jar. Rule Name Quick Action Taken Fix Avoid using a . Use correct case for tag attribute Yes JSP taglib attributes are case-sensitive in names WebSphere Application Server.0 Date: Friday. The quick fix provided moves all EJB references defined in WebLogic-specific deployment descriptors to standard deployment descriptors. Version 1. Rule Name Quick Action Taken Fix Do not use local JNDI names No Select the rule and press F1 for manual conversion instructions. the JSP Conversions category has rules described in the following table. These references map the EJB reference to the JNDI name. it is flagged.xml) might contain names resource references. These references map the EJB reference to the JNDI name. This rule flags any taglib attribute that is not case correct. Use standard deployment Yes WebLogic-specific deployment descriptors descriptors for EJB reference (weblogic. The quick fix takes you to the refactor dialog to change the file name and all of its references.xml or weblogic-ejb-jar. IBM SWG . Web services and other XML file issues. 2009 . The quick fix changes the case as it is defined in the tag library. they must © 2009.jsp extension rather than .

be moved to the standard Java EE deployment descriptors (web. December 04.29 .xml file instructions.xml No Select the rule and press F1 for manual conversion file instructions.xml file No Select the rule and press F1 for manual conversion instructions. Do not use weblogic-cmp-jar.0 Date: Friday.xml file instructions.xml file No Select the rule and press F1 for manual conversion instructions. Version 1.xml or  The presence of weblogic-webservices.xml or ejb-jar. Do not use weblogic-ejb-jar. Use WebSphere bindings to define No Select the rule and press F1 for manual conversion message driven descriptor instructions. No Select the rule and press F1 for manual conversion diagnostics.xml). 2009 . The quick fix provided moves all resource references defined in WebLogic-specific deployment descriptors to standard deployment descriptors.xml file instructions. Do not use weblogic. Use WebSphere bindings to define No Select the rule and press F1 for manual conversion JNDI names instructions. Do not use weblogic-ra. The following rule flags any WebLogic unhandled or partially handled XML file: Rule Name Quick Action Taken Fix Do not use weblogic. The WebLogic Web services migration category has the following rule: Rule Name Quick Action Taken Fix Do not use WebLogic Web services Yes This rule looks for the Web services deployment deployment descriptor descriptor as follows:  The presence of web-services. IBM SWG . Use WebSphere extensions to No Select the rule and press F1 for manual conversion define transaction timeout seconds instructions. Do not use weblogic-cmp-rdbms. Do not use weblogic.0. No Select the rule and press F1 for manual conversion application. © 2009. No Select the rule and press F1 for manual conversion jar.xml and the Java EE deployment descriptor (webservices.xml file No Select the rule and press F1 for manual conversion instructions. Use WebSphere extensions to No Select the rule and press F1 for manual conversion define concurrency strategy instructions.xml) in the same folder.

The quick fix generates an ANT script that uses IBM WebSphere ANT tasks. the fix might also generate the Service Endpoint Interface (SEI) for the service and add it to the project class path. Depending on the deployment descriptor.MF for application Yes This rule looks for any classes or libraries contained class path within an APP-INF directory of an EAR file. copy the generated artifacts to the project.0 Date: Friday. Class path review The Class-Path Review provider verifies the MANIFEST.MF class path is set up properly.0. 2009 . for example. IBM SWG . The quick fix adds an entry to the class path of each affected Web module by updating the Class-Path entry of the module's MANIFEST. December 04. and possibly add additional targets such as the endpoint enabler. The user can then run the ANT script. Rule Name Quick Action Taken Fix Use MANIFEST. which generates the appropriate artifacts for the list of Web services based on the information collected from the deployment descriptors. © 2009.MF file.30 . Version 1.

then the Rational Software Analyzer checkbox might be displayed. In the Customize Perspective window. you have new Software Analyzer menu and toolbar options in the Java. Click OK. December 04. Version 1. the projects must be set up with their appropriate project facets. © 2009. projects that contain enterprise beans must have the EJB Module facet. From your perspective. 2. C++. IBM SWG . complete the following steps: 1. You can see facets for a project by right-clicking on the project in the project explorer and selecting Properties. 3. For example. enable these options manually. select Window > Customize Perspective from the Eclipse menu.0 Date: Friday. and Plug-in Development perspectives. click the Commands tab and select the Software Analyzer checkbox. To customize other perspectives. If you are running Rational Application Developer. When using other perspectives. Projects containing Web modules must be dynamic Web projects.0.Troubleshooting Software Analyzer options not shown After the Application Migration Tool is installed.31 . 2009 . Figure 20: Software Analyzer availability Java EE constructs or JSP not read correctly For the tooling to read project files correctly. Select the Project Facets property. See Importing applications in Eclipse on page 9 for more information. Debug.

An HTML report is displayed in a Web browser. Clicking the marker displays a pop-up that allows a quick fix action and displays help text.ini property file. eclipse.ibm. For exported history. Known Issues No popup window displays when clicking on the marker This issue effects non-Java based rules. Enable the migration tool’s trace by setting the appconversion.  The Application Migration Tool service logs are located in the <workspace>/.trace=true  eclipse.trace system variable on the Eclipse command line or in the eclipse. This log contains all error information as well as detailed trace information if trace is enabled. IBM SWG . © 2009.analysis.ini file found in the same directory as the eclipse.0. the analysis provider tabs have buttons used to export selected analysis history to file and to generate reports. Figure 21 Error! Reference source not found. Java Code Review is the only results view that has support for reports.xtools. the report is displayed when the report is finished.0 Date: Friday.ws.exe file: -Dappconversion.appconversion.reporting/reports directory. For example:  Command line option.metadata/. 2009 .plugins/com. Add the system variable to the command line that starts Eclipse.plugins/com. For generated reports.shows that analysis of a Java rule results in a clickable marker in the left margin on line 31.32 .metadata/.base directory.exe -vmargs -Dappconversion. You can configure the Web browser under the Eclipse properties for General > Web Browser. you can specify the location for the generated result.log) contains our severe error logs as well as Rational Software Analyzer logs. Add the following line to the eclipse. The generated files are put in the <workspace>/.metadata/.ibm. Version 1. December 04.ini option. PDF reports are displayed in the system’s default PDF viewer.trace=true Reports and history In the Software Analyzer Results view.Logging and trace The Application Migration Tool writes error information to two log files:  The workspace log (<workspace>/.

0. December 04. Version 1. and hovering over the marker only displays the help text.Figure 21: Java quick fix marker Figure 22 shows an example of an XML rule violation that results in a marker on line 11. IBM SWG . Double-clicking on a marker in a manifest file removes the marker Figure 23Figure 23 shows Class-Path analysis results and the file displayed when you view results.0 Date: Friday. However. © 2009. clicking on the marker has no action.33 . Double-clicking on the marker on the first line removes the marker as shown in Figure 24. 2009 . Figure 22: XML quick fix marker Solution: Use the Software Analyzer Results view to select the Quick Fix action in non-Java files.

indicating that there are several markers on this line. 2009 . December 04. © 2009. You must carry out the action of the first marker in order to select successive markers. Can not select multiple markers on the same line When there are multiple markers on the same line of text. line 24 has multiple segments of underlined text. Figure 25 Multiple markers on a line Figure 26 shows that hovering over line 24 in the left margin displays a message indicating there are multiple markers. In Figure 25. IBM SWG . Version 1.34 .Figure 23: Manifest file markers Figure 24: Manifest file after double-clicking on the marker Solution: Rerun the class path rule to display the marker again.0.0 Date: Friday. you cannot toggle between the different markers.

December 04. Figure 27: Marker actions When using the marker in the left margin. you must resolve all issues with prior rules before you can get to successive quick fix actions. © 2009. 2009 . no text is selected and highlighted. Clicking on View Result for XML rules has no highlighted text When viewing the results of any XML rule. Solution: Use the marker in the left margin to view the line causing the rule violation. Version 1. Solution: Use the Software Analyzer Results view to select the Quick Fix action you want.Figure 26: Marker hover help Figure 27 shows that clicking on the marker on line 24 results in displaying only the first rule’s actions. although there is a marker in the left margin.0 Date: Friday.0.35 . IBM SWG .

programs. Therefore. in the United States. revenue growth. References in this publication to IBM products. Passport Advantage. it is provided AS IS without warranty of any kind. developerWorks. the IBM logo. nor shall have the effect of. other countries or both. Other company. While efforts were made to verify the completeness and accuracy of the information contained in this publication. IBM SWG .0. nor shall have the effect of. © 2009. or altering the terms and conditions of the applicable license agreement governing the use of IBM software.36 . or otherwise related to. this information is based on IBM’s current product plans and strategy. and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in this publication is intended to. which are subject to change by IBM without notice. Nothing contained in these materials is intended to.0 Date: Friday. © Copyright IBM Corporation 2009. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors. creating any warranties or representations from IBM or its suppliers or licensors. 2009 . or services do not imply that they will be available in all countries in which IBM operates. Version 1. savings or other results. other countries or both. the storage configuration. and WebSphere are trademarks of International Business Machines Corporation in the United States. Inc. product and service names may be trademarks or service marks of others. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. express or implied. the I/O configuration.Copyrights and trademarks . IBM. IBM shall not be responsible for any damages arising out of the use of. stating or implying that any activities undertaken by you will result in any specific sales. In addition. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems. this publication or any other materials. no assurance can be given that an individual user will achieve results similar to those stated here. December 04. All Rights Reserved The information contained in this publication is provided for informational purposes only. including considerations such as the amount of multiprogramming in the user's job stream. and the workload processed. The actual throughput or performance that any user will experience will vary depending upon many factors. Rational.

December 4.0. IBM SWG .Document change history Check the date in the footer of the document for the version of the document. 2009 Release 1. 2009 .37 .0 © 2009.0 Date: Friday. Version 1. December 04.0.