Porting J2EE Applications
Purpose
This process enumerates the basic considerations that you need to observe for each of the steps of the porting project. It mainly concentrates on the assessment phase where you perform different analyses to determine the scope of the project and the corresponding risks.
Use of the Process
This process is part of the following IT scenarios:
IT Scenario |
Scenario Variant |
Leveraging J2EE Standards for Porting and Adopting Applications |
Prerequisites
You have a J2EE application running on any of the J2EE-compliant application servers on the market that you need to port to SAP NetWeaver.
Process Flow
The following IT process runs in AS Java and DI usage types.
...
1. Assessment phase of the porting project
You need to analyze different aspects of the application that you port ranging from its architecture to the single pieces of source code. For example, the analyses include investigating important aspects such as the level of J2EE conformity (whether any vendor-specific extensions to the standard are used or not), any clustering requirements and how can they be fulfilled in SAP NetWeaver, persistency techniques and so on. The strictly J2EE-conformant components are migrated as-is; the other components of the application must be mapped to alternative components or techniques provided by the SAP NetWeaver. The results of the analysis give you a clear picture of the potential risks associated with the project, an estimation of the efforts required and can serve as input for creating the actual planning of the porting project.
Part of this phase can also be the preparation of a test suite that examines the application’s behavior prior to porting it. The same test can be executed at the end of the porting project and compare the results to verify the porting did not change the application’s behavior.
2. Implementation of the project
You need to import the sources of your J2EE application in the SAP NetWeaver Developer Studio so that you can carry out further migration tasks, such as changing application’s source code, generating deployment descriptors and so on. You import the respective J2EE modules your application consists of into the corresponding J2EE module project types (Web Module or EJB Module) using the Import function of the SAP NetWeaver Developer Studio.
For more information about the J2EE Migration Kit, see the SAP Developer Network at sdn.sap.com.
Result
The application’s modules are imported into the SAP NetWeaver Developer Studio and can be modified later on (if necessary at all) according to the plan of your porting project.