Documentation Archive Developer
Search
Table of Contents Previous Section

Solaris Post-Installation Steps

 After you've finished installing on Solaris, perform the following steps:

Install the Java Native Threads Pack

 If you are running Solaris 2.5.1 (with patches 103566, 103600, and 103640), you must install the Java Native Threads Pack. You can download the Native Threads Pack from JavaSoft's Java Development Kit website.

Rebuild the Executable WODefaultApp

On Solaris, 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 HTTP Server Process Owner

 You should change the user used to launch server processes if you want to be able to autostart WebObjects applications. You autostart a WebObjects application when you type its URL directly in the web browser without starting its executable first. Autostarting is a convenience that some people prefer to use when testing applications; however, you don't have to enable autostarting. In fact, autostarting is not recommended for WebObjects deployment sites. If you can't autostart, you can still launch applications from the command line.

By default, the user nobody owns CGI processes, and so it is used to launch autostarted WebObjects applications. This user does not have access to the NEXT_ROOT environment variable. Without access to the NEXT_ROOT environment variable, autostarted applications won't be able to locate OpenStep and WebObjects resource files.

This problem won't affect you if you've installed WebObjects under the root directory (that is, NEXT_ROOT is /). If you installed WebObjects in some other directory, change your HTTP server's configuration so that CGI processes are launched by a user with the appropriate environment setup rather than user nobody. This will allow you to autostart web applications from the browser.

You may want to keep the user nobody for security reasons. If so, you can still launch WebObjects applications by hand in a command shell window. Only autostarting will not work.

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.

Table of Contents Next Section