Installation and Configuration Supplement
Here are some ways that you might put the UDB documentation on a
central server, with the details for particular platforms and web
servers. If you use a different platform or web server, you should find
it has corresponding features that allow you to achieve similar
results.
In this scenario, you are using your OS/2 machine as the DB2 server,
and decide to use the Lotus Domino Go! web server to make the DB2 online
documentation available to the rest of your intranet.
- Install the DB2 Universal Database documentation
- You install the DB2 documentation along with the DB2 Enterprise Edition
server, on the E: drive. The HTML files are located in
the subdirectory e:\sqllib\doc\html. The server
documentation includes such books as the SQL Reference, Command
Reference, SQL Getting Started, Administration Guide, and the Quick
Beginnings book for that particular server. Because the
Enterprise Server includes the DB2 Connect function and its documentation, you
also get the DB2 Connect User's Guide and the DB2 Connect
Enterprise Edition Quick Beginnings manual. Assume that your
company does not do any application development, so you do not install the
Personal Developer's Edition, which includes the programming books such
as the API Reference.
- Install the Web Server
- Install the Lotus Domino Go web server from its installation
CD-ROM. In this scenario, assume the web server is installed in
c:\www and that its TCP/IP host name is
udbserv.
- Make the DB2 UDB Documentation Available through the Web Server
- To serve files from the DB2 directory, add a line like the following to
the c:\www\httpd.cnf file:
Pass /db2docs/* e:\sqllib\doc\html\*
Make sure that it comes before the line:
Pass /* document_root\*
Then, restart the web server.
Or, to copy the files to the web server directory, use the xcopy
command with the /s option to copy
e:\sqllib\doc\html\*.* to the
c:\www\html\db2docs directory. Your users can now
access the DB2 documentation by going to the URL
http://udbserv/db2docs/index.htm.
- Customize (Optional)
- Later, you get a phone call from a user who tried to select the API
Reference and received a "file not found" error because that book was
not present on the web server. Another user tried to select the
Quick Beginnings book for UNIX and got a similar error. You
might edit the file e:\sqllib\doc\html\index.htm,
removing the links to the programming books, and changing the links to the
Windows and UNIX Quick Beginnings books to point to a different intranet web
server that has those books installed.
Because the company has its own help desk for database problems, you add
the help desk's phone number and a mailto: link to the
index.htm file. Keep in mind that corrective service
releases might include an updated version of index.htm, so
be sure to keep a backup copy of any changes you make.
You are a system administrator running Netscape Enterprise server
2.02 on Windows NT. You are starting to roll out DB2 Universal
Database and have not yet decided if you will combine the database server and
the web server on a single machine, or use separate servers.
- Install the DB2 Universal Database documentation
- Assuming that your company does not do any application development, you
would not get the DB2 Universal Database Application Developer's Kit, and
thus would not get the programming books such as the API Reference,
Call Level Interface Guide and Reference, or the Application
Development Guide. (Note that you do get these programming books
as part of the database server documentation for UNIX systems.)
On this system, DB2 is installed on the E: drive, so the
HTML files are all stored under e:\sqllib\doc\html.
- Install the Web Server
- To test the performance of a combined web and database server, you might
install the Netscape Enterprise web server on the same system, named
udbserv on the company's intranet. The web server is
installed on the H: drive.
- Make the DB2 Documentation Available
- Initially, the web server only contains the DB2 documentation, so you want
the default home page of http://udbserv/ to display the file
e:\sqllib\doc\html\index.htm, the central list of DB2
books. To make the DB2 documentation available you need to perform the
following steps:
step 1.
| Run the Administer Netscape Servers program from the Netscape
folder, and choose udbserv as the server.
|
step 2.
| Under Content Mgmt, change the Primary Document
Directory to e:\sqllib\doc\html.
|
step 3.
| Use Document Preferences to add index.htm as
one of the default document names so that the browser displays
index.htm instead of a list of files in the directory.
|
Later, you decide to store other HTML files on the web server, and
configure the server so that the DB2 books are located at
http://udbserv/db2docs/:
- Change the Primary Document Directory back to a general
directory, such as h:\netscape\server\docs.
- Under Content Mgmt, select Additional Document
Directories and map the db2docs subdirectory to
e:\sqllib\doc\html.
- From the new default page for the web server, add a link to the
db2docs directory:
<a href="db2docs/index.htm">DB2 Online Documentation</a>
- Transfer Files (Optional)
- Eventually, the load on the combined web and database server becomes too
great and you decide to transfer the web server to a different machine.
You use an archiving tool such as pkzip or a Windows version of
tar to package the directory tree underneath
e:\sqllib\doc\html. You restore all the files
somewhere on the web server machine, then configure the web server as before
to serve the HTML files.
On a different system, you decide to uninstall the DB2 server and keep the
HTML files available for the web server. Before uninstalling the
server, you use the xcopy command to copy the
e:\sqllib\doc\html directory tree to
h:\netscape\server\docs\db2docs, then remove the web server
mapping for the additional document directory named db2docs.
In this scenario, you are using your personal Windows NT 4.0
machine as the DB2 server, and decide to use the Peer Web Services to make the
DB2 online documentation available to the rest of your workgroup. The
steps are similar whether you use Peer Web Services or Internet Information
Server.
- Install the DB2 Universal Database Documentation
- Install the DB2 documentation into the same directory as in the previous
scenarios: e:\sqllib\doc\html.
- Install the Web Server
- If Peer Web Services is not installed at the same time as the Windows NT
system, you run the program
c:\winnt\system32\inetins.exe to install the code from
the Windows NT installation CD-ROM. You use the Services
dialog in the Control Panel to make this service start
automatically.
- Make the DB2 Documentation Available through the Web Server
- You run the Internet Service Manager from the Microsoft Peer
Web Services folder of the Start menu, going to the WWW
section and then the Directories subsection. Initially, you
edit the home directory entry, changing the path from
c:\inetpub\wwwroot to e:\sqllib\doc\html and
the default document to index.htm. Later, when you
need to serve other documents as well as the DB2 books, you change the home
document back to c:\inetpub\wwwroot and add a new virtual
directory named db2docs.
- Customize (Optional)
- If you want to use the built-in search facility of Peer Web Services, you
must replace the file e:\sqllib\doc\html\db2srch.htm
with the file inetpub\samples\isapi\srch.htm, and copy the
DB2 HTML files as explained below.
- Copy Files (Optional)
- To use the built-in search facility of Peer Web Services, you need to copy
the DB2 HTML files to the c:\inetpub\wwwroot directory
tree. You create a directory named db2docs, and use the
xcopy /s command to preserve the directory structure during the
copy. Now you remove the virtual directory db2docs so that
the files under the real db2docs directory will be used.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]