5
Post-installation

This chapter describes post-installation procedures for Oracle 9iFS. Topics include:

• Make the Changes Identified by the Configuration Assistant

• Start/Stop the Oracle 9iFS Domains and Nodes from the Oracle9i Enterprise Manager Console

• Start/Stop the Oracle 9iFS Domains and Nodes from the Commandline

• Run the Oracle 9iFS Servlets with the Oracle HTTP Server

• Install the Oracle 9iFS Portlet

• Configure the NFS Server

• Configuring and Using JRE 1.3.0

Make the Changes Identified by the Configuration Assistant

A number of configuration tasks must be performed after the Oracle 9iFS Configuration Assistant has successfully completed. These include manual procedures as well as tasks involving entities outside of the Oracle 9iFS administrative tools.

Start the Oracle 9iFS Mail Servers

If you want to use the Oracle 9iFS e-mail servers, run the ifsemailsetup script, as the root user, from $ORACLE_HOME/9ifs/bin.

This should only be run if you want to receive mail on Oracle 9iFS using the public domain sendmail. If you don't want to receive mail into the users' inboxes, or if you are using a Sendmail Inc., sendmail, do not run this script. Running the ifsemailsetup script will replace your sendmail (if you are using the Solaris sendmail) and your sendmail configuration file.

Restart the Intelligent Agent

Because the Oracle 9iFS Configuration Assistant makes changes to the configuration settings for the Domain Controller and the node, you must restart the Intelligent Agent (IA). You need to define ORACLE_SID in the environment when you start or restart IAs. See "Task 5: Set Database Parameters" in Chapter 2, "Pre-installation" for more information.

As the user who installed the Oracle database, typically 'oracle', enter these commands:

$ agentctl stop 
$ agentctl start 

Rediscover the Host

Because the Oracle 9iFS Configuration Assistant makes changes to the configuration settings for the Domain Controller and the node, you must rediscover the host where your Domain Controller and node reside in the Oracle9i Enterprise Manager Console. Refer to the Oracle 9iFS Setup and Administration Guide.

Restart the Oracle HTTP Server

Because the Oracle 9iFS Configuration Assistant makes changes to the HTTP node, you must restart the Oracle HTTP Server located in $ORACLE_HOME/Apache/Apache/bin. To do so:

$ apachectl stop
$ apachectl start

Run ifsomssetup

Optionally, if you want to monitor Oracle 9iFS from this machine, you can run the ifsomssetup script. ifsomssetup will ask you for three values:

• OEM repository schema name and schema password are the values you specified when you ran emca during "Task 7: Set Up the the Oracle9i database Enterprise Manager" in Chapter 2, "Pre-installation"

• OEM repository TNS name is the local TNS name for the database where you configured the OEM repository.

After running ifsomssetup, restart Oracle Management Server. See "Start Oracle Management Server".

Re-populate the Oracle Text Index (Upgrades Only)

Re-populate the Oracle Text index for all existing documents in the Oracle 9iFS schema that was upgraded. To do this, log on to SQL*Plus as the Oracle 9iFS schema user (the database user that owns the schema, the default is IFSSYS), and type the following:

exec ctx_output.start_log('ifsidx.log')
update odmz_context_router set contentprocedure = 
contentprocedure;
commit;
exec ctx_ddl.sync_index('ifs_text');
exec ctx_output.end_log

This process can take several hours or longer, depending on the number of documents in the Oracle 9iFS schema. If this step is not performed, the Oracle 9iFS servers will still run, but you will not be able to search on the content of any documents. Monitor the file ifsidx.log located in the $ORACLE_HOME/ctx directory for any problems during the re-indexing.

Modify Oracle Text Indexing Scripts (Upgrades Only)

In Oracle 9iFS, a new Oracle Text index replaces the old Oracle Text index. The new index uses the USER_DATASTORE feature to use multiple content stores with only one Text index. The name of the Text index, IFS_TEXT, is no longer derived from internal content store objects.

If you are upgrading from Oracle iFS 1.0 or 1.1, you need to update any scripts, such as DMBS_JOB procedures, with the new name. For 1.0, the index was named INDEXEDBLOB_I. For 1.1, the index was named GLOBALINDEXEDBLOB_I.

See Appendix E in the Oracle 9iFS Setup and Administration Guide for additional information.

Start/Stop the Oracle 9iFS Domains and Nodes from the Oracle9i Enterprise Manager Console

To start Oracle 9iFS, start the Oracle Management Server and then the domain.

Start Oracle Management Server

As the user who installed the Oracle database, typically 'oracle', perform these steps:

1. Enter the command:

   $ oemctl start oms 
   

   You will be asked to change the password for OMS administrator sysman. The initial password for sysman is oem_temp.

2. To check the status of the OMS or to stop OMS, assuming the password for sysman is oemanager, enter:

   $ oemctl status oms sysman/oemanager   
   $ oemctl stop oms sysman/oemanager 
   

Start the Oracle 9iFS Domains and Nodes

1. Launch the Oracle9i Enterprise Manager Console with a connection to OMS using the oemapp console script.

2. Discover the Oracle 9iFS targets on all middle-tier machines.

3. Select the Oracle 9iFS Domain Controller you want to start and click the Start Domain command on the Object menu.

Stop the Oracle 9iFS Domains and Nodes

1. Right-click the domain name.

2. Select Stop Domain from the Object menu. The Stop the 9iFS Domain dialog displays.

3. If you saved your schema password as a preferred credential, it will be displayed. If not, enter your schema password. You can save it as a preferred credential now, to avoid entering it in the future.

4. Choose whether to stop all the nodes within the domain or not.

5. Click OK.

The domain and nodes, if selected, are stopped.

Start/Stop the Oracle 9iFS Domains and Nodes from the Commandline

You can also start and stop domains and nodes from the Commandline.

Start the Domains and Nodes from the Commandline

On the machine where you want to run the Domain Controller:

1. Launch the Domain Controller using the ifslaunchdc script, located in $ORACLE_HOME/9ifs/bin. You can run this as the user that installed the Oracle 9i database or the root user.

2. On the machines that you want to run the node, launch the node using the ifslaunchnode script located in $ORACLE_HOME/9ifs/bin. You must be the root user to run this script.

3. Start the Domain Controller using the ifsstartdomain script located in $ORACLE_HOME/9ifs/bin. You should run this as the same user who ran ifslaunchdc.

Please refer to Chapter 2, "Administering an Oracle 9iFS Domain" in the Oracle 9iFS Setup and Administration Guide.

Stop the Oracle 9iFS Domain from the Commandline

Run the ifsstopdomain script located in $ORACLE_HOME/9ifs/bin. You should run this as the same user who ran ifsstartdomain.

Run the Oracle 9iFS Servlets with the Oracle HTTP Server

The Oracle HTTP Server for Oracle9i is powered by Apache coupled with Jserv. Servlets that run under this infrastructure can run either in the default Jserv process that is launched by the web server or in a separate, distinct Jserv process listening on another port. In either case, servlets need to be configured appropriately.

Running Oracle 9iFS Servlets in a Separate Jserv Process

This is the default configuration when you install Oracle 9iFS. The configuration files in use are jserv.conf, ifs.properties, and ifsprops.properties. The files are in <ORACLE_HOME>/Apache/Jserv/etc.

Starting and Stopping Oracle 9iFS Jserv

The process for starting and stopping the Oracle 9iFS Jserv process is distinct from that of starting and stopping the Apache server.

Use the script ifsJservctl present in the <ORACLE_HOME>/9ifs/bin directory.

ifsJservctl -start	Starts the 9iFS JServ process. Also starts Apache if it is not running.
ifsJservctl -stop	Stops the 9iFS JServ process. Does not stop Apache if it is running.

Running in the Default Jserv Process

To use this configuration, the user needs to modify the following files which are in <ORACLE_HOME>/Apache/Jserv/etc:

1. jserv.conf

   You need to uncomment this line (remove the "#"):

   #ApJservMount /ifs /ifs
   
   

   Then you need to comment out the line (add a "#"):

   ApJservMount /ifs ajpv12://localhost:13138/ifs
   
   

   The file contains instructions above each of the lines.

2. jserv.properties

   Go to the iFS section in the file and comment out all the wrapper declarations and the zone declarations in this section only. The section is very clearly marked in the file.

   Stop the Oracle 9iFS Jserv process, if running, and restart Apache. The iFS Servlets are enabled by just starting and stopping Apache using the apachectl command.

   To stop Apache, execute apachectl stop, located under <oracle_home>/Apache/Apache/bin/. To start Apache, execute apachectl start.

Install the Oracle 9iFS Portlet

The Oracle 9iFS portlet is a Portal component that provides a summary of information about the user's Oracle 9iFS data. On the portlet, users can see their quota, initiate a search, list documents or folders, and upload documents. The portlet links to the Oracle 9iFS Web interface. There are several setup and configuration steps for the administrator to perform before users can add the portlet to their Oracle Portal.

Register the Oracle 9iFS Portlet with Oracle Portal

Oracle Portal administrators can add the Oracle 9iFS portlet to their own installation of Oracle Portal, by registering it as a Web Provider on the portal:

1. On the portal, click the Administer tab.

2. In the Provider portlet, click the Add a Portlet Provider link.

3. Fill out the form to create a Web Provider.

Parameter	Value
Name	9iFS
Display Name	Oracle 9iFS
Timeout	100
Timeout Message	9iFS portlet timedout
Implementation Style	Web
Register on Remote Node	No
Provider Login Frequency	Once per User Session
URL	http://<hostname>:<port>/ifs/portlet
Web provider in the same cookie domain as the portal	Do not check the checkbox.

4. Click OK.

For more instructions on adding the portlet to a portal page see the Oracle Portal documentation.

Verifying the Portlet Provider Is Running

The Oracle 9iFS portlet provider is available at the following URL:

http://<hostname>:<port>/ifs/portlet  

The hostname is the name of the machine you have installed Oracle 9iFS on. The port is the port of the Apache listener.

Edit Default Parameters

You can edit the following default parameters of the portlet using Oracle 9iFS Manager. For details on changing these parameters, see the Oracle Internet File System Setup and Administration Guide.

• To set whether or not the Quota section of the portlet is displayed: IFS.SERVER.PROTOCOL.PORTLET.QuotaDisplayed=[true|false]

• To set whether or not the Search section of the portlet is displayed: IFS.SERVER.PROTOCOL.PORTLET.SearchDisplayed=[true|false]

• To set whether or not the Files/Folder List is displayed: IFS.SERVER.PROTOCOL.PORTLET.ItemListDisplayed=[true|false]

• To set whether or not top-level folders can be expanded: IFS.SERVER.PROTOCOL.PORTLET.ExpandFolders=[true|false]

• To set the number of items to be listed for each top-level folder:
  IFS.SERVER.PROTOCOL.PORTLET.FolderItemCount=4

• To set which files/folders are listed by default: IFS.SERVER.PROTOCOL.PORTLET.FileList+=HOME_FOLDER
  IFS.SERVER.PROTOCOL.PORTLET.FileList+=/public

Figure 5-1 The Oracle 9iFS Portlet

Text description of the illustration 5portlet.gif

Configure the NFS Server

The Oracle 9iFS Network File System protocol (NFS) server can be configured either as the primary NFS server or as a secondary NFS server. On Unix systems, the standard Unix NFS server will normally be the primary NFS server and the Oracle 9iFS NFS server will be configured as a secondary NFS server. The Oracle 9iFS NFS server can be configured as the primary NFS server provided that the standard Unix NFS server is shut down. Windows NT systems do not have an existing NFS server, so the Oracle 9iFS NFS server is normally configured as the primary NFS server on Windows NT.

The primary NFS server runs on the standard NFS port (port 2049). The primary NFS and Mount servers are also registered with the Portmap server, which allows clients to locate the port numbers for the primary NFS and Mount servers. A secondary NFS server can run on any other port which is not in use. The secondary Mount server may also run on any port which is not in use. The secondary NFS and Mount servers are not registered with the Portmap server since doing so would overwrite the registrations of the primary NFS and Mount servers. Because the secondary NFS and Mount servers are not registered with Portmap, clients must explicitly specify the port number when mounting from the secondary NFS server.

NFS User Authentication

The Oracle 9iFS NFS server uses the system authentication method. The system authentication method allows the user to log in once to the Unix system and access Oracle 9iFS through the NFS server without having to log in again to Oracle 9iFS. The user logs in to Unix using his/her Unix username and password. Using system authentication, it is not necessary for the user to specify his/her Oracle 9iFS password when accessing Oracle 9iFS through the NFS server once he or she has logged into Unix. Access to Oracle 9iFS is granted because the user has already been authenticated when he/she logged on to Unix. The Unix password and Oracle 9iFS password may be different, they do not have to be the same.

The system authentication method uses the user id number (UID) assigned to each Unix user account to identify the user. This assumes that the server machine and the client machines all share a common set of user account definitions. This will generally be true in a network environment where the machines are administered by a central administrator. In this environment, all the machines will share the same set of user accounts and the UIDs for the user accounts will be the same on every machine.

Using the system authentication method, the Oracle 9iFS NFS server receives the UID of the user on each request that it receives from a client. The Oracle 9iFS NFS server maps this UID to an Oracle 9iFS username and then uses this username to access Oracle 9iFS. Normally, the UID will map to an Oracle 9iFS username which is the same as the Unix username; however, it is possible to map the UID to an Oracle 9iFS username which is different from the Unix username. If the Oracle 9iFS NFS server is unable to map the UID to an Oracle 9iFS username, access is given to Oracle 9iFS using the anonymous user, guest.

Configuring the Oracle 9iFS Users for NFS

The Oracle 9iFS NFS server uses a file to define the mapping from the Unix UIDs to the Oracle 9iFS usernames. This file is stored within the Oracle 9iFS repository and is named /ifs/nfs/config/UidToName. This file can be viewed or modified through any of the Oracle 9iFS protocols by a user with administrative privileges. The format of this file is similar to the standard Unix password file, /etc/passwd, which contains Unix usernames and UIDs.

After the initial installation, the /ifs/nfs/config/UidToName file will contain a default mapping which maps all Unix UIDs to the iFS guest user. Because admin privileges are required to update the UidToName file, the initial update of the file after installation must be done by an admin user through a different protocol, such as FTP, SMB, etc.

If the Oracle 9iFS usernames are the same as the Unix usernames, the Unix password file, /etc/passwd, can be copied to /ifs/nfs/config/UidToName. This will cause the Oracle 9iFS NFS server to map the UIDs to an Oracle 9iFS username which is the same as the Unix username. After copying /etc/passwd to /ifs/nfs/config/UidToName, the /ifs/nfs/config/UidToName file should be edited to change the Unix root user (UID 0) to the Oracle 9iFS account you want to use for root access to Oracle 9iFS. For security reasons, the root user should be mapped to the iFS guest account

If the Oracle 9iFS usernames are not the same as the Unix usernames, then it is necessary to edit the /ifs/nfs/config/UidToName file and create entries for mapping the Unix UIDs to Oracle 9iFS usernames. This file has the same format as the Unix password file, where each line consists of fields separated by colons. The Oracle 9iFS NFS server only reads the first three fields of the line which are

username : password : uid : 

The password field is ignored and only the username and uid fields are used to create a mapping from the UID to the Oracle 9iFS username. For example, the following entries would map the Unix UID 1123 to the Oracle 9iFS user scott and the Unix UID 1124 to the Oracle 9iFS user guest.

scott:x:1123: 

guest:x:1124: 

Security Considerations

The system authentication method depends upon the server machine and the client machines having the same user accounts and the same UIDs. The system authentication method also depends upon being able to trust the client machines and that root access to the client machines is secure. If root access to the client machines is not secure, it would be easy for someone on a client machine to create a user with the same UID as a different user on the server machine and then access NFS on the server machine as that user.

For this reason, you may decide to deny access through the Oracle 9iFS NFS server to Oracle 9iFS accounts which contain sensitive data. This can be done by changing the UID mapping in the /ifs/nfs/config/UidToName file to map the UID to a different Oracle 9iFS username, such as guest.

NLS Support

The NFS protocol specifications do not provide any explicit support for the use of non-ascii characters in filenames. By convention, NFS clients will transmit strings, such as filenames, to the NSF server in the default character encoding of the client. The server must use the same character encoding when reading these strings for these strings to be interpreted correctly.

The Oracle 9iFS NFS server has a parameter which specifies the character encoding to be used when interpreting strings which it receives from the clients. To set this parameter, use the Oracle 9iFS Manager to edit the NFS server configuration (NfsServerConfiguration) and add the following parameter name with a value type of String.

IFS.SERVER.PROTOCOL.NFS.CharacterEncoding

The value of this parameter should be set to a Java character encoding name, such as ISO8859_1 or CP437. This will be the character encoding used by the Oracle 9iFS NFS server to interpret strings received from the clients.

Supporting Hummingbird NFS Maestro Clients

Hummingbird NFS Maestro clients require services in addition to those provided by the Oracle 9iFS NFS server. These services include

• An authentication server to validate the username and password used by the client to link to a directory on the NFS server.

• A lock server to support DOS style locking.

Hummingbird supplies a daemon program called hclnfsd which supplies these services. The hclnfsd program is supplied by Hummingbird in source code format which can be compiled for different Unix platforms. Refer to the Hummingbird NFS Maestro documentation for information on compiling and running the hclnfsd program.

The hclnfsd daemon must be running on at least one Unix machine in order to provide an authentication service to the NFS Maestro clients. If the hclnfsd daemon will be running on a machine which is different than the iFS NFS server machine, the NFS Maestro clients should configure the default authentication server to the machine running the hclnfsd daemon.

The hclnfsd daemon also provides a lock server which supports DOS style locking for the NFS Maestro clients. In order to provide support of DOS style locking, the hclnfsd daemon must be running on the same machine as the iFS NFS server. If there are multiple iFS NFS server machines, then the hclnfsd daemon should be started on each of these machines.

If the hclnfsd daemon is not running on an Oracle 9iFS NFS server machine, then DOS style locking will not be available to NFS Maestro clients linking to that server. Without DOS style locking, Oracle 9iFS will still prevent two users from simultaneously updating a file. However, if the hclnfsd daemon is not available and the NFS Maestro client tries to use DOS style locking there may be a considerable delay and the NFS Maestro client may appear to hang. If the hclnfsd daemon is not available, the NFS Maestro client should disable DOS style locking by unchecking the DOS style sharing box or specifying the '/L:' option on the command line.

Special Considerations for Oracle 9iFS Servers on Windows NT

The hclnfsd daemon is a Unix based program. If the Oracle 9iFS NFS server is running on a Windows NT system, then there must be at least one Unix system on the network on which to run the hclnfsd daemon as an authentication server. Since it is not possible to run the hclnfsd daemon on the Windows NT system running the Oracle 9iFS NFS server, DOS style locking will not be available for the Oracle 9iFS NFS server running on Windows NT. NFS Maestro clients linking to an Oracle 9iFS NFS server running on Windows NT should disable DOS style sharing.

Limitations

The Oracle 9iFS NFS server has the following limitations.

• The Oracle 9iFS NFS server does not allows access to the checked out version of a versioned document.

  The Oracle 9iFS NFS server does not allow access to the checked out version of a versioned document because this would violate the algorithm for the NFS client caching of files. NFS provides for caching of files on the client in order to improve performance. The client caching algorithm assumes that the contents of a file are the same for all users and that it can return the cached contents of a file to any user requesting that file. Allowing access to the checked out version of a document would violate this rule because the user who has the document checked out would see different contents from other users.

• A versioned document cannot be deleted, moved or renamed.

  A versioned document cannot be deleted, moved or renamed. This is to prevent programs such as MS Office from deleting previous versions of a versioned document. Programs such as MS Office save files by first saving the data to a temporary file, deleting the original file and then renaming the temporary file to the original name. In the case of versioned documents, this would result in the loss of previous versions.

• Handles returned by the Oracle 9iFS NFS server are not compatible with the Unix lock manager (NLM).

  Programs that try to lock a file from the Oracle 9iFS NFS server will see an error returned by the Unix lock manager. Programs that require the Unix lock manager will not work with the Oracle 9iFS NFS server.

• Unix links (hard links and symbolic links) are not supported

  Unix style links are not compatible with Oracle 9iFS. Oracle 9iFS links may be used instead.

• Changing the owner, group, or mode for a file using the Unix chown, chgrp, and chmod commands is not supported.

  The Oracle 9iFS Command-line Utilities may be used to change the owner and access control list for a file.

Configuring and Using JRE 1.3.0

Oracle 9iFS ships with JRE 1.2.2_05a and is configured to use this JRE by default. Oracle 9iFS is also certified with JDK 1.2.2_05a and JRE 1.3.0. If you would like to configure Oracle 9iFS servers using JRE 1.3.0, do the following:

1. Modify the Oracle 9iFS Java Runtime environment to point to JRE 1.3.0 in the ifsenv.sh file, located under <ORACLE_HOME/9ifs/bin.

   For example, replace:

   IFS_JRE_HOME = $IFS_HOME/jre
   

   with:

   IFS_JRE_HOME = <JRE_PATH>
   

   where:

   <JRE_PATH> points to the location of JRE 1.3.0.

2. If you are running Oracle 9iFS servlets in a separate Jserv process, modify the Java Virtual Machine Interpreter, location in the ifsprops.properties file located under <ORACLE_HOME>/Apache/Jserv/etc.

   For example, replace:

   wrapper.bin = $ORACLE_HOME/9ifs/jre/bin/java
   

   with:

   wrapper.bin = <JRE_PATH>/bin/java
   
   

3. If you are running Oracle 9iFS servlets in the default Jserv process, modify the Java Virtual Machine Interpreter location in jserv.properties, located under <ORACLE_HOME>/Apache/Jserv/etc.

   For example, replace:

   wrapper.bin = $ORACLE_HOME/Apache/jdk/bin/java

   with:

   wrapper.bin = <JRE_PATH>/bin/java

4. Stop and restart the domain controller, Oracle 9iFS nodes, and the Oracle 9iFS Jserv process or the Oracle HTTP Server.

   Note: If you run ifsconfig again, the above changes will need to be performed again.