| Oracle Internet File System Installation Guide Release 9.0.1.1.0 for Microsoft Windows NT/2000 Part Number A85272-03 |
|
This chapter describes installation of the client packages used with Oracle 9iFS. Various clients are provided for administrators and end users. Topics include:
The Oracle 9iFS Windows Utilities provides users with Microsoft Windows clients access to content management features such as check-in/check-out and versioning.
The Oracle 9iFS Windows Utilities installation package is loaded into the Oracle 9iFS server, in the /ifs/clients/winui directory. To access this directory from a Windows client, users can map a network drive using SMB or use the Network Neighborhood. They can also access this directory using FTP.
To install the Oracle 9iFS Windows Utilities, users should follow these steps:
Setup.exe file in the /ifs/clients/winui/ directory.
Setup.exe program, or run it from the Run command in the Start Menu.
By default, the Oracle 9iFS Windows Utilities are installed in the following directory:
C:\Program Files\Oracle\iFS
Three required Microsoft components will be installed if they are not already on your system:
Once you've installed the Oracle 9iFS Windows Utilities, the Windows Explorer File menu and the Windows Explorer context menu (right-click menu) will include utilities for advanced Oracle 9iFS features. To view the context menu, right-click a file or folder on an Oracle 9iFS drive.
To access Oracle 9iFS through HTTP, use the following URL:
http://<server-name>:<port-number>/ifs/files
This URL is required for the following:
The Oracle 9iFS portlet is a Portal component that gives users a summary of information about their Oracle 9iFS data. On the portlet, users can see their quotas, initiate a search, list documents or folders, and upload documents. The portlet links to the Oracle 9iFS Web interface.
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 FileSync component provides users with a restricted disconnected client for Oracle 9iFS. This component is only installable on a Windows client PC. To install the FileSync component, users execute the Setup.exe self-installing file located in the /ifs/clients/filesync directory in an Oracle 9iFS repository. They can access this file using SMB, WebFolders, or the Web interface. The steps for users to follow are:
The Oracle 9iFS Command Line Client Utilities are available on any machine where Oracle 9iFS has been installed. They can also be installed on a Solaris client or a PC, or by copying a directory from the Oracle 9iFS server to a directory on your local machine.
You can map a network drive using SMB or use the Network Neighborhood on your local machine to access these directories. You can also access these directories using FTP.
|
Note: You do not need to perform any of the following tasks if you are not installing the Command Line Utilities on a separate client machine. |
To install the Oracle 9iFS Command Line Utilities:
c:\cd cmdline
/ifs/clients/cmdline/unix.
ifs/clients/cmdline/win32.
c:\cmdline in the example above.
ifscmdline.sh or ifscmdline.bat file. If you are using a Windows client, use WordPad to save the formatting.
IFS_CMD_CLASSPATH--The location of the cmdlineutils.jar file. Set to the path on the local machine; for example, c:\cmdline\cmdlineutils.jar in the example.
IFS_COOKIE_DIRECTORY--The session information for the Command Line Client Utilities is maintained in the IfsCookie file, which is generated each time a user logs in. This variable specifies where this file should be placed on the local system. If this variable is not set, the IfsCookie file will be saved into the current working directory.
JRE_CMD--The location of either the JDK binary. For example, C:\jdk1.2.2\bin\java.
IFS_CUP_SERVER--Set this variable to the server where the Command Line Utility Protocol Server (CUP) is running, for example, ifstestmachine. This variable must be set when running the Command Line Utilities on a client machine since the Command Line Utility Protocol Server (CUP) will not be locally available.
IFS_CUP_PORT--All Oracle 9iFS commands access the CUP using the default port, 4180. If the CUP server is started on a port other than 4180, this variable must be set to that port number. For example, if you start the CUP on port 4182, this variable must be set to 4182.
For more information on the Command Line Utilities, see the Oracle Internet File System Setup and Administration Guide.
The Network File System (NFS) protocol is used to provide file sharing between a client machine and a server machine across a network. The NFS protocol is a standard protocol widely used for file sharing on UNIX platforms. Although used primarily on UNIX platforms, the NFS protocol is designed to be operating system-independent and implementations of the NFS protocol exist for other platforms, such as Windows. This section describes how to install NFS clients for the various platforms.
If the Oracle 9iFS NFS server is running as the primary NFS server on the host, then a standard mount command can be used to mount Oracle 9iFS.
Syntax:
mount <host>:<pathname> <mount_point>
Example:
mount ifsserver:home /data/ifs
If the Oracle 9iFS NFS server is not the primary NFS server on the host, then the port number for the Oracle 9iFS NFS server must be explicitly specified. Either of the following two commands can be used to mount a secondary iFS server.
Syntax:
mount -o port=4049,public <host>:<pathname> <mount_point>
Example:
mount -o port=4049,public ifsserver:home /data/ifs
Syntax:
mount nfs://<host>:4049/<pathname> <mount_point>
Example:
mount nfs://ifsserver:4049/home /data/ifs
If the Oracle 9iFS NFS server is running as the primary NFS server on the host, then a standard mount command can be used to mount Oracle 9iFS.
Syntax:
mount <host>:<pathname> <mount_point>
Example:
mount ifsserver:home /data/ifs
If the Oracle 9iFS NFS server is not the primary NFS server on the host, then the port number for the Oracle 9iFS NFS server and the Oracle 9iFS Mount server must be explicitly specified. The following command can be used to mount a secondary Oracle 9iFS server.
Syntax:
mount -o port=4049,mountport=4048 <host>:<pathname> <mount_point>
Example:
mount -o port=4049,mountport=4048 ifsserver:home /data/ifs
Before using the Hummingbird NFS Maestro client to access the Oracle 9iFS NFS server, you will need to check that the NFS Maestro client is properly configured.
NFS Maestro will first try to access an authentication server on the NFS server machine. If an authentication server is not running on the NFS server machine, NFS Maestro will try to use the default authentication server. Check with your system administrator to determine if you will need to specify a default authentication server.
If the Oracle 9iFS NFS server is running as the primary NFS server on the host, then the following NFS Maestro nfs link command can be used to mount Oracle 9iFS.
Syntax:
nfs link <drive>: \\<host>\<pathname> <username>
Example:
nfs link n: \\ifsserver\home scott
If the Oracle 9iFS NFS server is not the primary NFS server on the host, then the port number for the Oracle 9iFS NFS server must be explicitly specified. The following command can be used to mount a secondary Oracle 9iFS server.
Syntax:
nfs link <drive>: \\<host>\<pathname> <username> /n:<port_number>
Example:
nfs link n: \\ifsserver\home scott /n:4049
If no other options are specified, the nfs link command will use the default values configured for the NFS Maestro Client. If the NFS Maestro Client has not been configured for Oracle 9iFS, the following options can be used to set the proper values for the Oracle 9iFS NFS server.
Check that the correct host name and port number are specified and that the Oracle 9iFS NFS server is running.
Check that the host name and pathname are correctly specified. Also check that the correct port is specified for the Oracle 9iFS NFS server. If the Oracle 9iFS NFS server is not on the standard port number then the 'public' option must be specified on Solaris and the mount port must be specified on Linux. Note: The 'public' option is not supported in Solaris 2.6.
If you are using DOS-style sharing and the hclnfsd daemon is not running on the server machine, or you are using UNIX lock manager, the NFS Maestro client will appear to hang or respond very slowly. Uncheck the DOS-style sharing and UNIX lock manager options or specify '/L:' on the command line.
From a command prompt, enter the command 'nfs use'. This will list your current NFS Maestro mapped drives and their parameters. Check that the locking parameter is '/L:'.
NFS Maestro was unable to connect to the authentication server. Check with the system administrator if the hclnfsd daemon is running or check if the default authentication server is specified correctly. Also, see the troubleshooting section for "NFS Maestro reports 'Bad Network Name.'"
The username and password may have been specified incorrectly. Make sure that a Unix username and password which are valid on the authentication server are specified.
Check that the host name and pathname are correctly specified. If these are correctly specified, then use the NFS Maestro Rpcinfo tools to check if the NFS server, program number 100003, is running on the host. If Rpcinfo does not show an NFS server running on the host, check with the system administrator to see if the NFS server is running.
Check that the correct host name and port number are specified and that the Oracle 9iFS NFS server is running.
Check that the correct port number is being used for the Oracle 9iFS NFS server. Note: A TCP connection will always use the standard NFS port (2049). Do not use this option if the Oracle 9iFS NFS server is running on an alternate port.
|
|
![]() Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|