Installation and Setup of the Conversion Environment

There are two ways to create a system on which you can run the automated conversion process.

  1. Developer - This is the best starting point for someone that is new to the FWD technology.
  2. Build System - This is useful for organizations that want a system on which to convert and build the result. It does not include the runtime components needed to execute the converted result.


This is suitable for developers (ABL and/or Java) that are working on getting an application converted. This system is intended to allow running the automated conversion process AND also running the resulting converted code for testing or debugging purposes. It would support the full range of development tasks while providing a conversion and runtime environment that is contained on a single system.

To install/setup this developer system, follow these instructions:

Development Environment Setup

Build System

Once an application is fully converting and can be tested and/or put into production, it can be helpful to have a system on which the conversion runs. This is normally integrated with source code management and a build environment for a larger application. Optionally this can easily be integrated with continuous integration technology (e.g. Jenkins) or deployment/configuration management tools (e.g. Chef, Puppet, Salt). This can run completely automated or it can be launched manually when needed.

The key point with this approach is that it does not include the runtime components needed to execute the converted result. This is meant to be a build/conversion system only.

To install/setup this conversion system, follow the instructions in both of these chapters (in this order):

Building FWD From Source
Minimal Conversion Environment Setup

© 2004-2017 Golden Code Development Corporation. ALL RIGHTS RESERVED.