To use AcuConnect, your application needs to contain both client and server components. If it does not already have these two components, you have two choices: 1) you can write a simple COBOL program for the client that CALLs your existing application on the server; or 2) you can divide your existing application into two.
For performance reasons, we recommend that your client application contain the user interface portion of the program and all of the interactive components. The server application, on the other hand, should be reserved for batch processing components -- components that do not require user interaction.
Exactly how much processing is performed on the client and how much on the server is totally up to you. The AcuConnect User's Guide provides some guidelines for designing a thin client, a fat client, and a medium client.