Sanae BEKKAR – My Blog –

To run an administration application as a Java applet within a Java-enabled browser:
1. Open a browser window.
2. Log in to the Content Server instance as an administrator or subadministrator.
3. Choose Administration then choose Admin Applets.

The Repository Manager can be run as an applet or in standalone mode.
To run the Repository Manager as an applet:
1. Use the main menu to choose Administration, then Admin Applets.
2. Choose Repository Manager.
The Repository Manager applet opens.

To filter the Content list by revision:
1. On the Content tab of the Repository Manager application, select the Use Filter
check box, then click Define Filter.
2. On the Define Filter page, select the check boxes for the filter criteria to use and
add values for the fields.
3. Click OK.
To filter revisions by Release Date:
1. On the Content tab of the Repository Manager application, select Release Date
Since.
2. Select a predefined date range.
3. Click OK.
To change the columns displayed on the Content tab:
1. On the Content tab of the Repository Manager application, click Show Columns.
2. On the Show Columns page, select the columns to be displayed. Custom fields are
at the bottom of the list.
3. Click OK

To Change Default Sort Order :                                                                                                                          When the Repository Manager application is started, it runs a default query against
the database that returns all content released the previous day. By default, the query
sorts the results by the ContentID of the content items.

To change the order, disable the DoDocNameOrder configuration setting.                        When the value  is set to true (the default), content items are sorted by ContentID.                                                                                                                                                    When set to false, content items are not sorted. When the sort order is changed to optimize the query, enable the JDBC Query Trace to log trace information to the console log where database queries can be viewed.

To disable the DoDocNameOrder configuration setting:
1. In a text editor, open the IntradocDir/config/config.cfg file.
2. Add the following configuration setting:  DoDocNameOrder=false
3. Save and close the config.cfg file.                                                                                                         4. Restart Content Server.

To enable Query Tracing:
1. Use the main menu to choose Administration then System Audit Information.
2. On the System Audit Information page, scroll to the bottom of the Edit Active
Console Output Tracing section.
3. From the Action Sections list, select systemdatabase.
The systemdatabase is added to the list of active sections.
4. Click Update.
5. Restart Content Server.

Adding a New Content Item
To add a new content item using the Repository Manager:                                                                1. Start the Repository Manager in standalone mode.
2. Click the Content tab.
3. Click Add New.
4. On the Add New Content Item page, enter the required and optional information
for the content item.
5. Click OK.
The specified file is checked in as a new content item.

Managing Content Metadata
To view the metadata for a revision using the Repository Manager:
1. Use the main menu to choose Administration then Admin Applets.
2. Choose Repository Manager then the Content tab.
3. Highlight the revision for metadata review.
4. Choose Functions then Info or right-click and click Info.                                                             5. On the Approve Revision page, click OK to close the page.
To update the metadata for a revision using the Repository Manager:
1. Use the main menu and choose Administration then Admin Applets.
2. Choose Repository Manager then the Content tab.
3. Select the revision to update.
4. Choose Functions, Update, or right-click and select Update.
5. On the Update Content Info page, enter new metadata as necessary.
6. Click OK.
The metadata is updated without checking in a new revision.

Managing Expired Content
To review expired content from Repository Manager:
1. Use the main menu to choose Administration then Admin Applets.
2. Choose Repository Manager then the Content tab.
3. From the Content tab, select Define Filter.
4. On the Define Subscription Filter page, select Enable Revision Status, and select
Expired.
A list of expired content is displayed.
To automate email notification for the author and administrator when the content
expires:
1. Edit IntradocDir/config/config.cfg in a text editor and enter the following:
EnableExpirationNotifier=1
2. Adjust optional configuration entries. For more information about these and other
configuration variables, see Configuration Reference for Oracle WebCenter Content:
■ NotificationQuery: Defines the criteria for the automatic query that searches
for expired content.
■ NotifyExtras: Defines the users who receive a list of expired content.
■ NotificationIntervalInDays: Defines how often a notification query is run.
■ NotifyTime: Defines the time of day the query is run.
■ NotificationMaximum: Defines the maximum number of content items to be
returned by the query.

By default, an email message is sent to the administrator at midnight, seven days
before a piece of content is set to expire. Additionally, an Expired Content link is
added for the author and system administrator on their respective Content
Management menus.

3. Restart Content Server.

Managing Workflow Revisions
A workflow specifies how content is routed for review and approval before it is
released to the system. Users are notified by email when they have a file to review.
From a workflow participant’s point of view, there are two types of workflows:
■ A basic workflow defines the review process for specific content items, and must
be initiated manually.
■ In a criteria workflow, a file enters the workflow automatically upon check in
when its metadata matches predefined criteria.
When a workflow revision is approved using the Repository Manager, any approval
steps in the workflow are bypassed.                                                                                                                     The workflow may complete normally, but bypassing approval steps can have unanticipated consequences. For example, if a workflow step requires an electronic signature and the associated revision is approved through the Repository Manager, there will be no record of an electronic signature, even though the workflow completes and the revision is approved.

To approve or reject a revision in a workflow using the Repository Manager:
1. From the main menu, choose Administration then Admin Applets.
2. Choose Repository Manager then the Content tab.
3. Select one or more revisions to approve.
4. Choose Functions then Approve or Reject. You can also right-click and choose
Approve or Reject.
5. To exclude a revision from the list, clear the check box next to the revision.
6. Click OK.