Copyright: Copyright © 1995 Novell, Inc.


Add the NetWare Application Launcher to the NetWare client
  Make the NetWare Application Launcher available on the NetWare client

Purpose

The executable for the NetWare Application Launcher should be installed in an accessible directory on the network server, i.e. SYS: PUBLIC. Each NetWare Client workstation should have a program item pointing to the NetWare Application Launcher executable on the server.

To make the Launcher available in Windows

1.	Select or create a program group for the NetWare Application Launcher

2.	Create a program item for the NetWare Application Launcher

3.	Type or browse the path to the executable NAL.EXE

4.	Select the desired icon

5.	Press OK.

To add the NAL to a Win95 StartUp folder

1.	Browse to NAL.EXE

2.	In a separate window, open the Windows StartUp folder (typically C:\WINDOWS\Start Menu\Programs\StartUp).

3.	Drag NAL.EXE to the Windows StartUp folder.

To create  Win95 shortcut to NAL

1.	Select FILE | NEW | SHORTCUT menu item.

2.	For the command line enter the path to NAL.EXE then press NEXT.

3.	Enter any name you want for the shortcut then press FINISH.


Administrating Desktops Go To
Topic Outline

The situation

Using local computer resources

Using the network

Using the NetWare Application Launcher

Benefits of using the NetWare Application Launcher

Related Topics

Why would I use application objects


Administrating desktops Example
  Administrating Desktops Using the Network Application Launcher

The situation

A NetWare Administrator of a company with 100 employees receives an application and wants to distribute it to the employees who need it. The application is a calculator which performs specific business functions unique to the company. About half the employees have duties which could be simplified by using the calculator.

The calculator application requires no special drive mappings, printer ports, environment variables, or user configuration files.

Solution #1 Using local computer resources

The administrator installs the calculator application on each user’s hard drive. This is the most time-intensive option requiring the administrator to install, upgrade, and support the application and computer hardware on at each user's location.

Solution #2 Using the network

The administrator installs the calculator on the network. It is installed on a NetWare server called PRODUCTS. in the SYS:\APPS\CALC\V1.0 directory. A group object is then created called CALC GROUP in the NetWare Administrator. File system rights are granted to CALC GROUP in the directory where the application is installed. Users requiring access to the calculator application are made members of CALC GROUP.

The application is now available; however, since no calculator icons appear on the desktop, the users are not aware that the calculator application is available. The administrator may communicate that the calculator is available and explain where the application is located and how to set it up, or must physically visit each desktop.

Some problems that still exist:

1.	Even though the calculator icon appears on the user's workstation, the application resides on the network.  If the user is not logged in when the application icon is double-clicked on the icon, an error message comes up stating that the path is invalid. Users may be confused by the error and require support.

2.	The user may delete the icon and would then need help by the administrator to restore it.

3.	The icon references the executable file (calc1.exe) in the \\PRODUCTS\SYS\APPS\CALC\V1.0 directory. To move or rename the executable, or upgrade to version 2.0 without removing version 1.0, the path must be changed at each workstation.

Solution #3 Using the NetWare Application Launcher

The administrator installs the calculator application on server PRODUCTS in the SYS\APPS\CALC\V1.0 directory, creates CALC GROUP, and makes each user who needs the application a member of the group.

Using NWAdmin, The administrator creates an application object called CALC1.  The CALC1 object contains the path to the program file and other information such as command-line parameters, the working directory, and a description of what the application does.  The administrator associates CALC1 application object with CALC GROUP.

The CALC1 application icon appears on each user's workstation. No setup is required at the user's workstation. The application may now be launched by double-clicking the icon.

Benefits of the NetWare Application Launcher:

1.	If the user is not logged in to the network, the icon is not displayed.

2.	The user cannot delete the icon or change any of the path information.

3.	If the administrator wants to move or rename the executable file, only the CALC1 object must be modified and the user is unaware of any changes.

4.	The upgrade can be installed anywhere (i.e. \\PRODUCTS\SYS\APPS\CALC\V2.0). Using the NetWare Administrator, Version 1.0 can be replaced by modifying the path to the new application executable.

5.	Both versions can be available by creating a new CALC2 application object and associating it with CALC GROUP.


Application class defined
Application objects can be one of the following classes:

DOS

Windows 3.X

Windows 95

Windows NT

Select the type of class that corresponds with the application.


Application objects GO TO
Related Topics

What is an application object

Why would I use application objects

Examples of using application objects


Application objects See Also
Related Topics

NetWare Application Manager

NetWare Application Manager Overview


  Assign an application to multiple users or groups

Purpose

Application objects assigned to the launcher will appear on the user's desktop.

To assign an applications to multiple users or groups:

1.	Using the NetWare Administrator, select the application object from the NDS tree.

2.	Select Associations.

3.	Choose Add or Delete.

Note: Using this procedure, the administrator can only assign application objects which will appear as icons for the user. An application cannot be assigned to automatically launch. See Assign multiple applications to a user, group, or container.


  Assign application objects to a launcher overview

Application objects assigned to the launcher will appear on the user's desktop. Applications can be assigned to users, groups, or containers.

If the application is associated with a user, the user can view and launch the application. If the application is associated with a group, each user in the group can view and launch the application. If the application is associated with a container, each user or group in the container can view and launch the application.

Applications can also be designated to automatically launch when the user accesses the Launcher.


  Assign application objects to launch

Assign application objects to launch

Overview

Assign multiple applications to a user, group, or container

Assign an application to multiple users or groups

View application objects assigned to a user, group, or container


  Assign multiple applications to a user, group, or container

Purpose

Application objects assigned to the launcher will appear on the user's desktop.

To assign applications to launch:

1.	Using the NetWare Administrator, select a user, group, or container object from the NDS tree.

2.	Select Object, Details.

3.	Select Applications

4.	Choose Add

5.	Select the desired application to launch.


  Available at no charge

A prerelease version of the NetWare Application Manager will be made electronically available free of charge via CompuServe in the NetWare Operating System Files Forum (NWOSFILES) on NetWire and through Novell’s World Wide Web home page at http://www.netware.com in late October.

The final version of NetWare Application Manager will be included in the NetWare Client 32-based client kits, which will begin shipping in late 1995.


Browse button defined
The browse button allows you to walk down the directory tree to find the appropriate file or directory.


  Configure the NetWare Application Launcher

Purpose

The NetWare Application Launcher allows the System Administrator to specify how each user can view the Application Launcher. The Launcher can be customized for an organization or a user object.

To configure the NetWare Application Launcher:

1.	From NetWare Administrator, select the user or container object.

2.	Select Object, Details

3.	Select Launcher Configuration from the button bar


  Create the application object

Purpose

Using the NetWare Administrative, any Windows or DOS executable may be created as an Novell Directory Service (NDS) application object. Application objects can be available to users running the NetWare Application Launcher.

To create the application object:

1.	Using the NetWare Administrator, select a container object from the NDS tree.

2.	Select Object, Create.

3.	Select the Application class.

4.	Select OK.

5.	Type the Application Name.

6.	Type or browse the Full path to the executable.

7.	Select Define Additional Properties.

8.	Select Create.

(Optional) Select Environment to specify drive mappings or print captures that the application may require.

(Optional) Setup a contact for the application


Define application object properties
  Create and define application object properties

Create the application object properties

Overview

Create the application object

Define the application object properties

Identify the application object properties

Setup application support contacts

Set up the application environment

Set application object options

Manage setup and cleanup scripts


Dynamically updates user desktops

With the NetWare Application Manager, network applications delivered to users’ Windows desktops are dynamic and can be refreshed automatically. This ensures that any changes the administrator makes are quickly reflected on users’ desktops.

For example, if a new version of a network application is installed, the administrator can quickly move the appropriate users to that new version using the NetWare Application Manager. The administrator simply modifies the properties in the application object defined in NDS to point to the new version of the application.The NetWare Application Manager then updates that network application on the appropriate user desktops. The next time a user double-clicks on the icon for that application, the updated version is launched automatically.

The NetWare Application Manager makes it easy to install new applications and migrate users to new versions of applications without requiring the administrator to travel to each user’s workstation.


E-mail defined
Electronic mail correspondence is available from the NetWare Application Launcher. If the end user selects the e-mail button, the contact's address is placed in an electronic mail message and a mail message is sent to the contact.


Easy to Install and Use

The NetWare Application Manager consists of both an administrator component and a user component. The administrator component is a Windows DLL that snaps into the NetWare Administrator utility and adds new property buttons to the Details listing of the appropriate NDS objects. This allows administrators to work from a familiar and consistent interface. The user component is an executable file that is run in each user’s Windows Startup or other program group as desired.


  Eliminates the Need for Login Scripts

Because the NDS application objects store pointers to the actual location of network applications, users no longer need drive mappings established through login scripts. Each NDS application object can also store login scriptlike subroutines that can map additional drives and capture printers as users launch applications. This saves considerable administration time and costs since administrators are no longer required to create and manage network login scripts.


  For more information

In the United States and Canada, call 1-800-NETWARE (1-800-638-9273). In all other locations, call

1-801-429-5588.


  Frequently asked questions & answers

Listed below are the most commonly asked questions about the NetWare Application Launcher and the Snap-in for NWAdmin (APPSNAP).

Q:	What does NAL do when a drive it needs to map is already mapped?

A:	If an application needs a drive that is already mapped and that drive is mapped to the correct place, it will go ahead and use the existing drive mapping.  If the drive is not already mapped to the right place, NAL will fail the launch with an error message that describes the resource conflict.  The user can manually un-map the needed drive and attempt a re-launch of the application.  NAL will not override an existing mapping.  Most applications do not handle the situation very well if drive mappings that it is dependant on are changed.  Many applications will crash, hang, or malfunction if this were done.  Because of that reason, NAL will not override an existing drive mapping.

Q:	How does NAL handle local configuration files like INI and registry settings?

A:	NAL provides a setup mechanism called the ‘script to run before launching the application’.  This ‘pre-launch’ script is where any workstation configuration commands that need to take place can be done here.  There is also a ‘script to run after the application terminates’ script.  This ‘post-termination’ script is run after NAL detects that the application has terminated.  Like the pre-launch script this script follows the login script language syntax.  Commands relating to cleaning-up the changes made by the pre-launch script should be placed here.

Q:	What workstation software is needed in order to run NAL?

A:	You must be running a NetWare client that supports Directory Services calls.  On DOS/Windows 3 this would be VLMs or Client-32.  On Windows 95 this would be Client-32.

Q:	What files are needed in order to run NAL?

A:	For a Windows 3 end-user, NAL.EXE, NALW31.EXE, NALRES.DLL, NALBMP.DLL, and NAL.HLP.  For a Windows 3 or Windows 95 administrator, APPSNAP.DLL and APPSNAP.HLP.  For a Windows 95 end-user, NAL.EXE, NALW95.EXE, NALRES32.DLL, NALBMP32.DLL, and NAL.HLP.

Q:	When will there be OS/2 and Windows NT versions of NAL?

A:	A Windows NT version of NAL is currently in development.  An OS/2 version of NAL is being investigated.

Q:	What is the syntax for drive mappings in NAL?

A:	Syntax for mapping a drive:

D:=SERVER\VOLUME:PATH

D:=\\SERVER\VOLUME\PATH

D:=VOLUME_OBJECT_NAME:PATH

D:=DIRECTORY_MAP_OBJECT_NAME:PATH

Syntax for capturing a port:

LPT1:=SERVER\DS_QUEUE_NAME:

LPT2:=\\SERVER\DS_QUEUE_NAME

LPT1:=DS_QUEUE_NAME

LPT3:=\\\DS_QUEUE_NAME

Q:	Does NAL support bindery servers?

A:	NAL will not create connections to bindery servers, however, is NAL needs a connection to a specific server and the workstation is already attached to it, NAL will use that connection.

Q:	Do I have to use Novell’s Client-32 in Windows 95?

A:	NAL for Windows 95 requires Client-32.  NAL for Windows 95 is a Win32 application that uses the NetWare 32-bit libraries which require Client-32.  You can use NAL for Windows 3 in Windows 95.  It is a Win16 application that can make 16-bit calls through VLMs or Client-32.

Q:	Does NAL support directory map objects?

A:	NAL supports directory map objects as well as aliases to them in the EXE path, working directory, and drive mapping strings.

Q:	How does NAL figure out what icons to show?

A:	NAL builds a view of icons based on application object associations in Directory Services.  First, NAL checks the current user object for any application objects associated with that user and adds them to the list.  Next, NAL checks every group object that the user is a member of for application object associations and adds them to the list.  Finally, NAL will check parent containers, depending on the ‘container levels’ setting for application object associations and adds them to the list.  Once the list is built, NAL filters out all duplicates and filters out application object it is incapable of running.  For instance NAL for Windows 3 will filter out all Windows 95 application objects.  Once the list has been filtered, the icons are displayed to the user.

Q:	Right now, I can only choose icons from the EXE file defined with the application object. Is there a way to select icons from a file other than the EXE like in Program Manager?

A:	Currently, you can only select from the icons in the EXE the application object points to.  In the future this feature will be added.

Q:	I have too many icons in my main view and would like a way of filtering them.  Will NAL support a group or folder view in the future?

A:	Yes!  In the future NAL will support folder or group types of views.


Full path defined
The Full Path to the executable may be typed in, either as a UNC path or a file directory path, or use the browse button to walk through the file directory structure to find the desired executable.


  Help - Application Associations

Purpose

Displays user, group, or container objects which can launch the application object.

Screen options

Add a user, group or container object to provide access to the application object.

Delete a user, group or container object to remove access to the application object.


  Help - Application Contacts

Purpose

Assigns support contacts to specific application objects. This assignment appears in the NetWare Application Launcher.

Screen options

A list of people displays all users assigned as support contacts.

Add an additional user object as a support contact.

Delete a user object as a support contact.


  Help - Application Environment

Purpose

Identifies the environment which may be required by an application object.

Screen options

Command line parameters are required to run some applications in a desired mode or view.

Working directories can be designated for any application object.

Drive mappings are required for some applications which look for files on predetermined drives. Example

Printer ports can be redirected for applications and users who prefer to print to a specific printer. Example


  Help - Application Identification

Purpose

Identifies the specific properties of an application object.

Screen options

Application Description appears under the icon in the NetWare Application Launcher and defaults to the Application Name. The description can be different than the Application Name. It can contain periods and other special characters.

The Full Path to the executable may be typed in, either as a UNC path or a file directory path, or use the browse button to walk through the file directory structure to find the desired executable.

Run Application launches the application.

Change Icon allows an icon to be assigned to the application object. The icon appears in the NetWare Application Launcher.


  Help - Application Options

Purpose

How applications appear and function in the NetWare Application Launcher can be customized with options.

Screen options

Automatically minimize application window minimizes the NetWare Application Launcher window when the application is launched.

Do not cleanup network resources allows the user to exit the application and retain the drive mappings and printer ports associated with the last launched application.

Note: If the application does not have available mappings after launching, you may be running a wrapper. Setting Do Not Cleanup Network Resources may eliminate this problem.

A short description can be accessed by the user through the NetWare Application Launcher help. If the user is unfamiliar with the application, the description may be very helpful.


  Help - Application Scripts

Purpose

 ???Still under construction, We need to put some examples in here???

Scripts are run prior to launching the application and after the application closes.

Screen options

Script to run before launching application

Script to run after application terminates


Help - Create Application Object
  Help - Create Application

Purpose

Windows 95, Windows, and DOS executables may be created as an NDS application object.

Screen options

The Application Name will display in the NDS tree. The name is limited to 64 characters and may not contain periods, or other special characters.

The Full Path to the executable may be typed in, either as a UNC path or file directory path, or use the browse button to walk through the file directory structure to find the desired executable.

Create Another Application will allow you to create several application objects. After specifying the name and the path of the application object, you will return to the Create Application dialog box. You may later go into each application and define the additional properties by selecting the Details of the Application object in the Directory tree.

Define Additional Properties allows you define the identification, contacts, environments, options, scripts, and view associations of the Application object. You may later define additional properties by selecting the application object and selecting Object, Details.


Help - Create Application See Also
Related Topics

Create the application object

NetWare Application Manager


Help - Desktop Application List
  Help - Applications

Purpose

Displays application objects associated with the selected user object.

Screen options

Applications to launch when the user selects are available in the launcher and will launch when double-clicked.

Applications to launch automatically will be run when launching the NetWare Application Launcher.

Add associates an application object with the selected user.

Delete removes an application object from the selected user.


Help - Environment See Also
Related Topics

Set up the application environment


Help - Identification See Also
Related Topics

NetWare Application Manager


Help - Launcher Configuration

Purpose

???Still under construction???

The NetWare Application Launcher allows the System Administrator to specify how each user can view the NetWare Application Launcher. The Launcher can be customized for an organization or a user object.

Screen options

Use default settings

Allow the user to exit the launcher

Allow the user to login

Allow the user to refresh icons

Enable timed refresh

Save window size and position on local drive

Allow icons to be moved to the desktop

Restricting container levels

User objects - Launch if user selects

User objects - Launch automatically


Help Environment - syntax2
Syntax for capturing a port:

LPT1:=SERVER\DS_QUEUE_NAME:

LPT2:=\\SERVER\DS_QUEUE_NAME

LPT1:=DS_QUEUE_NAME

LPT3:=\\\DS_QUEUE_NAME


Help environment - syntax
Syntax for mapping a drive:

D:=SERVER\VOLUME:PATH

D:=\\SERVER\VOLUME\PATH

D:=VOLUME_OBJECT_NAME:PATH

D:=DIRECTORY_MAP_OBJECT_NAME:PATH


  Identify the application object properties

Purpose

Application objects are identified by description, name, path and icon.

To view or change the properties of an application object:

1.	Using the NetWare Administrator, select the application object from the NDS tree

2.	Select Object, Details

3.	Select Identification.


  Install Windows 95 from the network

Purpose

Using the NetWare Application Launcher, every workstation on the network easily upgrade to Windows 95.

To install Windows 95 from the network:

1.	Create an application object of type Application (Windows 3.x).

2.	Set the Full Path to the executable file to be SETUP.EXE in the root of the Windows 95.

In my case, I have the Windows 95 CD mounted as a volume on my server.  I entered the path \\GT\WINDOWS95\SETUP.EXE.  If you copied the CD to a server you'd adjust the path to point to SETUP.EXE.

3.	Set the Working directory to be the same directory that SETUP.EXE is located in.

In my case that was \\GT\WINDOWS95.

4.	(Optional) Enter a description and/or contacts.

Note:  Windows 95 needs access to the install CD if the user goes in and changes configuration and/or installs Client-32.  Users may need to be told where it came from so if they are prompted for it, they can enter the path.  An administrator may want to put this info in the long description.


Install the NDS Application object software Get Started
  Install the application object software

Get started

Overview

Install the application object software

Modify directory schema


  Install the application object software

Purpose

Installing the application object software extends the NDS schema to include attributes specific to application objects.

To install the application object software

1.	Copy APPSNAP.DLL and APPSNAP.HLP to an accessible network or local directory.

Hint: Copy the files on the network to SYS:PUBLIC.

2.	Edit NWADMIN.INI (found in the Windows directory on the local workstation). Under the [Snapin Object DLLs] add the following line:

<snapin name>=<path>

 where <snapin name> is a unique identifing name (like "SNAPIN1"), and <path> is the path where the APPSNAP.DLL is located (like"\\prufrock\sys\public\appsnap.dll").

For example:

[Snapin Object DLLs]

SNAPIN1 = \\prufrock\sys\public\appsnap.dll

Note: The NWADMIN.INI needs to be modified on each machine that will run the NetWare Administrator (NWAdmin).

3.	To modify the schema, run NWADMIN.EXE. If the tree doesn't have the necessary extensions already, you will be prompted to modify the tree's schema.


Install the software
  Install the NetWare Application Launcher software

Purpose

The NetWare Application Launcher is installed on the network and is configured using NWAdmin.

To install the NetWare Application Launcher software

1.	Copy NAL.EXE and NALW95.EXE to a directory that is accessible by all users (such as the PUBLIC directory on a server), or on the local hard-drive.

2.	Copy NALRES32.DLL, NALBMP32.DLL, and NAL.HLP to a directory that is accessible by all users (such as the PUBLIC directory on a server), or on the local hard-drive.

Note that NALRES32.DLL, NALBMP32.DLL, and NAL.HLP can be either in the NAL.EXE directory, or in the NLS\<language> directory.

3.	(Optional) Add the NAL.EXE application to the Windows Startup folder.


Installing MS Office

Purpose

The NetWare Application Launcher can install and run MS Office over the network.  Some applications require additional and modified files and update files on the workstation. This doc is intended to tell you what dll’s need to be copied to the local workstation.

To allow users to install MS Office

1.	Create the MS Office setup program as an application object

2.	Assign application object to the NetWare Application Launcher

3.	Have endusers run minimum setup.

To run MS Office applications (WordWin, Excel, PowerPoint)

1.	Set up each application as an application object

2.	Assign application objects to the NetWare Application Launcher

3.	Set the working directory to where the application object executable is located.

Note: MS Word requires SDM.DLL in WINDOWS\SYSTEM. You will need to copy this file or use the startup script to do this function.

Note: MS PowerPoint produces an error that it can not find an INI file. The error message indicates that you must run MS PowerPoint setup. PowerPoint still seems to run without the INI file.


  Manage setup and cleanup scripts

Purpose

Scripts can automatically be executed each time the application is launched and closed. Unlike the environment parameters, the setup and exit scripts can overwrite existing drive mappings and printer ports.

Setup scripts are executed after the environment is set and before the application is launched.

Cleanup scripts are executed before the network resources are cleaned up and after the application is closed.

To manage setup and cleanup scripts:

1.	Using the NetWare Administrator, select the application object from the NDS tree.

2.	Select Object, Details.

3.	Select Scripts.


Modify directory schema
  Modify directory schema to include application objects

Purpose

The schema that shipped with NetWare 4.1 should be modified to include the attributes required to use Application objects.

To modify the schema:

Prerequisites: You must have administrative rights at the root of the NDS tree.

1.	Install the application object software (APPSNAP.DLL) into the directory with the NetWare Administrator.

2.	Start the NetWare Administrator.

3.	Press OK when asked if you want to modify the schema to accept application objects.

The additional attributes are now available for creating and using Application objects.


  NetWare Application Launcher Overview

The NetWare Application Launcher (NAL) allows users to run applications that were previously configured by a system administrator, and whose setup information is stored as an application object in the NetWare directory tree.  NAL displays icons for all available applications in a window, and lets the user double-click on an icon to launch an application.

Users don't need to worry about drive mappings, paths, or rights.  The administrator can manage the application launcher on a Container, Group, or User object level.


NetWare Application Launcher See Also
Related Topics

NetWare Application Manager


  NetWare Application Manager

Overview

Overview of NetWare Application Manager

Suggested reading

Get started

Prerequisites

Setup and use the NetWare Application Manager

Set up Application objects

Overview

Install the NDS Application object software

Create and define application object properties

Assign application objects to launch

Set up the NetWare Application Launcher

Overview

Install the NetWare Application Launcher software

Configure the NetWare Application Launcher

Make the Launcher available on the NetWare client

How to use the NetWare Application Launcher

Install Windows 95 from the network

Install MS Office applications

Reference

Frequently asked questions & answers

View README file

Trademarks and disclaimer


Network requirements Example
An application requires a drive mapped to S: and uses a specific printer on the network. The user needs no prior mappings or capture statements. When the application object is launched, the launcher configures the application requirements by transparently mapping S: to the desired directory and capturing the desired printer. When exiting the application, the printer and S: are returned to their pre-launch configuration.

Note: If S is already mapped to a resource prior to launching the application, S: will not be mapped. An error will be returned stating that the resource is already in use.


  Overview of NetWare Application Manager

Overview

What is the NetWare Application Manager?

Examples of NetWare Application Management

Benefits

Simplifies administration of network applications

Eliminates the need for login scripts

Simplifies user access to network applications

Dynamically updates user desktops

Easy to install and use

Available at no charge

Software and hardware requirements

For more information


Overview of application launchers

Several companies are partnering with Novell to provide application launchers.


Overview of application object properties

Properties define what happens before, what happens after, how and who to contact for support when an application object launches.


  Overview of creating an application object

Install the software

The application object software should be copied to an accessible network or local directory. The [Snapin DLLs] section of NWADMIN.INI must be edited to include the name and path of APPSNAP.DLL.

Modify the schema

After the application object software has been installed, NWAdmin will prompt you to modify the schema. Modifying the schema to include the working directory, printer ports, drive mappings, and other attributes will allow creation and use of application objects.

Create the application object

Application objects are created using NWAdmin.exe


Prerequisites

Prerequisites

Creating application objects that use the NetWare Application Launcher requires the following:

NW 4.x with a Novell Directory Service (NDS) tree

NW Admin 4.10.2

Windows 3.1 or 95

Administrative rights

Modification rights at the root of your tree if your schema has not been modified.

Client 32 or VLMs (NETX is not supported)

Note: The NetWare Application Launcher and application objects will not work with a bindery attachment.

The following files are needed for the NetWare Application Launcher to run with Windows 3.1:

AUDWIN16.DLL

CALWIN16.DLL

CLNWIN16.DLL

CLXWIN16.DLL

LOCWIN16.DLL

NCPWIN16.DLL

NETWIN16.DLL


  Process to setup application objects

Install the software

After installing APPSNAP.DLL, the schema is modified to allow the NetWare Administrator to create and define application objects.

Create and define the application object

An application object is defined by its unique properties. Properties like name, location of executable, and support contacts are assigned to each application object.

An application may require unique drive mappings, printer ports, or environment variables. These specific variables must be specified in the application environment.

Assign application objects to launch

Application objects may be assigned to users, groups, or containers.


Reduce login time example
Login script commands like If member of group=ACCT, then MAP F:=SYS/ACCT can be removed and configured when the application is launched.


Schema defined
The schema is a list of attributes which define an object and its relationship with other NDS objects. The schema exists at the root of the NDS tree. The NDS schema can be modified and expanded to suit the specific needs of your organization.


  Set application object options

Purpose

How applications appear and function in the NetWare Application Launcher can be customized with options.

To set other application object options:

1.	Using the NetWare Administrator, select the application object from the NDS tree

2.	Select Object, Details

3.	Select Options.


  Setup the application environment

Purpose

Some applications require custom configuration parameters to function properly. Before launching the application, the NetWare Application Launcher will configure the workstation to properly run the application. The parameters, directories, mappings, and printer ports associated with the application will automatically execute. Upon exiting the application, the user's original configuration will be restored.

These mappings and captures don't actually happen until the user launches the application. When the user closes the application, the mappings and captures are removed. The user can view (but not change) environment settings in the Application Launcher, by selecting File|Properties, and then Resources.

To set up the application environment:

1.	Using the NetWare Administrator, select the application object from the NDS tree

2.	Select Object, Details

3.	Select Environment.


Setup and use Application objects Overview
  Setup and use Application Objects - Overview

Overview

What is an application object

Why would I use application objects

Setting up application objects


Setup the NetWare Application Launcher - Overview

Overview

The NetWare Application Launcher (NAL) allows users to run applications that were previously configured by a system administrator, and whose setup information is stored as an application object in the NetWare directory tree.  NAL displays icons for all available applications in a window, and lets the user double-click on an icon to launch an application.

Users don't need to worry about drive mappings, paths, or rights.  The administrator can manage the application launcher on a Container, Group, or User object level.

Prerequisites:

APPSNAP.DLL must be installed in the directory with NWADMIN.EXE.

The NetWare Administrator's NWADMIN.INI must include the path to the APPSNAP.DLL. See Install the application object software.

To setup the NetWare Application Launcher:

1.	Install the software to the appropriate directories

2.	Configure the NetWare Application Launcher.

3.	Assign application objects to launch

4.	Make the Launcher available on the NetWare Client


Setup the NetWare Application Manager
  Setup the NetWare Application Manager - Overview

The NetWare Application Manager consists of two components, (1) Application objects and (2) the NetWare Application Launcher.

1.	Application objects software allows the NetWare Administrator to create and define application objects. The following files are installed and used with NWAdmin:

appsnap.dll

appsnap.hlp

2.	The NetWare Application Launcher software allows the user to launch applications. Although NAL.EXE is run by all client platforms, the following files are copied to an accessible directory on the network:

nal.exe

nalw31.exe - Windows 3.1 only

nalw95.exe - Windows 95 only

nalres32.dll - Windows 95 only

nalres.dll - Windows 3.1 only

nalbmp32.dll - Windows 95 only

nal.hlp

The NetWare Application Launcher files should be installed in a network directory available to all network users, i.e. SYS\PUBLIC.

Note: For Windows 3.1 use, some additional DLLs are required - See Prerequisites.


Simplifies Administration of Network Applications

The NetWare Application Manager works together with NetWare Directory Services (NDS) to simplify management of network applications by allowing administrators to centrally control users’ Windows desktops. Using NetWare Administrator, the NetWare Application Manager gives administrators the ability to create NDS objects that represent network-based applications.

These objects contain information about where the network applications are physically located on the network and which users are authorized to use those applications. Network administrators can then use these objects to create a custom Windows program group for each Windows 3.x, Windows 95 or Windows NT user on the network.

Without leaving their workstation, administrators can deploy these applications managed through NDS to user desktops across the network. This eliminates time-consuming effort and significantly reduces installation costs of new network applications.

Network administrators no longer have to travel to each user’s desktop to create a standard Windows program item for each application on the network. They simply use NDS to centrally administer and deploy network applications from the convenience of their own workstation.

Using the NetWare Application Manager, administrators can assign network applications by user, user group, container or any combination of the three. This makes setting up network applications on users’ Windows desktops quick and easy. Access to files and directories is handled through NDS file system security, ensuring that network security is maintained.


Simplifies User Access to Network Applications

To access network applications, users run the NetWare Application Manager from their Windows Startup group or other Windows program group. This will present users with an NDS-delivered set of network applications the administrator has assigned to them. To launch an application, a user simply double-clicks on the appropriate icon in the group. The NetWare Application Manager does the rest, taking care of drive mappings and paths automatically. When using the NetWare Application Manager, standard Windows program items that represent network applications are no longer required and should be deleted from Windows desktops.

The NDS-delivered network applications are associated with a user’s network login ID, so they follow the user around the network. Regardless of the login location, the user always sees the same set of network applications. This ensures that people who work from multiple locations or physical workstations always have a consistent set of network applications.

For each NDS-delivered network application, the administrator can include a support number and E-mail address to use if help is required. This information is displayed in the properties of each application icon on the user’s desktop. The help information can be tailored so each user is directed to the support group for his or her location. The administrator can also specify that some network applications are to be launched automatically when the user runs the NetWare Application Manager.


Software and hardware requirements

Software requirements

Windows for Workgroups 3.11, Windows 3.1,Windows 95 or Windows NT

NetWare 4.1

NetWare Client for DOS/Windows 1.2 (included with NetWare 4.1) or the new NetWare Client 32-based clients

Hardware requirements

There are no additional hardware requirements associated with running this program in a Windows environment.


Specify application support contacts
  Setup application support contacts

Purpose

The user objects designated as Application Contacts appear in the NetWare Application Launcher as resources for support. The end user may contact the assigned contact in person, phone, or use the Application Launcher to send an e-mail.

To select a user as an application contact:

1.	Using the NetWare Administrator, select the application object from the NDS tree

2.	Select Object, Details

3.	Select Contacts

4.	Choose Add or Delete

5.	Type or select one or more user objects from the browser.


Suggested reading

I know you hate to read long help topics, but here is an overview of what you can find in this help file:

To get an introduction of what the NetWare Application Manager can do for you, following the Overview of NetWare Application Manager links.

Before you do anything, read Prerequisites. Make sure you get a brief overview of the installation process and the files required in Setup and use the NetWare Application Manager.

When you ready to create and define application objects, read the links in the Set up Application objects section. Don't forget to read the Overview.

Read the Overview in the Set up the NetWare Application Launcher section before installing and configuring the NetWare Application Launcher. It will give you the big picture of the tasks required to manage and launch your applications.

Check out the [image] located in the upper-right corner of some help screens. They lead you to related links and give you an outline of the contents in long topics.

We're building a great section about how to use NetWare Application Launcher with many popular applications. Check out the How to use the NetWare Application Launcher section. One link, Install Windows 95 off the network will give you the steps to easily upgrade all your workstations to Windows 95. We'll add more in later releases.

Finally, read through the Frequently asked questions & answers and View README file. These sections may be just the thing you are looking for.

If you have any suggestions about how to improve the documentation, please fax it to (801) 429-3002. Sorry, technical support is not available at this number.


Trademarks

© 1995 Novell, Inc.

Registered trademarks of Novell, Inc.

Novell

NetWare

NetWare Application Manager,

NetWare Directory Services,

NDS,

NetWare Administrator,

NetWare Client,

Registered service marks of Novell

NetWire

Registered trademarks of Microsoft Corporation

Windows


UNC path defined
NetWare supports the use of Universal Naming Convention (UNC) redirection for path statements in dialog boxes. UNC provides :

the ability to use a network resource without setting up a drive mapping to it

the use of applications and programs within Windows to access network volumes and directories

the ability to assign network applications, volumes, and directories to icons within Windows

An example of a valid UNC path is \\SERVER1\SYS\APPS\SOLITAIRE\SOL.EXE\.


View Readme.nal
View README file

Readme for NetWare Application Launcher

Beta 1.1

October 6, 1995

(c) Copyright 1995, Novell, Inc.  All rights reserved.

This readme file contains information for installing and using the

NetWare Application Launcher product.

IMPORTANT! All of the information in this readme file and the Beta release of the Application Launcher is subject to change in later revisions of the product.  Caution should be used when modifying the schema of a production Directory Tree, as the schema modifications are permanent (unless you remove the directory and re-install it).

Unauthorized distribution of this Beta is strictly forbidden.

OVERVIEW

The NetWare Application Launcher (NAL) allows users to run applications that were previously configured by a system administrator, and whose setup information is stored as an application object in the NetWare directory tree.  NAL displays icons for all available applications in a window, and lets the user double-click on an icon to launch an application.  Users don't need to worry about

drive mappings, paths, or rights.  The administrator can manage the application launcher on a Container, Group, or User object level.

LIMITATIONS AND CAVEATS

These bugs, limitations, and caveats apply only to this beta.

If a drive mapping exists, applications that need the drive letter with a different mapping will not execute. File system rights are not automatically granted when the application object is assigned to a user, group, or container. These file system rights must be explicitly granted by the administrator.

Caution should be used when setting the timed refresh setting. Frequent refreshes of large numbers of users can adversely impact network traffic.  The default is timed refresh turned off.

Changes to user configurations don't actually take place until the user closes the Application Launcher, and re-runs it.

INSTALLATION

The following files make up the Application Launcher:

 APPSNAP.DLL

 APPSNAP.HLP

 NAL.EXE

 NALW95.EXE

 NALRES32.DLL

 NALBMP32.DLL

 NAL.HLP

(Administrators use NWADMIN and the snap-in (APPSNAP.DLL), users run

NAL.EXE on all platforms).

Manual installation is done in two parts:

PART 1 - Administrator

Installing APPSNAP.DLL

1.  Copy APPSNAP.DLL and APPSNAP.HLP to any directory on the network or local drive that the network administrator has access to.

These files are typically copied to a server into the SYS:PUBLIC directory.

2.  Edit NWADMIN.INI (found in the Windows directory). Under the "[Snapin Object DLLs]" add the following line:

<snapin name>=<path>

where <snapin name> is a unique identifing name (like "SNAPIN1"), and <path> is the path where the APPSNAP.DLL is located (like "\\prufrock\sys\public\appsnap.dll").

For example:

    [Snapin Object DLLs]

    SNAPIN1 = \\prufrock\sys\public\appsnap.dll

3.  To modify the schema, run NWADMIN if the tree doesn't have the necessary extensions already, you will be prompted to modify the tree's schema.

PART 2 - User

Installing NAL.EXE

1.  Copy NAL.EXE and NALW95.EXE to a directory that is accessible by all users (such as the PUBLIC directory on a server), or on the local hard-drive.

2.  Copy NALRES32.DLL, NALBMP32.DLL, and NAL.HLP to a directory that is accessible by all users (such as the PUBLIC directory on a server), or on the local hard-drive.  Note that NALRES32.DLL, NALBMP32.DLL, and NAL.HLP can be either in the NAL.EXE directory, or in the NLS\<language> directory.

3.  (Optional) Add the NAL.EXE application to the Windows Startup group.

CREATING APPLICATION OBJECTS

To create an Application object in NDS, complete the following steps:

1.  Run NWADMIN. (The application launcher snap-in should be installed and initialized.)

2.  Select Object|Create.

3.  Select "Application (Windows 95)", "Application (Windows 3.x)" or "Application (DOS)" from the object list.

4.  Specify the path of the application, using UNC or drive-letter syntax, in the application dialog.

5.  Press "Create" to create the application object.

6.  (Optional) Select the Environment page to specify any drive mappings or print captures that are needed for this application.

These mappings and captures don't actually happen until the user launches the application. When the user closes the application, the mappings and captures are removed. The user can view environment settings in the Application Launcher (but not change them), by selecting File|Properties, and then Resources.

    Syntax for mapping a drive:

           D:=SERVER\VOLUME:PATH

           D:=\\SERVER\VOLUME\PATH

           D:=VOLUME_OBJECT_NAME:PATH

           D:=DIRECTORY_MAP_OBJECT_NAME:PATH

    Syntax for capturing a port:

           LPT1:=SERVER\DS_QUEUE_NAME:

           LPT2:=\\SERVER\DS_QUEUE_NAME

           LPT1:=DS_QUEUE_NAME

           LPT3:=\\\DS_QUEUE_NAME

7.  (Optional) Specify a contact for the application.

Contact telephone numbers and email names are available to users in the Application Launcher.  The phone number and email name are retrieved from the user object data in the tree.

Once the Application objects are created, you can associate them with user, group, or container objects by doing the following:

1.  In NWADMIN, view details on the Container, Group, or User object you want to associate the application object with.

2.  Select the "Applications" button. (This button is one of two new property buttons that appear at the bottom of the NWADMIN buttons after you have installed and initialized the application launcher snap-in.)

3.  Add an Application object to the "Applications to launch when the user selects" list and the "Applications to launch automatically" list.

Applications in the "Applications to launch automatically" list are launched when the NAL.EXE file is executed. To launch applications in the "Applications to launch when the user selects" list, the user must double click.

4.  Save the changes to the object.

The application launcher is updated as specified by the refresh rate. The default is no refresh. To change this refresh rate, in NWADMIN select the "Launcher Configuration" page for that object, and modify the "Refresh seconds" field.

ASSOCIATING APPLICATION OBJECTS WITH USERS

When the Application Launcher loads, it determines which applications to display for the user. It does this by using the following algorithm:

-   Display all applications associated with the user object.

-   Display all applications associated with groups that the user

    belongs to.

-   Display all applications associated with containers the user is part

    of (the number of containers to search is configured in the

    "Launcher Configuration" page of user objects and container

    objects).

Here are three simple scenarios and how they affect which applications the user sees:

Scenario #1

 Associations: WordPerfect and Quattro Pro are associated with the user object.

 User sees:    WordPerfect and Quattro Pro.

Scenario #2

 Associations: User belongs to a group named PerfectOffice. The PerfectOffice group has 3 applications associated with it: WordPerfect, Quattro Pro, and Presentations.

 User sees:    WordPerfect, Quattro Pro, and Presentations.

Scenario #3

 Associations: The context of the user is .CPT.NPD.NOVELL. The CPT container has an application named Schema Manager associated with it, NPD has GroupWise associated with it, and NOVELL has PhoneW associated with it. The "Container Levels" field in the "Launcher Configuration" page for the user is set to 2.

 User sees:    Schema Manager and Groupwise. User does not see PhoneW.


  View application objects assigned to a user, group, or container

Purpose

Application objects assigned to a user, group, or container can be viewed using NetWare Administrator. The application objects may be assigned to launch when the user double-clicks the application icon, or may launch automatically when the Launcher is accessed.

To view the application objects assigned to a user, group, or container:

1.	From NetWare Administrator, select the user, group, or container.

2.	Select Object, Details.

3.	Select Applications from the button bar.


  What is an application object

Any DOS, Windows, Windows 95 or Windows NT executable can be designated as an application object. Application object icons appear in the NDS tree.

Application Class

DOS

Windows 3.x

Windows 95

Windows NT


What is the NetWare Application Manager?

The NetWare Application Launcher (NAL) allows users to run applications that were previously configured by a system administrator, and whose setup information is stored as an application object in the NetWare directory tree.

NAL displays icons for all available applications in a window, and lets the user double-click on an icon to launch an application.

Users don't need to worry about drive mappings, paths, or rights.  The administrator can manage the application launcher on a Container, Group, or User object level.


  Why would I use application objects

By creating application objects for your applications, you can manage which applications appear on the user's desktop. Using application objects simplifies the administrative tasks of assigning rights, customizing login scripts, and providing application support.

Application management

Using NetWare Administrator, applications for an entire organization, group, or user can be centrally administered. By configuring executables as application objects, the NetWare Administrator can perform upgrades and control versions of applications on the network.

Application access & rights

Assigning an application object to a container, group, or user object makes the application available to users who are trustees of the container, group, or user object.

Reduce drive mapping requirements  example

When launching the application, all network drive mappings, printer ports, and additional parameters are automatically configured. When the user exits the application, drive mappings and printer ports are returned to their original configuration.

Reduce login time  example

Because application objects configure their required resources when launched, system and user scripts can be reduced.

Provide application information and support contacts

Application information and support contacts can be assigned to each application object. The application information is available to users on their desktops.


Why would I use application objects related
Topic outline

Application management

Application access & rights

Reduce drive mapping requirements

Reduce login time

Provide application information and support contacts


drive mappings or print captures
These mappings and captures don't actually happen until the user launches the application. When the user closes the application, the mappings and captures are removed. The user can view (but not change) environment settings in the Application Launcher, by selecting File|Properties, and then Resources.

Syntax for mapping a drive:

D:=SERVER\VOLUME:PATH

D:=\\SERVER\VOLUME\PATH

D:=VOLUME_OBJECT_NAME:PATH

D:=DIRECTORY_MAP_OBJECT_NAME:PATH

Syntax for capturing a port:

LPT1:=SERVER\DS_QUEUE_NAME:

LPT2:=\\SERVER\DS_QUEUE_NAME

LPT1:=DS_QUEUE_NAME

LPT3:=\\\DS_QUEUE_NAME


Glossary

application class

browse button

e-mail

full path

schema

UNC path