WebObjects 3.5.1 Administration FAQ

This article contains frequently asked questions (FAQ) regarding WebObjects 3.5.1 installation and administration, with answers to those questions.
Questions answered in this article:
  1. What databases/adaptors are supported by WebObjects Enterprise 3.5.1?
  2. How do I configure Microsoft IIS for WebObjects?
  3. I've read all the Release Notes and still can't get WebObjects installed and running!

Question 1: What databases/adaptors are supported by WebObjects Enterprise 3.5.1?

Answer: Apple provides Sybase, Oracle and generic ODBC adaptors for WebObjects on most platforms. Third-party adaptors may be available for other databases, including Informix, Quickbase, AS/400, Supra, DB2, Gupta SQL Base, VSAM, ADABAS, IMS/DB, and NCR Teradata. Other databases may be accessed programmatically through custom libraries provided by your database vendor.

Question 2: How do I configure Microsoft IIS for WebObjects?

Answer: This bug concerns Microsoft IIS Server running on Windows NT Server (Microsoft IIS Server does not currently run on Windows NT Workstation). On Windows NT Server, if you install WebObjects 3.1 or 3.5.1 under a C:\\NeXT directory, the cgi adaptor won't autostart your applications correctly. The IIS Server creates subprocesses with a special user that has no privilege at all, and that has no access to the NEXT_ROOT environment variable. An autostarted application won't have any privilege either, and won't be able to locate WebObjects resources (for example TimeZone files).


First:


After installation:

Then, either:

Or:

Also, if you're using the IIS Server, the URL to your WebObjects application should contain /Scripts/WebObjects.exe instead of /cgi-bin/WebObjects, as the cgi-bin directory is actually called Scripts. For example, http://server/Scripts/WebObjects.exe/Examples/HelloWorld is the right way to invoke the HelloWorld application.


Question 3: I've read all the Release Notes and still can't get WebObjects installed and running!

Answer: It seems that on some systems the /tmp or C:\\TEMP directories either don't exist or don't have read/write permissions set correctly. Be sure the directory can been seen and accessed by all. WebObjects, other apps and users need access to this directory to work properly.

Published Date: Feb 20, 2012