| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration 10g Release 3 (10.3.0.1) Part Number E12891-02 |
|
|
View PDF |
| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration 10g Release 3 (10.3.0.1) Part Number E12891-02 |
|
|
View PDF |
This chapter provides information on the tasks required to administer and maintain Oracle WebCenter Collaboration. It includes the following sections:
Configuring Oracle WebCenter Collaboration for Importing Files into the Knowledge Directory
Configuring the Notification Service for Working with Experience Definitions
For details on assigning moderators to folders and discussions, see Assigning Moderators to Folders.
For details on clustering Oracle WebCenter Collaboration, see information about load balancing activity services in the Oracle Fusion Middleware Networking and Authentication Guide for Oracle WebCenter Interaction.
When Oracle WebCenter Collaboration is installed, two default Oracle WebCenter Collaboration administrator groups are created in the portal as follows:
Collaboration Project Administrators: By default, this group contains the portal Administrators group and has the following activity right:
Manage Collaboration Projects
Collaboration Administrators: Initially, this group does not have any members. An authorized portal administrator must add the first user and/or group to this new group. By default, this group is installed with the following activity rights:
Access Administration
Access Utilities
Manage Collaboration
Manage Collaboration Projects
Collaboration Project Administrators can create and manage projects and project templates.
Collaboration Administrators can configure global settings that apply to all Oracle WebCenter Collaboration projects by using the Collaboration Administration Utility. They can also manage the Oracle WebCenter Collaboration project folder hierarchy.
For more information on the activity rights granted to the default administrator groups, see Activity Rights.
The Collaboration Administration Utility controls global settings that affect the functionality of Oracle WebCenter Collaboration across all Oracle WebCenter Collaboration projects.
This section outlines the tasks that can be performed using the Collaboration Administration Utility. It includes the following topics:
Collaboration Administrators can access the Collaboration Administration Utility through the portal from the Select Utility drop-down list.
To access the Collaboration Administration utility:
Log in to the portal.
Click the Administration tab.
In the Select Utility drop-down list, click Collaboration Administration Utility.
The Diagnostics page provides diagnostic and configuration information about the various components of Oracle WebCenter Collaboration. If there is a failure with a component, the Diagnostics page displays the failure, related settings, and a possible resolution. We recommend that you check diagnostics:
After you have installed Oracle WebCenter Collaboration.
After the system has failed. For example, you can check the Diagnostics page to confirm that the Notification Service is down if users have stopped receiving notification messages for subscriptions.
Each test returns one of these messages to the Status column:
OK: The installation or startup was successful, or the component is functioning correctly.
FAIL: The installation or startup was not successful, or the component is not functioning correctly.
The message provides a reason for failure and might provide troubleshooting recommendations.
NOT ENABLED: The component is not enabled. This is not necessarily an error if the component is not being used.
This table describes the diagnostics that are provided for Oracle WebCenter Collaboration's components:
Table 2-1 Oracle WebCenter Collaboration Diagnostics
If the portal is down, you can access the Diagnostics page by typing the following URL in a browser's address bar: http://server_name:port_number/collab/admin/diagnostic/index.jsp. For example: http://brettg-gx:8080/collab/admin/diagnostic/index.jsp.
Note:
When you access the Diagnostics page by typing the URL, the JS Controls and Portal Connection tests are not visible.You can also perform diagnostic tests on the groupware servers that are integrated with Oracle WebCenter Collaboration. For information on testing groupware servers, see Testing Groupware Servers.
The following sections describe configuration options on the Miscellaneous Settings page.
To limit the size of projects, select Enforce a Maximum Project Size, then type the size limit in megabytes. Set the storage space according to the anticipated number and size of documents or files and their revisions.
By default, Oracle WebCenter Collaboration does not limit the size of projects. If a project size limit was previously set and you want to go back to the original setting of unlimited project sizes, clear the check box.
The size limit is for individual projects, not the entire collection of projects in Oracle WebCenter Collaboration. This setting affects every project in Oracle WebCenter Collaboration. A Project Leader can define the maximum size for a specific project in that project's General Settings page. Project Leaders with the Manage Collaboration Projects activity right can set a project size that exceeds the maximum set here.
Note:
Oracle WebCenter Collaboration includes objects in the Project Recycle Bin in its calculation of a project's memory usage.The personal projects feature lets users create and maintain their own personal project. A personal project contains documents, task lists, notes, and calendar features. To enable this feature, select Enable Personal Projects. To restrict the size of each personal project, type the size in megabytes.
By default, Oracle WebCenter Collaboration does not limit the size of personal projects. If a project size limit was previously set and you want to go back to the original setting of unlimited project sizes, clear the check box.
If you want your users to be able to add projects to their My Page, select the Enable Add To My Page check box. By default, this check box is selected.
If you want your users to be able to select individual users within portal groups or entire portal groups at once to receive notifications, select the Enable portal group notifications check box. By default, this check box is cleared.
To hide project folders that contain only projects that users cannot access, select Hide project folders that contain only projects a user cannot access. By default, this check box is cleared.
Enabling this option might cause the Project Explorer to perform more slowly due to the added security checks.
If you want your users to use Oracle WebCenter Collaboration's desktop integration features, select Enable WebDAV. To be able to select and clear this check box, you must set the <fullWebDAVAccessToThisServer> node in the config.xml file to yes. Config.xml also includes other nodes that you must set for WebDAV. Changes that you make to this option are never carried over to config.xml.
WebEdit simplifies the process of editing a document in Oracle WebCenter Collaboration. Using this feature a user can edit a Microsoft Office document “in-place,” without having to perform check-ins, check-outs, uploads, and downloads.
If you want your users to edit Microsoft Office documents on their desktop, select Enable WebEdit. To be able to select and clear this check box, you must set the <webEdit enabled> node in the config.xml file to yes. Config.xml also includes other nodes that you must set for WebEdit. Changes that you make to this option are never carried over to config.xml.
To use WebEdit, an end user's browser must not be configured to disable Microsoft ActiveX controls. Users can still employ the features of WebEdit without having the Collaboration Office Tools Add-In installed on their computers.
The Bulk Upload feature allows users to upload multiple documents or to copy a directory hierarchy from a local computer to Oracle WebCenter Collaboration. To enable this feature:
If you did not choose to enable the Bulk Upload feature during installation, you must edit config.xml and set the bulkUpload.enabled element to yes.
Alternatively, you may enable Bulk Upload by using the Collaboration Administration utility.
Click the Administration tab.
Select the Collaboration Administration utility.
Click Miscellaneous Settings.
Click Enable bulk upload.
Grant the corresponding activity rights by performing the following:
Click the Administration tab.
Select the Activity Manager utility.
Click Enable bulk upload.
Click Add Group.
Select the groups you want to add.
Click OK.
Click Finish.
This section describes the client settings required to use the Bulk Upload feature. After Bulk Upload has been enabled, the following software must be installed on the client computer:
Java Runtime Environment (JRE), version 1.4.2 or higher, JRE 1.5 or higher, and JRE 1.6 or higher
Java Plug-in, version 1.4 or higher
The Bulk Upload Applet
When a user attempts to use the Bulk Upload feature, the browser verifies if the Java Runtime Environment and the Java Plug-in are installed. If they are not, the user is prompted to download and install them.
If they are installed, the Java Plug-in attempts to load the Bulk Upload applet. If the applet is not found, it is downloaded from the Image Service. The user is then prompted to trust the applet. Users should answer “Always” when prompted to trust the applet.
If you want your users to be able to download folders and multiple documents as .zip files, select Enable zip download. Type the size limit for the .zip file in the box. The download aborts if the .zip file exceeds the size limit.
To limit the number of document versions that Oracle WebCenter Collaboration manages, select the Enable system-wide control of document versions check box and type a number from 3 to 999 into the Maximum number of versions allowed box. Oracle WebCenter Collaboration keeps the most recent specified number of versions and permanently removes the extra versions.
For example: Oracle WebCenter Collaboration has 25 versions of a document. You specify 10 as the maximum number of versions allowed. Oracle WebCenter Collaboration removes versions 1-15 of the document, keeping versions 16-25 (which are the 10 most recent versions). A user creates version 26 of the document. As a result, Oracle WebCenter Collaboration removes version 16, keeping versions 17-26 (again, Oracle WebCenter Collaboration keeps the 10 most recent versions). This process continues for as long as users create new versions of the document.
Note:
Oracle WebCenter Collaboration removes versions on a nightly basis. For this reason, users can access all versions before Oracle WebCenter Collaboration removes them. You cannot recover document versions after Oracle WebCenter Collaboration has removed them.In addition, Oracle WebCenter Collaboration always keeps:
The working version of the document. If the working version is older than the first version that you allow, Oracle WebCenter Collaboration keeps the number of versions that you specify, plus the working version.
The version of the document that has been published to the Knowledge Directory. If it is older than the first version that you allow, Oracle WebCenter Collaboration keeps the number of versions that you specify, plus the published version.
Note:
This setting does not affect document versions that are in the Project Recycle Bin.If you want the maximum size of an uploaded file to be anything other than the default, type a number from 1 to 999 into the Maximum single file upload in MB box. This setting applies to all individual files that are uploaded, whether using the Upload, Single File or Upload, Multiple Files options. The default is 10 MB. Oracle WebCenter Collaboration always uses the setting that you configure here except during upgrade, when it uses the <maxUploadMegabytes> node in config.xml. Changes that you make to this option are never carried over to config.xml.
If you want the maximum number of characters in a message to be anything other than the default, type a number from 1000 to 99999 into the Maximum number of characters in a discussion message box. The default is 16000. Oracle WebCenter Collaboration always uses the setting that you configure here except during upgrade, when it uses the <maxMessageChars> node in config.xml. Changes that you make to this option are never carried over to config.xml.
To allow users to add custom properties to Oracle WebCenter Collaboration documents, select Enable Custom Properties. When an Oracle WebCenter Collaboration document is crawled or published to the Knowledge Directory, custom properties are attached to the corresponding document in the Knowledge Directory. Project leaders can define project-wide properties that exist for all documents in a project. Additionally, a project-wide property can be designated as required for publishing to the Knowledge Directory.
To allow users to view RSS feeds for objects in Oracle WebCenter Collaboration, select Enable RSS. Users can view RSS feeds for all objects that they have permission to access. Users also have a personal RSS feed which lets them view the contents of all RSS feeds to which they have subscribed.
The Holidays page lets you create, change the properties of and delete holidays from Oracle WebCenter Collaboration's calendar. You can create a maximum of one holiday per day. Holidays appear on and affect every project calendar in Oracle WebCenter Collaboration. You cannot create, edit or delete holidays from the Calendar portlets or projects.
You can set up Oracle WebCenter Collaboration so that users can manually publish files into the Knowledge Directory by configuring the Collaboration Publishing Content Source. The Collaboration Publishing content source must be configured before any publishing activity can take place. This section discusses how to configure the Collaboration Publishing content source. For more information on setting up crawlers for automatic importing of files into the Knowledge Directory, see Configuring Oracle WebCenter Collaboration for Importing Files into the Knowledge Directory.
To configure a content source for publishing to the Knowledge Directory:
Go to the Collaboration Administration utility.
Click Publish to Directory.
Click Configure a Content Source.
In the Content Source dialog box, select Collaboration Publishing.
This data source is preconfigured when the Collaboration6.pte file is loaded into the portal.
Click OK.
Click Finish.
Note:
After a document is published to the Knowledge Directory, access to the published version from the Knowledge Directory inherits the access settings of the parent Knowledge Directory folder. For example, if the Everyone group has Read access to the Knowledge Directory folder, the version of the Oracle WebCenter Collaboration document published is accessible from the Knowledge Directory by all users, including Guest Users.To configure a new groupware server:
Go to the Collaboration Administration utility.
Click Groupware Servers.
Click Add Server.
Enter the configuration information:
If you are configuring a Microsoft Exchange back-end server, enter the following configuration information:
Table 2-2 Microsoft Exchange Configuration Parameters
| Parameter | Description |
|---|---|
|
Server Name/IP/URL |
The server name, IP address, or URL of the groupware server. Note: If you are upgrading Oracle WebCenter Collaboration from 3.x, you should use the value of the serverURL element in the 3.x version of the configuration file and add the http:// protocol prefix. Example: http://mail.company.com/exchange |
|
Alias |
An optional descriptive name for this groupware server. |
If you are using a Lotus Domino back-end server, enter the following configuration information:
Table 2-3 Lotus Domino Configuration Parameters
| Parameter | Description |
|---|---|
|
Server Name/IP/URL |
The server name, IP address, or URL of the groupware server. Note: If you are upgrading Oracle WebCenter Collaboration from 3.x, you should use the value of the serverURL element in the 3.x version of the configuration file and add the http:// protocol prefix. Example: http://mail.company.com/exchange |
|
Alias |
An optional descriptive name for this groupware server, which is available to end users. Example: MyCompany Exchange Server |
|
Server Port |
If your server port number is other than 80, type a port number; otherwise leave this blank. |
|
Proxy Host/Firewall Port |
If you are using a proxy server or a firewall, type the host name; otherwise leave this blank. |
|
Use SSL |
If you are using https, select the check box. |
|
HTTPS Port |
If you are using an https port number other than 443, type the port number; otherwise leave this blank. |
|
Session Based Authentication |
If you are using form-based authentication (cookies), select this; if you are using basic authentication, clear the check box. |
|
Notes Server Temp Dir |
Type the local directory of the Lotus Domino server that stores the attachments. |
|
Notes Server Temp UNC |
Type the UNC path of the directory of the Lotus Domino server that stores the attachments. This should be the same directory that you typed in the Notes Server Temp Dir box. For example: \\Lotus_Domino_server_name\directory_name. |
Note:
Other tasks are required for groupware integration besides configuring this page. For complete information, see Integrating Oracle WebCenter Collaboration and Groupware.You can perform a diagnostic test on all of the groupware servers that are integrated with Oracle WebCenter Collaboration.
To test groupware servers:
Go to the Collaboration Administration utility.
Click Groupware Servers.
Click Test Servers.
Test results appear in the Status column for each groupware server. Each test returns one of these messages:
OK: The groupware server is functioning correctly.
FAIL: You incorrectly added the groupware server, or the groupware server is not functioning correctly.
The message provides a reason for failure and might provide troubleshooting recommendations. The detailed error information can be found in the Oracle WebCenter Collaboration log. You can find the log at:
By default, install_dir is C:\bea\alui. However, if you upgraded to Oracle WebCenter Collaboration 10.3, install_dir is the same as in the previously installed version of Oracle WebCenter Collaboration.
The Notification Health Monitor sends a notification e-mail to an administrator when there is a problem contacting or using the Notification Service. The administrator at the specified e-mail address is alerted when the Notification Service experiences an error, requires a restart, or can be contacted after a failure.
To configure notification health monitoring:
Go to the Collaboration Administration utility.
Click Collaboration Notification.
Specify the e-mail host used by the Notification Service, the e-mail address of the administrator to be contacted, and the frequency at which the notification health check is performed.
Click Finish.
The Collaboration Administration utility lets you monitor the status of the Search Server and rebuild its data.
Oracle WebCenter Collaboration provides the following information about the Search Server:
Table 2-4 Descriptions of Search Server Statuses
| Status | Description |
|---|---|
|
The length of time the Search Server has been running. |
|
|
The location where the Search Server is installed. |
|
|
The number of Oracle WebCenter Collaboration items in the Search Server index. |
|
|
The number of requests outstanding for indexing Oracle WebCenter Collaboration objects. |
Rebuilding reconciles data between the Oracle WebCenter Collaboration database and Search Server index. Since this is a lengthy and computationally expensive process, use the rebuild operation only when absolutely necessary.
To rebuild the Search Server database:
Go to the Collaboration Administration utility.
Click Search Server.
Click Rebuild Search Collection.
Click OK.
When Oracle WebCenter Collaboration is configured, it is associated with a primary portal, known as the owning portal. Oracle WebCenter Collaboration has a direct relationship with its owning portal, including access to the owning portal's database.
Every portal accessing Oracle WebCenter Collaboration sends an authentication name and password. Oracle WebCenter Collaboration uses this authentication information to ensure that the attempted access is coming from the owning portal. The owning portal is assigned a unique authentication identifier so that Oracle WebCenter Collaboration can identify each portal.
Oracle WebCenter Collaboration determines its owning portal based on the values specified in config.xml. However, you can also change the owning portal using the Collaboration Administration utility by performing the following:
Access the Collaboration Administration utility.
Click Portal Access.
Manually enter the values for the following fields:
Web Service ID
Gateway Page URL
Collaboration Service URL
Click Finish.
You can configure content crawlers to automatically import files from Oracle WebCenter Collaboration into the Knowledge Directory. You must have the proper activity rights in the portal to be able to create and configure content crawlers. For information on the necessary activity rights, see the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.
This section discusses:
For more information on setting up Oracle WebCenter Collaboration so that users can manually publish files into the Knowledge Directory, see Setting Up Oracle WebCenter Collaboration for Publishing.
You create content crawlers from the Collaboration Crawler Content Source to import files from Oracle WebCenter Collaboration into the Knowledge Directory. You must use the Collaboration Crawler Content Source with Oracle WebCenter Collaboration content crawlers. The authentication settings for the Collaboration Crawler Content Source must match the authentication settings in the Collaboration Remote Server object.
The API Service and the Automation Service must be installed for Oracle WebCenter Collaboration files to be imported into the Knowledge Directory. For more information about installing them, see the Installation Guide for Oracle WebCenter Interaction.
To configure a content crawler for importing files from Oracle WebCenter Collaboration into the Knowledge Directory, perform the following on the content crawler's Main Settings page:
Click Browse next to the Project icon to choose the project that contains the folder that you want the content crawler to access. You can only select projects for which you are a Project Leader.
Click Browse next to the Folder icon to choose a folder. You must have Admin access to the folder. Additionally, you must make this folder content crawler-accessible by selecting Accessible to Content Crawlers in the folder's properties. Content crawler accessibility settings are passed down to child folders.
By default, the maximum number of levels within the folder that the content crawler can access is unlimited. You can change this number using the Maximum number of levels to crawl drop-down list.
We recommend the following settings for content crawlers that import files into the Knowledge Directory:
On the content crawler's Main Settings page, select the Mirror the source folder structure option
On the content crawler's Advanced Settings page:
Select the from this Content Source option.
Select the refresh them option.
Select the regenerate deleted links option.
Error information about content crawler jobs can be found in:
The job history for each content crawler job.
The Collaboration log, which can be found at:
For more information about creating content crawlers, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.
Documents that are published and crawled into the Knowledge Directory contain the Checked In By property, which is an Oracle WebCenter Collaboration property that contains the name of the user who checked in the version of the document that is accessible in the Knowledge Directory. In order for the Checked In By property to be displayed, you must add it to the Global Document Property Map by performing the following:
Log in to the portal.
Click the Administration tab.
From the Utilities drop-down list, select Global Document Property Map.
The Global Document Property Map appears.
Click Add Property.
In the Add Property window, select Checked In By.
Click OK.
The Checked In By property is added to the Global Document Property Map page.
Click the Checked In By link.
In the Document Attributes column of the Checked In By Row, type: CheckedInBy.
Click Finish.
Oracle WebCenter Collaboration writes log messages to:
Collaboration.log, which is the local Oracle WebCenter Collaboration log file. This log file exists at install_dir\ptcollab\version_number\settings\logs\collaboration.log. No setup is required to enable logging to the Collaboration log file and view the log.
Logging Spy, which is the primary log message receiver in the Logging Utilities. Logging Spy provides a graphical user interface for displaying log messages as they stream in from Oracle WebCenter Collaboration and other log message senders (such as the portal or Publisher).
This section discusses:
Setting Up Logging Utilities for Oracle WebCenter Collaboration Logging
Configuring Logging Spy to Display Oracle WebCenter Collaboration Messages
Note:
You must set up logging utilities for Oracle WebCenter Collaboration logging before you configure Logging Spy to display Oracle WebCenter Collaboration messages.To set up Oracle WebCenter Collaboration logging, you use the OpenLog section of the audit.xml file. By default, the audit.xml file is installed in install_dir\ptcollab\10.3.0\settings\config, where install_dir is, by default, C:\bea\alui. The following is an example of this section and a description of each of the nodes in the section:
<openlog enabled="yes">
<serverName value=""/>
<restrictToLocalMachine value="no"/>
</openlog>
This node enables or disables OpenLog. By default, <openlog enabled> is set to yes.
This node:
Defines the Oracle WebCenter Collaboration logging name, which distinguishes it from all other Oracle WebCenter Interaction applications that use the logging framework.
Facilitates the viewing of Oracle WebCenter Collaboration log messages.
During installation, the Oracle WebCenter Collaboration installer sets the Oracle WebCenter Collaboration logging name to:
collab.computer-name.user-name
In this default, computer-name is the name of the computer on which Oracle WebCenter Collaboration is installed. user-name is the name of the user who runs the installer.
You can override the default Oracle WebCenter Collaboration logging name by typing your own string into the <serverName value> node. The string that you enter must meet these criteria:
The logging name can contain only visible ASCII characters and the space character.
It cannot contain invisible ASCII characters such as tabs, carriage returns, and so on. It also cannot contain the slash character (/).
The logging name cannot exceed 128 characters in length.
The <restrictToLocalMachine> XML node enables or disables remote spying of Oracle WebCenter Collaboration log messages. When the value is no, instances of Logging Spy that run on other computers on the network can receive log messages from Oracle WebCenter Collaboration. When the value is yes, only instances of Logging Spy that run on the computer on which Oracle WebCenter Collaboration is installed can receive log messages from Oracle WebCenter Collaboration. The default value is no.
For successful remote spying of Oracle WebCenter Collaboration log messages, you must configure the network to allow UDP multicast messages between the computer on which Oracle WebCenter Collaboration is installed and the computer on which Logging Spy is installed. For help with configuration, see your network administrator.
This section discusses how to configure Logging Spy to display Oracle WebCenter Collaboration messages.
Note:
You must set up logging utilities for Oracle WebCenter Collaboration logging before you configure Logging Spy to display Oracle WebCenter Collaboration messages. For more information, see Setting Up Logging Utilities for Oracle WebCenter Collaboration Logging.To configure Logging Spy to display Oracle WebCenter Collaboration messages:
Launch Logging Spy by navigating to Start |All Programs | BEA | ALI Logging Utilities | Logging Spy. For more information on using Logging Spy, see the online help provided with Logging Spy.
Note:
If you upgraded to Oracle WebCenter Collaboration 10.3, the path to Logging Spy is the same as in the previously-installed version of Oracle WebCenter Collaboration.Open the Filter Settings dialog box by selecting View | Set Filters.
To add a logging server, right-click anywhere in the Filter Settings window.
The context menu appears.
Select Add Message Sender.
The Add Message Sender dialog box appears.
Type a server name or select it from the list of names and click OK.
Server names exists in the <serverName> nodes of the openLog section in the audit.xml file.
When you add a server as a message sender, it appears as a tree structure in the Filter Settings window. Click the plus sign to expand the server and see a list of its message-sending components.
In the Filters Settings window, expand each component under a server to see the selected logging levels for that component.
The check box next to each component has three states:
Gray with a check mark: the initial four logging levels (listed above) are selected.
Clear with a check mark: all of the logging levels are selected.
Clear: none of the logging levels are selected.
You can toggle through these states by clicking the check box next to the component.
You can perform the following additional actions in the Filter Settings window:
To remove a message-sending server and its components, right-click the server name, and select Remove Message Sender.
To enable a selected logging level for all components of a server, right-click the server name, and select Enable LoggingLevel, for example, Enable Performance.
To enable or disable logging levels for a single component, expand the component, and select or clear the check box next to the logging level.
To clear all logging levels for all components of a server, right-click the server name, and select Clear All Filters. Then click OK when asked to confirm. This prevents those components from sending logging messages to this instance of Logging Spy.
To reset logging levels for all components of a server to the original four levels, right-click the server name, and select Reset Filters. Then click OK when asked to confirm.
Click OK when finished.
The filter settings in Logging Spy are independent of the logging levels specified in Oracle WebCenter Collaboration's audit.xml file. The settings in audit.xml affect only the messages written to the collaboration.log file and do not affect the messages that appear in Logging Spy. Conversely, the settings in Logging Spy have no effect on the messages written to the collaboration.log file.
Because the filter settings in Logging Spy are independent of the settings in audit.xml, you can use Logging Spy to debug problems with Oracle WebCenter Collaboration without changing the logging level in audit.xml and restarting Oracle WebCenter Collaboration. To debug problems, launch Logging Spy and enable the Debug logging level on all relevant components to view debug messages from Oracle WebCenter Collaboration.
Note:
When you enable the Debug logging level in Logging Spy, you affect Oracle WebCenter Collaboration performance. Do not leave debug logging enabled in Logging Spy for long periods of time when it is used with an installation of Oracle WebCenter Collaboration that is used in a production context.This section discusses how to back up and restore Oracle WebCenter Collaboration.
To back up Oracle WebCenter Collaboration:
Ensure that the Oracle WebCenter Collaboration database, portal database, and Document Repository are synchronized by performing the following at the same time:
Back up the Oracle WebCenter Collaboration database that you created when you installed Oracle WebCenter Collaboration. For details, refer to the instructions for your database type.
Back up the portal database.
Back up all of the Document Repository files. By default, they are located in install_dir\ptdr\documents\PTCollab.
Back up Oracle WebCenter Collaboration's configuration files.
(Optional) Back up the Search index, which you can rebuild when you restore Oracle WebCenter Collaboration.
(Optional) Back up any customizations that exist in your deployment.
To restore Oracle WebCenter Collaboration:
Shut down the portal and Oracle WebCenter Collaboration.
Restore the Oracle WebCenter Collaboration and portal databases.
Restore the Document Repository files.
Restore Oracle WebCenter Collaboration's configuration files.
(Optional) If you backed up the Search index, restore the Search index.
(Optional) If you backed up any customizations that exist in your deployment, restore them.
Restart the portal and Oracle WebCenter Collaboration.
Notification Service-generated e-mails can include user-specific URLs that point to Experience Definitions. To enable the Notification Service to include links to Experience Definitions, edit the Notification Service's config.xml and set the <experience-definitions enabled> node to yes.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|