Select Repository Manager then the Subscription tab.Р”В¬lick Function then Subscribers, or right-click and select Subscribers. Set the values for the criteria fields specified earlier. On the Select User page or Select Alias page, choose the users or aliases to be subscribed. On the Add Subscription page, select User or Alias then click Select. Select Repository Manager then the Subscription tab. The system quits after it encounters five errors in the work queue log and does not notify the rest of the subscribers.Р”Р‡rom the main menu, choose Administration then Admin Applets. If any of the users added to subscription do not have a correct email address, notification fails. Section 4.5.4, 'Deleting a Criteria Subscription' Section 4.5.3, 'Viewing Subscription Information' Section 4.5.2, 'Adding or Unsubscribing Users' Section 4.5.1, 'Adding or Editing a Criteria Subscription' These are common tasks in managing subscriptions, as discussed in the following sections: If an alias is assigned, the users in that alias cannot unsubscribe. If individual users are assigned, each user can unsubscribe if they want. Managed subscription: An administrator assigns users and aliases to a particular subscription. Open subscription: Users voluntarily subscribe to a content item through a Basic or Criteria subscription. If aliases are used, users cannot unsubscribe. If a subscription is set up with users, users can unsubscribe if they want. Administrators can set up a Criteria subscription in two ways: with users or with aliases. This type of subscription is predefined.Р”В¬riteria subscription: Users can subscribe to a group of content items based on metadata criteria. WwSubscriptionMailSubject string (in ww_strings.htm file)Р”В«asic subscription: Users manually subscribe to individual content items. Subscription_mail_subject include (in std_page.htm file) To change the subscription notification message, use Component Architecture to customize the following:

Additionally, an Expired Content link is added for the author and system administrator on their respective Content Management menus. NotificationMaximum: Defines the maximum number of content items to be returned by the query.Р”В«y default, an email message is sent to the administrator at midnight, seven days before a piece of content is set to expire. NotifyTime: Defines the time of day the query is run.

NotificationIntervalInDays: Defines how often a notification query is run. NotifyExtras: Defines the users who receive a list of expired content. NotificationQuery: Defines the criteria for the automatic query that searches for expired content. For more information about these and other configuration variables, see Configuration Reference for Oracle WebCenter Content: To automate email notification for the author and administrator when the content expires:Р”В®dit IntradocDir /config/config.cfg in a text editor and enter the following:Р”Р„djust optional configuration entries. On the Define Subscription Filter page, select Enable Revision Status, and select Expired. Use the main menu to choose Administration then Admin Applets.Р”В¬hoose Repository Manager then the Content tab.Р”Р‡rom the Content tab, select Define Filter. To review expired content from Repository Manager: The systemdatabase is added to the list of active sections.Р”Р‡or more information about tracing reports and restarting Content Server, see Administering Oracle WebCenter Content. On the System Audit Information page, scroll to the bottom of the Edit Active Console Output Tracing section.Р”Р‡rom the Action Sections list, select systemdatabase. Use the main menu to choose Administration then System Audit Information. In a text editor, open the IntradocDir /config/config.cfg file. To disable the DoDocNameOrder configuration setting: 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. When set to false, content items are not sorted. When the value is set to true (the default), content items are sorted by ContentID. To change the order, disable the DoDocNameOrder configuration setting. It may be preferable to have faster query results without the predictable order. But sorting by ContentID can be time-consuming.

Ordering by ContentID is advantageous because the order is predictable when the Repository Manager has a long list of content items. By default, the query sorts the results by the ContentID of the content items. When the Repository Manager application is started, it runs a default query against the database that returns all content released the previous day.

Gem wk4 year was made