Skip to main content

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
Mike,
A succesful remote processing environment our clients use is a combination of acuthin, terminal server(or citrix) and any acuconnect supported server(like linux, unix, windows, etc). The terminal server speeds up remote client access and the acuthin speeds up the terminal server sessions because acuconnect launches the runtime on a seperate application server. This is all a very scalable n-tier solution and you can throw more terminal servers into the mix when needed. So you could describle the n-tier as client, communication server, application server.

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
One thing to know about thin client, apart of the difference between a modem connection and a broadband connection is that it pays off to have a designated ip address for the server, e.g. not a dynamic one. I have experienced significant performance differences between dynamic ip and static ip at various installations.

If all you want to have remote is your application, putting Windows Terminal Server and possibly Citrix on the server is a waste. In particular as the latter would require purchase of a Windows Server of some kind, let alone with Acuconnect, your server doesn't have to be Windows.

As for an opportunity to have some of our guys talk technical details with your possible customer, I am sure we can work something out, but I would advise you to contact your account manager at Acucorp for this.

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
As Gisle said, for simple connections to the application just acuthin should work and terminal server would be a waste. But, we have found, through real world trial and error experiences, that on a larger scale terminal server stabalizes things.

Here are some important benefits our larger clients get using the terminal server/acuthin solution:

1.) Terminal server sessions require less bandwidth than acuthin for acceptable performance. This is based on feedback from our clients and with the dealer base of Southware Innovations, a large Acucorp reseller. This can be a cost savings.
2.) Terminal server sessions are more stable. They are more resilient to data corruption across the internet than acuthin. Acuthin can be very sensative to any corupt message information going back and forth to acuconnect and application crashes can occur. This is no joking matter when imortant application data can be affected by a hung acuthin session or when file locks get stuck and other application users are locked out during a busy work day. As you probably know, clients can get very, very angry when this happens.
3.) Terminal sesssions add more security. They provide an extra layer of abstraction from the application and can be encrypted. Add acuthin's own security to this and and you've got very strong multi-layered security.
4.) Remote management. Terminal server/citrix remote management tools are excellent. This is less important in a small company, but if your client is a large company, as you have mentioned, then these administration tools are invaluable.
5.) Centralize applications. If your client depends heavily on windows office automation software like ms office, then these products can all be installed on the terminal servers which centralizes management and document storage for these products.

The negative to this setup is initial cost. But, you must compare that to the value of the benfetis I listed above. You can save money by using linux on the application(acuconnect) server. This will save on windows client licenses.

For instance, we have a client who was absolutely determined to use a linux server with acuconnect and connect remotely with acuthin. We thought this would work fine, but when we set it up, they had problems immediately with speed and with application crashes. Their networking consultant suggested they try adding a terminal server temporarily, and when they did the speed was much better and the crashes reduced drastically. So, they now have a terminal server and linux server running side by side communicating through acuthin and accuconect and they connect remotely via the internet to the terminal server with the terminal server client software. Yes, adding the terminal server cost them more money, but they are more stable now, so it was a worthy investment.

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
Thanks Dan, for an extensive and informative message. Appreciate it.
I recognize some of the issues you mention here, but I would like to emphasize that we also have successful installations with unix servers that do not require fronting. I have one case here in Norway in which as you tell, they experienced problems with performance. But getting set up with a static ip resolved that issue.
Nevertheless, for scaleability and security, Terminalserver does add value.

You coming to the conference?

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
Gisle, I guess no two acuthin installs are exactly alike! ;-) But, I guess a good approach, if there is time, is to try acuthin direct to the server first, and if things are too unstable a terminal server could possibly help.
I'll definately be at the developer conference. Looking forward to all the new goodies in 6.2! Hopefully, I get the beta soon.

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
Thanks to both of you for your posts. I am meeting with my client and their network team next week to do some testing. I have evaluation copies of AcuConnect and AcuGt runtime (10 users). After reading your responses, do I need an eval of the AcuThin product as well?

Please excuse my ignorance but let me ask if I have this right. They have a server running Windows terminal server. They also have an application server. I would load AcuGt and AcuConnect on the application server? Does AcuThin need to be loaded on the remote workstation? Does AcuGt runtime need to be on the remote workstation? Vision files containing the application data will reside on the application server. Thanks again for your excellent guidance,
Mike Skeen

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
Originally posted by Mike_Skeen
After reading your responses, do I need an eval of the AcuThin product as well?

No, AcuThin is available for free. You can get it off an Acucobol install CD or even download from the Acucorp website.

Originally posted by Mike_Skeen
I would load AcuGt and AcuConnect on the application server?

Correct. The application server will run the aucobol programs and so will need the runtime and AcuConnect(acurcl).

Originally posted by Mike_Skeen
Does AcuThin need to be loaded on the remote workstation?

No, the remote workstations would only run the terminal server thin client to connect to the terminal server. The AcuThin thin client would be installed on the Terminal Server and have a desktop shortcut that can be shared by remote workstations. Your clients terminal server admin should know how to do this. Think of it as a thin-client running inside of a thin-client. In this case, the acuthin thin-client runs inside of the terminal server thin-client.

Originally posted by Mike_Skeen
Does AcuGt runtime need to be on the remote workstation?

No. This is because the remote workstation only needs the terminal server client to connect to the terminal server which will have the acuthin thin-client installed on it. When the acuthin thin-client runs it will communicate to AcuConnect on the application server and AcuConnect will then execute the runtime on the application server which will process your acucobol programs and vision data and return the results to the acutthin thin-client which has it's display sent back to the remote workstations by the terminal server thin client. Hope that wasn't too confusing. ;-)

Originally posted by Mike_Skeen
Thanks again for your excellent guidance.

Feel free to contact me at 845-534-7100 if that would help.

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
I had my visit with the prospective client yesterday. After installing AcuConnect and reading some of the documentation I sensed I would not be able to configure the product without first doing some careful reading to get a better understanding of how it is done. I loaded the runtime and my application on their application server on a mapped drive. We then drove to a office close by which was connected by a T1 line, the application seemed to run very well under Windows Terminal Server without AcuConnect. They were satisfied with the performance (dragged a little on list boxes). Their question is why do they need AcuConnect and what will it add to ability they have with terminal services. Thanks again.

[Migrated content. Thread originally posted on 09 July 2004]

I market an application (Construction Accounting) written in AcuGt. (also the author of the application software). I have a potential client who would be a real prize for me but I need some technical assistance. This is a large company with remote locations and that is where I need some help. My application has traditionally run on a pc network (win 2003, nt, etc) AcuRuntime, programs, and data files reside on the mapped drive. I use the Vision file structure. I have on occasion used AcuServer as well. How is the best way to approach the remote processing. I tried AcuThin on a test basis but found it slow (could have been how I configured it, my application,??) How does that compare with Citrix, Windows terminal server? They are currently using an AS400 with a pc server hooked up somehow and do remote processing with their current application software(GEAC) I would appreciate any ideas or guidance. If anyone from AcuCorp reads this, would it be possible for a systems engineer to talk "tech" with their IT people concerning this. Thanks,
We tell clients that Acuconnect and Acuthin allow for a more distributed and scalable system for the application. Since Acuthin requires less memory and processing resources than the windows runtime, it puts less stress on the Terminal Servers, which allows you to run more users per Terminal Server. Also, we've found it speeds up performance on the local area network because large chunks of vision data and programs are no longer being passed back to the terminal server by the application(file) server. Instead, mostly messages are being sent back and forth which lessens the stress on the network. Even the application(file) server is benefited by not having to allocate possibly thousands of file and record buffers, and lock handles, etc, and passing this data back to the terminal server(s) when many users are connecting to vision files across the network using the windows runtime. That kind of traffic can really bog down a network card on an application(file) server. Using Acuconnect reduces this strain.
These improvements in resource distribution definately help the scaleability of the whole system. These issues are not so important for terminal server systems supporting less than 25 or 30 users, but above that it can start to make a difference. You can also compenstate by using bigger, beefier servers.
Terms & ConditionsAccessibility statement