Novell Documentation: Novell OnDemand Services 2 - OnDemand Services Installation Worksheet

OnDemand Services Installation Worksheet

Item	Description
1) Novell Portal Services 1.5 Requirement Continue: Yes No	OnDemand Services requires version 1.5 of Novell Portal Services (NPS). If NPS 1.5 is not installed, the Installation program will install a runtime version of NPS 1.5. You need to make sure to not install OnDemand Services to a pre-1.5 version of NPS. Doing so will cause the Installation program to overwrite the pre-1.5 version with the NPS 1.5 runtime version. Because the runtime version's functionality has been limited to support only OnDemand Services, you will lose any gadgets, pages, and so forth configured in your pre-1.5 NPS installation.
2) LDAP Server Login Server IP address or hostname: Admin user context: Admin user password:	The Installation program uses LDAP to access Novell eDirectory^TM. You need to supply the hostname or IP address of an LDAP server that can provide access to the eDirectory tree where you want to create the OnDemand Services objects. In addition, you need to provide the LDAP context and password of the Admin user (or Admin-equivalent user). Example: LDAP Server IP address or hostname: 123.456.78.90 Admin user context: cn=admin,o=novell Admin user password: bigredn
3) Company Root Container:	Specify the container you want to designate as the root container for your company. The OnDemand Services components begin user searches in this container, which means that the container must branch down to all OnDemand Services users. IMPORTANT: We recommend that, if possible, all objects associated with OnDemand Services (User objects, Application objects, Cost Center object, OnDemand Administrator object, OnDemandService object, and so forth) reside within the Company Root container or its subcontainers. This ensures that the OnDemand Administrator (ODSAdmin) object has the required rights to each of these objects. If you place any of these objects outside of the Company Root, you will need to manually assign rights to the ODSAdmin object. For instructions, see ODSAdmin Trustee Rights . If the container you want to use does not exist, the Installation program will let you create it. Example: o=novell
4) Packages Container:	Applications are made available to users through OnDemand Services packages. Specify the container where you want your Package objects to reside. This container becomes the OnDemand Services catalog root; any packages created (and enabled) within this container are made available to users. The container you specify must reside under the Company Root (see item 3). If the container you want to use does not exist, the Installation program will let you create it. Example: ou=packages,ou=services,o=novell
5) Cost Center Object name: Container:	When a user purchases a package, the purchase and usage charges are recorded against the user's cost center. Each user must belong to a cost center and you can have one or more cost centers. Because OnDemand Services requires at least one cost center, the Installation program lets you create one. Specify the name you want to use for the cost center object and the container where you want the object created. Do not use an & character in the name. If the container you want to use does not exist, the Installation program will let you create it. Example: Object name: CostCenter1178 Container: ou=services,o=novell
6) OnDemand Administrator Container: Password:	The OnDemand Services components authenticate and receive rights to eDirectory through the OnDemand Administrator object. This object is named ODSAdmin and cannot be changed. Specify the container where you want to create the ODSAdmin object and then supply the OnDemand Administrator password. If the container you want to use does not exist, the Installation program will let you create it. Example: ou=services,o=novell
7) OnDemandService Object Object name: Container: Mail server: Mail from: Mail subject:	The OnDemandService object contains e-mail and currency information required by other OnDemand Services components. Specify a name for the object (the default is OnDemandService) and and the container where you want the object created. If the container you want to use does not exist, the Installation program will let you create it. A mail server is required to send e-mail notifications for requested, approved, and denied packages. Specify the fully qualified host name of an SMTP server. Enter a valid e-mail address to include in the From line of e-mail notifications sent to users. Enter the text to include in the Subject line of the e-mail notifications. Example: Object name: OnDemandService Container: ou=services,o=novell Mail server: mailserver.novell.com Mail from: jsmith@novell.com Mail subject: ApprovalFlow Notification
8) Currency Code	Specify the currency code (for example, USD for United States Dollar or GBP for United Kingdom Pound Sterling) that you want associated with any monetary values displayed in OnDemand Services. The Installation program lets you select currency codes from a list. If you don't know your currency code, wait until you run the Installation program to select one from the list. Example: USD
9) Maintenance and Usage Server Platform NetWare^® Windows 2000	Select the operating system of the server where you will install the OnDemand Services Maintenance and UsageServer processes. The Maintenance process cleans up purchase and usage records (objects) in eDirectory. The UsageServer tracks application usage. Example: NetWare
10) Maintenance and UsageServer Installation Directory	Specify the server location where you want to install the Maintenance and Usage Server files. For a NetWare server, you need to use a drive mapped to the server's sys: volume. For a Windows server, you can select any location. The Installation program will create an ondemand directory structure in the location you specify. Example: z:\ondemand
11) Maintenance and UsageServer LDAP Configuration LDAP Server: Admin context: Container:	The Maintenance and UsageServer processes authenticate to eDirectory through LDAP. Specify the LDAP Server and Admin user (or Admin-equivalent user) you want the processes to use to authenticate. The Maintenance and UsageServer processes must know what container to use as the base context for purchase and usage records. The two processes restrict their processing to purchase and usage records located in the container and its subcontainers. Because purchase and usage records are stored as objects under Package objects, you can generally use the Packages container as the base context. Example: LDAP Server: 123.456.78.90 Admin context: cn=admin,o=novell Container: ou=packages,ou=services,o=novell
12) Maintenance and UsageServer LDAP Authentication Yes No	Specify whether the Maintenance and UsageServer processes should use the SSL protocol when communicating with the LDAP Server. Example: Yes
13) ConsoleOne^® Snap-Ins Installation Location	Specify the ConsoleOne location where you want to install the OnDemand Services snap-ins. The path must include the consoleone.jar file. The consoleone.jar file will not be modified. It is simply used to determine the installation locations. Example: c:\novell\consoleone\1.3\consoleone.jar
14) ZENworks Location	This item applies only if you have ZENworks for Desktops 3.2 installed. Select the ZENworks for Desktops server location where you want to install the ZENworks OnDemand Services UsageClient files. The UsageClient files are required to track usage of applications distributed through Novell Application Launcher. The files must be installed to the same directory as zenapp32.dll (typically sys:\public or c:\novell\public). Example: z:\public

Item

Description

1) Novell Portal Services 1.5 Requirement

Continue:

OnDemand Services requires version 1.5 of Novell Portal Services (NPS). If NPS 1.5 is not installed, the Installation program will install a runtime version of NPS 1.5.

You need to make sure to not install OnDemand Services to a pre-1.5 version of NPS. Doing so will cause the Installation program to overwrite the pre-1.5 version with the NPS 1.5 runtime version. Because the runtime version's functionality has been limited to support only OnDemand Services, you will lose any gadgets, pages, and so forth configured in your pre-1.5 NPS installation.

2) LDAP Server Login

Server IP address or hostname:
Admin user context:
Admin user password:

The Installation program uses LDAP to access Novell eDirectory^TM. You need to supply the hostname or IP address of an LDAP server that can provide access to the eDirectory tree where you want to create the OnDemand Services objects. In addition, you need to provide the LDAP context and password of the Admin user (or Admin-equivalent user).

Example:

LDAP Server IP address or hostname: 123.456.78.90
Admin user context: cn=admin,o=novell
Admin user password: bigredn

3) Company Root

Container:

Specify the container you want to designate as the root container for your company. The OnDemand Services components begin user searches in this container, which means that the container must branch down to all OnDemand Services users.

IMPORTANT: We recommend that, if possible, all objects associated with OnDemand Services (User objects, Application objects, Cost Center object, OnDemand Administrator object, OnDemandService object, and so forth) reside within the Company Root container or its subcontainers. This ensures that the OnDemand Administrator (ODSAdmin) object has the required rights to each of these objects. If you place any of these objects outside of the Company Root, you will need to manually assign rights to the ODSAdmin object. For instructions, see ODSAdmin Trustee Rights .

If the container you want to use does not exist, the Installation program will let you create it.

Example: o=novell

4) Packages

Container:

Applications are made available to users through OnDemand Services packages. Specify the container where you want your Package objects to reside. This container becomes the OnDemand Services catalog root; any packages created (and enabled) within this container are made available to users. The container you specify must reside under the Company Root (see item 3).

If the container you want to use does not exist, the Installation program will let you create it.

Example: ou=packages,ou=services,o=novell

5) Cost Center

Object name:
Container:

When a user purchases a package, the purchase and usage charges are recorded against the user's cost center. Each user must belong to a cost center and you can have one or more cost centers.

Because OnDemand Services requires at least one cost center, the Installation program lets you create one. Specify the name you want to use for the cost center object and the container where you want the object created. Do not use an & character in the name.

If the container you want to use does not exist, the Installation program will let you create it.

Example:

Object name: CostCenter1178
Container: ou=services,o=novell

6) OnDemand Administrator

Container:
Password:

The OnDemand Services components authenticate and receive rights to eDirectory through the OnDemand Administrator object. This object is named ODSAdmin and cannot be changed. Specify the container where you want to create the ODSAdmin object and then supply the OnDemand Administrator password.

If the container you want to use does not exist, the Installation program will let you create it.

Example: ou=services,o=novell

7) OnDemandService Object

Object name:
Container:
Mail server:
Mail from:
Mail subject:

The OnDemandService object contains e-mail and currency information required by other OnDemand Services components.

Specify a name for the object (the default is OnDemandService) and and the container where you want the object created. If the container you want to use does not exist, the Installation program will let you create it.

A mail server is required to send e-mail notifications for requested, approved, and denied packages. Specify the fully qualified host name of an SMTP server.

Enter a valid e-mail address to include in the From line of e-mail notifications sent to users.

Enter the text to include in the Subject line of the e-mail notifications.

Example:

Object name: OnDemandService
Container: ou=services,o=novell
Mail server: mailserver.novell.com
Mail from: jsmith@novell.com
Mail subject: ApprovalFlow Notification

8) Currency Code

Specify the currency code (for example, USD for United States Dollar or GBP for United Kingdom Pound Sterling) that you want associated with any monetary values displayed in OnDemand Services. The Installation program lets you select currency codes from a list. If you don't know your currency code, wait until you run the Installation program to select one from the list.

Example: USD

9) Maintenance and Usage Server Platform

NetWare^®
Windows 2000

Select the operating system of the server where you will install the OnDemand Services Maintenance and UsageServer processes. The Maintenance process cleans up purchase and usage records (objects) in eDirectory. The UsageServer tracks application usage.

Example: NetWare

10) Maintenance and UsageServer Installation Directory

Specify the server location where you want to install the Maintenance and Usage Server files. For a NetWare server, you need to use a drive mapped to the server's sys: volume. For a Windows server, you can select any location. The Installation program will create an ondemand directory structure in the location you specify.

Example: z:\ondemand

11) Maintenance and UsageServer LDAP Configuration

LDAP Server:
Admin context:
Container:

The Maintenance and UsageServer processes authenticate to eDirectory through LDAP. Specify the LDAP Server and Admin user (or Admin-equivalent user) you want the processes to use to authenticate.

The Maintenance and UsageServer processes must know what container to use as the base context for purchase and usage records. The two processes restrict their processing to purchase and usage records located in the container and its subcontainers. Because purchase and usage records are stored as objects under Package objects, you can generally use the Packages container as the base context.

Example:

LDAP Server: 123.456.78.90
Admin context: cn=admin,o=novell
Container: ou=packages,ou=services,o=novell

12) Maintenance and UsageServer LDAP Authentication

Specify whether the Maintenance and UsageServer processes should use the SSL protocol when communicating with the LDAP Server.

Example: Yes

13) ConsoleOne^® Snap-Ins Installation Location

Specify the ConsoleOne location where you want to install the OnDemand Services snap-ins. The path must include the consoleone.jar file. The consoleone.jar file will not be modified. It is simply used to determine the installation locations.

Example: c:\novell\consoleone\1.3\consoleone.jar

14) ZENworks Location

This item applies only if you have ZENworks for Desktops 3.2 installed.

Select the ZENworks for Desktops server location where you want to install the ZENworks OnDemand Services UsageClient files. The UsageClient files are required to track usage of applications distributed through Novell Application Launcher. The files must be installed to the same directory as zenapp32.dll (typically sys:\public or c:\novell\public).

Example: z:\public