Installing NPS with Apache and Tomcat
Articles and Tips: tip
01 Feb 2003
Taken from Technical
Information Document #1006869
So you are trying to install Novell Portal Services (NPS) v1.5 on a NetWare 6 server and you want it to live peaceably with Apache and Tomcat. Are there any hints to make this happen?
Let's give it a try. While this explanation may be a bit long, it will be helpful. Unlike NPS v1.01, you can install NPS v1.5 from the NetWare 6 GUI. It can also be installed from a workstation on the network if desired. However, you will need Java Virtual Machine (JVM) 1.3 or later to install this product.
Since NetWare 6.0 has JVM 1.3 by default, we will perform this installation from the NetWare 6 server. To do this, you can either place the NPS 1.5 CD in the CDROM and then enter
at the server console prompt, or you can copy the CD over to a volume on the server and run it from there. Then at the server console prompt, enter the following command:
JAVA -JAR VOL:/PATH/NPS_SETUP.JAR
This will launch the GUI and start the installation. If the GUI does not start after a few moments, you will need to check the path you are entering in. The initial screen that you will see is the Novell Portal Services (NPS) welcome screen. Just click next to continue.
The next screen is the license agreement. After reading the agreement, if you agree with the license, then click next to continue. Here you will enter the destination of the web server. The web server can be either on the same server or it can be running on a different server. You can use either the IP address or the domain name. (However, if you use the domain name, you will already need the DNS resolution setup for that IP address.)
The server name is listed by default. This may or may not work, depending on whether the IP address of the server is given to Apache or to another web service. It is suggested that the IP address or domain name be used, not the server name.
Next we will choose the operating system, web server, and web application server. For this installation, we will choose NetWare 6.0, Apache, and Tomcat. Novell Portal Services 1.5 is not supported on NetWare 5.1 or lower.
The first section within this dialog box is the "Protocol Inter-Server Communication" section. This section is for encryption between the portal server and services running on other servers. This is not to be confused with encryption between the web server and a user's browser. This is a service that would be provided with the web server, iChain, or similar service.
The next section is for pointing to the directory structure within the web application server that will hold the NPS web application. Click NEXT to continue. In this dialog box we are whether or not you wish to upgrade NetWare WebAccess.
If you choose to upgrade, the NetWare WebAccess will no longer be accessed from the /webaccess URI. It will be accessed from the /nps URI. If you are going to upgrade they you will need to look at the following document. For this example we are going to choose NO to the upgrade. This will allow you to have Novell Portal Services running side by side with NetWare WebAccess. This means that NetWare WebAccess will be accessed from the /webaccess URI, and Novell Portal Services will be accessed from the /nps URI.
You will only get this message if an NPS directory exists under SYS:\WEBAPPS from a previous installation of Novell Portal Services. If you choose YES to this then the NPS directory will be overwritten. This message is not an option of an upgrade. This message is telling you that it will overwrite the directory. If you do not want to overwrite the directory, then choose NO. For this example we will choose YES. Again, you will only receive this dialog box if you already had the NPS directory installed. If you do not get this dialog box, don't worry. You're not missing a step here.
The ADMINSERV.CONF file is the main configuration file for Apache on NetWare. It should pick this path up by default. If the path is incorrect, or if the file does not exist, then the installation will not allow you to proceed. Click NEXT to continue.
Setting Up the LDAP Server
Now it is time setup the LDAP server. You will need a user with administration rights before proceeding. The DIRECTORY SERVER AND PORT section is to place the IP address or Domain Name for the LDAP server. If you are going to use the Domain Name, you will first need to have DNS resolution setup. For this example we will use the IP address.
To the right of this section are the SSL (encryption) options. Use the first one is if you are installing Novell Portal Services over a remote connection and you want to encrypt the install. Use the second option if your LDAP server is not on the same server as your portal server and you want the information between the portal server and the LDAP server to be encrypted. Turning this option on will affect performance.
The next two sections are for the administrators user name and password. This needs to be typed in using the fully distinguished, typeful, and in LDAP format (commas).
You will see an error if there is an issue resolving the administrators user name and password. This can be caused from several reasons.
You have chosen not to install over SSL and you do not have ALLOW CLEAR TEXT PASSWORDS checked in the LDAP Group object.
You are not using eDirectory. (eDirectory is installed on NetWare 6 by default).
Your LDAP server is not running.
You are using NDS format instead of LDAP format (periods instead of commas).
If you do not get this error, don't worry. This error will only happen if NPS is unable to resolve the administrators name.
Now we need to create the Portal Configuration Object (PCO). To make administration simple, it is suggested that you create an Organizational Unit to place all of your objects in. This is not necessary to run Novell Portal Services, but it will be done in this example. An NPS directory was created under the main Organization. Here you will place the PCO, gadgets, public user, etc. Again, this needs to be in LDAP format, fully distinguished, and typeful. For this example we will name the object portal.
Now we need to create a public user that will be used to hold the authentication gadget, which allows us to login to Novell Portal Services. Again, we will place this object under the NPS directory and it will need to be specified in LDAP format, fully distinguished, and typeful.
You do not need to worry about creating the public user before installing Novell Portal Services. If the user has not been created, you will receive the dialog box asking if you want to create the user. Click YES to continue.
This is where we will specify the containers that we want to have contextless login. If you have multiple Organizations (Os) at the same level, then you can hold down your CTRL key and select more than one Organization. Rights flow down from there.
You have the option to change the name and location of the gadgets being installed. For this example we will leave everything at the defaults and click NEXT to continue.
By default the communities OU are created under the O or OU that you have specified to hold Portal's gadgets. If you want community support, make sure that the ENABLE SUPPORT FOR COMMUNITIES box is checked. Again, you can change the name and location of the gadgets that will be installed if desired. For this installation we will accept the defaults and click NEXT to continue.
This dialog box will appear if you chose the option to install the community's OU. Click YES to create the OU and to continue with the installation. If you have any other *.NPG files that the installation can pick up, you will have the option to install them here.Click NEXT to continue.
Next is the list of what will be installed, where it will be installed, along with the amount of hard drive space NPS will take. Click NEXT to continue. (Installation time may vary depending on all that you are installing.) The last screen is just a summary of what will be installed. Click FINISH.
Now we need to test the installation of Novell Portal Services. To do this, go to the following URL: http://www.novell.com/nps
(For more information this procedure, see TID #1006869.)
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.