Skip Headers
Oracle® Content Database Installation Guide
10g Release 1 (10.2.0.0.0) for HP-UX PA-RISC (64-Bit)

Part Number B31416-01
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

7 Oracle Content DB Middle-Tier Postinstallation Tasks

This chapter discusses necessary tasks to perform after installation of Oracle Content DB is complete.

In addition to the tasks described in this chapter, Oracle recommends that upon successful installation of Oracle Content DB, you read Oracle Content Database Administrator's Guide.

This chapter includes the following topics:

7.1 Verifying Oracle Content DB Configuration

To ensure that the Oracle Content DB node and HTTP node are running, run the following opmnctl command:

$ $ORACLE_HOME/opmn/bin/opmnctl status

In opmnctl commands, the Oracle Content DB node typically has the ias-component=Content and process-type=Node parameters. The Oracle Content DB HTTP node typically has the ias-component=Content and process-type=OC4J_Content parameters.

Table 7-1 lists access URLs used with Oracle Content DB basic functionality.

Table 7-1 Expected Oracle Content DB Basic Functionality

Access Method Access URL

Oracle Content DB Web Client

http://middle_tier_host:port/content

Oracle Records DB Web Client

http://middle_tier_host:port/rm

WebDAV

http://middle_tier_host:port/content/dav


Note:

The FTP and FTPS protocols, as well as the Oracle Records DB application, are not enabled by default after you install and configure Oracle Records DB.

See Chapter 5, "Choosing Oracle Content DB Options" in Oracle Content Database Administrator's Guide for information about how to enable Oracle Records DB, FTP, and FTPS.


7.2 Getting Started with Oracle Content DB

This section discusses how to get started using Oracle Content DB after completing the installation.

This section includes the following topics:

7.2.1 Choosing Deployment Options for Oracle Content DB

After you install and configure Oracle Content DB, you can choose various deployment options, depending on your requirements. For example, you can enable Oracle Records DB, integrate Oracle Content DB with an antivirus solution, or enable the FTP or FTPS protocols.


See Also:

"Choosing Oracle Content DB Options" in Chapter 5 of Oracle Content Database Administrator's Guide for information about choosing deployment options

7.2.2 Signing In to Oracle Content DB for the First Time

When you first sign on to Oracle Content DB, use the orcladmin user for the default realm. This user has all of the Oracle Content DB access roles. Once you have signed on, you can delegate access roles to additional users, as well as set defaults for the Site.


See Also:

Oracle Content Database Application Administrator's Guide for more information about delegating access roles and setting Site defaults

7.2.3 Creating Additional Sites

In Oracle Content DB, a Site is a discrete organizational entity whose users can collaborate on files and folders. Users in one Site do not have access to the content of users in another Site. Sites are based on identity management realms.

A default Site, based on the default realm in Oracle Internet Directory, is created during installation. You can create additional Sites using Application Server Control.

7.2.4 Designating an Administrator E-mail Address for Site Quota Notifications

Each Site has an allocated quota that specifies the amount of content (in MB, GB, or TB) that can be stored in the Site. When the quota consumed by any given Site reaches 95% of the allocated quota, an e-mail notification is sent to any users of that Site with the Quota Administrator role, as well as to the administrator e-mail address specified in the IFS.DOMAIN.EMAIL.AdministratorAddress property.

This property is empty by default. To designate an administrator e-mail address at which to receive the quota notifications, use the Application Server Control.

To designate an administrator e-mail address for Site quota notifications:

  1. Access Application Server Control and navigate to the Application Server Home page.

  2. Click the name of the Oracle Content DB domain (typically Content) to access the Content DB Home page. See Oracle Content Database Administrator's Guide for more information about the Oracle Content DB domain.

  3. In the Administration section, click Domain Properties.

  4. On the Domain Properties page, click IFS.DOMAIN.EMAIL.AdministratorAddress. You may need to move to the next page to find this property, or you can use the Search field.

  5. Provide the e-mail address you want to use for receiving error reports in the Value field and click OK.

  6. Return to the Content DB Home page and click Restart Domain.

7.3 NFS Installations

If you installed Oracle Content DB on an NFS disk, you must edit the LockFile directive in the $ORACLE_HOME/Apache/Apache/conf/httpd.conf file so that it points to a local disk. This file is used by Oracle HTTP Server.


See Also:

Oracle HTTP Server Administrator's Guide for more information

7.4 Enabling SSL

Depending on your security requirements, you can enable Secure Sockets Layer (SSL) for the Oracle Content DB middle tier. You can also enable SSL for the connection between Oracle Content DB and Oracle Internet Directory.


See Also:

*Chapter 3, "Oracle Content DB Security" in Oracle Content Database Administrator's Guide for information about configuring SSL for Oracle Content DB, as well as configuring SSL for Oracle Content DB communication with Oracle Internet Directory

7.5 Backup and Recovery

Oracle recommends performing a complete Oracle Content DB environment backup after installing Oracle Content DB. This enables you to restore a working environment in case an error occurs from which you cannot recover.


See Also:

Oracle Content Database Administrator's Guide for information on how to perform a complete Oracle Content DB environment backup

You should also perform a complete Oracle Content DB environment backup after each successful patch set upgrade and after each successful configuration change.