Important: The information in this document is obsolete and should not be used for new development.
System Requirements
Before You Install
Installing WebObjects
Installing Web Server Adaptors
Installing Third-Party JAR Files
Removing WebObjects
Upgrading Your License
Solaris 8
256 MB of RAM
at least 1 GB of available hard disk space
Before installing WebObjects, you should remove any previously installed WebObjects components.
Note: If you are upgrading a dual-deployment installation of WebObjects 4.5.1 and WebObjects 5.0, remove both and then reinstall WebObjects 4.5.1 Deployment and WebObjects 5.2 Deployment.
WebObjects Deployment needs the Java Runtime Environment (JRE) version 1.3.1. If you do not already have it installed, install the JRE available at http://java.sun.com before installing WebObjects.
WebObjects Deployment works in concert with your HTTP server software. If you haven’t installed an HTTP server already, do so before installing WebObjects Deployment.
Before installing, you need to determine if you are going to perform a full installation or install only the Web server adaptors. If you plan to install the WebObjects application server on another computer than the computer (or computers) running your Web server, do an adaptor-only installation on the computer running a Web server; perform a full installation on the computer that you will use as your WebObjects application server. The installer gives you this option.
During installation, you will be prompted to enter the paths to your HTTP server’s cgi-bin (or scripts) directory and document root directory. Although you can specify a temporary directory for the installed files, you may want to note the paths before beginning your installation. By default Apache uses /var/apache/cgi-bin and /var/apache/htdocs respectively. If you do not set these paths during the installation you will need to manually copy the appropriate files after installation:
Copy /opt/AppleNOAdaptor/Library/WebObjects/Adaptors/CGI/WebObjects into your cgi-bin directory.
Copy the /opt/AppleNOAdaptor/Library/WebObjects/WODocumentRoot/WebObjects directory into your Web server’s document root directory.
Make sure to have a valid license key handy.
Log in as the root user.
If necessary, mount the CD-ROM.
Navigate to Deployment/SOLARIS/WebObjects/ in the mount directory of the CD-ROM.
Start the install script with this command:
./install.sh |
Follow the onscreen prompts to complete the installation.
Note: You cannot install WebObjects into an existing directory, including the file system root (/). If you specify a directory that already exists, the installation script displays a warning and gives you the choice of either specifying a different directory or quitting the installation.
As the installer finishes, it mentions three installation details to finalize:
Add the following line to your httpd.conf file:
Include /opt/Apple/Library/WebObjects/Adaptors/Apache/apache.conf
Enable WebObjects services to start when your computer starts (if you want this and did not choose that option when prompted) by typing:
/opt/Apple/Library/WebObjects/Executables/WOServices enable
Define the NEXT_ROOT environment variable in your shell startup script. Unless you have chosen a nonstandard location to install WebObjects, this should be defined as /opt/Apple.
With the completion of the installation process, all of the necessary files are copied to the target computer, the cgi-bin and document root directories are created (if necessary), an uninstall script is created, startup scripts for WebObjects services are created (if requested), and WebObjects services are started (if requested).
This completes the installation of WebObjects. If you did a full installation, you can verify a successful installation of WebObjects Deployment by connecting to port 1085 of your computer. You should see a page that displays the configuration information for wotaskd.
If you did an adaptors-only installation, you can verify that the adaptors are functioning properly or troubleshoot incorrect behavior using the following procedure:
Stop your Web server.
As the root user: touch /tmp/logWebObjects
Start your Web server.
This enables WebObjects logging. When your Web server starts, it creates a file in /tmp named WebObjects.log. The existence of this file verifies that your adaptor is correctly installed.
If you specify a cgi-bin directory during installation, the installer puts WebObjects CGI adaptors into this directory and configures WebObjects to use them. WebObjects also includes a number of other Web server adaptors. To use one of these, see the online adaptor installation instructions in NEXT_ROOT/Library/WebObjects/Adaptors/. These adaptors are provided in source form and can be customized. For instructions on rebuilding these WebObjects Web server adaptors, see NEXT_ROOT/Developer/Examples/WebObjects/Source/Adaptors/BuildingInstructions.html.
WebObjects 5.2 includes third-party JAR files that you need for applications that use Enterprise JavaBeans (EJB), JavaServer Pages (JSP), Java Servlet integration, Web services, or Java Database Connectivity (JDBC). The JAR files you need are provided for you in the ThirdPartyJars directory on your WebObjects 5.2 CD. They should be copied into NEXT_ROOT/Local/Library/WebObjects/Extensions.
Stop your Web server.
Find and kill any WebObjects processes that may be running.
ps -ef | grep -i wo will help you in finding running WebObjects processes.
From the root level of your directory structure (/), run NEXT_ROOT/Library/Executables/uninstall.sh.
Note: The uninstaller does not remove files that were not explicitly installed by the installer. You may find that NEXT_ROOT/ is not empty after running the uninstaller because configuration files that have been modified since installation are not removed. If you do not want to keep any of the files that may remain, you can safely remove the entire NEXT_ROOT/ directory.
To apply a deployment license to an existing deployment installation, you need only change the installed serial number. Using a text editor, edit NEXT_ROOT/Library/Frameworks/WebObjects.framework/Resources/License.key and replace the license key found there with the new license key obtained from Apple.
Last updated: 2002-11-01