The following sections provide information to help you deploy Application Management:
Application Management requires users to have the Novell Client installed on their workstations. The client version must meet the following requirements:
You can roll out the Novell Client to users before you begin installing Application Management. Both Novell Clients listed above are compatible with ZENworks for Desktops 2.
For information about installing the Novell Client, see the Novell Client documentation at the Novell Documentation Web site.
To extend the schema of an NDS tree to support the Application Management objects and properties or to install the Application Management software to one or more servers, complete the tasks in the following sections:
Before you can install Application Management, you must perform the following tasks:
To install Application Management:
Select a network workstation where you can later run ConsoleOne to administer Application Management. This is the workstation where you will run the installation program.
IMPORTANT: Make sure that this workstation and all other administrative workstations are not running ConsoleOne while the installation program is running.
At the workstation, insert the ZENworks for Desktops Program CD.
The WINSETUP.EXE program will autorun. If it does not autorun, run it from the root of the CD.
Click English > Install ZENworks to launch the NIS setup program.
Follow the prompts until you reach the ZENworks Install Types dialog box.
In the ZENworks Install Types dialog box, select Custom > click Next.
In the Components dialog box, deselect all components except Application Management > click Next.
IMPORTANT: If you want to install the Sybase database to enable storing of Application Management events in the database, select Sybase in addition to Application Management. For more information about Sybase and Application Management reporting, see Sending Events to a Database.
In the ZENworks Part Selection dialog box, select the parts (Files, Schema Extensions, and NDS Objects) you want to install > click Next.
IMPORTANT: If you have not previously installed ZfD 3 Application Management, you should select all three parts. If you have already installed to the tree and are simply installing the software files to another server in the tree, select the Files option only.
In the ZENworks List of Trees dialog box, select the NDS tree where you want to install Application Management > click Next.
In the ZENworks List of Servers dialog box, select the servers where you want to install Application Management > click Next.
For information about where you should install Application Management, see Selecting NDS Trees and Network Servers.
If you are installing the Sybase database, the Database Server Selection dialog box is displayed. Click the name of the server where you want to install the database > click Next > select the server volume > click Next.
In the Languages dialog box, select the language to install > click Next.
If you are installing the Sybase database, the Site ID for Database dialog box is displayed. Enter a site ID (a number between 0 and 255) and site name (cannot include underscore (_) characters) > click Next.
In the Summary dialog box, review the products to be installed > click Finish > follow the prompts to complete the installation.
Once you've installed Application Management, you can start Application Launcher or Application Explorer on users' workstations. The following sections explain the rights required by Windows NT/2000 users, how to manually start the applications, and how to automate the starting of the applications:
Application Launcher/Explorer needs to be able to copy files to the workstation, write to the Windows registry, and so forth.
On Windows NT, users need to be members of the Users group to receive all the required rights
On Windows 2000, users need to be members of the Power Users group.
You can run either Application Launcher or Application Explorer on a workstation. Do not run both on the same workstation.
To manually start Application Launcher or Application Explorer on a workstation:
Make sure that the Novell Client for Windows 95/98 (version 3.3 with SP4 or later) or the Novell Client for Windows NT/2000 (version 4.8 with SP4 or later) is installed on the workstation. For information, see Rolling Out the Novell Client.
To start Application Launcher, run NAL.EXE from the SYS:\PUBLIC directory on a server where you installed Application Management.
NAL.EXE copies Application Launcher files to the workstation and starts Application Launcher. For details about Application Launcher files, see Setting Up Application Launcher/Explorer in Administration.
To start Application Explorer, Run NALEXPLD.EXE from the SYS:\PUBLIC directory on a server where you installed Application Management.
NALEXPLD.EXE copies Application Explorer files to the workstation and starts Application Explorer. For details about Application Explorer files, see Setting Up Application Launcher/Explorer in Administration.
You can run either Application Launcher or Application Explorer on a workstation. Do not run both on the same workstation.
To automatically start Application Launcher each time a user logs in to NDS:
Make sure that the Novell Client for Windows 95/98 (version 3.3 with SP4 or later) or the Novell Client for Windows NT/2000 (version 4.8 with SP4 or later) is installed on the workstation. For information, see Rolling Out the Novell Client.
To use Application Launcher, enter the following line in the user's login script:
@\\servername\sys\public\nal.exe
where servername is the actual name of your network server.
You can enter this line in a container, profile, or user login script. If the login script also contains an entry for the Automatic Client Upgrade (ACU), make sure the NAL.EXE entry is listed before the ACU entry.
To use Application Explorer, enter the following line in the user's login script:
@\\servername\sys\public\nalexpld.exe
where servername is the actual name of your network server.
You can enter this line in a container, profile, or user login script. If the login script also contains an entry for the Automatic Client Upgrade (ACU), make sure the NALEXPLD.EXE entry is listed before the ACU entry.
You can also add Application Launcher or Application Explorer to the Windows Startup folder. This enables Application Launcher/Explorer to start when the workstation is disconnected from NDS. You configure this option in ConsoleOne and can have it apply to a single user, a group of users, or all users in a container. To do so, right-click a User, Group, or container object > click Properties > click the Application Launcher tab. On the Application Launcher page, click Edit > click the User tab > scroll to select the Auto-Start NAL When Disconnected option > set the option to Yes.
You can set up software metering as part of Application Management deployment or you can implement it at a later time. If you want to set up software metering at this time, complete the following tasks:
As with software metering, you can set up event reporting as part of Application Management deployment or you can implement it at a later time.
See the following sections for information about setting up the type of event reporting you want:
To set up database reporting, you need to complete the following tasks:
If you are using the Sybase database that comes with ZfD and have already installed it, the installation program creates the database object in NDS. You can skip to the next section, Configuring the Database's JDBC and ODBC Information.
If you are using another database, such as the Oracle* database that comes with NetWare 5.1, you will need to create a ZENworks Database object in NDS to represent the database.
To create a ZENworks Database object:
Right-click the container in which you want to create the object > click New > click Object to display the New Object dialog box.
Select ZENworks Database > click OK to display the New ZENworks Database dialog box.
In the Name box, type a name for the database, such as ZfDAppManReports.
Select the Define Additional Properties box > click OK.
In the Server DN field, browse for and select the Server object for the server where the database is physically installed and running.
If you want to set up Read-Write, Read-Only, or Write-Only users, enter information in the appropriate username and password fields.
Click OK to save the information.
ConsoleOne uses a JDBC driver to pull information from the database for a set of predefined Application Management reports. If you want to use these predefined reports, you need to configure the ZENworks Database object with the correct JDBC driver information.
Application Launcher/Explorer uses an ODBC driver to write event information to the database. You need to configure the ZENworks Database object with the ODBC driver information that Application Launcher/Explorer will need.
To provide the JDBC and ODBC information:
Right-click the ZENworks Database object > click Properties.
Click the JDBC Driver Information tab.
If you are using a Sybase or Oracle database, click the appropriate Populate option > click Populate Now to automatically populate the fields with the default information for a Sybase or Oracle database.
or
If you are using a different type of database, fill in the fields with the appropriate information for your database. Click the Help button for a description of each field.
Click the ODBC Driver Information tab. Fill in the following fields:
Driver File Name: Enter the name of the ODBC driver file that resides on the workstation to enable Application Launcher/Explorer to access the database. For Sybase, the driver file name is DBODBC6.DLL.
Data Source Name: Enter NAL Reporting.
Connection Parameters: Enter the appropriate commands to connect to the database. For Sybase, these commands are:
CommLinks=TCPIP{Host=IPAddress:2638};AutoStop=Yes;Integrated=No;DBN=NAL;ENG=IPAddress
where IPAddress is the actual IP address of the server where the database resides.
Click OK to save the JDBC and ODBC driver information.
You need to grant users Read and Compare rights to the ODBC properties you defined for the ZENworks Database object in the previous section. This allows Application Launcher/Explorer to retrieve the ODBC information it needs to access the database.
To grant rights:
Right-click the ZENworks Database object > click Trustees of This Object.
Click Add Trustee.
Select [PUBLIC] > click OK to add [PUBLIC] to the list of trustees.
Adding [PUBLIC] as a trustee gives every user Read and Compare rights to all of the database object's properties, including the various usernames and passwords that can be used to access the database. To avoid this, you need to limit the [PUBLIC] access to the three ODBC properties.
In the Property list, select [All Attribute Rights] > click Delete Property to remove it from the list.
Click Add Property to display the Add Property dialog box > select zendbODBCConnectionParameters > click OK to add it to the Property list.
The default rights, Read and Compare, are sufficient. You do not need to change these rights.
Repeat Step 5 to add the following two properties: zendbODBCDataSourceName and zendbODBCDriverFileName. Keep the default rights (Read and Compare).
Click OK > OK to save the changes.
Before Application Management can use the database, you need to:
To enable the ZENworks Database policy:
In ConsoleOne, right-click the Service Location Package you want to use > click Properties.
or
If you do not have a Service Location Package, right-click the container where you want to create one > click New > click Policy Package. Follow the instructions provided in the Policy Package Wizard to create a Service Location Package.
On the General page, check the box in the Enabled column to enable the ZENworks Database policy.
Select the ZENworks Database policy in the list > click Properties.
Click the Application Management tab.
In the Database DN field, browse for and select the ZENworks Database object you want to use for Application Management reporting. This should be the same object you configured in Configuring the Database's JDBC and ODBC Information.
Click OK to return to the General page.
Click Associations to display the Associations page.
You use this page to associate the Service Location Package with the containers where Application objects reside. If you have Application objects in multiple containers, make sure to add all containers to the list (unless you don't want events reported for applications in those containers, or want to use another database for those applications' events). If a parent container includes several containers where Application objects reside, you can select the parent container rather than each individual container.
Click Add > browse for and select the container you want to add > click OK to add it to the list.
Repeat Step 8 to add additional containers.
When you've finished adding containers, click OK to save the information.
Event reporting is configured on a per-application basis. You can choose which objects you want to collect event reports for and which ones you don't.
You use an Application object's Reporting page (Common tab) to configure which events are reported and to instruct Application Launcher/Explorer to save them to the database. For detailed instructions, see Reporting on Application Management Events in Administration.
Application Management includes a set of predefined reports for you to use. There are six basic reports that let you report on the success or failure of an event either by application, by user, or by workstation. For example, you could use the Failure by App report to view a list of all application distributions, sorted by user, that failed. Or you could use the Failure by User to view a list of all application launches, sorted by user, that failed.
IMPORTANT: Before you can generate an Application Management report from the ZENworks database, the database needs to include at least one Application Management event. To generate an event, configure an Application object to use database reporting (see Configuring Application Objects to Use Database Reporting) and then perform a task with the application (distribute, uninstall, cache, or so forth) that will create an event report.
To access the predefined reports:
Right-click the ZENworks Database object > click Reporting.
In the Available Reports list, expand the ZENworks NAL Reports category > select the report you want.
In the Event Type list, select the event you want to include in the report.
Click Run Selected Report.
To set up SNMP trap reporting, you need to complete the following tasks:
Before Application Management can use SNMP traps for event reporting, you need to:
To do so, complete the following steps:
In ConsoleOne, right-click the Service Location Package you want to use > click Properties.
or
If you do not have a Service Location Package, right-click the container where you want to create one > click New > click Policy Package. Follow the instructions provided in the Policy Package Wizard to create a Service Location Package.
On the General page, check the box in the Enabled column to enable the SNMP Trap Targets policy.
Select the policy in the list > click Properties to display the SNMP Trap Targets list.
Click Add to display the SNMP Target dialog box > enter the IP address of the workstation or server where the management console is running > click OK to add the IP address to the list.
Repeat Step 4 to add additional targets.
When you've finished adding targets, click OK to return to the General page.
Click Associations to display the Associations page.
You use this page to associate the Service Location Package with the containers where Application objects reside. If you have Application objects in multiple containers, make sure to add all containers to the list (unless you don't want events reported for applications in those containers, or want to use another management console for those applications' events). If a parent container includes several containers where Application objects reside, you can select the parent container rather than each individual container.
Click Add > browse for and select the container you want to add > click OK to add it to the list.
Repeat Step 8 to add additional containers.
When you've finished adding containers, click OK to save the information.
Event reporting is configured on a per-application basis. You can choose which objects you want to collect event reports for and which ones you don't.
You use an Application object's Reporting page (Common tab) to configure which events are reported and to instruct Application Launcher/Explorer to send them as SNMP traps. For detailed instructions, see Reporting on Application Management Events in Administration.
To set up log file reporting, you need to complete the following tasks:
With log file reporting, you have two options. You can have Application Launcher/Explorer log events for each individual user to a file on the user's local driver, or you can have Application Launcher/Explorer log events for all users to a file in a common network location.
If you want Application Launcher/Application Explorer to log events to a file in a common network location, you need to establish the network directory and provide users with Read and Write rights to files in the directory.
Because log file names are established on a per-application basis, you can have individual log files for each application (by specifying a different log file name for each Application object) or one log file for all applications (by specifying the same log file name for all Application objects). You cannot have log files on a per-user basis, unless you have Application Explorer/Launcher save the files to the users' local drives.
Event reporting is configured on a per-application basis. You can choose which applications you want to collect event reports for and which ones you don't.
You use an Application object's Reporting page (Common tab) to configure which events are reported and to instruct Application Launcher/Explorer to log them to a text file. For detailed instructions, see Reporting on Application Management Events in Administration.
As you configure the location for the log file that will be used for an application's events (using the Application object's Reporting page), make sure you enter a network location for the log file if you want events for all users logged to the same file, and that all users have Read and Write rights to the network location. If you want each user to have an individual log file for the application, enter a path on the users' local drives (for example, C:\TEMP).