Startup Script or Batch Files

The next technique for setting APPX-related environment variables is to do so directly in the script or batch file invoked by system users to start APPX, or invoked by the system to start appxd.

Benefits

• If the site already maintains a script or batch file to start APPX, this may be convenient
• Like appx.env, this does not require reboots or system logout/logins for changes to take effect, just exiting and re-entering APPX
• Already present in the start-appxd.sh file for client/server installations
• Only affects APPX/Client users if placed in the appxd start up script (Unix only)
• When placed in the appxd startup file, all variables can be placed in one file

Disadvantages

• If you do not already have an APPX startup script or batch file for some other site-specific purpose, you probably do not want to add one; it is another file to maintain and remember the purpose of
• Does not offer anything beyond appx.env’s functionality, if you are not already doing other things in an APPX startup script that need scripting or batch file programming capabilities
• If someone ever runs APPX by invoking APPX.EXE directly, the script’s variable settings will not be executed
• Only affects non-APPX/Client users
• When placed in the start-appxd.sh file, site administrators should be careful to back up this file prior to an APPX upgrade in case a new version includes an updated template start-appxd.sh file