Documentation Archive Developer
Search

WebObjects Release 3.1 Post-Installation Notes

This file contains:

Using WebObjects with Your Web Server

At this point you should have installed WebObjects and rebooted your computer. The following topics tell how to get WebObjects working with your Web server.

Windows NT

The WebObjects installation program automatically sets up WebObjects to work with your Web server. No further steps are necessary.

Mach

The following instructions will help you make sure your Web server sees the WebObjects Adaptor and the examples.

If you're using WebObjects with the Apache server

You're done with installation. To start up the server, su to root and give this command: 

/NextLibrary/WebServer/httpd -d /NextLibrary/WebServer > /dev/console

If you're using WebObjects with any other Web server

You'll need to move the contents of two directories. You may have to su or log in as root before doing this.

  1. Identify your Web server's cgi-bin and DocumentRoot directories.

    • The cgi-bin directory is commonly located as /usr/local/etc/httpd/cgi-bin.

    • The DocumentRoot is commonly located as /usr/local/etc/httpd/htdocs.

    • If you don't know how to identify these important directories, see your system administrator.

  2. Move files under /NextLibrary/WebServer to your Web server's directories.

    • Move the two files under /NextLibrary/WebServer/cgi-bin to your Web server's cgi-bin directory.

    • Move the two directories under /NextLibrary/WebServer/htdocs to your Web server's DocumentRoot directory.

  3. Make sure your Web server is running.

Solaris and HP-UX

If you're using WebObjects the Apache Web server

To install the Apache Web server provided with the WebObjects release, follow these steps:

  1. On Solaris, cd to WebServer-3.0/Solaris in the mount directory for the CD-ROM.
    On HP-UX, cd to WebServer-3.0/HP-UX in the mount directory for the CD-ROM.

  2. Start the install script with this command:

    sh WebServerInstall

  3. When the install script asks you to confirm that you want the Apache HTTP server software installed, type "y" to proceed or "n" to cancel the installation.

  4. On HP-UX, there may be an incompatibility between the standard user and group ID numbers for nobody and those required by the Apache HTTP server. One work-around for this problem is to create a new user account to own the files on your web server. Create the user (using any name you wish) with the standard HP-UX utilities.

    Then modify the /NextLibrary/WebServer/conf/httpd.conf file by replacing "nobody" with the name of the new user in the following line

    User nobody

  5. To start the server, open a shell, su to root, and give this command:

    /NextLibrary/WebServer/httpd -d /NextLibrary/WebServer > /dev/console

This completes the installation of the Apache server.

If you're using WebObjects with any other Web server

Follow these steps to move the contents of two directories. (You may need to su to root before doing this.)

  1. Identify your web server's cgi-bin and document root directories.

  2. Move the files under /NextLibrary/WebServer/cgi-bin to your web server's cgi-bin directory.

  3. Move the two directories under /NextLibrary/WebServer/htdocs to your web server's document root directory.

Customizing URLs

In the WebObjects documentation, links from the documentation to example WebObjects applications are of the form:
    http://localhost/cgi-bin/WebObjects/Examples/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. On Windows NT, this script runs automatically during the installation process. On UNIX platforms, you must run this script by hand. The script is in $NEXT_ROOT/NextLibrary/Documentation/NextDev/WebObjects.

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
    curls.sh -h Mars -c Scripts -F WOPages
(On a Mach machine, you'd cd to /NextLibrary/Documentation/NextDev/WebObjects before running the curls command.)

See the curls.sh script itself for more information about its operation.


Uninstalling WebObjects for Windows NT

OPENSTEP Enterprise includes an "uninstaller" that automatically removes OPENSTEP Enterprise from your computer. However, this uninstaller doesn't work on computers that have OPENSTEP for Windows 4.0 or D'OLE (4.0 or earlier) installed. Versions 4.0 and earlier of OPENSTEP for Windows and D'OLE must be uninstalled using the following procedure.
  1. Terminate all running OPENSTEP for Windows and D'OLE programs by double-clicking each item in the NeXT Software program group. If you've double-clicked a running program, you get a dialog asking if you want to terminate it. If the program wasn't running, you just started it; double-click it again to terminate it.

  2. Locate and delete the directory containing the OPENSTEP or D'OLE software, and all files and subdirectories contained within. If you're unsure which directory to delete, open the System control panel and look in the System Environment Variables section. The directory in question is identified by the NEXT_ROOT environment variable.

    If you can't delete a file, that means it is still running. Double-click the file in Explorer to terminate it. Then delete the file.

  3. Clean up your program groups. Use the appropriate procedure for your version of Windows NT:

    For Windows NT 3.51:

    • Select -- but do not open -- the NeXT Software program group icon in the Program Manager.
    • Press Delete, or choose Delete from the File menu. In the Delete confirmation dialog that appears, click Yes.
    • Double-click the Start-up group icon in the Program Manager.
    • If the Start-up group contains icons labeled MachD, Mach nmserver, WindowServer, or Pasteboard Server, select each icon and press Delete. In the Delete confirmation dialog that appears, click Yes.

    For Windows NT 4.0:

    • Click Start. Choose Settings, then Taskbar.

    • Click the Start Menu Programs tab in the Taskbar Properties dialog. In the Customize Start Menu section, click Remove.

    • In the Remove Shortcuts/Folders dialog, select the NeXT Software folder and click Remove to delete it.

    • Double-click the Start-up group folder to open it. If the Start-up group contains icons labeled MachD, Mach nmserver, WindowServer, or Pasteboard Server, select each icon and click Remove.

    • Click Close in the Remove Shortcuts/Folders dialog. Click OK in the Taskbar Properties dialog.

  4. Clean up your system environment variables as follows:

    • If you're using Windows NT 3.51, go to the Windows NT Program Manager and open the Main program group. Double-click the Control Panel icon. If you're using Windows NT 4.0, click Start, select Settings, then select Control Panel.

    • Within the Control Panel window, double-click the System icon.

    • The System panel appears. On Windows NT, select the Environment tab. This panel is where you can alter the environment variable settings that Windows NT uses.

    • Select NEXT_ROOT in the System Environment Variables section. Click Delete.

    • If developer software was installed, select the lib (or Lib) system-environment variable definition. Highlight that portion of the definition that names directories removed in step 2, above, and press the Delete key (do not click Delete). Click Set to register the change.

    • Select the Path system-environment variable definition. Highlight that portion of the definition that names directories removed in step 2, above, and press the Delete key (do not click Delete). Click Set to register the change.

    • Click OK in the System dialog.

  5. Clean up the Windows NT Registry, using the appropriate procedure for your version of Windows NT. This step is not required.

    Note: You must take great care when editing the Windows Registry; it's possible to alter your configuration so that your computer will no longer boot. If you aren't comfortable working with the Windows NT Registry, skip this step.

    For Windows NT 3.51:

    • Start the Windows Registry Editor. This program is named REGEDIT.EXE, and is typically found in your WINNT35 directory.

    • Select Find Key... from the View menu. In the Find What field, type "NeXT".

    • Click Find Next in the Find panel to locate a key. Examine the key. If it appears to be one that was created for use with OPENSTEP or D'OLE, press the Delete key to delete it.

    • Repeat step c, above, until Find indicates that there are no keys that contain the string "NeXT". Close the Registry Editor.

    For Windows NT 4.0:

    • Start the Windows Registry Editor. This program is named REGEDIT.EXE, and is typically found in your WINNT directory.
    • Select Find from the Edit menu. In the Find What field, type "NeXT". Click Find Next to locate the first key.
    • Examine the key. If it appears to be one that was created for use with OPENSTEP or D'OLE, press the Delete key to delete it. Press F3 to find the next key.
    • Repeat step c, above, until Find indicates that there are no keys that contain the string "NeXT". Close the Registry Editor.

Uninstallation is now complete.