Release 9.0.1.1.0 for Microsoft Windows NT/2000
Part Number A85272-03
 Contents |
 Index |
| Oracle Internet File System Installation Guide Release 9.0.1.1.0 for Microsoft Windows NT/2000 Part Number A85272-03 |
|
This chapter describes post-installation procedures for Oracle 9iFS. Topics include:
Oracle recommends you also complete the tasks in Chapter 5, "Getting Started with Oracle Enterprise Manager," and become familiar with Oracle 9iFS administration and management.
As shown in Figure 3-13, "Oracle 9iFS Configuration Complete Dialog" in Chapter 3, when the Oracle 9iFS Configuration Assistant successfully completes, the Oracle iFS Configuration Complete window displays a list of several additional tasks you must perform before you can begin using Oracle 9iFS. This section details those and other related tasks necessary to get Oracle 9iFS up and running.
If you did not restart the computer when the Oracle iFS Configuration Assistant completed, do so now. When the machine restarts, follow the steps below to confirm that the Oracle services also restarted. You'll find these services in the Windows NT or Windows 2000 control panel; the service name includes the name of the Oracle home. Access the Services control panel as follows:
Table 4-1 Oracle Services Listed in Windows NT/2000 Services Control Panel
Depending on your specific deployment, only some of these may be running on the machine. For example, in a multiple machine installation in which the database is on one machine and Oracle 9iFS is on another machine, the Oracle Management Service will likely be running on the database machine only.
Restarting the HTTP Server (Oracle<oracle_home>HTTP Server) does not start the Oracle 9iFS JServ process. You must restart JServ manually on each machine where Oracle 9iFS has been installed, as follows:
%ORACLE_HOME%\9ifs\bin sub-directory and execute this command:
ifsjservctl -start
At this point, you can start the Oracle 9iFS node, start the domain, and test basic operations. To keep the installation process simple and ensure that Oracle 9iFS is functioning properly, use the first three batch file (scripts) listed in Table 4-2 to startup the domain and the node, and then check basic functionality of Oracle 9iFS.
Once you've established that your installation and configuration succeeded, you can perform other tasks in the Optional Post-installation Tasks section. You should also proceed to the Chapter 5, "Getting Started with Oracle Enterprise Manager," and complete the setup for the integrated Oracle Enterprise Manager and Oracle 9iFS Management Consoles.
All the batch files listed in Table 4-2 are located in the sub-directory:
%ORACLE_HOME%\9ifs\bin
Run the launch and start commands in the order shown in Table 4-2. When you run ifsstartdomain, you will be prompted for the Oracle 9iFS schema password, and then shortly after you enter the appropriate password, an Operation Successful message displays. The domain and the node are now operational, and you can begin using Oracle 9iFS.
Each of these scripts leaves a command prompt console window open on the machine. To avoid having these console windows open, you should follow the steps in Chapter 5, "Getting Started with Oracle Enterprise Manager," so that you can use Oracle 9iFS Manager to start and stop the domain and nodes (and thus avoid having a user account logged on to keep these processes running).
To validate that the domain and node started and that the core Oracle 9iFS components are working, you can attempt to connect to the system from another machine on the network.
Not all Oracle 9iFS protocols are started automatically. For example, on Windows NT or Windows 2000 Oracle 9iFS deployments, you must install and configure NFS components separately, as discussed in Configure the NFS Server.
As shipped, Oracle 9iFS includes three user accounts and default passwords:
scott/tiger guest/welcome system/manager
| Protocol or server | Access address or method | Expected result |
|---|---|---|
| HTTP |
http://<hostname>/ifs/files/ifs |
A browser login dialog will appear. Enter scott/tiger or system/manager to see a directory listing of files in the /ifs directory. |
| Oracle 9iFS Web Interface |
http://<hostname>/ifs/files |
A logon web page should display in the browser. Use scott/tiger or guest/welcome to logon to Oracle Internet File System. |
| SMB |
\\<hostname>\root |
Prompts for Windows domain or workgroup user account. If you logon as Administrator, you will have access to system/manager information. (The scott/tiger, guest/welcome, and system/manager user account/passwords won't work in this mode unless you create corresponding Windows accounts on the Windows NT/2000 server.) See "Enable Windows Users to Map Oracle 9iFS as Network Drives" below. |
You should change passwords for the system and scott user accounts as soon after installation as possible, to avoid potential security breaches. Do not change the guest account, or some protocols will stop functioning. See the Oracle Internet File System Setup and Administration Guide for details about changing user account passwords, including the system user account.
The Oracle 9iFS Web Interface enables Oracle 9iFS users to logon using their Oracle 9iFS accounts without requiring Windows NT/2000 user accounts. However, Windows NT/2000 drive mapping (over SMB) is controlled independently from Oracle 9iFS, by the native Windows security mechanisms. Oracle 9iFS users must be authenticated by Windows before they can access an Oracle 9iFS instance on a Windows NT/2000 server as a Windows file share. That means that in order for users to map Oracle 9iFS NTFS protocol servers as Windows network drives:
Once users have authenticated to Windows, they will gain access to Oracle 9iFS as the user of the same name as the Windows account. Users who don't have accounts in Oracle 9iFS or who have not been authenticated by Windows (because they don't have an appropriate Windows NT/2000 user account) are automatically logged on as guest and will have limited access to Oracle 9iFS.
Oracle 9iFS administrators and Windows NT/2000 administrators should ensure that appropriate user accounts have been created on Windows and in Oracle 9iFS. The individuals associated with Oracle 9iFS user accounts should be the same individuals associated with Windows NT/2000 accounts, to avoid inappropriate access to information.
If the Oracle 9iFS instance is running on a UNIX server, users accessing the NTFS protocol on a UNIX server do not need Windows user accounts and passwords. Users must provide valid Oracle 9iFS user accounts and passwords, or they will automatically be logged on with "guest" status (if the guest account is enabled).
If users are unable to map a network drive to an Oracle 9iFS instance, you (or the Windows NT/2000 administrator) can create a separate Windows NT/2000 file share (independent of Oracle 9iFS), and have users attempt to map to this "test" drive to determine if the problem is with Windows NT/2000. If user cannot map to the native Windows NT/2000 file share, see the Windows NT/2000 documentation to resolve the problem.
Depending on your requirements and the specifics of your Oracle 9iFS deployment, you may want to perform some or all of these post-installation tasks.
None of these tasks is required to get Oracle 9iFS up and running, unless you want to use the JRE 1.3.0 instead of the default, in which case you'll need to make the configuration file changes described in Modifications Required to Support Using JRE 1.3.0.
To use the Oracle 9iFS e-mail servers, you must setup Sendmail for NT on your machine and configure Oracle 9iFS to use it, as follows:
ifsemailsetup batch file (ifsemailsetup.bat), using the location of your Sendmail installation as a command-line argument. For example:
c:\ora9ihome\9ifs\bin\ifsemailsetup e:\PROGRA~1\Sendmail
The Oracle 9iFS portlet is an Oracle Portal component that provides summary 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. You must perform several setup steps to enable Oracle 9iFS users to add the Oracle 9iFS portlet to their 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:
For more instructions on adding the portlet to a portal page see the Oracle Portal documentation.
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 Oracle HTTP listener.
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.
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.
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.
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:
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.
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.
Hummingbird NFS Maestro clients require services in addition to those provided by the Oracle 9iFS NFS server. These services include
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.
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.
The Oracle 9iFS NFS server has the following limitations.
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. 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.
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 style links are not compatible with Oracle 9iFS. Oracle 9iFS links may be used instead.
The Oracle 9iFS Command-line Utilities may be used to change the owner and access control list for a file.
By default, Oracle 9iFS uses JRE 1.2.2_07 (which ships as part of the Oracle HTTP Server). Oracle 9iFS is also certified with JDK 1.2.2_07 and JRE 1.3.0. To configure Oracle 9iFS servers to use JRE 1.3.0, you must modify several files that contain references to the location of the default JRE and point instead to the correct location of the JRE 1.3.0 on your system.
ifsenv.bat (located in %ORACLE_HOME%\9ifs\bin directory) to point to JRE 1.3.0 as the IFS_JRE_HOME. For example, replace:
IFS_JRE_HOME = %IFS_HOME%\jre
with:
IFS_JRE_HOME = <jre_home_for_1.3.0>
where:
<jre_home_for_1.3.0> is the complete path to the location of JRE 1.3.0.
Node.def (located in %ORACLE_HOME%\9ifs\settings). For example, replace:
IFS.DOMAIN.NODE.JavaCommand=%ORACLE_HOME%\9ifs\jre\bin\java -mx256m
with
IFS.DOMAIN.NODE.JavaCommand=<jre_home_for_1.3.0>\bin\java -mx256m
IfsManager.def file. For example, replace:
DashboardJVMCommand = <IFS_JRE>/bin/java
with
DashboardJVMCommand = <jre_home_for_1.3.0>\bin\java
ifsprops.properties file located under %ORACLE_HOME%\Apache\Jserv\conf. For example, replace:
wrapper.bin = %ORACLE_HOME%\9ifs\jre\bin\java
with:
wrapper.bin = <jre_home_for_1.3.0>\bin\java
jserv.properties, located under %ORACLE_HOME%\Apache\Jserv\conf. For example, replace:
wrapper.bin = %ORACLE_HOME%\Apache\jdk\bin\java
with:
wrapper.bin = <jre_home_for_1.3.0>\bin\java
The Oracle HTTP Server for Oracle9i is powered by Apache coupled with JServ. There are two ways to run servlets in this infrastructure:
The default JServ configuration for Oracle 9iFS is a separate JServ process that must be manually started from a command line (see "Starting and Stopping Oracle 9iFS JServ" below). It runs as a separate process and listens on another port. When you install Oracle 9iFS, this is the JServ process in which Oracle 9iFS Servlets run.
The configuration files are located in ORACLE_HOME%\Apache\Jserv\conf, and include jserv.conf, ifs.properties, and ifsprops.properties. You do not need to modify these files to activate the default Oracle 9iFS behavior, but you do need to start the JServ process:
Use the ifsJservctl batch file (located in the %ORACLE_HOME%\9ifs\bin directory).
| ifsJservctl -start |
Starts the 9iFS JServ process. |
| ifsJservctl -stop |
Stops the 9iFS JServ process. |
The standard Oracle JServ process is launched by the Oracle HTTP Server web server when the Oracle HTTP Server starts. It runs in the same process space and listens on the same port as the Oracle HTTP Server.
To use the standard Oracle JServ process (rather than the default Oracle 9iFS JServ process), you must modify several configuration files:
To use this configuration, modify the files listed below, located in the %ORACLE_HOME%\Apache\Jserv\conf directory:
jserv.conf
Remove the comment (#) from this line:
#ApJServMount /ifs /ifs
Comment-out (add a "#") this line :
ApJServMount /ifs ajpv12://localhost:13138/ifs
The file contains instructions above each of the lines.
jserv.properties
In the iFS section of the file only, comment-out all the wrapper declarations and the zone declarations. The section is very clearly marked in the file.
Stop the Oracle 9iFS Jserv process, if it's running, and restart the Oracle HTTP Server; the iFS Servlets are enabled by starting and stopping the Oracle HTTP Server.
These tasks need only be completed if you upgraded an existing Oracle Internet File System instance that included Oracle Text to the current release.
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\log directory for any problems during the re-indexing.
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.
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|