*** Welcome to piglix ***

Forte 4GL


Forté 4GL was a proprietary application server that was developed by Forté Software and used for developing scalable, highly available, enterprise applications.

Forté 4GL was created as an integrated solution for developing and managing client/server applications. Forté 4GL consists of an application server, tools for deploying and monitoring an application and an object oriented proprietary programming language, TOOL (transactional object oriented language). Given that TOOL only runs on the Forté application server, many users simply refer to their "TOOL" applications as "Forté" applications. The first release of Forté 4GL was published in August 1994. After releasing this initial product, Forté Inc. proceeded to build several extensions including:

In 1999, Forté Software came out with a version of Forte that was based on Java instead of TOOL named synerJ and was also referred to as "Forté for Java". As with the original TOOL-based products this consisted of a development IDE, a code repository, and a runtime environment. This new java product was of interest to Sun Microsystems who bought out the company. The TOOL-based listed above were bundled together and re-branded as Unified Development Server (UDS) and Integration Server (IS) under the IPlanet division. The server modules were later bundled together as Enterprise Application Integration (EAI).

Sun declared the product's end-of-life, indicating no future plans to continue development of the product. Sun's official support of Forte ended in April, 2009.

Being an enterprise application development system, Forté 4GL supported close linkage to a number of different relational database systems, including Oracle, Sybase, Microsoft SQL Server, Informix, and DB2. These linkages could be via SQL embedded within the TOOL code, or via SQL constructed on the fly.

It also had support for distributed applications: the developer would create an instance of a specific class, which would be placed on a user-specified server. Calls to methods through instance would be sent across the network transparently; the developer would not need to know the underlying details of how the call would be transmitted.


...
Wikipedia

...