1. Open OpenLegacy Perspective (Window -> Open Perspective).
  2. Select File -> New, OpenLegacy project.
  3. Supply a name to the application and default package name.
  4. Select “the desired backend solution type (Screens), and front end solution type
  5. On the next page, select host type AS/400 or Mainframe) for connecting to your Legacy application. Use mockup if you wish to practice OpenLegacy or to work offline.
  6. Define the host address (name/IP) port and code page of the legacy application (when working with real host)
  7. Select a theme for the web project
  8. If you are using an Eclipse plugin, and not OpenLegacy IDE, On the first time, your application will download using Maven all JAR dependencies from Maven central repository and OpenLegacy Maven repository. This may take a few minutes (most are Maven development related plug-ins).
  9. You may need to run Project -> Clean in case of errors in the project.
  10. Right click on “run-emulation.launch”, and select Run As -> run-emulation. This will run a standalone emulator, pointing to the configured host (it’s based on a Maven plug-in). You may need to edit this launcher to point to a JDK. If you are using eclipse (not STS), you may also need to define Maven within the Launcher (Launcher editing is done via right click on the Launcher -> Run As -> Run Configuration). For web projects you can alternatively run “run-application.launch”, to see the emulator within the web application.
  11. Your browser should be opened to to http://localhost:1512 and you should get the first screen of your legacy application (typically a login screen).
  12. You can control via the launcher “run-emulation.launch”, the port, browser (FF by default) and Spring context file (all has good defaults).
  13. Navigate through a few screens you wish to modernize, and click “Logoff” when you are done.
  14. Go back to Eclipse. Refresh the folder “src/test/resources”. A folder named “trails” should be created, which records a trail file  (XML format) of the screens you navigated through.
  15. Right click on the newly created trail file, and select “OpenLegacy” -> “Generate Model”. Verify the package name matches your organization convention.
  16. Alternatively, you can generate single screens, by opening the trail file, and clicking on one of the screens in the list.
  17. At this point, OpenLegacy screens analyzer gets to work. It analyzes the snapshots within the trail file and generates a class for each unique snapshot within the trail, and a JUnit test, which uses the API and performs the same actions you manually performed. You can customize the generated classes during generation preview.
  18. Now that you have created the API, you can generate from it a Web/Mobile solution, a REST API solution or a Web Service solution