The OnDemand Services Installation program launches the Novell Portal Services (NPS) Installation program. The NPS Installation program will either 1) install NPS (the runtime version) and the OnDemand Services gadgets or 2) install only the OnDemand Services gadgets if an existing NPS 1.5 portal already exists.
The following table lists the information the NPS Installation program will prompt you for. If the NPS 1.5 runtime version is being installed, you will be prompted for all of the information. If NPS 1.5 is already installed, you will be prompted for items 1, 5, and 10.
1) Web Server Address |
Enter the IP address or DNS hostname of the Web server where you will install NPS. Example: services.novell.com |
2) System Configuration - Operating system:
- Web server:
- Web App server:
|
Specify the operating system (NetWare 6.0 or Windows 2000) where the Web server is running. Specify the type of Web server being used. OnDemand Services requires Apache or IIS. Specify the Web Application server being used. OnDemand Services requires Tomcat. Example: - Operating system: NetWare 6.0
- Web server: Apache
- Web App server: Tomcat
|
3) Protocol, Port, and Web Apps Location |
Specify the communication protocol (HTTP or HTTPS) you want NPS to use. Specify the port number to be used. If you select HTTP as the protocol, the port defaults to port 80. If you select HTTPS, the port defaults to 443. These are the standard ports for these two protocols. Specify the directory where the Web Application server files are installed. Example: - Protocol: HTTPS
- Port: 443
- Web Apps: \\npsserver\sys\webapps
|
4) Web App Server Information |
Depending on the Web Application server you are using, you might be prompted for additional Web Application server information. For example, if you are using Tomcat, you will be prompted for the path to the Tomcat configuration file. |
5) LDAP Directory Server and Credentials - Server and port:
- Admin distinguished name:
- Admin password:
|
The NPS Installation program requires access to eDirectory to update the directory. This access must be through LDAP. Specify the IP address/hostname and port number of the LDAP server that can provide directory access. The standard non-SSL LDAP port is 389. The standard SSL LDAP port is 636. Specify the distinguished name and password of the Admin user. Example: - Server and port: 123.45.67.890:389
- Admin distinguished name: cn=admin,o=novell
- Admin password: bigredn
|
6) Portal Object - Distinguished name:
- Password seed:
|
NPS requires a Portal object in eDirectory. Specify the distinguished name (context) for the Portal object. and then specify a password seed. Example: - Distinguished name: cn=portal,ou=services,o=novell
- Password seed: novell
|
7) Public User Object: - Distinguished name:
- Password:
|
NPS requires a public user in eDirectory. You can specify an existing user as the public user, or you can have the NPS Installation program create a new public user. Example: - Distinguished name: cn=publicuser,ou=services,o=novell
- Password: novell
|
8) User Contexts |
To configure NPS for contextless login (meaning users only need to enter a common name rather than a full distinguished name when logging in), specify the contexts where User objects reside. Example: - ou=users,o=novell
- ou=users,ou=services,o=novell
|
9) NPS System Gadgets |
NPS includes several gadgets required to configure and maintain the NPS system. By default, the objects for these gadgets are created in the same context as the Portal object (item 6). If desired, you can change the objects' default context and names. |
10) OnDemand Services Gadgets |
OnDemand Services includes nine gadgets. By default, the objects for these gadgets are created in the same context as the Portal object (item 6). If desired, you can change the objects' default context and names. |