Skip Headers
Oracle® Content Database Administrator's Guide
10g Release 1 (10.2)
Part Number B31268-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

4 Oracle Content DB Protocol Support

This chapter discusses the protocol servers supported by Oracle Content DB, and the client access paths and software for the supported protocols.

This chapter provides information about the following topics:

About the Oracle Content DB Protocol Servers

Users can connect to Oracle Content DB using protocols appropriate to their platform. For example, Windows users can use the Oracle Drive client or connect using Web Folders, Macintosh users can connect through WebDAV, and UNIX users can connect using FTP. Users on all platforms can connect using HTTP for browser-based access.

Oracle Content DB supports the following protocols:

Table 4-1 lists some of the client platforms, protocols, and access methods supported by Oracle Content DB. See OracleMetaLink at http://metalink.oracle.com for complete client certification information.

Table 4-1 Client Platforms and Protocol Support

Client Platform Protocols Supported Access UsingFoot 1 

Windows

HTTP, WebDAV, FTP/FTPS

Browser, Oracle Drive, Windows Explorer, FTP/FTPS client

Macintosh (Mac OS 10.3)

HTTP, WebDAV, FTP/FTPS

Browser, WebDAV client, FTP client

UNIX

HTTP, FTP/FTPS

Browser, command line

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

HTTP, FTP/FTPS

Browser, command line

Footnote 1 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 host name.

Using FTP with Oracle Content DB

FTP can move large amounts of data faster than the other protocols. For bulk operations, such as migrating files from an existing system, FTP is the preferred protocol. FTP is disabled, by default, after Oracle Content DB is installed and configured.

Oracle Content DB also supports FTPS, which uses SSL to provide a confidential, integrity-protected channel. FTPS defines a mechanism to implement the FTP Security Extensions based on the TLS protocol. There is wide support for FTPS among FTP clients. Do not confuse FTPS with SFTP, a service of the Secure Shell that is not related to FTP. FTPS is also disabled, by default, after Oracle Content DB is installed and configured.

Note that if you define a policy on a folder or Library that requires users to enter data associated with uploaded content, users will not be able to place content in that folder or Library using FTP. This limitation is because the FTP protocol does not provide a facility to enter metadata.

This section contains the following topics:

Accessing Oracle Content DB Using FTP or FTPS

After FTP or FTPS has been enabled, users can use FTP or FTPS with Oracle Content DB, as long as the following requirements are met:

  • An FTP or FTPS client must be installed on the local computer of the user.

  • The user must know which port number to use. The default port number for FTP and for explicit FTPS is 21; the default port number for implicit FTPS is 990.

  • For FTP only, each user must use a separate FTP password for greater security. Users can set their FTP password on the User Preferences page in the Oracle Content DB Web client.

  • Users who are not members of the default Site must specify their realm name when they access Oracle Content DB through FTP or FTPS, in the format username@realmname.

Oracle Content DB supports several FTP Quote commands that users can issue during an FTP or FTPS session. See Appendix F, "FTP Quote Command Reference" for more information.

Note that users with multibyte user names cannot sign on to Oracle Content DB using FTP. For this reason, you should not create Oracle Content DB user names that contain multibyte characters.

Enabling FTP

You can enable FTP for Oracle Content DB so that users can upload and download files using FTP. FTP is disabled, by default, after Oracle Content DB is installed and configured.

To enable the Oracle Content DB FTP server:

  1. Access the Application Server Control and go to the Content DB Home page.

  2. You may want to change the default port number for the FTP server. To do this:

    1. In the Administration section, click Server Configurations.

    2. Click FtpServerConfiguration.

    3. In the Properties section, click IFS.SERVER.PROTOCOL.FTP.Port.

    4. In the Value field, enter the desired port number and click OK.

    5. On the Edit Server Configuration page, click OK.

  3. Return to the Content DB Home page, and in the Administration section, click Node Configurations.

  4. Click the name of the node configuration that corresponds to the node where you want to run the FTP server. You can only run the FTP server on regular nodes; you cannot run FTP on HTTP nodes.

  5. Scroll down to the Servers table and click FtpServer.

  6. Select Active and Initially Started.

  7. On the Edit Server page, click OK.

  8. On the Edit Node Configuration page, click OK.

  9. Return to the Content DB Home page and restart the node.

Repeat this procedure for any additional regular nodes on which you want to run FTP.

Enabling Anonymous FTP Access

For security reasons, anonymous FTP access is disabled by default. If you want to enable anonymous access, you must first modify the FTP server configuration to allow anonymous access, then allow public access to particular folders in Oracle Content DB.

After public access has been enabled for a particular folder, users can connect directly to that folder using anonymous FTP. In most cases, anonymous users should use FTP links to connect. For example, if an administrator only enables public access to the folder /us/TestFiles/PublicViewing, users would need to configure an FTP client to connect directly to that folder. Anonymous users would not be able to connect to the root folder and navigate to the PublicViewing folder, because the us and TestFiles folders do not have public access enabled.

Modifying the FTP Server Configuration

To modify the FTP server configuration to allow anonymous access:

  1. Connect to the Application Server Control and go to the Content DB Home page.

  2. In the Administration section, click Server Configurations.

  3. Click FtpServerConfiguration.

  4. In the Properties section, select IFS.SERVER.PROTOCOL.FTP.AnonymousAllowed and click Edit, or just click the property name.

  5. Set the Value to true and click OK.

  6. On the Edit Server Configuration page, click OK.

  7. Return to the Content DB Home page and restart the node.

Enabling the Ability to Grant Public Access

Before you can allow public access to a particular folder, you must ensure that the ability to grant public access has been enabled at the Site level.

To ensure that the ability to grant public access is enabled for the Site:

  1. Connect to Oracle Content DB as a user with the Content Administrator and User Administrator roles, such as orcladmin.

  2. Change to Administration Mode.

  3. Access the Sharing Properties for the root Site folder.

  4. Ensure that the option Allow public access to be granted has been enabled.

Allowing Public Access to Oracle Content DB Folders

To grant public access to a particular folder:

  1. Connect to Oracle Content DB as a user with the Content Administrator and User Administrator roles, such as orcladmin.

  2. Change to Administration Mode.

  3. Access the Sharing Properties for the folder to which you want to grant public access.

  4. Add the special group Public to this folder. If you cannot add this group, make sure that you enabled the ability to grant public access at the Site level, as described in the previous procedure.

Enabling FTPS

You can enable FTPS for Oracle Content DB so that users can upload and download files using FTPS. The FTPS protocol is disabled, by default, after Oracle Content DB is installed and configured. Users sign on to Oracle Content DB over FTPS using their regular single sign-on password.

There are two types of FTPS supported by Oracle Content DB: implicit FTPS and explicit FTPS. Implicit FTPS secures the channel on connection, while explicit FTPS (Auth TLS) secures the connection when the client issues an AUTH command. An explicit FTPS connection starts out as a regular FTP connection; the connection becomes secure only after the client issues an AUTH command. You can choose to enable the implicit FTPS server, the explicit FTPS server, or both.

To set up FTPS, you first need to use Oracle Wallet Manager to create a new wallet and obtain a security certificate. You must configure the wallet for automatic login. For more information, see Oracle Database Advanced Security Administrator's Guide.

After you have obtained a security certificate, you can use the Application Server Control to enable the Oracle Content DB FTPS servers.

Enabling the Explicit FTPS Server

To enable explicit FTPS:

  1. Connect to the Application Server Control and go to the Content DB Home page.

  2. In the Administration section, click Server Configurations.

  3. Click FtpsServerExplicitConfiguration.

  4. Select IFS.SERVER.PROTOCOL.FTP.Port and click Edit, or just click the property name.

  5. In the Value field, enter the appropriate Explicit FTPS port number (for example, 21) and click OK.

  6. Select IFS.SERVER.PROTOCOL.FTPS.WALLET.Location and click Edit, or just click the property name.

  7. Update the value with the location of the wallet file (for example, /CSHome/WALLET/cwallet.sso) and click OK.

  8. On the Edit Server Configuration page, click OK.

  9. Return to the Content DB Home page and click Node Configurations in the Administration section.

  10. Click the name of the regular node configuration that corresponds to the node where you want to run the Explicit FTPS server.

  11. In the Servers section, select FtpsServerExplicit and click Edit, or just click the server name.

  12. Select Active and Initially Started, then click OK.

  13. On the Edit Node Configuration page, click OK.

  14. Return to the Content DB Home page and restart the node.

Enabling the Implicit FTPS Server

To enable implicit FTPS:

  1. Connect to the Application Server Control and go to the Content DB Home page.

  2. In the Administration section, click Server Configurations.

  3. Click FtpsServerImplicitConfiguration.

  4. Select IFS.SERVER.PROTOCOL.FTP.Port and click Edit, or just click the property name.

  5. Update the Value with the appropriate Implicit FTPS port number (for example, 990) and click OK.

  6. Select IFS.SERVER.PROTOCOL.FTPS.WALLET.Location and click Edit, or just click the property name.

  7. Update the value with the location of the wallet file (for example, /CDBHome/WALLET/cwallet.sso) and click OK.

  8. On the Edit Server Configuration page, click OK.

  9. Return to the Content DB Home page and, in the Administration section, click Node Configurations.

  10. Click the name of the regular node configuration that corresponds to the node where you want to run the Implicit FTPS server.

  11. Select FtpsServerImplicit and click Edit, or just click the server name.

  12. Select Active and Initially Started, then click OK.

  13. On the Edit Node Configuration page, click OK.

  14. Return to the Content DB Home page and restart the node.

Using WebDAV with Oracle Content DB

The WebDAV protocol is enabled, by default, after Oracle Content DB is installed and configured.

Note that if you define a policy on a folder or Library that requires users to enter data associated with uploaded content, users will not be able to place content in that folder or Library using WebDAV. This limitation is because the WebDAV protocol does not provide a facility to enter metadata.

Accessing Oracle Content DB Using WebDAV

Use the following URL to access Oracle Content DB with WebDAV:

http://server_name:port/content/dav

The value for port varies depending on your platform, and depending on whether OracleAS Web Cache is running. If OracleAS Web Cache is running, the typical values are:

  • 7777 for UNIX systems

  • 80 for Windows systems (unless port 80 is in use when the middle tier is configured)

If OracleAS Web Cache is not running, the port number is typically 7778.

Users who are not members of the default Site must specify their realm name when they access Oracle Content DB through WebDAV, in the format username@realmname.

Note that users with multibyte user names cannot sign on to Oracle Content DB using WebDAV. For this reason, you should not create Oracle Content DB user names that contain multibyte characters.

Authenticating Against WebDAV and FTP

The user name that needs to be entered when authenticating against WebDAV and FTP can vary. The user name format depends on whether the user is a member of the default realm, and on the nickname attribute set for the realm in Oracle Internet Directory (uid or mail).

The default nickname attribute is uid. You can use Oracle Directory Manager to view or change the nickname attribute for the realm; see Oracle Internet Directory Administrator's Guide for more information about using Oracle Directory Manager.

Table 4-2 summarizes the user name format that users need to enter for WebDAV and FTP, according to these two factors.

Table 4-2 User Name Format for Authenticating Against WebDAV and FTP

Realm Type Nickname Attribute Example User Names in Oracle Internet Directory Example User Names to Enter When Authenticating Against WebDAV and FTP

Default realm

Example: oracle

uid

user_name

jsmith

user_name

jsmith

Non-default realm

Example: mycompany

uid

user_name

jsmith

user_name@mycompany

jsmith@mycompany

Default realm

Example: oracle

mail

user.name@mydomain.com

jsmith@anotherdomain.com

user.name

jsmith

Non-default realm

Example: mycompany

mail

user.name@mydomain.com

jsmith@anotherdomain.com

user.name@mycompany

jsmith@mycompany

Using Oracle Drive with Oracle Content DB

Oracle Drive is a native Windows application that lets users use Windows Explorer, Microsoft Office, and other Windows applications to access content in Oracle Content DB and other Oracle WebDAV servers such as OracleAS Portal. Oracle Drive displays files and folders in Oracle Content DB as a mapped drive in Windows Explorer. Oracle Drive also provides an effective offline solution that lets users edit files on their computers when offline, and then synchronize with the server when they reconnect.

Oracle Drive is available on the Oracle Drive client CD that comes with the Oracle Content DB software.

Oracle Drive runs on Microsoft Windows 2000 and Windows XP. For the most up-to-date certification information, see OracleMetaLink at http://metalink.oracle.com.

Oracle Drive requires Microsoft .NET Framework 1.1. The Oracle Drive installation installs the Microsoft .NET Framework 1.1 on the client computer.

You can set up an administrator-configured installation of Oracle Drive so that Oracle Drive is automatically deployed on user workstations, or you can copy the Oracle Drive executable to an accessible location so that users can install Oracle Drive themselves. You can also include service details with the Oracle Drive executable so that users don't have to configure their Oracle Drive service. The following sections provide more information about these topics:

Setting Up an Administrator-Configured Installation of Oracle Drive

Setting up an automatic installation of Oracle Drive for your users is strongly encouraged. Oracle Drive is the client of choice for uploading and downloading many files at once, and also provides synchronization capabilities. Setting up an administrator-configured install will encourage user adoption and reduce support calls.

Configuring Oracle Drive Service Details For Your Users

You can choose to specify Oracle Drive service details as part of your Oracle Drive deployment. Setting up an Oracle Drive service for your users is strongly recommended so that users do not have to configure Oracle Drive themselves. Note that individual users can still edit service details as necessary for their own computers.

To specify Oracle Drive service details, update the parameters in the config.xml file. Then, specify the location of the config.xml file in the update.xml file. Both of these files need to be copied to an HTTP server that is accessible to all your users, without requiring a login.

Finally, specify the location of the update.xml file in odrive.ini, then copy it to the same location as the ODriveSetup.msi file. See the "Preparing for Deployment Using Active Directory" for more information about ODriveSetup.msi.

These steps are detailed in the following sections:

Setting Up config.xml

The config.xml file contains the details for the Oracle Drive service you want to deploy. Update config.xml by providing your own values for each parameter. Then, copy the file to an HTTP server that is accessible to all your users, without requiring a login. You can find config.xml in the \Extra folder on the Oracle Drive client CD.

You can configure multiple services for your users by providing additional <item> entries, with parameters, in config.xml. Refer to Table 4-3 for information about the parameters in config.xml.

Example 4-1 shows the format of the config.xml file, with sample values for two services.

Example 4-1 config.xml

<wfc-config>

<item> 
  <type>service</type> 
  <name>Oracle Content DB</name> 
  <hostname>myhost1.company.com</hostname> 
  <port>7777</port> 
  <secure>1</secure> 
  <server-directory>/users/mydir</server-directory> 
  <drive-letter>k</drive-letter> 
  <sharing-level>3</sharing-level> 
  <map-home>1<map-home> 
  <auto-reconnect>2</auto-reconnect>
  <basic-authentication>0</basic-authentication>
</item> 

<item> 
  <type>service</type> 
  <name>Oracle Portal</name> 
  <hostname>myhost2.company.com</hostname> 
  <port>7778</port> 
  <secure>1</secure> 
  <server-directory>/my_location</server-directory> 
  <drive-letter>z</drive-letter> 
  <sharing-level>3</sharing-level> 
  <map-home>1<map-home> 
  <auto-reconnect>2</auto-reconnect>
  <basic-authentication>0</basic-authentication>
</item> 

</wfc-config>

Table 4-3 Parameter Values for config.xml

Parameter Name Description

<type>

The value for this parameter must always be "service." Do not change this value.

<name>

The name of the service (for example, Oracle Content DB) as it will appear in Oracle Drive.

<hostname>

The host name of the Oracle Content DB server (for example, myhost.mycompany.com).

<port>

The port number of the Oracle Content DB server (for example, 7778). If you do not specify this value, the port number defaults to either 80 or 443, depending on the value you specify for <secure>.

<secure>

Whether HTTP or HTTPS will be used to connect to Oracle Content DB. The possible values are:

  • 0 (use HTTP)

  • 1 (use HTTPS)

<server-directory>

The Oracle Content DB folder location to mount, or in other words, the folder location that will appear as the top-level folder when users connect to Oracle Content DB using Oracle Drive (for example, /content/dav/my_site/Libraries/mydir).

You must include /content/dav at the beginning of the specified path.

<drive-letter>

The Windows drive letter to use for this service. The value can be any drive letter from D-Z.

If you do not specify a value, or if the letter you specify is not available, the first drive letter available will be used.

<sharing-level>

The default value for the refresh interval to use for this service.

The longer the refresh interval, the better the performance. However, when the refresh interval is longer, files and directories are refreshed less frequently, so users may notice a lag in seeing file and directory changes made by other users.

In addition, the longer the refresh interval, the fewer server resources are needed (such as CPU or disk I/O).

The possible values are:

  • 0 (1 hour)

  • 1 (15 minutes)

  • 2 (3 minutes)

  • 3 (15 seconds)

<map-home>

Whether to map to the Personal Library of the user by default (if the Personal Library exists). The possible values are:

  • 1 (map to the Personal Library of the user)

  • 2 (do not map to the Personal Library of the user)

The Personal Library can only be mounted if the value for <server-directory> begins with /content/dav.

<basic-authentication>

Whether users can use basic authentication to connect to WebDAV servers that require cleartext passwords. The possible values are:

  • 0 (do not use basic authentication)

  • 1 (use basic authentication)

Because Oracle Content DB does not require cleartext passwords, enter 0 for this parameter.

<auto-reconnect>

Whether or not to automatically connect to the service when Oracle Drive starts. The possible values are:

  • 1 (automatically connect to the service)

  • 2 (do not automatically connect to the service)

Setting Up update.xml

The update.xml file holds the value for the location of the config.xml file. You can find update.xml in the Extra folder on the Oracle Drive client CD.

Edit the update.xml file by providing your own values for each parameter:

  • <date>: Provide a string value (such as a date, in any format, or other representation) that corresponds to the configuration file version you are using. If Oracle Drive detects that the string value has changed since the last time it started, Oracle Drive will process the new config.xml file.

  • <location>: Provide the URL to config.xml.

Then, copy the file to an HTTP server that is accessible to all your users, without requiring a login.

Example 4-2 shows the format of the update.xml file, with sample values.

Example 4-2 update.xml

<?xml version="1.0" ?>
<config-update>
  <date>2006.07.31 13:41:PST</date>
  <location>http://myserver.mycompany.com/config.xml</location>
</config-update>
Setting Up odrive.ini

The odrive.ini file holds the value for the location of the update.xml file. You can find odrive.ini in the Extra folder on the Oracle Drive client CD.

Update odrive.ini by providing the URL for your update.xml file, then copy odrive.ini to the same directory where the ODriveSetup.msi file is located. See the "Preparing for Deployment Using Active Directory" for more information about ODriveSetup.msi.

Example 4-3 shows the format of the odrive.ini file, with sample values.

Example 4-3 odrive.ini

[General]
AutoupdateURL=http://myserver.mycompany.com/odrive/update.xml

Preparing for Deployment Using Active Directory

You must use a Windows Domain Controller computer to deploy Oracle Drive using Active Directory. If you need to promote a Windows 2000 or 2003 server to be a Domain Controller, you can use the Microsoft utility DCPromo.exe.

You must also install Active Directory on the Domain Controller computer, if it is not installed already.

Finally, you must extract the ODriveSetup.msi file, along with other files required for installation, from the Oracle Drive installation executable. To do this:

  1. Open a command prompt and navigate to the directory where the Oracle Drive executable is located.

  2. Exit Oracle Drive, if it is running. To do this, right-click on the Oracle Drive icon in the system tray and choose Exit.

  3. Run the Oracle Drive executable in administrative mode, as follows:

    executable_name /a

    For example:

    ODriveSetup10.2.0.0.0.exe /a

  4. Follow the wizard instructions. On the Network Location screen, specify the location on your local (not network) drive where you want to put the MSI and other files.

  5. Click Finish to exit the wizard.

  6. Copy the files to a public share accessible to all the users of that domain. If you are specifying Oracle Drive service details for your users, make sure to copy odrive.ini to the same location.

Deploying Oracle Drive Using Active Directory

You can use Active Directory to automatically deploy Oracle Drive (using MSI) on user workstations. With this technique, you can deploy Oracle Drive on all computers for your users from a single server.

Microsoft Windows 2000 or later operating systems include tools that allow administrators to install and maintain software applications based on Group Policy. An administrator can assign Oracle Drive to a particular computer by creating a computer-level software distribution Group Policy. Assigning Oracle Drive to user computers is the simplest way to use Group Policy to manage a package. With this method, Oracle Drive is automatically installed on the computer the first time a designated computer is started and the software installation portion of the Group Policy is applied.

This feature allows administrators to set up the environment required for the whole group, including specifying Oracle Drive service details.

To set up an automatic installation of Oracle Drive using Active Directory and MSI:

  1. From the Windows Start menu, choose Active Directory for Users and Computers. The Active Directory application appears.

  2. In the tree view, under the domain name, create a new organization unit (for example, OdriveOU).

  3. By default, all the computers in the domain appear in the Computers organization unit. Move the computers on which you want to deploy Oracle Drive to the new organization unit you created in Step 2.

    Oracle recommends you deploy Oracle Drive to a small subset of computers first, for testing purposes, before deploying to your entire organization.

  4. Right-click the organization unit you created and select Properties.

  5. Click the Group Policy tab and create a new group policy object link.

  6. Double-click the group policy object link you created in Step 5. The Group Policy Object Editor appears.

  7. In the tree view, go to Computer Configuration > Software Settings > Software Installation. Ensure that Software Installation is selected, then right-click in the right pane and choose New > Package.

  8. Specify the extracted MSI file for the new package, then, in the Deploy Software dialog box, select Advanced for the deployment method.

  9. After you have created the new package, right-click the package and select Properties. Click the Deployment tab and ensure that the Deployment type is set to Assigned, then click OK.

Any errors that occur during the deployment of Oracle Drive will appear in the Event Log for the Windows Domain Controller computer. The Event Log can be viewed locally, or remotely.

Most files installed with Oracle Drive are put in the Oracle Drive installation directory. In addition, Oracle Drive installs additional files in the System32 directory for use by Windows. Table 4-4 lists these additional files.

Table 4-4 Files Installed by Oracle Drive Into the System32 Directory

File Name File Location

tdfsd.sys

Windows_folder\System32\Drivers

TDShell.dll

Windows_folder\System32

TDHook.dll

Windows_folder\System32

XDNP.dll

Windows_folder\System32

ODriveHelper.dll

Windows_folder\System32

Redeploying Oracle Drive

You can upgrade the version of Oracle Drive on user workstations by redeploying Oracle Drive using Active Directory.

To redeploy Oracle Drive:

  1. On the Windows Domain Controller computer, from the Start menu, choose Active Directory for Users and Computers. The Active Directory application appears.

  2. In the tree view, right-click the organization unit you created for the Oracle Drive deployment and select Properties.

  3. Click the Group Policy tab, then double-click the group policy object link. The Group Policy Object Editor appears.

  4. In the tree view, go to Computer Configuration > Software Settings > Software Installation. Right-click the package in the right pane and choose All Tasks > Redeploy application.

Removing Oracle Drive from User Workstations

You can undeploy Oracle Drive from user workstations using Active Directory.

To undeploy Oracle Drive:

  1. On the Windows Domain Controller computer, from the Start menu, choose Active Directory for Users and Computers. The Active Directory application appears.

  2. In the tree view, right-click the organization unit you created for the Oracle Drive deployment and select Properties.

  3. Click the Group Policy tab, then double-click the group policy object link. The Group Policy Object Editor appears.

  4. In the tree view, go to Computer Configuration > Software Settings > Software Installation. Right-click the package in the right pane and choose All Tasks > Remove.

Packaging Service Information with the Oracle Drive Executable

As an alternative to automatically installing Oracle Drive on user workstations, you can provide service information as part of the Oracle Drive executable. Using this method, users install Oracle Drive themselves, but do not have to configure service details after installation completes.

To include service information with the Oracle Drive executable:

  1. Copy the contents of the Oracle Drive client CD to a location on your local hard drive (for example, C:\odrive).

  2. In the Extra folder, open the file config.xml in a text editor. Provide service details, then copy the file to an accessible location. See "Setting Up config.xml" for more information.

  3. In the Extra folder, open the file update.xml in a text editor. Provide the location of config.xml, then copy the file to an accessible location. See "Setting Up update.xml" for more information.

  4. In the Extra folder, open the file odrive.ini in a text editor and provide the location of update.xml. See "Setting Up odrive.ini" for more information.

  5. In the Extra folder, open the file OracleDrive10.2.SED in a text editor. Edit the TargetName, SourceFiles0, and SourceFiles1 properties, as necessary:

    • For TargetName, provide the location where you want to put the Oracle Drive executable.

    • For SourceFiles0, provide the location on your hard drive where you copied the Binaries folder.

    • For SourceFiles1, provide the location on your hard drive where you copied the Extra folder.

    If you copied the Oracle Drive files to C:\odrive, you can keep the defaults and skip this step.

    The following example shows a portion of the OracleDrive10.2.SED file:

    TargetName=C:\odrive\OracleDrive10.2.exe
FriendlyName=Oracle Drive 10.2.0.0.0
AppLaunched=ODUpgrade.exe
PostInstallCmd=<None>
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="ODriveSetup10.2.0.0.0.exe"
FILE1="ODUpgrade.exe"
FILE2="dotnetfx.exe"
FILE3="odrive.ini"
[SourceFiles]
SourceFiles0=C:\odrive\binaries\
SourceFiles1=C:\odrive\extra\
[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=
[SourceFiles1]
%FILE3%=

  6. Use the IExpress utility to re-package the files into a self-extracting executable. To do this, open a command prompt and go to the location where the SED file is located, then run this command:

    iexpress /N OracleDrive10.2.SED

  7. Copy the Oracle Drive executable to a location where users can download it. You can find the executable at the location you specified for TargetName in the SED file.

Installing Oracle Drive from the Client CD

If you choose not to set up the administrator-configured installation of Oracle Drive for your users, you can copy the installation files from the Oracle Drive client CD to a location where your users can download them. In order to install Oracle Drive, there must available disk space equivalent to twice the size of the install files

The following instructions explain how to install Oracle Drive from the client CD or from a posted location.


Note:

If you install Oracle Drive on a computer that has firewall software running, such as the native Windows XP firewall, you may see a message similar to the following: 
Windows Security Alert: To help protect your computer, Windows Firewall has blocked some features of this program.  Do you want to keep blocking this program? ODFWAgent.exe

If you see this message, select Unblock to allow Oracle Drive to run.

To install Oracle Drive:

  1. On the Oracle Drive client CD, or from the location where the installation files have been posted, double-click the Oracle Drive executable.

  2. If you are accessing the installation files from a remote location, in the File Download window, select Run this program from its current location, then click Yes in the warning dialog box.

    You can also download the installation program to your local hard drive and run it from there. After downloading, double-click the executable file to begin installation.

  3. If you have a previous version of Oracle Drive installed, the installation wizard prompts you to uninstall the previous version first. You must close any browser windows you have open before proceeding.

  4. Oracle Drive requires Microsoft .NET Framework 1.1. If you do not have Microsoft .NET Framework 1.1, the installation wizard will install it for you.

  5. On the Choose Setup Language screen, select a language and click OK.

  6. On the Welcome screen, click Next.

  7. On the Destination Folder screen, accept the default installation directory, or click Change to select a different installation directory. Then, click Next.

  8. On the Miscellaneous Options screen, choose whether to add a shortcut to Oracle Drive on your desktop, and whether you want Oracle Drive to start automatically when Windows starts. Then, click Next.

  9. On the Ready to Install the Program screen, click Install to install Oracle Drive, or click Back to change any values that you entered.

  10. On the InstallShield Wizard Completed screen, click Finish.

  11. The Oracle Drive installer prompts you to restart your computer. Select Yes to restart your computer automatically, or select No and restart your computer manually.

For complete information about how to set up a WebDAV connection between Oracle Drive and Oracle Content DB, as well as information about how to use Oracle Drive, see the Oracle Drive Help.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us