The following sections list the requirements for OnDemand Services:
The OnDemand Services user interface is created through gadgets that plug in to Novell Portal Services (NPS) 1.5. The OnDemand Services gadgets must be installed to one of the server environments listed in the table below.
If you have already used the full version of NPS 1.5 to create an NPS 1.5 portal, you can install the OnDemand Services gadgets to that portal. Otherwise, OnDemand Services includes a runtime version of Novell Portal Services 1.5 that can be installed during installation. The runtime version includes limited functionality and only supports the OnDemand Services gadgets.
OnDemand Services includes two Java* processes, Maintenance and UsageServer. The Maintenance process cleans up purchase and usage records in Novell eDirectoryTM and closes out usage tracking of applications when the UsageServer becomes unavailable. It needs to be running at all times. The UsageServer process enables application usage to be tracked. It needs to be running if you want to be able to charge for an application based on the number of times or minutes it is used.
The OnDemand Services Maintenance and UsageServer processes can be installed on either a NetWare 5.1/6.0 server or a Windows NT*/2000 server. Because these are Java processes, the server must also have JVM 1.2.2 (or later) installed.
You can install the UsageServer and Maintenance processes to the Web server or to a different network server. Your decision should be based on the Web server's workload and processing power.
OnDemand Services requires eDirectory 8.5 or higher. We recommend that you have the latest release of the version you are using (8.5x, 8.6.x, etc.). The latest releases of these versions correct several issues with auxiliary classes (which are used by OnDemand Services) and provide better compatibility between eDirectory versions in a mixed eDirectory environment.
As you prepare your envinronment for OnDemand Services, please be aware of the following eDirectory requirements and issues:
NOTE: NDS 6/7 servers are capable of synchronizing the schema associated with auxiliary classes and can therefore coexist in the same tree. However, objects which have auxiliary classes on them are converted to "Unknown" objects on NDS 6/7 servers. These objects will be displayed as "Unknown" objects and this will prevent you from administering these objects when your primary connection is to a NDS 6/7 server. In addition, OnDemand users whose objects appear as "Unknown" will be unable to authenticate to the NDS 6/7servers
OnDemand Services requires ConsoleOne® 1.3.2 or higher. You can download the latest version of ConsoleOne from the Novell Downloads site.
In all areas of the eDirectory tree that will be accessed by OnDemand Services, you should make sure that object names (including container and leaf objects) do not include any of the following characters. These characters, when used in LDAP names (for example, cn=jsmith,ou=users,o=novell), will result in invalid syntax.
" (double quote) |
+ (plus) |
= (equals) |
\ (backslash) |
< (open angle bracket) |
; (semicolon) |
> (close angle bracket) |
/ (forwardslash) |
, (comma) |
# (pound sign) |
To distribute thin-client (terminal server) applications, OnDemand Services requires DeFrameTM 2.01. DeFrame 2.01 is included in the OnDemand Services package.
To distribute desktop applications, OnDemand Services requires ZENworks for Desktops (ZfD) 3.2.
The following table lists the desktop operating systems and Web browsers that OnDemand Services supports.
| Operating System | Web Browsers |
|---|---|
Windows 98 SE |
Microsoft* Internet Explorer 5.5 with SP2 |
Netscape* browsers are not supported by OnDemand Services in this release.
You should make sure that the latest support pack is applied to each of these software components.