Overview:

Installation and Configuration

Install APPX/Client on Client PC.

Install APPX/Server for Unix ("appxd")

Get a Product Registration for APX / GCS.

1. Check for presence of APPX/Server components.

1. There are two components to APPX/Server: the 'appxd' daemon, and the 'start-appxd.sh' shell script. The script is used to invoke the 'appxd' daemon. Both components reside in the 'tools' directory ($APPXPATH/../tools/).

   The "root" user must run 'start-appxd.sh'. It launches the appxd daemon that then runs in background, waiting for APPX/Clients to start up. When new APPX/Clients link up with appxd, they spawn new APPX/Server sessions, one per client.

1. 'appxd' must be owned by root, and have its 's' bit set.

1. 
   These may be accomplished by:

1. Modify 'start-appxd.sh' to specify the correct APPXPATH.

1. In 'start-appxd.sh', you will find a statement ...

1. Set your TCP/IP Socket Port to assign to the Application Server

1. You will find the statement ...

1. Point APPX_SERVER to the desired APPX Engine.

Make sure the APPX_SERVER appx engine actually exists at the path indicated in the last step.

1. Launch 'start-appxd.sh', as 'root' user.

1. You must launch 'start-appxd.sh' as the root user, either from the Unix command line or through some operating system facility such as 'inittab'.

   To see your presentation server(s) running in background, execute the command:

   ... or ...

Install APPX/Server for Windows ("WinAppxD")

1. Get a Product Registration for APX / GCS.

1. (Note: only required for releases prior to APPX 4.1.a)
   

   The GCS (GUI Client/Server) Product Registration is a lower level registration to your main APPX Registration. Product Registrations are editable from the APPX Main Menu via 3) System Administration, 1) System Setup, 1) System Registration. Then press ENTER to edit your Product Registrations.

   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).

1. Check for presence of required Windows NT Resource Kit components.

1. 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.

   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 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.

1. Create an NT user account to run the WinAppxD service

1. 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.

   If installing APPX on a Windows NT Workstation computer, and your LAN's logins are normally validated against a PDC, and that NT Workstation computer is a member of a domain, go to your PDC and create the account using User Manager for Domains. (Don't just create it locally on the server. Unless you have the domain user management tools from the \CLIENTS\SRVTOOLS directory on the NT Server CD-ROM installed on the NT Workstation machine, which you probably do not, you can't create a domain account from your NT Workstation).

   If installing APPX on a Windows NT Server computer that you installed as NOT being part of a domain, and your LAN does not have a domain to join (possibly because this is just your test "play" system and NT has not been rolled out yet), use the User Manager application on the NT Server computer to add the user.

   What to do next depends on how your organization's NT network is set up. If in doubt about NT network issues, check with your site's NT administrator to find out whether the following applies to you.

   If the organization's network includes a 'Primary Domain Controller' and an NT domain, but the server you are installing APPX on is a 'member server' of the domain, NOT a Primary or Backup Domain Controller, you must perform the following extra steps:

   The steps below describe how to do this on an NT Server computer. NT Workstation has a slightly different user interface, so the instructions below can't be followed "click by click" if you're installing on NT Workstation.

   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.

1. Assign WinAppxD User Rights

1. You are ready to add required Advanced User Rights to the WinAppxD User:

1. Give Users Local Logon rights

1. While 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.

1. Install the WinAppxD service

1. 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.

1. Set application path for WinAppxD service

1. Assign WinAppxD to an NT User

1. Install and configure APPX License Server

1. Repeat 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.)

1. Set APPX environment variables

1. Using the System applet in the Control Panel, add the following variables to the environment:

   APPX_SERVER=c:\appx\appx.exe
   APPXPATH=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.

1. Set desktop heap size to 512 for non-interactive processes

1. Follow the instructions in the Microsoft Knowledge Base articlehttp://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).

1. Reboot and enter registration data

1. Reboot the machine, and enter your registration 'c:\appx\appx.exe

1. Start a license server and run APPX

1. Start 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.

1. Reboot

1. Reboot 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".

Invoke APPX/Client from Client PC.

Create Multiple APPX/Servers.

NOTES:

The Default Keymap shipped with APPX/Client follows. We expect to be able to edit the default keymap in a future release.