Before starting the OnDemand Services Installation program, you might want to gather the information you will be prompted for. This information is described in Installation Worksheets .
You can print the worksheets to record your information, or you can simply review the worksheets to see the information you will be prompted for.
Complete the tasks in the following sections to install the OnDemand Services software:
Complete the steps in this section if you don't already have an existing Novell Portal Services (NPS) 1.5 portal where you want to install the OnDemand Services gadgets.
Make sure you are at a Windows workstation that has drive mappings to the server locations where you will install files.
If you are installing any OnDemand Services components to a Windows 2000 server, we recommend that you install from that server.
Make sure the LDAP server is configured for Clear Text Passwords. OnDemand Services requires this.
Insert the Novell ZENworks OnDemand Services 2 CD.
Run odsetup.exe from the \ondemand directory to display the Introduction page.
NOTE: If you copy the odsetup.exe file from the CD to another location and attempt to run it from there, it will fail unless you copy the entire \ondemand directory structure.
At the Introduction page, click Next to display the License Agreement page.
After reviewing the license information, select I Accept the Terms of the License Agreement > click Next to display the Installation Type page.
The Installation program provides two installation options: Typical and Custom. At this point, you should use the Typical option unless you don't have ZENworks for Desktops (ZfD) 3.2 installed. The Typical option installs the OnDemand Services component that provides usage tracking of desktop applications. If you don't have ZfD 3.2, you shouldn't install this component.
To install all components, click Typical, then click Next to display the Novell Portal Services 1.5 Requirement page.
or
To deselect the OnDemand Components for ZENworks, click Custom, deselect the component, then click Next to display the Novell Portal Services 1.5 Requirement page.
The Novell Portal Services 1.5 Requirement page warns you that OnDemand Services requires NPS l.5. You should not attempt to install OnDemand Services to an earlier NPS version.
Click Yes to continue with the installation.
or
Click No to exit the Installation program.
Follow the prompts to complete the installation. If you filled out the worksheets (see Installation Worksheets ), use the information you recorded.
Two installation log files are saved to the c:\documents and settings\username\local settings\temp directory. The novell_zenworks_ondemand_services_2_installlog.xml file contains information about where files were installed. The ondemandinstall.log file contains information about schema extensions added to the Novell eDirectoryTM tree.
Installing the Software (excluding NPS 1.5 Runtime)
When using an existing NPS 1.5 portal for OnDemand Services, before beginning the OnDemand Services installation you need to take precautions to ensure that your existing NPS 1.5 portal will not accidently be overwritten with the NPS 1.5 runtime version included with OnDemand Services. The following sections, Locating the Nps.pdt File and Verifying the Nps.pdt Information , explain what you need to do. After you've reviewed the information in these sections, continue with Running the Installation Program .
Locating the Nps.pdt File
During installation, the OnDemand Services Installation program launches the Novell Portal Services (NPS) 1.5 Installation program. The NPS 1.5 Installation program is designed to install the NPS 1.5 runtime version if it does not detect an existing NPS 1.5 portal. The way it detects an existing installation is through the presence of an NPS.PDT file.
When NPS 1.5 is installed to a NetWare® server, the NPS.PDT file is created in the server's sys:\system directory regardless of whether the NPS installation was performed from a Windows workstation or from the NetWare server console. If you are installing the OnDemand Services gadgets to an existing NPS portal on a NetWare server, there are no issues with locating the nps.pdt file. The NPS 1.5 runtime version's Installation program will find the nps.pdt file regardless of the Windows workstation where you perform the OnDemand Services installation.
When NPS1.5 is installed to a Windows server, the nps.pdt file is created on the C: drive of the Windows machine from which you performed the NPS installation. If the installation was performed on the Windows server, the nps.pdt file will be on the server's C: drive. If the installation was performed from another Windows workstation, it will be on that workstation's C: drive. If you are installing the OnDemand Services gadgets to a Windows server, you need to ensure that the correct nps.pdt file is being found. Otherwise, your existing NPS portal will be overwritten by the NPS 1.5 runtime version. To ensure that this does not happen, you have the following options:
Run the OnDemand Services Installation program from the same machine used to install NPS 1.5. Check the C:\ directory to ensure that the nps.pdt file is present.
Copy the nps.pdt file from the NPS 1.5 installation machine to the C:\ drive of the machine you will use to run the OnDemand Services Installation program.
Deselect the Installation program option to install the OnDemand Services gadgets and then manually install the gadgets. This allows you to ignore where the nps.pdt file is located.
Verifying the Nps.pdt Information
The nps.pdt file contains several pieces of information that you need to make sure you correctly match when running the NPS 1.5 runtime version's Installation program. To verify the exact information you need to enter:
Open the nps.pdt file in a text editor.
Verify the information in the following properties:
NPSWebServerAddress: When the NPS Installation program prompts you for the Web server's address, you need to enter it exactly as recorded in this property. Otherwise, the Installation program will not recognize the existing NPS portal and will overwrite it. In addition, if the address is a NetWare server name rather than IP address, you need to add the server name to the Windows workstation's hosts file (typically in c:\winnt\system32\drivers\etc) so that it can resolve the server name to the correct IP address.
NPSDir: Make sure the path listed in this property is correct from the perspective of the machine where you will run the OnDemand Services Installation program. For example, for a NetWare server, you would need to change the directory path from sys:webapps\nps to \\server_name\sys\webapps\nps.
NPSLDAPDir: Make sure the address for the LDAP server that will access eDirectory is correct.
Save the file.
Running the Installation Program
To install the software:
Make sure you are at a Windows workstation that has drive mappings to the server locations where you will install files.
If you will be installing the OnDemand Services gadgets to an existing NPS 1.5 portal on a Windows 2000 server, we recommend that you install from that server.
Make sure the LDAP server is configured for Clear Text Passwords. OnDemand Services requires this.
If you will have the OnDemand Services Installation program install the OnDemand Services gadgets to an existing NPS 1.5 portal, make sure the nps.pdt file, as explained in Locating the Nps.pdt File above, is in the C:\ directory.
Insert the Novell ZENworks OnDemand Services 2 CD.
Run odsetup.exe from the \ondemand directory to display the Introduction page.
NOTE: If you copy the odsetup.exe file from the CD to another location and attempt to run it from there, it will fail unless you copy the entire \ondemand directory structure.
At the Introduction page, click Next to display the License Agreement page.
After reviewing the license information, select I Accept the Terms of the License Agreement, then click Next to display the Installation Type page.
The Installation program provides two installation options: Typical and Custom. At this point, you should use the Typical option unless:
You want to manually install the OnDemand Services gadgets to an existing NPS 1.5 portal rather than having the Installation program do it. In this case, select Custom and deselect the OnDemand Services Gadgets option.
You don't have ZENworks for Desktops (ZfD) 3.2 installed so you don't need to install the OnDemand Services component that provides usage tracking of desktop applications. In this case, select Custom and deselect the OnDemand Components for ZENworks option.
To install all components, click Typical, then click Next to display the Novell Portal Services 1.5 Requirement page.
or
To install selected components only, click Custom, click Next, deselect the components you do not want to install, then click Next to display the Novell Portal Services 1.5 Requirement page.
The Novell Portal Services 1.5 Requirement page warns you that OnDemand Services requires NPS l.5. You should not attempt to install OnDemand Services to an earlier NPS version.
NOTE: If you deselected the OnDemand Services Gadgets componen,t the Novell Portal Services Requirements page is not displayed. Skip to Step 10.
Click Yes to continue with the installation.
or
Click No to exit the Installation program.
Follow the prompts to complete the installation. If you filled out the worksheets (see Installation Worksheets ), use the information you recorded.
IMPORTANT: If you have chosen to install the OnDemand Services gadgets, the NPS Installation program will be launched after you've provided the OnDemand Services information. After entering the Web server's address, you should only be prompted for the Admin user's context and password and for the context where you want the gadgets to be created. If you are prompted for additional information, such as the Web server's operating system, type, and Web Application server, either you did not enter the Web server's address exactly as it is recorded in the NPSWebServerAddress property in the nps.pdt file or the file is not in the expected location. Reenter the Web Server address or verify that the file is in the C:\ directory. If this does not solve the problem, you should cancel the NPS installation. Continuing the installation will result in your existing NPS 1.5 portal being overwritten. After you've cancelled the NPS installation and finished the OnDemand Services installation, see Manually Installing the OnDemand Services Gadgets .
To manually install the gadgets to an existing NPS 1.5 portal:
Use a zip utility (for example, WinZip*) to extract the nine OnDemand Services gadget package (.npg) files from the ondemand.npa file. The ondemand.npa file is located in the \ondemand\gadgets\ondemand directory on the ZENworks OnDemand Services 2 CD.
Log in to NPS as an administrator.
Click Administer the Portal.
Click Gadget, then click Create.
Enter a name for the gadget you want to create. OnDemand Services includes the following gadgets:
ConfigWizardGadget: Used to store the OnDemand Administrator (ODSADMIN) context and password information in a place where the other gadgets can get it in order to authenticate. You must run the Configuration Wizard before any other OnDemand Services gadgets will work. Recommended gadget name: OD_ConfigWizardGadget.
UserAdminGadget: Used to create, modify, enable, and disable user accounts, and to assign packages to users. Recommended gadget name: OD_UserAdminGadget.
ApprovalGadget: Used to approve or deny user requests for packages. Recommended gadget name: OD_ApprovalGadget.
CurrentBHGadget: Used to select which budget holder is the currently active budget holder and to add or remove budget holders. Recommended gadget name: OD_CurrentBHGadget.
PackageRequestGadget: Used to request packages. Recommended gadget name: OD_PackageRequestGadget.
EditAccountGadget: Used to edit user account information (for example, name, password, and e-mail address). Recommended gadget name: OD_EditAccountGadget.
WorkflowTrackingGadget: Used to check the status of package requests and to cancel requests. Recommended gadget name: OD_WorkflowTrackingGadget.
LaunchItemGadget: Used to launch applications. Recommended gadget name: OD_LaunchItemGadget.
ReportGadget: Used to create reports showing purchase and usage costs for packages. Recommended gadget name: OD_ReportGadget.
Browse to the location where you extracted the gadget's package file (.npg) and select the file. The following table lists the package filenames for the gadgets.
Gadget
Package Filename
ConfigWizardGadget
OD_ConfigWizardGadget.npg
UserAdminGadget
OD_UserAdminGadget.npg
ApprovalGadget
OD_ApprovalGadget.npg
CurrentBHGadget
OD_CurrentBHGadget.npg
PackageRequestGadget
OD_PackageRequestGadget.npg
EditAccountGadget
OD_EditAccountGadget.npg
WorkflowTrackingGadget
OD_WorkflowTrackingGadget.npg
LaunchItemGadget
OD_LaunchItemGadget.npg
ReportGadget
OD_ReportGadget.npg
Click Create, then click OK to add the gadget to the gadgets list.
Repeat Step 4 through Step 7 until you've created all of the OnDemand Services gadgets.
Enabling Purchased Desktop or Thin-Client Applications to be Associated with Users
This section applies only if you are using ZENworks for Desktops (ZfD) 3.2 to provision desktop applications or Novell DeFrameTM 2.01 to provision thin-client applications.
OnDemand Services uses a ZfD 3.2 support library to associate desktop and thin-client applications with users who have purchased the applications. On a NetWare server, the support library is zenapp32.nlm. On a Windows server, it is zenapp32.dll. This support library must reside on the server where your NPS 1.5 portal (with the OnDemand Services gadgets) is located.
If your NPS 1.5 portal is on a NetWare server, you should have installed the zenapp32.nlm to the sys:\system directory on that server when you ran the OnDemand Services Installation program. If you did not or you installed the OnDemand Services gadgets to multiple NPS NetWare servers, you need to copy the zenapp32.nlm file to the NetWare server or servers. See Copying Zenapp32.dll or Zenapp32.nlm to the NPS Server below for instructions.
If your NPS 1.5 portal is on a Windows server, you need to complete the tasks in the following sections to ensure that OnDemand Services has access to zenapp32.dll and that the DLL has appropriate eDirectory access:
Logging in as a User Who Has Trustee Rights to Application Objects
To associate an application with a user, zenapp32.dll needs to have rights to the Application object in eDirectory. This requires the following:
The Novell ClientTM to be installed on the Windows server.
A user login from the Windows server to eDirectory. The eDirectory user account must provide rights to all Application objects. By default, the ODSAdmin user (created during installation) has all required rights. You can log in as the ODSAdmin user or any other user with the required rights (Admin, for example).
Copying Zenapp32.dll or Zenapp32.nlm to the NPS Server
If zenapp32.dll is not already installed on the Windows server where your NPS portal and OnDemand Services gadgets reside, you can use either of the following methods to install it:
Copy the file from the sys:\public directory of an existing ZENworks server to the NPS Windows server and then add the zenapp32.dll directory to the server's PATH variable (if necessary).
Modify the ODSAdmin user's login script (or the login script of the user account the Windows server is using to log into eDirectory) to launch Novell Application LauncherTM. This will cause Novell Application Launcher, including zenapp32.dll, to be copied from the specified ZENworks server to the NPS Windows server. For instructions, see Application Management in the ZENworks for Desktops 3.2 Administration Guide at the Novell Documentation Web site.
IMPORTANT: You must use a version of zenapp32.dll dated 1/31/2002 or later. Using an earlier version will cause launched applications to fail.
If zenapp32.nlm is not already installed on the NetWare server where your NPS portal and OnDemand Services gadgets reside, you need to:
Copy the file from the ondemand\services\system directory on the Novell ZENworks OnDemand Services 2 CD to the sys:\system directory of the NetWare server.
Applying Support Pack 1
OnDemand Services 2 Support Pack 1 resolves a variety of issues and increases the reliability and stability of OnDemand Services 2. We recommend that you apply the support pack to the software components you just installed.
To update the OnDemand Services software, follow the instructions included in the support pack's Readme_ods2sp1.txt file.
Increasing the Tomcat Servlet Engine's Heap Size
To ensure that the Tomcat Java servlet engine has sufficient memory to operate properly, you need to increase its initial heap size.
The amount you increase the Java servlet engine's heap size is dependent on the server's available memory, the number of OnDemand Services users that will be supported, and so forth. We recommend that the minimum heap size memory allocation be no less than 128 MB for the first 200 users and that you increase the allocation by 64 MB for every 200 additional users. The maximum heap size memory allocation should be limited only by the amount of the server's memory you want allocated to the Java process.
NetWare Server
To modify the Java servlet engine's heap size:
Open the tomcat33.ncf file, located in the sys:\tomcat\33\bin directory.
On the Java line, change the initial heap size memory allocation parameter (Xms), the maximum heap size memory allocation parameter (Xmx), and the heap size buffer allocation parameter (Xss).
The following example shows the recommended parameter settings for supporting up to 200 users.
-Xms128m -Xmx400m -Xss256k
The maximum heap size parameter (Xmx) should reflect the maximum amount of the server's memory you want used by the Java servlet engine. On NetWare, this amount cannot exceed 400 MB; if you enter a value greater than 400, the Java servlet engine will revert to using only 32 MB.
Open the tomcat.bat file, located in the c:\jakarta_tomcat-3.3x\bin directory.
Add the following settings to the TOMCAT_OPTS environment variable. If the file doesn't include a TOMCAT_OPTS environment variable, you will need to add it.
set TOMCAT_OPTS= -Xms128m -Xmx512m -Xss256k
The above example shows the recommended initial heap size memory parameter (Xms) setting for supporting up to 200 users.The maximum heap size parameter (Xmx) should reflect the maximum amount of the server's memory you want used by the Java servlet engine.
If you want to support extended characters, you need to configure the Tomcat servlet engine and Novell Portal Services to support extended characters.
Configuring the Tomcat Servlet Engine
For the Tomcat servlet engine to support extended characters (for example, in package and application names displayed in the OnDemand Services gadgets), you need to enable extended character support.
On a NetWare server, open the nwserver.xml file, located in the sys:\tomcat\33\conf directory.
or
On a Windows 2000 server, open the server.xml file, located in the c:\tomcat\conf directory.
![OnDemand Services Installation program[apos ]s Introduction page](../graphics/ods_install1.gif)