| Oracle® Content Database Administrator's Guide 10g Release 1 (10.2) Part Number B31268-02 |
|
|
View PDF |
| Oracle® Content Database Administrator's Guide 10g Release 1 (10.2) Part Number B31268-02 |
|
|
View PDF |
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. Each Site has an allocated quota that specifies the amount of content (in MB, GB, or TB) that can be stored in the Site. Oracle Content DB Sites are based on identity management realm.
You can use the Application Server Control to create new Sites, or enable, disable, modify, or delete existing Sites. You can also grant the Security Administrator role to a particular Site user.
This chapter provides information about the following topics:
Oracle Content DB Sites are based on realms that were defined in Oracle Identity Management. A realm is a collection of identities and associated policies that is typically used when enterprises want to isolate user populations and enforce different identity management policies for each population.
Each installation of Oracle Content DB has a default Site, based on the default realm in Oracle Identity Management.
|
Important: If you want to choose another realm as the default, or if you want to change the name of the default realm, you must make the change before you install and configure Oracle Content DB. You cannot change the default realm or realm name after Oracle Content DB has been installed and configured. |
You can create and manage additional realms using the Oracle Internet Directory Self-Service Console. You must configure OracleAS Single Sign-On for multiple realms if you want to have more than one realm in your deployment. For information about how to do this, see SOracle Application Server Single Sign-On Administrator's Guide.
There are a number of application administrators for each Site who perform functions such as allocating quota and assigning roles. The application administration roles include the User Administrator, Content Administrator, and Quota Administrator. For more information about the application administrator roles and tasks, see Oracle Content Database Application Administrator's Guide.
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 a Site reaches 95 percent of the allocated quota, an e-mail notification is sent to the administrator e-mail address, and to any users of that Site with the Quota Administrator role. The administrator e-mail address is specified in the IFS.DOMAIN.EMAIL. AdministratorAddress domain property. See "Changing Domain Properties" for information about how to specify this administrator e-mail address.
Quota warning e-mail notifications are issued by the Cleanup Agent. You can change the properties of this agent to adjust the warning threshold, or to specify whether files in the Archive count against Site quota. These properties are not Site-specific; they apply to all the Sites in your deployment. See "Cleanup Agent" for more information about these properties.
Each new Site that you create must be based on an existing realm; if all the realms have been used for other Sites, you must create a new realm in Oracle Internet Directory before you can create a new Site.
To create a new Site:
Connect to the Application Server Control and go to the Content DB Home page.
In the Administration section, click Sites.
On the Sites page, click Create.
In the Name field, provide a name for the new Site.
Oracle recommends that you use the name of the realm on which this Site will be based for the name of the Site. Because users for this Site will need to provide the realm name during authentication, having the Site name based on the realm name provides consistency.
The Site name is used as the top folder name for the new Site and will appear in all Site paths. Because of this, you cannot use the following characters in the Site name: backslash (\), slash (/), colon (:), asterisk (*), question mark (?), quotation mark ("), left angle bracket (<), right angle bracket (>), and vertical bar (|). Keep Site names short to avoid long path names, and avoid using spaces because these characters will be replaced by %20 in URLs, making the URL long and hard to read.
For Realm, select a realm on which you want to base the new Site.
Specify an Allocated Quota for the new Site, in megabytes (MB), gigabytes (GB), or terabytes (TB).
Specify whether you want the new Site to be enabled by default. Disabled Sites cannot accept new user sessions.
Click OK.
Return to the Content DB Home page and restart OC4J_Content. If you are using Oracle Records DB, you must also restart OC4J_RM. If you are running these processes on multiple middle tiers, you must restart these processes on all middle tiers.
If you need to change the default location of the Personal Libraries for new users of this Site, modify the Site after it has been created, and specify the required properties. See the following section for more information.
You can change settings for existing Sites, including changing the Site name, updating Site quota, and changing the location of Personal Libraries for new users.
To modify an existing Site:
Connect to the Application Server Control and go to the Content DB Home page.
In the Administration section, click Sites.
Click the name of the Site you want to modify.
If necessary, provide a new name for the Site. Since the Site name is used as the top folder name for the Site, any bookmarks to existing URLs will break. Also, in Oracle Drive, any paths designated for scheduled backups will need to be changed.
You cannot use the following characters in the Site name: backslash (\), slash (/), colon (:), asterisk (*), question mark (?), quotation mark ("), left angle bracket (<), right angle bracket (>), and vertical bar (|). Keep Site names short to avoid long path names, and avoid using spaces because these characters will be replaced by %20 in URLs, making the URL long and hard to read.
Specify the amount of quota you want to allocate in the Allocated Quota field, then specify whether you want to allocate the quota in Megabytes (MB), Gigabytes (GB), or Terabytes (TB) by selecting from the list. The quota you allocate must be larger than the quota that has already been used by the Site.
In the Personal Libraries section, you have the option of changing the location of the Personal Libraries for new users. Using this option requires custom Java code; contact your Oracle Support Services representative for more information. To change the location of the Personal Libraries for new users, provide the following two parameters:
Locator Class Name: Specify the name of the custom class you created for the new Personal Library location.
Root Path: Specify the new root path for the Personal Libraries.
Only the Personal Libraries for new users will use the new path. Personal Libraries for existing users will remain in the old location.
Click OK.
If all existing Site users with the Security Administrator role are deleted or deprovisioned, you can use the Application Server Control to grant the Security Administrator role to a Site user.
For more information about the Security Administrator role, see Oracle Content Database Application Administrator's Guide.
To grant the Security Administrator role to a Site user:
Connect to the Application Server Control and go to the Content DB Home page.
In the Administration section, click Sites.
Select the Site where you want to grant Security Administrator access.
Click Grant Security Role.
On the Grant Security Role page, enter the name of the user to whom you want to grant the Security Administrator role.
Click OK.
You can choose whether to enable or disable Sites. Disabled Sites cannot accept new user sessions.
To enable a Site:
Connect to the Application Server Control and go to the Content DB Home page.
In the Administration section, click Sites.
Select the Site you want to enable and click Enable.
On the Warning page, click Yes.
To disable a Site:
Connect to the Application Server Control and go to the Content DB Home page.
In the Administration section, click Sites.
Select the Site you want to disable and click Disable.
On the Warning page, click Yes.
After you disable a Site, it will not accept any new sessions. To terminate existing sessions, return to the Content DB Home page and click Restart Domain.
Delete a Site only if you are sure that you will not need to access anything in the Site again. When a Site is deleted, all content and associated metadata is deleted. The Containers, Libraries, users, groups, roles, categories, and the Archive for the Site are also deleted. You cannot delete the default Site.
To delete a Site:
Connect to the Application Server Control and go to the Content DB Home page.
In the Administration section, click Sites.
If the Site you want to delete is enabled, select the Site and click Disable. Then, on the Warning page, click Yes. Enabled Sites cannot be deleted.
Select the Site and click Delete. Then, on the Warning page, click Yes. Everything associated with that Site, including content, metadata, users, and Libraries, is deleted, and the Site is removed from the Sites list.
You cannot delete a Site that contains records. See Oracle Records Database Administrator's Guide for information about managing records.
