9
Configuration and Back Up

A major feature of Oracle iFS is its support of multiple protocols, such as FTP, SMB, and IMAP. This chapter provides information on setting up, configuring, and administering these protocols and e-mail. Topics include:

Configuration and Port Issues

Each protocol used by Oracle iFS listens on a port. These ports are assigned numbers by default although they can be reconfigured. Some protocols also need to be configured before they can be used. If you configure a protocol, remember to start and stop that protocol's server.

Protocols and their Ports

The following table displays the Oracle iFS protocols and the default ports they run on, whether or not the parts can be configured, and what definition file to use to configure them. All definition files are located in the following directory:

$ORACLE_HOME/ifs<version>/settings

Protocol Default Port Port Configurable? Definition File Variable to Configure

File Transfer Protocol (FTP)

21

Yes

FtpServer.def

Change in the definition file.

Command Line Utility Protocol (CUP)¹

4180

Yes

CupServer.def

Change the IFS_CUP_PORT variable and the port number.

Simple Mail Transfer Protocol (SMTP)²

2500

Yes

SmtpServer.def

Change the port number in SmtpServer.def, Sendmail.cf and ifs.m4

Internet Messaging Access Protocol (IMAP)

143

Yes

ImapServer.def

Change in the definition file.

HyperText Transfer Protocol (HTTP)

80

Yes

Not Applicable

Use the JWS administration utility and change using port 1717.

Windows Client Protocol (WCP)³

Generated

Not Applicable

WcpServer.def

Not applicable.

Server Message Block (SMB)

139

No

SmbServer.def

Do not configure SMB.

¹ This is a proprietary protocol used for Oracle iFS operations.
² This is a simple implementation to support verification and delivery.
³ This is a proprietary protocol used for Oracle iFS operations.

Protocol	Default Port	Port Configurable?	Definition File	Variable to Configure
File Transfer Protocol (FTP)	21	Yes	FtpServer.def	Change in the definition file.
Command Line Utility Protocol (CUP)¹	4180	Yes	CupServer.def	Change the `IFS_CUP_PORT` variable and the port number.
Simple Mail Transfer Protocol (SMTP)²	2500	Yes	SmtpServer.def	Change the port number in SmtpServer.def, Sendmail.cf and ifs.m4
Internet Messaging Access Protocol (IMAP)	143	Yes	ImapServer.def	Change in the definition file.
HyperText Transfer Protocol (HTTP)	80	Yes	Not Applicable	Use the JWS administration utility and change using port 1717.
Windows Client Protocol (WCP)³	Generated	Not Applicable	WcpServer.def	Not applicable.
Server Message Block (SMB)	139	No	SmbServer.def	Do not configure SMB.

Note:
If you decide to configure these protocols manually instead of using the Configuration Utility provided during installation, the steps may generate multiple errors.

Configuring E-mail

When you create users, among the folders automatically created is a mail folder within which there is an inbox folder. The user's mail messages are delivered into the inbox folder. You can use either Outlook Express or Netscape 4.7 Messenger as your e-mail clients. You must set up e-mail accounts appropriately.

E-mail Setup for UNIX

Oracle iFS uses an open-source implementation of the Sendmail 8.9.3 product as the mail transfer agent. Oracle iFS has an SMTP server to support verification and delivery. In addition, Oracle iFS also provides an IMAP server.

Basic e-mail configuration is completed as part of installation and configuration of Oracle iFS. When e-mail is configured during installation, the following is done:

A new sendmail executable is placed in /usr/lib.
A sendmail.cf file is generated and placed in /etc.

Sendmail Configuration for UNIX

The sendmail.cf file generated during installation is created from a template. This template is used by the Oracle iFS configuration program only; Oracle iFS also provides .m4 and .mc files to support your own configuration of Sendmail. Configuring the sendmail.cf file is not recommended unless completed by qualified Sendmail specialists; it will not be supported by Oracle.

Note:
Oracle will not provide support in configuring Sendmail. The sendmail.cf file provided with Oracle iFS allows you to use Oracle iFS e-mail. Any further extensions and enhancements to the sendmail.cf file is the responsibility of the user. In accordance with open source licensing requirements, a full copy of the sendmail source is also provided with Oracle iFS. To view the full sourcecode for Sendmail, Version 8.9.3, use the sendmail.8.9.3.tar.gz in the $ORACLE_HOME/ifs<version>/admin/email/<platforms>/opensrc directory.

The .mc and .m4 files that can be used for configuration are found in the following location:

$ORACLE_HOME/ifs<version>/admin/email/<OS>/ifs-<OSNAME>.mc

where <OS> and <OSNAME> can be the following:

Platform <OS> <OSNAME>

AIX

aix

aix4

HP-UX

hp-ux

hpux10

Linux

linux

linux

Tru64

osf1

osf1

Solaris

solaris

solaris2

$ORACLE_HOME/ifs<version>/admin/email/common/cf--For the base of the .m4 directory tree.

Platform	<OS>	<OSNAME>
AIX	`aix`	`aix4`
HP-UX	`hp-ux`	`hpux10`
Linux	`linux`	`linux`
Tru64	`osf1`	`osf1`
Solaris	`solaris`	`solaris2`

For the default configuration:

Added files--$ORACLE_HOME/ifs<version>/admin/email/cf/mailer/ifs.m4

Note for Solaris Users:
For configuration, use the GNU M4. The Solaris version of the M4 macro-processor is not compatible with the open source Sendmail m4 files. For reference, go to www.gnu.org or see the Help for UNIX System Administrators, Sendmail guide (ISBN: 1-56592-222-0, publisher: O'Reilly). GNU M4 is not shipped with Oracle iFS 1.0.

Integrating Oracle iFS Mail and Sendmail Pro 8.9.3 For Solaris

The Oracle iFS e-mail system provides an IMAP server and an SMTP protocol server that provides verification and local delivery support. Oracle iFS e-mail does not have its own mail transfer agent, but relies on sendmail to act as the mail transfer agent. This section pertains to the Sendmail Pro product from Sendmail, Inc., and the following steps guide you through set up and configuration of Sendmail Pro version 8.9.3.

Note::
The following information pertains to Sun Sparc Solaris only.

Installing Sendmail Pro 8.9.3

To install Sendmail Pro 8.9.3 on a Solaris, refer to the Sendmail Pro 8.9.3 documentation. The installation is completed using the standard UNIX pkgadd utility. For further installation instructions, refer to the INSTALL document located for your platform of the Sendmail Pro distribution.

Oracle iFS Installation Dependencies

When the Oracle iFS Configuration Assistant is run during installation of Oracle iFS, the required pre-configuration (.m4 and .mc) files are prepared for e-mail configuration.

Configuring Sendmail

The configuration process involves running the ifsemailsetup_pro893 script located in the $ORACLE_HOME/ifs<version>/bin directory. This script sets up .m4 and .mc files and generates a sendmail configuration file that is used to integrate Oracle iFS and Sendmail Pro 8.9.3. You must run this script as the root user.

Quick Setup Steps

Steps 1 and 2 can be executed in any order.

Configure Oracle iFS using the Configuration Assistant. This step can be completed independently of the Sendmail install.
Install Sendmail Pro 8.9.3.
Run the script ifsemailsetup_pro893 for configuring Oracle iFS e-mail.

Note:
If you want to migrate to use open source Sendmail instead of Sendmail Pro 8.9.3, you must first de-install Sendmail Pro 8.9.3.

Sendmail Pro 8.9.3 Graphical Administration Tool

Sendmail Pro 8.9.3 includes a graphical administration and configuration tool. This is a Web-based tool that allows access to the configuration files from a Web server. However, due to the fact that the Sendmail Pro administration tool does not know about Oracle iFS, the tool cannot be used to configure Oracle iFS. If the tool is used to configure Sendmail pro, Oracle iFS support will not be included in the new configuration. Sendmail administrators will need to use the .m4 and .mc files provided in the distribution to reconfigure Sendmail.

Using E-mail with Oracle iFS

To use e-mail:

Make sure that Sendmail is running.
Make sure the SMTP and IMAP servers are running.
Make sure the Outbox Agent is running.

Using the Windows NT File System Protocol Server

To provide Explorer-based access to an Oracle iFS instance running on Windows NT, use the Windows NT file system protocol server (NTFS). This file system protocol server allows the Oracle iFS repository to appear as a local drive on the Windows NT system running the Oracle iFS server. Once the Oracle iFS repository is mounted as a local drive, the Oracle iFS repository can be shared using the standard Windows networking functions.

Accessing Oracle iFS through the Windows NT File System Protocol Server

When the Oracle iFS repository is mounted as a local hard drive using the file system protocol server, access to the Oracle iFS repository is controlled by Windows NT. The standard Windows networking functions can be used to control shared access to the local Oracle iFS drive from Windows client machines.

To enable network access from Windows client machines, the Oracle iFS NT file system protocol server must be started and the Oracle iFS repository mounted as a local drive on the server machine. The local Oracle iFS drive can then be shared by the server machine using the Windows Explorer or the NET SHARE command from the command line. A Windows client machine can then map to the shared drive using the Windows Explorer or the NET USE command from the command line.

When a Windows client maps to a shared drive, the Windows client supplies a username and password to the Windows server machine. The Windows server machine checks that the user is a valid Windows user, either on the local machine or in the domain, and grants access to the shared drive. If the shared drive is an Oracle iFS drive, the Windows username used to map the drive is also passed to the Oracle iFS repository as the Oracle iFS user to determine the user's Oracle iFS access permissions. In order to be able to access a shared Oracle iFS drive, the Windows user used to map the Oracle iFS drive must also be an Oracle iFS user and an Oracle iFS user must also be a Windows user.

Starting the Windows NT File System Protocol Server

The Oracle iFS administrator username, by default is system. Any Oracle iFS user can be granted administrator privileges. Any user who is a member of the Windows NT administrator group can start the Oracle iFS Windows NT File System Driver. However, when connecting from the local machine that user will always appear as system.

Users connecting from a remote machine must have a valid Windows NT account on the machine hosting the NTFS driver. When they connect to the local machine, Windows NT will first validate that they have permission to see the mount points created by the NTFS driver (Root, Home and Public). Once they mount one of these mount points (which is managed by Windows File Sharing, not Oracle iFS), their access permission to files and folders inside the mount point is governed by the rights granted to the user they connected as.

Note:
Using Windows NT, access to the Oracle iFS mount points is controlled by the native Microsoft Windows NT file sharing capabilities, and the NTFS driver simply exposes three more mount points for Windows NT file sharing to manage. This is different from the UNIX implementation where the Oracle iFS SMB Server actually manages the File Sharing directly.

Backup and Recovery of Data

There are two important issues regarding backup and recovery of data:

Saving the software installation as a backup
Saving the data

Saving the Software Installation

You should back up the software installation so that you can easily restore the files in case of a disk crash or other failure. To save the software, you should make a backup on a type of media, such as tape or CD-Rom. This only needs to be done once after completing Oracle iFS installation.

Saving the Data

All Oracle iFS data is currently stored inside the database, which allows you to rely on the usual backup and recovery mechanism used for all other Oracle data. This is an important step when migrating data; if you use FTP to migrate data, all versioning, ACLs, ownership of files, and extended attributes will be lost. It is highly recommended that you backup your data before you migrate your data.

For more information on using Oracle's back up and recovery mechanism, see the Oracle 8.1.6 Server Backup and Recovery Guide. This guide explains what to do for the different possible scenarios, what software is required, and what to set up.

When saving files, there is no way of restoring a single document from a backup. The database is saved in a way which does not allow you to restore complete data files or to restore until a defined point in time, to save the document with all repository data describing it, or to restore this information back into the system.

Configuring Oracle Apache Web Server

To use the Oracle Apache Web Server with Oracle iFS, run the ifsapachesetup script located in the following directory:

Platform Location

UNIX

$ORACLE_HOME/ifs<version>/bin

Windows NT

%ORACLE_HOME%\ifs<version>\bin

Platform	Location
UNIX	`$ORACLE_HOME/ifs<version>/bin`
Windows NT	`%ORACLE_HOME%\ifs<version>\bin`

This script configures Apache and Jserv so that Oracle iFS can be accessed through port 7777 and allows users to access the Oracle iFS site through the http://<server-name>:7777/ifs/ifsservlet URL.

The sections relevant to Oracle iFS configuration are identified in the server configuration files. The following files are changed during configuration:

jserv.conf
jserv.properties
zone.properties

These files can be found in the following directory:

Platform Location

UNIX

$ORACLE_HOME/Apache/Jserv

Windows NT

%ORACLE_HOME%\Apache\Jserv

Platform	Location
UNIX	`$ORACLE_HOME/Apache/Jserv`
Windows NT	`%ORACLE_HOME%\Apache\Jserv`

All other configuration is similar to the standard Apache and Jserv configuration.

Configuring Apache As Your Web Server on Windows NT

If you want to use Apache instead of JWS, this section provides configuration steps for Apache to be used with Oracle iFS. These are not comprehensive instructions and are more of a general set of rules you need to follow to configure Apache. It is expected that you are familiar with Apache and standard servlet engines.

These steps provide a mechanism to set Apache 1.3.12 with JRun 2.3.3 as the servlet engine. On the Apache Web site (www.apache.org), you can download the appropriate version. JRun can be purchased from allaire.com.

To install Apache and JRun:

Install Apache with Dynamic Shared Object (DSO) support.
Uncomment the following line in httpd.conf file to enable the mod_rewrite:
```
LoadModule rewrite_module modules/ApacheModuleRewrite.dll
```
Install JRun and run the JRunConnector.
While Running the Jrun Connecter, select the Use 1.3.6 DSO option from the DSO Support options.

To setup JRun to run Oracle iFS:

Place the correct class path, library path and Java Virtual Machine (JVM) arguments into the following directory:

<JRUN_HOME>/jsm-default/properties/jsm.properties

An example set of entries are:

jrun.rootdir=..
jrun.api21=false
redirect.stderr=true
redirect.stdout=true
admin.port=57860
admin.bindaddress=*
java.path=..\\examples\\jni;D:\\Oracle\\Ora81\\lib;D:\\Oracle\\Ora81\\Ct
x\\lib;C:\\JRun\\jre\\lib;D:\\Oracle\\Ora81\\jdbc\\lib; 
java.args=-classpath 
"C:/JRun/classes;C:/JRun/jsm-default/classes;C:/JRun/lib/jrun.jar;C:/JRu
n/lib/servlet.jar;C:/JRun/webl/WebL.jar;C:/JRun/lib/jsp.jar;C:/JRun/lib/
xml4j.jar;C:/JRun/lib/xt.jar;C:/JRun/lib/fesi.jar;C:/JRun/lib/cfanywhere
.jar;C:/JRun/lib/NetComponents.jar;C:/JRun/lib/OROMatcher.jar;C:/JRun/li
b/tools.jar;C:/JRun/instantdb/classes;C:/JRun/lib/jrunadmin/jrunadmin.ja
r;D:/Oracle/Ora81/ifs/jre/lib/classes.zip;D:/Oracle/Ora81/ifs/jre/lib/rt
.jar;D:/Oracle/Ora81/ifs/jre/lib/i18n.jar;D:/Oracle/Ora81/ifs/jre/jre/li
b/rt.jar;D:/Oracle/Ora81/ifs/jre/jre/lib/i18n.jar;D:/Oracle/Ora81/ifs/jr
e/lib/tools.jar;C:/JRun/lib/jrunadmin/swing.jar;D:/Oracle/Ora81/ifs/sett
ings;D:/Oracle/Ora81/ifs/jre/lib/rt.jar;D:/Oracle/Ora81/ifs/jre/lib/i18n
.jar;D:/Oracle/Ora81/jdbc/lib/classes111.zip;D:/Oracle/Ora81/lib/vbjorb.
jar;D:/Oracle/Ora81/jlib/xmlparserv2.jar;D:/Oracle/Ora81/ifs/lib/repos.j
ar;D:/Oracle/Ora81/ifs/lib/adk.jar;D:/Oracle/Ora81/ifs/lib/email.jar;D:/
Oracle/Ora81/ifs/lib/tools.jar;D:/Oracle/Ora81/ifs/lib/utils.jar;D:/Orac
le/Ora81/ifs/lib/release.jar;D:/Oracle/Ora81/assistants/jlib/jnls.jar;D:
/Oracle/Ora81/ifs/custom_
classes;D:/Oracle/Ora81/ifs/lib/installer.jar;D:/Oracle/Ora81/ifs/lib/je
wt-opt-4_0_15.zip;D:/Oracle/Ora81/ifs/lib/share-opt-1_1_
4.zip;D:/Oracle/Ora81/ifs/lib/swingall.jar;D:/Oracle/Ora81/ifs/lib/clien
tlib.jar;D:/Oracle/Ora81/ifs/webui_
classes;D:/Oracle/Ora81/ifs/lib/http.jar;D:/Oracle/Ora81/ifs/lib/webui.j
ar;D:/Oracle/Ora81/ifs/jws/lib/servlet.jar;D:/Oracle/Ora81/ifs/jws/lib/j
st.jar;D:/Oracle/Ora81/ifs/jre/lib/javac.jar;" 
java.exe=D:\\Oracle\\Ora81\\ifs\\jre\\bin\\jrew.exe
java.securitymanager=
java.classpath=

Map the DocumentServlet and IfsJspServlet to aliases such as docservlet and jspservlet, respectively, in the following directory:

<JRUN_HOME>/jsm-default/services/jse/properties/servlets.properties

Assuming the Oracle iFS schema password as "ifsuser", an example set of entries are:

servlet.docservlet.code=oracle.ifs.protocols.http.servlet.DocumentServle
t
servlet.docservlet.args=ifs.http.servicepassword=ifsuser
servlet.docservlet.preload=true
servlet.jspservlet.code=oracle.ifs.protocols.http.jsp.IfsJspServlet
servlet.jspservlet.args=ifs.http.servicepassword=ifsuser
servlet.jspservlet.preload=true

Set up Apache to forward all requests to JRun in the following directory:

<APACHE_HOME>/conf/httpd.conf