Difference: APPXClientServer (4 vs. 5)

Revision 52012-02-20 - ChrisBrower

Line: 1 to 1
 
META TOPICPARENT name="TheAPPXClient"

APPX Client/Server Installation and Configuration

Line: 80 to 80
 Typically this is ...

  • APPX_SERVER=$APPXPATH/../appx
Changed:
<
<
Make sure the APPX_SERVER appx engine actually exists at the path indicated in the last step.
>
>

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

Make sure the APPX_SERVER appx engine is actually an engine, and not a script that then executes an APPX engine.

Permissions on the APPX_SERVER appx engine should be 755 with the 's' bit set, and should be owned by the user 'appx'. You can do this by:

  • chown appx appx
  • chmod 755 appx
  • chmod u+s appx
The permissions on the directory containing the 'appx' engine should also be 755. You can do this by cd'ing to that directory and using:

  • chmod 755

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

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:

ps -ef | grep s=

or

ps -aux | grep s=


Install APPX/Server for Windows ("WinAppxD")

Get a Product Registration for APX / GCS

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

Check for presence of required Windows NT Resource Kit components

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.

Create an NT user account to run the WinAppxD service (first-time installations)

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.

  • From the 'Users' menu, open the 'Select Domain' dialog.
  • In the 'Domain' box, type the name of the machine on which you are installing WinAppxD. (Yes, that is counter-intuitive. However, it is necessary).
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.

Assign WinAppxD User Rights

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback