Table of Contents Previous Section

HP-UX Post-Installation Steps

 After you've finished installing on HP-UX, perform the following steps:

Rebuild the Executable WODefaultApp

 On HP-UX, the Enterprise Objects Framework cannot automatically load your database's client library and its adaptor, as it can on other platforms. Because of this, you must rebuild the WODefaultApp executable, which is installed with WebObjects and is used to run purely scripted applications. If you don't rebuild this executable, any purely scripted applications you run with WODefaultApp won't be able to access the database.

If you answered "y" to all questions you were asked during installation, the WODefaultApp executable has already been rebuilt by the installation process. If you answered "n" to the question about building WODefaultApp or you have installed new client libraries afterwards, you should rebuild WODefaultApp before testing your installation.

To rebuild WODefaultApp, run the script /NextLibrary/WOAdaptors/WODefaultApp/RebuildWODefaultApp.

Note: Each time you create a new project, you'll need to set it up so that it statically links the database's client library and adaptor. To do so, add the appropriate adaptor framework to the FRAMEWORKS makefile variable definition, and uncomment this line in the Makefile.preamble. 

include $(MAKEFILEDIR)/pdo-eoadaptor-linking.make

Change the UID for User nobody

 If you're using the Apache web server provided with the WebObjects package, you'll need to change the UID of the user nobody, which is used to launch CGI processes. By default, the UID is -2, which causes setuid to complain about an invalid argument.

Change the nobody UID and nogroup group ID in /etc/passwd and /etc/group to positive numbers.

Customize Documentation URLs

In the WebObjects documentation, links from the documentation to example WebObjects applications are of the form:

http://localhost/cgi-bin/WebObjects/Examples/WebScript/ApplicationName
As long as you are accessing the documentation from the HTTP server machine (that is, localhost) and the HTTP server stores scripts in a directory named cgi-bin, these links work. If you are accessing the documentation over the network, or the HTTP server doesn't call its scripts directory "cgi-bin", the links will be broken.

We've provided a script, curls.sh, that modifies these URLs to use the name of the host and scripts directory specific to your installation. The script is in $NEXT_ROOT/NextLibrary/Documentation/NextDev/WebObjects/Installer.

Assuming your computer's hostname is "Mars" and its scripts directory is "Scripts", you could modify the URLs in the documentation by running these commands in a terminal window:

	cd $NEXT_ROOT/NextLibrary/Documentation/NextDev/WebObjects/Installer
	curls.sh -h Mars -c Scripts -F WOPages
See the curls.sh script itself for more information about its operation.

Build the Examples

The section Verifying the Installation describes how to verify that your installation is working properly by running the examples, some of which are compiled examples. On HP-UX, you must build the examples before you can test your system. If you want to use the WebObjects examples to test your system, build the following examples:

<DocRoot>/WebObjects/ObjectiveC/DodgeDemo
<DocRoot>/WebObjects/ObjectiveC/HelloWorldCompiled

<DocRoot> is your HTTP server's document root.

Table of Contents Next Section