Novell Documentation: ZENworks 6.5 - NAL Cache Structure and Content

NAL Cache Structure and Content

By default, the NAL cache directory is created as a hidden \nalcache directory at the root of the drive, as shown in the following example.

When an application is associated with the user or workstation, Application Launcher creates a directory for the application under the \nalcache directory. The application's directory is named the same as the Application object's eDirectory distinguished name (for example, Simple App.applications.novell) and contains the files that make up the launch cache and install cache. These two caches are described in the following sections:

Launch Cache

The files in an application's launch cache contain the information Application Launcher needs to launch, run, and uninstall the application. Application Launcher automatically creates the application's launch cache when the application is distributed to the workstation. If Application Launcher has not yet distributed the application to the workstation, the launch cache contains only the information needed to display the application's icon on the workstation's desktop.

The launch cache files are located directly under the application directory (nalcache\edirectory_tree\app_object directory). The following table describes the launch cache files. Depending on the Application object's settings, some of the files might not be necessary, in which case they are not included in the launch cache.

File	Description
complete.bin	Contains the Application object's complete eDirectory name. If this file does not exist, Application Launcher assumes that the cache is bad and recreates the cache.
dsattr.bin	Contains all of the Application object's eDirectory attributes.
delta.bin	Flags the cache as a delta cache. This means the cache contains only the information required by Application Launcher to display the application's icon on the desktop, and exists only if Application Launcher has not yet distributed the application to the workstation. After Application Launcher distributes the application, it removes this file.
files.bin	Contains the file vitals for the cache files.
folders.bin	Contains the list of Application Launcher window folders and Start menu folders where the Application object displays.
strm1.bin	Contains the Application object's icon.
strm2.bin	Contains all text file modifications.
strm3.bin¹	Contains all files to be copied to the workstation.
strm4.bin¹	Contains registry modifications that are made during initial distribution.
strm5.bin¹	Contains INI modifications that are made during initial distribution.
strm6.bin¹	Contains shortcut modifications that are made during initial distribution.
strm7.bin	Contains macro information.
strm8.bin	Contains schedule information.
strm9.bin	Contains system requirements information.
strm10.bin	Contains Administrator notes.
strm11.bin	Contains the shutdown script.
strm12.bin	Contains the startup script.
strm13.bin¹	Contains registry modifications to be made each time the application is launched.
strm14.bin¹	Contains INI modifications to be made each time the application is launched.
strm15.bin¹	Contains files to be copied to the workstation each time the application is launched.
strm16.bin	Contains text file modifications to be made each time the application is launched.
strm17.bin¹	Contains icons to be modified each time the application is launched.
strm18.bin	Contains environment variable settings to be made.
strm19.bin	Contains the pre-distribution script.
strm20.bin	Contains the post-distribution script.
strm21.bin	Contains the pre-install schedule information.

¹ All files except those containing application files, INI settings, shortcut icons, and registry settings are refreshed each time Application Launcher performs a timed or manual refresh. The non-refreshed files remain the same until the version number (Application object > Distribution Options tab > Options page) is changed. This allows Application Launcher to successfully uninstall the application (including the files, INI settings, shortcuts, and registry settings) if necessary.

Install Cache

The install cache contains the application source files needed to install or verify (fix) the application. Application Launcher creates an install cache for an application in the following two situations:

The application is marked as Force Cache. Application Launcher retains the install cache for a Force Cache application as long as the application is associated with the user or workstation.
The application is not marked as Force Cache, but Application Launcher is running in Remote Mode and the application is launched. In this case, Application Launcher first copies the application to the install cache and then distributes it (which populates the launch cache). After the application is launched, Application Launcher removes its install cache.

The install cache is created in the nalcache\edirectory_tree\app_object\install directory.

Although the files in the install cache are compressed, they can still require a large amount of disk space on the workstation's local drive, so an application should only be cached if users need to install or verify the application while disconnected from eDirectory.

An application can still run in disconnected mode without being cached to the install cache. To run in disconnected mode, an application needs only to be distributed (installed) on the workstation. Caching an application to the install cache only enables the application to be installed or verified (fixed) while in disconnected mode.