Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Added: | ||||||||
> > | Using the System applet in the Control Panel <--, add the following variables to the environment:WYSIWYG content - do not remove this comment, and never use this identical text in your topics--> | |||||||
APPX Client/Server Installation and Configuration
| ||||||||
Line: 11 to 12 | ||||||||
APPX Application Server processes are identical to locally invoked copies of APPX, except that the APPX/Client at the other end of the TCP/IP connection handles keyboard screen and mouse operations. Also, facility is provided to run processes on the remote Client. | ||||||||
Changed: | ||||||||
< < | In addition to APPX/Client, APPX/Server can also service APPX/Net Clients. APPX/NET allows APPX Applications running on remote platforms (Windows or Unix) to access APPX data on local platforms (including data accessible locally via APPX/RDMS back end connections). | |||||||
> > | In addition to APPX/Client, APPX/Server can also service APPX/Net Clients. APPX/NET allows APPX Applications running on remote platforms (Windows or Unix) to access APPX data on local platforms (including data accessible locally via APPX/RDMS back end connections). | |||||||
Thus, APPX/Server can service both thin APPX/Clients and APPX/NET Client processes on remote processors. APPX/Server runs on all APPX platforms except VMS. | ||||||||
Line: 33 to 34 | ||||||||
If you don't have a copy of appx.exe readily available, you can download it: | ||||||||
Changed: | ||||||||
< < | From here for APPX Release 3.5 or | |||||||
> > | From here for APPX Release 3.5 or | |||||||
Changed: | ||||||||
< < | From here for APPX Release 4.x | |||||||
> > | From here for APPX Release 4.x | |||||||
(The Windows Client is ~1.6 meg.) | ||||||||
Line: 116 to 117 | ||||||||
To request a GCS Product Registration if you're running a release prior to APPX 4.1.a, send an email to Tech Support ( techsupp@appx.com).
Check for presence of required Windows NT Resource Kit components | ||||||||
Changed: | ||||||||
< < | Some files from the Microsoft WinNT Resource Kit are required to run the APPX/Server on Windows NT. The Resource Kit includes a utility that allows WinNT users to convert most desktop applications into a SERVICE application. This means that you can run an application behind the scenes i.e. it doesn't depend on a specific user to log on. SERVICE applications re-activate themselves after NT PCs loose power and re-boot themselves. | |||||||
> > | Some files from the Microsoft WinNT Resource Kit are required to run the APPX/Server on Windows NT. The Resource Kit includes a utility that allows WinNT users to convert most desktop applications into a SERVICE application. This means that you can run an application behind the scenes i.e. it doesn't depend on a specific user to log on. SERVICE applications re-activate themselves after NT PCs loose power and re-boot themselves. | |||||||
Changed: | ||||||||
< < | If you have already installed the WinNT Resource Kit, you should see three files in your server's \SRVANY directory: SRVANY.EXE, INSTSRV.EXE and SRVANY.WRI. | |||||||
> > | If you have already installed the WinNT Resource Kit, you should see three files in your server's \SRVANY directory: SRVANY.EXE, INSTSRV.EXE and SRVANY.WRI. | |||||||
Changed: | ||||||||
< < | If the directory and/or files don't exist, install them now using the instructions provided with the Resource Kit. Create a directory in the root called "\SRVANY", then copySRVANY.EXE and INSTSRV.EXE into it. (The Resource Kit must be purchased from Microsoft. It is not obtainable on-line. If you subscribe to Microsoft's TechNet, you may already have the Resource Kit on one of those CD's. Otherwise, obtain it directly from Microsoft or a bookstore. Be sure to get the Resource Kit version that matches the version of NT that you are running.) | |||||||
> > | If the directory and/or files don't exist, install them now using the instructions provided with the Resource Kit. Create a directory in the root called "\SRVANY", then copySRVANY.EXE and INSTSRV.EXE into it. (The Resource Kit must be purchased from Microsoft. It is not obtainable on-line. If you subscribe to Microsoft's TechNet, you may already have the Resource Kit on one of those CD's. Otherwise, obtain it directly from Microsoft or a bookstore. Be sure to get the Resource Kit version that matches the version of NT that you are running.) | |||||||
Be sure not to delete SRVANY.EXE as long as you want to use APPX/Server. Winappxd.exe is started by SRVANY.EXE, and if SRVANY isn't there, it can't start. | ||||||||
Changed: | ||||||||
< < | Create an NT user account to run the WinAppxD service (first-time installations) | |||||||
> > | Create an NT user account to run the WinAppxD service (first-time installations) | |||||||
Changed: | ||||||||
< < | Create the NT user account that will be used to run WinAppxD. You can name it anything you like. Place this account into the Administrators group. | |||||||
> > | Create the NT user account that will be used to run WinAppxD. You can name it anything you like. Place this account into the Administrators group. | |||||||
Use your normal net account-creation process. This usually involves invoking NT's User Manager or User Manager for Domains. | ||||||||
Line: 142 to 143 | ||||||||
Note: To perform this next step you MUST be physically seated in front of your APPX Server machine, and be typing on its keyboard, using its mouse. Performing this step from a PDC or BDC if your APPX server is not a PDC or BDC, is guaranteed not to work. Performing this step from another random server or workstation on your network, rather than the APPX server, is also guaranteed not to work.
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
The extra steps are necessary if you're running on a 'member server' or NT Workstation because User Rights must be set on a per-machine basis. If you add the rights on the PDC or BDC, they will not be in effect for any member servers or NT Workstation computers, just for the PDC and BDC. This is an NT security feature. If you are installing APPX on a PDC or BDC, then all you have to do is go to the 'Users' menu, choose 'Select Domain', and make sure that the domain of which that machine is a PDC or BDC, is selected. | ||||||||
Changed: | ||||||||
< < | Assign WinAppxD User Rights | |||||||
> > | Assign WinAppxD User RightsYou are ready to add required Advanced User Rights to the WinAppxD User:
Give Users Local Logon rightsWhile in User Administration, add the "Logon Locally" right to any NT User ID which will access APPX. This is not normally on by default. If you do not add it, the Windows and Java GUI clients will not be able to successfully start up and interact with an APPX session.Install the WinAppxD service (first-time installations)From the DOS Command prompt, navigate to the \SRVANY Directory. Type: INSTSRV WinAppxD c:\srvany\srvany.exe Notice the second element on the command line "WinAppxD". This is the "name" of the service that you will create. Later, you will go to the SERVICE applet in the CONTROL PANEL and will access the service by this name. If everything went well, you should see a message stating that the requested service has been added. If you do not get this message, review everything that you did so far. Make sure that the SRVANY.EXE and the INSTSRV.EXE are in the directory that you specify.Set application path for WinAppxD service (first-time installations)
Assign WinAppxD to an NT User (first-time installations)
Install and configure APPX License ServerRepeat the Service install steps 5 - 7 again for the license server. Call the service 'AppxLicSrv' instead of WinAppxD. If your appx.exe engine resides at C:\appx\appx.exe, then the Application value registry setting in step 5.7 will be c:\appx\appx.exe -l=c:\appx\log. (This tells APPX to store the server log in the APPX engine location.) You can use the same NT User Account created to run WinAppxD; there's no need to create another one. (Substitute the proper paths to your APPX executable and log file here.)Set APPX environment variablesUsing the System applet in the Control Panel, add the following variables to the environment: APPX_SERVER=c:\appx\appx.exeAPPXPATH=c:\appx\data APPX_KEYMAP=WINDOWS APPX_NET_LOG=C:\WinAppxD.log APPX_NET_LOG_MASK=0xFFFFFFFF Be sure to set these in the global System section, so that they will be in effect for every user, not just in the "User" section. To set an NT System environment variable, go to: Start, Settings, Control Panel, System, Environment Tab. You'll see System variables at the top of the scrolling list, User variables at the bottom. Click on one of the existing System variables. It will display down below in the variable/value editable fields. Overtype the existing variable name with your desired variable. Fill in the desired value in the value field. The new System variable/value should show up at the top of the System/User variables list, without deleting or changing the variable from which you cloned it. Set desktop heap size to 512 for non-interactive processesFollow the instructions in the Microsoft Knowledge Base article http://support.microsoft.com/support/kb/articles/Q142/6/76.asp to decrease the desktop heap size in the registry. If this is not done, you are likely to receive USER32.DLL errors when running external programs from APPX (including winprint.exe, which is used for printing APPX output). Reboot and enter registration dataReboot the machine, and enter your registration 'c:\appx\appx.exeStart a license server and run APPXStart a License Server "c:\appx\appx -l=c:\appx\log". Then start appx "c:\appx\appx.exe" to create System Administration file and add users. Make sure you add a user whose 'System ID' matches the name of the NT user account you're using to run the License Server, so that the license server you add as a service will be able to start.RebootReboot the system again and you should be ready to run. You can test your setup by shutting down the machine properly and re-booting. WinAppxD will be active before you even log on. Try to access the WinAppxD Server now from the same or another machine by running "appx.exe -c". If you run into problems, check out the WinAppxD FAQ. It includes answers frequently asked questions about installing and running APPX/Server on Windows NT. The APPX_NET_LOG set up above is used to monitor APPX/Server traffic, for debugging. Once you have APPX/Server working with APPX/Client, you should either remove the APPX_NET_LOG environment variables, or set APPX_NET_LOG_MASK=0x00000000 so you can just change the mask back if you ever need to do any debugging. APPX_NET_LOG can take quite a bit of disk space over time. See the WinAppxD FAQ , Section 6 (Troubleshooting), for more information on the use of the APPX_NET_LOG.Invoke APPX/Client from Client PC.
Create Multiple APPX/Servers.Once you have your base APPX/Server working, we recommend setting up multiple APPX/Servers. It's possible (though rare) for IP ports to get hung at the Network or O/S level. If you have fallback Server ports standing by (ex: 8061, 8062, ...), you can avoid having to reboot your Server to clear the port. To set up additional APPX/Servers, follow the "Install APPX/Server" instructions above, substituting other port numbers for 8060. For Windows APPX/Servers, you don't necessarily need to have different copies of WinAppxD.exe, but when you add the services, you must use different names, i.e.: INSTSRV WinAppxD1 c:\srvany\srvany.exeINSTSRV WinAppxD2 c:\srvany\srvany.exe When you enter the information in the registry, they will all point to the same .EXE file, but have different port numbers on the command line. There can be advantages to using renamed copies of WinAppxD. Different executable names allow you to differentiate APPX/Servers within your Windows Task Manager. Services can also start Batch files, which can be used to start WinAppxD with different ports and environment variables. You can use this to set up a port with APPX_NET_LOG debugging, or to run different APPX versions on different APPX/Server Ports. Note that you will have a CMD.EXE sitting in your NT task list until the task it started completes. A sample batch file to run an APPX/Server might be: SET APPX_SERVER=C:\appx\appx413\appx.exe SET APPXPATH=C:\appx\appx413\data SET APPX_KEYMAP=windows SET APPX_NET_LOG=C:\appx\appx413\net.log SET APPX_NET_LOG_MASK=0xFFFFFFFF C:\appx\appx413\tools\winappxd.exe -s=8413 This batch file would run an APPX instance in the C:\appx\appx413 directory tree, with APPX_NET_LOGing turned on. The directory and name of a batch file such this would be entered into the registry, in place of the "c:\appx\tools\WinAppxD.exe -s=8060" described in "7. Set application path for WinAppxD service" above. If you use a firewall, remember to punch holes in it for the ports you turn on. NOTES:The presence of Unix APPX/Server running in background may be detected via the command ...
The presence of Unix APPX/Server sessions (one per APPX/Client) may be detected via the command ...
Early versions of APPX/Client do not remember the prior settings for UserID, Password, RemoteHost IP Address, or ServerPort values for the prior session of APPX/Client, when logging in to subsequent sessions of APPX/Server. "Save as Default" will be implemented in future APPX/Client releases. Running "appx -c /login" will force the login dialog box under Windows 95 and NT, allowing override of the defaults pulled from the Windows installation files. Your choice of Windows Control-Panel Colors can significantly affect the "looks" of APPX/Client. If for example you specify (in Windows) that foreground text is 'White', then editable fields in APPX will display as White on White, and be unreadable. We expect enhancements to color-selection in future releases of APPX/Client. The Default Keymap shipped with APPX/Client follows. We expect to be able to edit the default keymap in a future release. esc=GO
f1=help
f2=scan
f3=select
f4=prev image
f5=next record
f6=pan
f7=scroll
f8=end
f9-12=Add/Delete/Inquire/Change
PageUp=Previous Screen
PageDown=Next Screen
`=Option
0-9=Numeric Digits
HOME=Home. Not currently mapped.
END=Vertical Tab. Not currently mapped. |