Application directories can contain Master Files, Access Files, FOCEXECs, StyleSheets, HTML files, and other types of files.

The following guidelines can be followed to set the Application Path (APP PATH).

• Add Application Directories that are common to all users to the server profile, edasprof.prf.
• Create Access Control Templates (ACL) to support domain-specific Application Directories. The rules defined by the ACL on the model Application Directory will be dynamically applied at run time.

• Set the APP PATH on the Server Properties of the Domain folder if there is not a consistent pattern between the Domain folders and Application Directories for which the ACL could not be used.

  Note: Application Directory baseapp is always implicitly included in the WebFOCUS application path so contents are available to all users. It is recommended, at the minimum, that you restrict Write access to the baseapp Application Directory using Access Control Rules or delete the baseapp directory.

Using One-Part and Two-Part File Names

• When referencing files on the Reporting Server, it is best to use two-part file names to avoid file conflicts with files of the same name, but residing in different Application Directories.
• Be consistent with the use of one-part file names or two-part file names. If you have elected to use one-part file names, use them consistently throughout applications. This is another reason for using a prefix on a file name.
• If you have elected to use two-part file names, use them consistently throughout applications.
• In Release 8.1.x and higher, InfoAssist has two-part file names enabled, by default. This is configurable from the WebFOCUS Administration Console/Utilities/InfoAssist Properties.