A Guide to Using Acucorp's Thin Client Technology Version 5.2

Table of Contents

1 Introduction
1.1 Overview 1.2 Platform Support 1.3 How It Works 1.4 Licensing 1.5 Security 1.6 Working With Other Acucorp Technologies 2 Preparing Your Application and Data for Thin Client Operation
2.1 Preparing Your Application 2.1 Preparing Your Application 2.1.1 When User Interface Work Is Necessary 2.1.2 When Other Application Work Is Necessary 2.2 Preparing Data 2.2 Preparing Data 3 Preparing the Server for Thin Client Operation
3.1 Preparing the Server 3.2 Installing Server Software Components 3.2 Installing Server Software Components 3.2.1 Server Components Required 3.2.2 Installing AcuLaunch 3.2.2 Installing AcuLaunch To install AcuLaunch on a UNIX server To install AcuLaunch on a Windows NT or Windows 2000 server 3.2.3 Installing the ACUCOBOL-GT Runtime 3.2.3 Installing the ACUCOBOL-GT Runtime 3.3 Configuring the Server 3.3 Configuring the Server 3.3.1 Configuring the Remote Application Runtime 3.3.1 Configuring the Remote Application Runtime ENCRYPTION_SEED THIN_CLIENT_ENCRYPT 3.3.2 Assigning Values to Server Configuration Variables 3.3.2 Assigning Values to Server Configuration Variables ACCESS_FILE ACURCL_PORT DEFAULT_USER FILE_TRACE FILE_TRACE_FLUSH NT_SECURITY PASSWORD_ATTEMPTS PROVIDE_PASSWORD_MESSAGES SERVER_ALIAS_FILE SERVER_IP and SERVER_NAME SERVER_RUNTIME TEXT_nnn 3.3.3 Creating a Server Alias File 3.3.3 Creating a Server Alias File Adding an alias Removing an alias Modifying an alias Displaying aliases 3.3.4 Modifying the Server Access File 3.3.4 Modifying the Server Access File Access record composition Adding access records Deleting access records Modifying access records Displaying an access record Exiting the access file manager 3.3.5 Assigning Ownerships and Permissions 3.3.5 Assigning Ownerships and Permissions UNIX ownerships and permissions on AcuLaunch files Ownerships and permissions on new files or processes umask 3.4 Starting AcuLaunch 3.4 Starting AcuLaunch To start acurcl on a UNIX server To start acurcl on a Windows NT or Windows 2000 server To start acurcl at system startup 3.5 Testing Your AcuLaunch Connection 3.5 Testing Your AcuLaunch Connection 3.6 Launching Thin Client Applications from a Web Page 3.6 Launching Thin Client Applications from a Web Page 3.6.1 Thin Client Command Line Files 3.6.2 Using Anchor Tags 4 Preparing the Client(s) for Thin Client Operation
4.1 Preparing the Client 4.2 Installing Client Software Components 4.2 Installing Client Software Components 4.2.1 Client Components Required 4.2.2 Installing the ACUCOBOL-GT Thin Client 4.2.3 Installing ActiveX Files 4.3 Launching Remote Programs From the Client 4.3 Launching Remote Programs From the Client 4.3.1 The acuthin Command 4.3.2 AcuLaunch Connection Logic 4.4 Launching Programs on the Internet 4.4 Launching Programs on the Internet 5 Managing the System
5.1 System Management 5.2 Security 5.2 Security 5.2.1 Maintaining the AcuAccess File 5.2.2 Passwords 5.3 Dynamic Configuration 5.3 Dynamic Configuration 5.4 Status Reports 5.4 Status Reports 5.5 Troubleshooting 5.5 Troubleshooting 5.5.1 Tuning System Performance 5.5.2 Frequently Asked Questions 5.5.3 Contacting Technical Support A The acurcl Command
A.1 acurcl Command A.1 acurcl Command acurcl -access acurcl -alias acurcl -config acurcl -info acurcl -install acurcl -kill acurcl -query acurcl -remove acurcl -start acurcl -version Glossary of Terms
Glossary of Terms

Acucorp, Acucobol, AcuBench, AcuConnect, AcuLaunch, AcuServer, AcuSQL, Acu4GL, and extend are trademarks of Acucorp, Inc. AcuODBC is a registered trademark of Acucorp, Inc. Acu4GL is protected by U.S. patent no. 5,640,550. Other brand and product names are trademarks or registered trademarks of their holders.