An OnDemand Services installation can be divided into three basic components: the Web server environment, the Novell eDirectoryTM information, and the Maintenance and UsageServer processes. The following sections describe what is upgraded with each of these components:
Because of the architectural changes to OnDemand Services 2 and the use of Novell Portal Services, the OnDemand Services 1.5 Web server components (JSPs, etc.) are not upgradeable. Modifications you made to your OnDemand Services 1.5 JSPs will not be carried over to the OnDemand Services gadgets.
If you install OnDemand Services 2 into the same eDirectory tree where you installed OnDemand Services 1.5, the OnDemand Services Installation program will prompt you to upgrade the OnDemand Services 1.5 Package objects. Only software packages can be upgraded. If desired, you can choose not to upgrade your software packages, in which case you will need to create new OnDemand Services 2 packages for your software applications.
When a software package is upgraded, the Package object retains its cost information and its association with the application. For desktop (ZENworks for Desktops) or thin-client (DeFrame) applications, the application is associated with the Package object by its Application object being added to the object's Package Items list. To make the package a multi-application package (a new feature of OnDemand Services 2), you can add additional applications to the package after the upgrade. For Web applications (or music, video, or document files accessed through a URL), a Commerce Item object is created to define the application in eDirectory, and the Commerce Item object is added to the Package Items list in the Package object.
During installation, the Installation program will prompt you for a Packages container. Only packages that reside within the Package container (or its subcontainers) are available to users. If you upgrade your current software packages, you should specify the container where those software packages reside as your OnDemand Services 2 Packages container.
After you're packages are upgraded to OnDemand Services 2 packages, users can continue to access and launch them through your OnDemand Services 1.5 JSP interface until you have your OnDemand Services 2 portal interface ready to roll out. However, this is not a supported configuration and you should move away from it as quickly as possible.
The Maintenance and UsageServer processes, while retaining their same basic purpose and functionality, have been improved. You need to install the new processes, either to the same location as the existing processes or to a new location.
You can continue to run the OnDemand Services 1.5 Maintenance and UsageServer processes during the upgrade. After you've upgraded the eDirectory schema to OnDemand Services 2, you need to do the following: