If you want users to be able to launch remote applications from their local machine, you can use our remote application server, AcuConnect, to accomplish your goal. Reasons for this may be that the application itself is revised frequently or the application is processing-intensive.
With AcuConnect, users or programs on client machines can launch applications on server machines, whether those servers are part of a local area network, wide area network, or global Internet. Some portions of your application can continue to run on the client while the resource-intensive portions run on the server, or all but the user interface can run on the server, in a thin client configuration.
In Using the Thin Client to Launch Web Applications, we described how to launch a thin client from a Web page or over the Internet from the command line. But you can also use AcuConnect with the standard ACUCOBOL-GT runtime to distribute your application resources between the client and one or more servers on the Internet. Exactly how much processing is performed on the client and how much on the server is up to you.
AcuConnect also provides users access to remote Vision data. If the data is on the same remote server as AcuConnect, data is considered local and no special software is required. If the data is on a third data server, AcuConnect can work in tandem with AcuServer to provide seamless data access. AcuConnect can also work with Acu4GL, our COBOL-to-RDBMS bridge, to provide access to relational data wherever it resides.
The following figures show AcuConnect in two-tier and three-tier environments. In a two-tier environment, applications and data are stored on the same remote server as follows:
In a three-tier configuration, the data files reside on a different server than the application. Sites may do this for security purposes or because this may make for more efficient use of system resources. When the applications and data are on different servers, the data files are considered remote, and AcuServer is required.
Consider using AcuConnect when your program is I/O-intensive or if you have reason to believe that the program will be updated frequently. You can determine how much reprogramming you want to do to facilitate remote application access for your users – either by embedding COBOL calls into your program or dividing it into client and server components. Your users do not require a Web browser for remote application access.