This chapter discusses the following topics:
The Repository Manager can be run as an applet or in standalone mode.
To run the Repository Manager as an applet:
To run Repository Manager in standalone mode, see the instructions in Administering Oracle WebCenter Content.
Use the Functions menu of the Repository Manager to perform a variety of administrative functions on specific revisions. Right-click a revision when displaying the revisions with the filter to open a shortcut menu, which includes all of the options on the Functions menu.
Administrators and subadministrators with RepMan rights can display a list of content item revisions in the Repository Manager. Administrators can display all content items; subadministrators with RepMan rights can display only content items for which they have Admin permission to the security group and account (if applicable). Search the revision list by specifying metadata fields and revision status as filter criteria.
This section discusses the following topics:
To filter the Content list by revision:
On the Content tab of the Repository Manager application, select the Use Filter check box, then click Define Filter.
On the Define Filter page, select the check boxes for the filter criteria to use and add values for the fields.
Click OK.
To filter revisions by Release Date:
On the Content tab of the Repository Manager application, select Release Date Since.
Select a predefined date range.
Click OK.
To change the columns displayed on the Content tab:
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.
Ordering by ContentID is advantageous because the order is predictable when the Repository Manager has a long list of content items. But sorting by ContentID can be time-consuming. It may be preferable to have faster query results without the predictable order.
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.
DoDocNameOrder configuration setting:To disable the DoDocNameOrder configuration setting:
In a text editor, open the IntradocDir/config/config.cfg file.
Add the following configuration setting:
DoDocNameOrder=false
Save and close the config.cfg file.
Restart Content Server.
To enable Query Tracing:
Use the main menu to choose Administration then System Audit Information.
On the System Audit Information page, scroll to the bottom of the Edit Active Console Output Tracing section.
From the Action Sections list, select systemdatabase.
The systemdatabase is added to the list of active sections.
Click Update.
Restart Content Server.
For more information about tracing reports and restarting Content Server, see Administering Oracle WebCenter Content.
Several common tasks are done when managing content and revisions with Repository Manager, as discussed in the following sections:
To add a new content item using the Repository Manager:
Note:
New content items cannot be added using the Repository Manager launched as a Java applet from a browser. Use the standalone application. For details on using standalone applications, see Administering Oracle WebCenter Content.
This section provides information on how to view or update the metadata fora revision using the Repository Manager.
To view the metadata for a revision using the Repository Manager:
Use the main menu to choose Administration then Admin Applets.
Choose Repository Manager then the Content tab.
Highlight the revision for metadata review.
Choose Functions then Info or right-click and click Info.
On the Approve Revision page, click OK to close the page.
To update the metadata for a revision using the Repository Manager:
Use the main menu and choose Administration then Admin Applets.
Choose Repository Manager then the Content tab.
Select the revision to update.
Choose Functions, Update, or right-click and select Update.
On the Update Content Info page, enter new metadata as necessary.
Click OK.
The metadata is updated without checking in a new revision.
This section describes how to manage expired content.
To review expired content from Repository Manager:
Use the main menu to choose Administration then Admin Applets.
Choose Repository Manager then the Content tab.
From the Content tab, select Define Filter.
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:
Edit IntradocDir/config/config.cfg in a text editor and enter the following:
EnableExpirationNotifier=1
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.
Restart Content Server.
A revision is a new or revised version of a content item. By default, revisions are numbered sequentially starting with Revision 1, and every time the content item is checked out and checked in again, the revision number is incremented by one and Content Server creates a new revision of that file. The new revision has the same content ID as the previous revision, but the native file and the metadata can be the same or different. The system stores the previous versions of a file, which can be reviewed as necessary.
This section discusses the following topics:
To check in a new revision or check out a revision using the Repository Manager:
Note:
These tasks must be performed using the standalone application. For details on running standalone applications, see Administering Oracle WebCenter Content.
To undo a check-out or resubmit a revision using the Repository Manager:
To delete a particular revision using the Repository Manager:
To delete all revisions of a content item follow the same steps, choosing Delete All Revisions from the appropriate menus.
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.
Note:
Be sure you understand the consequences of approving a workflow revision using the Repository Manager before doing so.
To approve or reject a revision in a workflow using the Repository Manager:
From the main menu, choose Administration then Admin Applets.
Choose Repository Manager then the Content tab.
Select one or more revisions to approve.
Choose Functions then Approve or Reject. You can also right-click and choose Approve or Reject.
To exclude a revision from the list, clear the check box next to the revision.
Click OK.
A subscription is a function that notifies users by email when a particular content item has been revised.
An email message buffer is 20000 bytes. If a large number of subscription email notices are sent at one time (for example, 40 content items with 40 subscribers each), the buffer can be overloaded and the email messages are not sent. The limit to the total size of a subscription notification email sent is 1 GB. The total number of subscription notification emails that can be included in one email sent to n users is 1 GB divided by the size of the subscription notification email.
Tip:
To change the subscription notification message, use Component Architecture to customize the following:
subscription_mail_subject include (in std_page.htm file)
wwSubscriptionMailSubject string (in ww_strings.htm file)
subscription_mail.htm template
Create subscriptions in two ways:
Basic subscription: Users manually subscribe to individual content items. This type of subscription is predefined.
Criteria subscription: Users can subscribe to a group of content items based on metadata criteria. Administrators can set up a Criteria subscription in two ways: with users or with aliases. If a subscription is set up with users, users can unsubscribe if they want. If aliases are used, users cannot unsubscribe.
Subscribe to content items in two ways:
Open subscription: Users voluntarily subscribe to a content item through a Basic or Criteria subscription.
Managed subscription: An administrator assigns users and aliases to a particular subscription. If individual users are assigned, each user can unsubscribe if they want. If an alias is assigned, the users in that alias cannot unsubscribe.
These are common tasks in managing subscriptions, as discussed in the following sections:
This section describes how to add or unsubscribe users.
Tip:
If any of the users added to subscription do not have a correct email address, notification fails. The system quits after it encounters five errors in the work queue log and does not notify the rest of the subscribers.
To add users to a Criteria subscription:
From the main menu, choose Administration then Admin Applets.
Select Repository Manager then the Subscription tab. Select the subscription to use.
Click Subscribers.
On the Users Subscribed page, click Add.
On the Add Subscription page, select User or Alias then click Select.
On the Select User page or Select Alias page, choose the users or aliases to be subscribed.
Click OK.
Set the values for the criteria fields specified earlier.
Click OK.
To unsubscribe a user:
From the main menu, choose Administration then Admin Applets.
Select Repository Manager then the Subscription tab.
Select the subscription to use.
Select the revision to unsubscribe.
Click Function then Subscribers, or right-click and select Subscribers.
On the Subscribers page, select the user alias to unsubscribe.
Click Unsubscribe.
On the confirmation page, click OK.
To view subscription information for a revision using the Repository Manager:
From the main menu, choose Administration then Admin Applets.
Select Repository Manager then the Subscription tab.
Select the subscription to use.
Select the revision to view the subscription information for.
Select Functions, Subscribers, or right-click and select Subscribers.
To narrow the Subscriptions list, on the Subscribers page:
Select the Use Filter check box.
Click Define Filter.
On the Subscription Detail page, enter the filter criteria.
Click OK.
To view all subscription details for a particular user or alias, select the user or alias and click View Details.
The Subscription Detail page opens.
Electronic signatures are used and managed in several different contexts:
Workflow: Used to specify that a particular step requires an electronic signature for approval.
Because electronic signatures are stored separately from both the content item and from its metadata, multiple users can sign a particular content item revision. For more information about using electronic signatures in workflows, see Managing Workflows.
Content Item: Used to sign a content item electronically and compare a local file against a signed content item (or against all repository content) to see if the local file matches. For more information, see Using Oracle WebCenter Content.
PDF Watermark: Used to apply a watermark that uses electronic signature metadata.
This section discusses the following topics:
An electronic signature is a unique identifier computed from the binary content of a content item and associated with other metadata such as the name of the user who signs the content item. Unlike a digital signature, which uniquely identifies both the document and the signer and encrypts the information with the document, an electronic signature is not stored with the document.
When a content item is checked in, Content Server generates the identifier and stores it with the revision metadata for the content item. When a content item is signed, a copy of the identifier is stored with the electronic signature metadata. When a modified revision of the content item is checked in, a new identifier is calculated.
Content Server can compare the identifier stored with the content item to the identifier stored with the electronic signature to help determine if a signed content item has changed and if existing signatures for a content item are valid.
Note:
The identifier is computed from the content only, not the associated metadata. A change in the metadata for a content item does not invalidate the electronic signature for the content item.
Because electronic signatures are stored separately from both the content item and from its metadata, multiple users can sign a particular content item revision. For example, in a workflow approval process, multiple reviewers may sign a revision of a content item. For more information, see Managing Workflows.
Any user with access to the Document Information page for a content item can sign the content item. For more information about signing a content item, see Using Oracle WebCenter Content.
When using the Archiver with the Electronic Signatures component, use the table archive feature to move the ElectronicSignatures table. If archived content is restored without the associated signature metadata, errors can occur. For more information about archiving content, see Administering Oracle WebCenter Content.
When Electronic Signature is enabled along with PDF Watermark, the PDF Watermark capabilities are enhanced to provide the ability to apply a watermark of selected electronic signature data on a PDF rendition of a document. For more information, see Add or Edit an Electronic Signature Watermark.
When a content item is signed electronically, the signature includes standard metadata about the user, such as the user name and password, and metadata about the content item itself, such as the name (dDocName) and revision (dRevisionID). The Electronic Signature component also provides the xESigHasElectronicSignatures field which is automatically set to 1 (true) when a content item is signed.
Metadata fields that are stored as part of the metadata for the electronic signature can also be defined. Electronic signature information is stored and managed in a separate ElectronicSignatures table in the database.
When creating a custom metadata field, select a basic data type, and optionally specify a choice-list of comma-delimited values, and designate one or more fields as required fields. The defined fields are displayed when the user signs a content item and when the user displays detailed signature information about a content item. For more information about these pages, see Using Oracle WebCenter Content.
Consider metadata requirements carefully before creating custom metadata fields. After creating a field (click Save Changes), the field name, the data type, or the required status cannot be changed. The field must be deleted and a new field created in order to delete it. When a custom field is deleted, any stored data associated with that field is also deleted.
To create or edit a custom Electronic Signature field:
By default, the Electronic Signatures component requires that Secure Socket Layer (SSL) security be enabled when applying electronic signatures to prevent the possible interception of password information in otherwise unsecured network transmissions.
For some applications, such as workflow sign-off on a secure company intranet, the requirement adds additional overhead that may not be necessary.
To disable the SSL requirement for Electronic Signatures, set the DisableESigSSLCheck configuration variable in the config.cfg file to True:
DisableESigSSLCheck=true
For information about setting configuration variables, see Configuration Reference for Oracle WebCenter Content.
The electronic signature authentication process redirects users to the Oracle WebLogic Server login page before they can sign content items.
The Sign Content Item page has a time-limit cookie, default is 2 minutes, for reauthenticating users before signing content items. You can specify the timeout by setting the ESigCookieTimeOut property (with the value in seconds) in the electronicsignatures_environment.cfg file.
For example, to set the cookie timeout value to 30 seconds, specify the following:
ESigCookieTimeOut=30
Note:
Unless Content Server is configured to work with an Inbound Refinery instance, files are all passed through to the website in their native format.
When Content Server is configured as a provider for an Inbound Refinery instance, you must specify what file formats to pass to the refinery for conversion, based on the file extension. You can do this in the following ways:
You can use the File Format Wizard, accessed from the Refinery Administration folder in the Administration tray
You can use the File Formats option of the Configuration Manager applet to map file extensions (.doc, .txt, and so on) to file formats and then map the file formats to the conversion option on the refinery. This option provides more flexibility in mapping different file extensions to different conversion options
You can create a custom component to base the conversion on the value of specified metadata fields for the content item, including the file format or custom fields.
After the job passes from Content Server to Inbound Refinery, the refinery configuration determines how to convert and return the native file.
File formats are automatically configured during installation or can be added and changed as needed.
For more information about conversions, see Managing Content Conversion.
When you define new file formats, specify the MIME (Multipurpose Internet Mail Extensions) type corresponding to the file extension (for example, the format mapped to the doc file extension is application/msword).
When a content item is checked in to the repository, the content item's format is assigned according to the format mapped to the file extension of the native file. If the native file is not converted, Content Server includes this format when delivering the content item to clients. Using the MIME type for the format assists the client in determining what type of data the file is, the associated helper applications, and so on.
Check MIME types and the list of registered MIME types at http://www.iana.org/assignments/media-types/index.html.
Oracle WebCenter Content Inbound Refinery supports using Microsoft Office Suite 32-bit installations for the greatest compatibility. Using 64-bit installations of Microsoft Office Suite is not supported. Microsoft Office Suite 32-bit is the default installation and is recommended by Microsoft for compatibility with third-party extensions. For more information, visit http://office.microsoft.com and search for articles HA010369476, HA102840825, and ee681792.
The native applications used to convert content must meet the following requirements.
| Native Application | Requirements |
|---|---|
|
MS Word MS Project MS Excel MS PowerPoint MS Visio |
Verify that the native application is installed if needed by Inbound Refinery for the conversion. Associate the file type to a conversion process on the File Formats tab. For Word and PowerPoint applications, use the Native Options tab on the Local Inbound Refinery Configuration page to specify whether to process links. |
|
MS Publisher FrameMaker PhotoShop PageMaker InDesign |
Verify that the native application is installed. Associate the file type to a conversion process on the File Formats tab. |
|
Other |
Verify that the native application is installed (if required). Install the custom conversion program in Inbound Refinery. Associate the file type to a conversion process on the File Formats tab. |
Associating file types with conversions is a two-stage process.
To add the file format and associate the file extension with the format:
From the main menu, choose Administration then Admin Applets.
Click Configuration Manager.
On the Configuration Manager page, choose Options then File Formats from the Page menu.
On the File Formats page, click Add in the File Formats pane to add a file format.
On the Add/Edit File Format page, enter the necessary information:
Format: Usually the MIME type.
Conversion type: Associates the format name with a conversion.
Description: A brief description of the file format.
Click OK.
To enter the file extension to associate with the format:
Click Add in the File Extensions pane.
On the Add/Edit File Extension page, enter the necessary information:
Extension: The designation for the file format. A file with this format is converted using the conversion specified by the Map to Format field.
Map To Format: A list of the available formats with specified conversions (defined in the File Formats pane). Select a format to directly relate all files with that extension to a specific conversion program.
Click OK.
Thumbnails are small preview images of content. They are used on search results pages and typically link to the web-viewable file they represent. This means that users do not need to rely solely on text information such as the title to tell if a file is the one for which they are looking. A thumbnail provides consumers with a visual sample of a file without actually opening the file itself. This enables them to check a file before committing to downloading the larger, original file.
You can automatically generate thumbnails for supported file types with options provided by Content Server.
Content Server provides a basic set of thumbnail creation options. Oracle WebCenter Content: Inbound Refinery provides a more extensive set of options for file conversion and thumbnail generation.
Files are grouped in directories designated by content types.
Content types become the names of the subdirectories in which documents are stored in the weblayout and vault directories.
Content types can correspond to departments (such as ENG, MKTG, and HR), document types (such as MEMO, FORM, and SPREADSHEET), or any other model needed.
Several content types are defined by default (Document, Binary, Digital Media, and so on), but you can modify or delete these.
Each content type is assigned an image, which helps users identify the content type on search result pages. Several images are provided or you can create and assign your own images.
Create a manageable number of content types, typically no more than 50. Too many content types increases the amount of effort required to maintain the system, and makes it difficult for contributors to assign the correct content types to their files.
When configuring content types, consider using the same prefix in a content type when grouping similar information. For example, the prefix MEMO is used in the following content types: MEMO_INT, MEMO_EXT, MEMO_EXEC.
Use this procedure to:
Create a new content type
Edit an existing type
Delete a content type
From the main menu, choose Administration then Admin Applets.
Click Configuration Manager.
On the Configuration Manager page, choose Options then Content Types from the Page menu.
To add a new type, on the Content Types page click Add.
To edit a type, highlight the type name and click Edit.
To delete a type, highlight the type name and click Delete.
Note:
You cannot delete a content type if content still exists with that type. Make sure no content is using the type before attempting to delete it.
On the confirmation page, click OK.
On the Add/Edit Content Type page, enter or edit the name and description of the type.
Select an image from GIF list to associate with the content type.
Click OK.