Skip Headers

Oracle Content Management Software Development Kit (Oracle CM SDK) Installation Guide
Release 9.0.3 for Windows NT/2000

Part Number B10053-01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

5
Client Access Paths and Software

Once Oracle CM 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.

Client Access Paths

With an account name and password, users--developers, administrators, or regular end-users--can access Oracle CM SDK using the client tool of their choice. Web users can use the HTML Admin tool for HTTP or FTP access. Windows users can map drives or use WebDAV; 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, NTFS, WebDAV, IMAP, SMTP

Windows Explorer; Oracle FileSync utility; Netscape Messenger

Macintosh

AFP, IMAP, SMTP

Macintosh Chooser (MacOS 9.x); Macintosh Go... Menu (Mac OSX.1); Netscape Communicator

UNIX

FTP, NFS

mount, link commands

Red Hat Linux 6.2

FTP, NFS

mount

This section provides some additional information about client access to Oracle CM SDK.

AppleTalk Filing Protocol (AFP) for Mac Clients

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

From MacOS 9.x Clients:

  1. Select Chooser...from the Apple menu. AppleShare servers, printers, and other resources display.

  2. Click on the AppleShare icon. AppleShare servers display in the right pane.

  3. Click the Server IP Address... button in the lower portion of the dialog. A subsequent dialog displays.

  4. Enter the IP address of the Oracle CM SDK machine running AFP Server.

The AppleShare icon displays on the client desktop.

From MacOS X Clients:

In MacOS X, the Chooser doesn't exist. Clients should connect using the new Go... menu, as follows:

  1. Select Go...from the menu.

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

  3. Enter the address of the Oracle CM SDK machine running AFP Server as a URL, as follows:

    afp://machine_name
    
    

The AppleShare icon displays on the client desktop.

WebDAV and Oracle FileSync Access

WebDAV and Oracle FileSync access to Oracle CM SDK is through the following URL:

http://server_name:7778/cmsdk/content

Note: Port number may vary depending on whether or not Webcache is configured.

This URL is required for access from:

NFS (Network File System) Protocol

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

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 its other protocol servers, Oracle CM SDK NFS uses ACLs (access control lists) to control access. That means that displaying the permission mode bits from an NFS client is meaningless.

The Oracle CM SDK NFS server also does not support:

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 would result in the loss of previous versions.

Solaris 7 and Solaris 8 Clients

If the Oracle CM SDK NFS server is running as the primary NFS server on the host, users can enter the following standard mount command:

mount host:pathname mount_point

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/home /data/ifs

For example, mount nfs://ifsserver:4049/pathname mount_point

Alternatively, you can enter:

mount -o port=port, public host:pathname mount_point

For example, mount -o port=4049, public ifsserver:home /data/ifs

Red Hat Linux 6.2 Clients

If the Oracle CM SDK NFS server is running as the primary NFS server on the host, users can enter the following standard mount command:

 mount host:pathname mount_point

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, as shown below:

mount -o port=port,mountport=port1 host:pathname mount_point

For example, mount -o port=4049, 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 one such client certified for use with Oracle CM SDK NFS Server.

See the Release Notes for other supported NFS client applications and version numbers.


Note:

Enter the fully-qualified hostname (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, you should 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 displays.

  2. Enter the host name of the Oracle CM SDK NFS server and the pathname in the Network Path field using this 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 Miscellaneous values:

    • DOS-style sharing: De-select DOS-style file sharing unless you have the HCLNFSD daemon running on the NFS server machine. 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: De-select UNIX lock manager if it's checked. The Oracle CM SDK NFS server is not compatible with the UNIX lock manager.

    • CD-ROM: De-select this box if it's selected. (Used for CD-ROM or other read-only filesystem.)

  5. Select the Advanced button 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 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 the Use TCP box. (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 Maestro command-line syntax, as follows:

nfs link drive: \\hostname\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, as follows:

    nfs link drive: \\host\pathname username /n:4049 

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-2.

Table 5-2 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 hclnsfd 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 port 2049 (the default).

Common problems are often due to incorrect port numbers. If the hclnfsd daemon is not running on the server, be sure that DOS-style locking and sharing is disabled on the client.

Maestro Error Messages

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

Table 5-3 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. Note: A TCP connection will always use 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 may have been specified incorrectly. Make sure that a UNIX username and password which are valid on the authentication server are specified.

"Bad Network Name" message

Verify that the host name and pathname are correctly specified. 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 machine. If it's not, either start the daemon (if possible), or verify that DOS-style sharing UNIX lock manager have been de-selected in the Maestro client settings. For the Maestro command line, be sure to specify '/L:' on the command line 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 correctly configured 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 correctly specified. 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 machine and folders in Oracle CM SDK synchronized.

Installing Oracle FileSync

Oracle FileSync is Windows client software that enables users to keep files synchronized between their local machine and Oracle CM SDK. To install FileSync, users should follow these steps:

  1. Save and exit all Windows applications.

    • If you have a previous release of Oracle FileSync software installed, be sure to first uninstall it by using the Add/Remove Programs control panel.

  2. Map a drive (for example O:) to the Oracle CM SDK server directory and navigate to:

    O:\ifs\clients\filesync\ 
    
    
  3. Double-click Setup.exe to run the installation program, or run O:\ifs\clients\filesync\setup.exe from the Windows Start...Run Menu.

  4. Follow the instructions and accept the defaults. The application will be installed in the Windows client machine in the directory:

    c:\Program Files\Oracle\Oracle 9iFS FileSync\ 
    
    
  5. To start the FileSync application, select Oracle FileSync from the Windows Start -> Programs menu.

See the Online Help for additional information about using Oracle FileSync.

CUP (Command-line Utilities Protocol) Client

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 Administration Guide for complete details.

The CUP server runs on the Oracle CM SDK instance, just as any other protocol server. The CUP client (a .jar file) is installed on the server machine when Oracle CM SDK is configured, and can be used on the server machine, but administrators and developers will likely want to install the software on their UNIX workstations and Windows machines so that they can use CUP remotely.

Installing the CUP Client

To install the Command Line Utilities, simply copy the entire directory where the files are located from the Oracle CM SDK server to a directory on your local machine, as follows:

  1. Make a directory on the local machine for the Command Line Utilities, and change to that directory; for example, on a Windows client:

    prompt>mkdir cmdline
    prompt>cd cmdline
    
    
  2. Select the version of the files for the client workstation into which you're installing, and either map a drive (from Windows) or use FTP to connect to that directory (see Table 5-4).

    Table 5-4 Command Line Utilities Client Software Location on the Oracle CM SDK Server
    Client Tool UNIX Client Software Windows Client Software

    Command Line Utilities

    /ifs/clients/cmdline/unix

    /ifs/clients/cmdline/win32

  3. Copy the contents to the local directory.

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

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

Table 5-5 ifscmdline Parameters
Parameter Description Example

IFS_CMD_CLASSPATH

Location of the cmsdk_client.jar file. Set to the path on the local machine.

c:\cmdline\cmsdk_client.jar

IFS_CUP_SERVER

Machine name of the server on which the Command Line Utility Protocol (CUP) Server is running.

ifstestmachine

IFS_CUP_PORT

The default port for CUP protocol is 4180. Enter the correct port number in the ifscmdline file if the CUP server is running on a port other than 4180.

set IFS_CUP_PORT=4182

Setting the Windows DOS Console Codepage

Before running the command-line utilities, you must make sure that your DOS console session is set for WinLatin1 code page. A code page 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 pages provide support for the character sets used in different countries. Code pages are referred to by number. For instance, code page 437 represents DOSLatinUS.

If you are running the command-line utilities from a Windows machine that has been configured for Western European locale, you should set the code to 1252 at the console session before running the command-line utilities, as follows:

c:\mode con codepage select=1252

The console displays a status listing of all console settings, including the codepage just entered.

For more information about using the Command Line Utilities, see the Oracle Content Management SDK Administration Guide.


Go to previous page Go to next page
Oracle
Copyright © 1999, 2002 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Contents
Go To Index
Index