5
Client Access Paths and Software

Once the Oracle Content Management SDK has been configured and is running successfully, administrators should create user accounts and groups, and set up a directory structure under mount points that are appropriate for the working environment. Topics in this chapter include:

• Client Access Paths

• Oracle FileSync Client Software

• CUP (Command-Line Utilities Protocol) Client [Administrators Only]

Client Access Paths

With an account name and password, users, including developers, administrators, or end users, can access Oracle CM SDK using the client tool of their choice. Web users can use a Web browser for HTTP access. Windows users can map drives or use WebDAV, and Macintosh users can use the Chooser to mount AFP (AppleTalk Filing Protocol) protocol server. Table 5-1 lists some of the supported client platforms, access methods, and protocols supported. See the Oracle Content Management SDK Release Notes for complete client certification information.

Table 5-1  Client Platforms and Protocol Support

Client Platform	Protocols Supported	Access Using
Windows	FTP, HTTP, SMB, WebDAV, NFS (Hummingbird Maestro), CUP	Browser, Windows Explorer, Oracle FileSync utility
Macintosh (Mac OS 10.2)	AFP, FTP, HTTP	Macintosh Go Menu (Mac OS X), Browser
UNIX	FTP, NFS, CUP	command line
Red Hat Linux Adv. Server 2.1 (Kernel 2.4.9-e.16)	FTP, NFS, CUP	mount

Note: For all protocols, if the server to which you are connecting uses DHCP, then you must use the current IP address of the host in the connection syntax instead of the hostname.

The following sections provide additional information about client access to Oracle CM SDK.

• AppleTalk Filing Protocol (AFP) for Mac Clients

• HTTP (Web Browser) and WebDAV Access

• NFS (Network File System) Protocol

AppleTalk Filing Protocol (AFP) for Mac Clients

Oracle CM SDK includes an AFP 2.2-compliant AppleTalk Filing Protocol (AFP) server. A MacOS X client can use the AFP Server as if it were an AppleShare server. The steps required to connect to the AFP server depend on the MacOS on the client. MacOS X clients use the Go menu from the desktop, as detailed below.

The Chooser does not exist in MacOS X. Clients should connect using the new Go menu, as follows:

1. Select Go from the menu.

2. Select Connect to Server. A dialog box appears.

3. Enter the address of the Oracle CM SDK middle-tier computer running the AFP Server in URL format:

   afp://computer-name
   
   

The AppleShare icon appears on the client desktop.

HTTP (Web Browser) and WebDAV Access

Use the following URL to access Oracle CM SDK with HTTP, WebDAV, and Oracle FileSync on UNIX or Windows server platforms:

http://<server-name>:7778/cmsdk/content

Note: The port number varies depending on whether Oracle Application Server Web Cache is configured. If Web Cache is configured, the value is typically 7777.

The URL is required for access from:

• Web browser

• DAV applications, such as Web Folders

• Oracle FileSync utility

NFS (Network File System) Protocol

Oracle CM SDK provides an NFS protocol server that is certified for use with several NFS clients, including:

• Solaris 2.8 and Solaris 2.9

• Red Hat Linux Adv. Server 2.1 (Kernel 2.4.9-e.16)

• Windows NT and 2000 Clients using Hummingbird Maestro NFS

If the Oracle CM SDK NFS server is configured as the primary NFS server, then UNIX clients (Solaris 2.8, Solaris 2.9, and Red Hat Linux Adv. Server 2.1) can access the server using the standard NFS mount command, as shown in Table 5-2.

Table 5-2  Mount NFS Server (Configured as Primary NFS Server)

Syntax	Example
mount <host>:<cmsdk_pathname> <mount_point>	mount ifsserver:home /data/ifs

If the Oracle CM SDK NFS server is configured as the secondary NFS server, or if the Oracle CM SDK NFS server is not on the standard port number, Solaris clients must specify the public option and Linux clients must specify the mount port, as described in "Solaris 2.8 and Solaris 2.9 Clients" and "Red Hat Linux Adv. Server 2.1 and Red Hat Linux 8.0 Clients".

Other caveats apply to Hummingbird Maestro clients, as detailed in "Linking an NFS Directory Using the NFS Maestro Network Access Tool".

NFS Server Limitations

Permission mode bits used by native UNIX NFS are not used by the Oracle CM SDK NFS protocol server. Instead, as it does with other protocol servers, Oracle CM SDK NFS uses access control lists (ACLs) to control access.

In addition, the Oracle CM SDK NFS server does not support the following:

• UNIX symbolic and hard links

• UNIX chown, chgrp, and chmod commands

  Use the command-line utilities to change the owner and access control list for a file.

• UNIX lock manager

  Handles returned by the Oracle CM SDK NFS server are not compatible with the UNIX lock manager. Applications requiring UNIX lock manager services do not work with Oracle CM SDK NFS server.

NFS clients cannot access the checked-out version of a versioned document. To avoid potential conflicts, the Oracle CM SDK NFS server does not allow access by NFS clients to the checked-out version of a versioned document.

Versioned documents cannot be deleted, moved, or renamed. Some applications, including Microsoft Office applications, 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. If a document is versioned, this process results in the loss of previous versions.

Solaris 2.8 and Solaris 2.9 Clients

If the Oracle CM SDK NFS server is running as the primary NFS server on the host, users can enter the standard mount command as shown in Table 5-2. If the Oracle CM SDK NFS server is the secondary NFS server on the host, you must explicitly include the port number in the mount command:

mount nfs://<host>:<port>/<cmsdk pathname> /<mount_point>

For example:

mount nfs://ifsserver:2049/home data/ifs

Alternatively, you can use the following command:

mount -o port=<port>,public <host>:<cmsdk pathname> <mount_point>

For example:

mount -o port=2049,public ifsserver:home /data/ifs 

Red Hat Linux Adv. Server 2.1 and Red Hat Linux 8.0 Clients

If the Oracle CM SDK NFS server is running as the primary NFS server on the host, users can enter the standard mount command as shown in Table 5-2. If the Oracle CM SDK NFS server is the secondary NFS server on the host, you must explicitly include the port number in the mount command:

mount -o port=<port>,mountport=<portno1> <host>:<cmsdk pathname> <mountpoint>

For example:

mount -o port=2049, mountport=4048 ifsserver:home /data/ifs

Windows Clients

While client access to NFS is available on all UNIX operating systems, Windows systems require additional client software. Hummingbird Maestro NFS is a Windows client certified for use with Oracle CM SDK NFS Server.

• Windows 2000 users who want to connect to Oracle CM SDK NFS Server must use Hummingbird Maestro NFS 7.0.

• Windows NT users who want to connect to Oracle CM SDK NFS Server can use Hummingbird Maestro NFS 6.0 or later.

See the Oracle Content Management SDK Release Notes for other supported NFS client applications and version numbers.

Note: Enter the fully-qualified hostname (for example, hostname.yourcompany.com) in the Windows client network configuration for the NFS client. Move the NFS client to the top of the list (network access in Network control panel, if you have more than one NFS client installed) to ensure that its driver is used for the connection.

Linking an NFS Directory Using the NFS Maestro Network Access Tool

Before using the Hummingbird NFS Maestro client to access the Oracle CM SDK NFS server, check that the NFS Maestro client is properly configured.

1. From the NFS Maestro folder, start the NFS Network Access tool. The NFS Network Access dialog appears.

2. Enter the host name of the Oracle CM SDK NFS server and the pathname in the Network Path field using the following format:

   \\<hostname>\<pathname>
   
   

3. In the Authentication Details area, enter the UNIX username and password for accessing the Oracle CM SDK NFS server. Select System/UNIX Authentication as the Authentication Protocol.

4. Set the following Miscellaneous values:
   • DOS-style sharing: Deselect DOS-style file sharing unless you have the HCLNFSD daemon running on the NFS server computer. HCLNFSD is required for DOS-style file sharing. If the HCLNFSD daemon is not running on the NFS server, response times in accessing files will be unacceptable.

   • UNIX lock manager: Deselect UNIX lock manager if it is checked. The Oracle CM SDK NFS server is not compatible with the UNIX lock manager.

   • CD-ROM: Deselect this box if it is selected. This is used for CD-ROM or other read-only file systems.

5. Click Advanced to display the Advanced Connection Properties dialog.

6. Select Preserve Case for Filename Case.

7. If the Oracle CM SDK NFS server is running as a secondary NFS server, change the value of NFS Port number from the standard port (2049) to the alternate port number that the Oracle CM SDK NFS server is using.

8. To use TCP instead of UDP for connection to the NFS server, select Use TCP.

   TCP uses the standard NFS port 2049. Do not select this box if the Oracle CM SDK NFS server is running on an alternate port.

Linking an NFS Directory Using the Command Line

If the Oracle CM SDK NFS server is the primary NFS server on the host, you can mount Oracle CM SDK using the following Maestro command-line syntax:

nfs link <drive>: \\<host>\<pathname> <username>

For example:

nfs link n: \\ifsserver\home scott

If the Oracle CM SDK NFS server is the secondary NFS server on the host, you must specify the Oracle CM SDK NFS server port number in the command line:

nfs link <drive>: \\<host>\<pathname> <username> /n:<port>

For example:

nfs link n: \\ifsserver\home scott /n:4049.

The nfs link command uses the default values configured for the NFS Maestro Client, unless you specify options listed in Table 5-3.

Table 5-3  Maestro Command-Line Options

Option	Meaning	Usage Note
/L:s	Use DOS-style sharing,	Requires that the HCLNFSD daemon run on the server.
/L:	Disables locking.	Use this parameter if the server does not have the HCLNFSD daemon running.
/M:p	Preserve case of filenames
/A:u	Use System/UNIX authentication	Always use this setting.
/T	Use a TCP connection instead of a UDP connection (optional).	TCP connections always use port 2049. Do not use this option unless the Oracle CM SDK NFS server is running on port 2049 (the default).

Problems are often caused by incorrect port numbers. If the HCLNFSD daemon is not running on the server, then DOS-style locking and sharing must be disabled on the client.

Maestro Error Messages

Table 5-4 lists some common error messages and other Maestro client problems.

Table 5-4  Maestro Client or Server Error Messages or Problem Symptoms

Problem	Corrective Action
"Access denied by server" message	Check that the correct port number is being used for the Oracle CM SDK NFS server. A TCP connection uses the standard NFS port (2049). Do not use this option if the Oracle CM SDK NFS server is running on an alternate port.
"Authorization Error" message	The username and password are invalid. Specify a UNIX username and password that are valid on the authentication server.
"Bad Network Name" message	Verify that the host name and pathname are specified correctly. If they are, then use the NFS Maestro Rpcinfo tool and verify that the NFS server (process number 100003) is running on the host.
Maestro client appears to hang	Verify that the HCLNFSD daemon is running on the server computer. If it is not, either start the daemon (if possible), or verify that DOS-style sharing and UNIX lock manager have been deselected in the Maestro client settings. For the Maestro command line, specify the /L: command-line option when linking to disable locking. You can check all current mapped drives by using Maestro's nfs use command.
"Network Timeout or HCLNFSD/PCNFSD not running on Host" message	Verify that the default authentication server has been configured correctly in the NFS client. Verify that the HCLNFSD daemon is running. Perform the verifications listed for the "Bad Network Name" message.
nfs link command hangs	Verify that the correct host name and port number are specified and that the Oracle CM SDK NFS server is running.
"NFS service not responding" error message	Verify that the correct host name and port number are specified and that the Oracle CM SDK NFS server is running.
"Permission denied" error message	Verify that the host name and pathname are specified correctly. Verify that the port is correctly specified for the Oracle CM SDK NFS server.

Oracle FileSync Client Software

In addition to using the networking protocols or client applications native to the Windows operating system, Windows users can install and use Oracle FileSync to keep local directories on a desktop computer and folders in Oracle CM SDK synchronized.

See the Oracle Content Management SDK Administrator's Guide for Oracle FileSync installation information. See the Oracle FileSync online help for additional information.

CUP (Command-Line Utilities Protocol) Client [Administrators Only]

The Oracle Command-line Utilities Protocol server enables administrators and developers to perform a variety of tasks quickly and easily from a Windows command-line or a UNIX shell. For example, you can batch load users, query the repository to see that users exist, and change and set ACLs. See the Oracle Content Management SDK Administrator's Guide for complete details.

The CUP server runs on the Oracle CM SDK instance, just as any other protocol server. The CUP client (a script file named ifsshell) is installed on the server computer when Oracle CM SDK is configured. The CUP client can be used on the server computer, but administrators and developers typically want to install the software on their client computers so that they can use CUP remotely.

Installing the CUP Client

To install the Command-Line Utilities, perform the following steps to copy the entire directory where the files are located from the Oracle CM SDK server to a directory on your local computer:

1. Create a directory on the local computer for the Command-Line Utilities and navigate to that directory. For example, on a Windows client:

   mkdir cmdline
   cd cmdline
   
   

2. Select the version of the files for the client workstation into which you are installing, and either map a drive (from Windows) or use FTP to connect to that directory on the Oracle CM SDK server (see Table 5-5).

   Table 5-5  Command Line Utilities Client Software Location on the Oracle CM SDK Server

   UNIX Client Software	Windows Client Software
   /ifs/clients/cmdline/unix	/ifs/clients/cmdline/win32

3. Copy the contents of the remote directory to the local directory.

4. In a text editor, open the ifscmdline.sh (UNIX) or ifscmdline.bat (Windows clients) file on the local computer. Edit the parameters listed in Table 5-6 to specify the appropriate path information for the Command-Line Utilities to run from the client and connect to the specified server.

Additional information about the settings is contained in the ifscmdline file.

Table 5-6  ifscmdline Parameters

Parameter	Description	Example
JAVA_HOME	Specify the location of the JDK/JRE installation. UNIX only.	/usr/local/jdk
JRE_CMD	Specify the location of the JDK/JRE binary.	c:\jdk1.4\bin\java (Windows) /usr/local/jdk/bin/java (UNIX)
IFS_CUP_SERVER	Computer name of the server on which the CUP Server is running.	ifstestcomputer
IFS_CMD_CLASSPATH	Location of the cmsdk_client.jar file. Set to the path on the local computer.	c:\cmdline\cmdsk_client.jar (Windows) /usr/cmdline/cmsdk_client.jar (UNIX)
IFS_CUP_PORT	The default port for the CUP protocol is 4180. Enter the correct port if the CUP server is running on a port other than 4180. Note: This parameter appears at the bottom of the ifscmdline file.	4180

Setting the Windows Command-Line Console Codescreen

Before running the command-line utilities, make sure that your command-line console session is set for the WinLatin1 code screen. A code screen is an internal table that the operating system uses to map symbols, such as letters, numerals, and punctuation marks, to a character number. Different code screens provide support for the character sets used in different countries. Code screens are referred to by number. For instance, code screen 437 represents DOSLatinUS.

If you are running the command-line utilities from a Windows computer that has been configured for Western European locale, set the code to 1252 at the console session before running the command-line utilities. Use the following command:

c:\mode con codescreen select=1252

The command-line console lists all console settings, including the codescreen that you just entered.