16 System Settings Overview

Oracle Enterprise Repository's System Settings section allows administrators to configure the basic Oracle Enterprise Repository operation and to enable/disable specific features.

This chapter contains the following sections:

16.1 Access System Settings

To access the system settings, perform the following steps:

  1. Click System Settings in the sidebar on the Oracle Enterprise Repository Admin screen.

    Figure 16-1 Oracle Enterprise Repository System Settings Page

    Description of Figure 16-1 follows
    Description of "Figure 16-1 Oracle Enterprise Repository System Settings Page"

    The System Settings section opens in the main pane.

    System Settings are organized into categories. Each category is further divided into feature groups.

    Figure 16-2 Functional Settings

    Description of Figure 16-2 follows
    Description of "Figure 16-2 Functional Settings"

  2. Click the plus icon to expand the display of any category or feature group.

  3. Click the minus icon to collapse the display.

16.2 Search for System Settings

System settings for particular features can be located using the System Settings Search.

  1. Enter a search term in the System Settings Search box. The relevant category sections expand to display the relevant System Settings.

    Figure 16-3 Functional Settings

    Description of Figure 16-3 follows
    Description of "Figure 16-3 Functional Settings"

  2. Click the Clear button to clear the search results.

16.3 Enable System Settings Properties

In some cases it may be necessary to enable specific properties in order to activate certain optional Oracle Enterprise Repository features. These properties is provided by Oracle Support.

  1. Obtain the necessary system setting property.

  2. Enter the system setting property in the Enable New System Setting text box.

  3. Click Enable. The appropriate System Setting category will open in the lower pane.

  4. Edit the system setting properties as necessary.

  5. Click Save when finished.

16.4 Move Settings to Database

Exercising this option moves all system settings stored in property files to the database. This action cannot be reversed.

  1. Click Move settings to database. All system settings are saved to the database. This is for a clustered environment. All servers in the clustered environment will now have one source for system settings.

For more information, see the Move Application Properties to the Database section in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository.

16.5 Functional Settings

This section contains the following topics:

16.5.1 General User Interface

Figure 16-4 General User Interface

Description of Figure 16-4 follows
Description of "Figure 16-4 General User Interface"

Properties

  • Default Browse Categorization

  • Default Browse Type

    • cmee.assettab.default-categorization-show-assettype

    • The True and False options toggle the default display of assets by Type in the Browse Tree on the Assets screen (subject to the system setting in Default Browse Categorization).

      True Results in..

      Figure 16-7 Browse Tree

      Description of Figure 16-7 follows
      Description of "Figure 16-7 Browse Tree"

  • Sticky Registrar Queues

    • cmee.registrar.stickyqueues

    • The True and False options toggle the default display of the selected Asset Editor tab when browsing assets.

      • True: Each asset opens to the Asset Editor tab in view from the previously selected asset.

      • False: Defaults to the Overview tab for each asset viewed in the Asset Editor.

  • Table Zoom

    • cmee.assettab.multiplegroupelement.force-zoom

    • The True and False options toggle the ability to open table elements in their own window.

  • Repeat Table Header

  • Show All Detail In Tabs

  • Long Date Format Specification

  • Short Date Format Specification

    • cmee.server.date.format.short.default

    • Specifies the date format for the display of abreviated date information (yyyy-MM-dd).

      • Similar to Long Date Format Specification.

  • Full Name Format

    • enterprise.defaults.fullname.format

    • Specifies the format for the display of user names. Can contain the strings "{prefix}", "{first}", "{middle}", "{suffix}" and punctuation immediately following any of these name parts in any order. Extra space is trimmed.

      • Note: Changes to this setting require server restart.

      Results in..

      Figure 16-13 Full Name Format

      Description of Figure 16-13 follows
      Description of "Figure 16-13 Full Name Format"

  • Show System-Supplied Relationships

    • cmee.show-system-supplied-relationships

    • The True and False options toggle the display of system-supplied relationships in the Asset Editor tab and and in the asset detail. The False setting will hide system-supplied relationships in the Asset Editor's Relationships tab and in the asset detail; however, they will remain visible in the Asset Editor's Configure Relationships dialog.

      System-supplied relationships are used for system-specific relationships within Oracle Enterprise Repository, such as allowing for more complex matches when doing asset updates. Therefore, users cannot create or delete system-supplied relationships, nor can they modify a system-supplied relationship's direction, which is always read-only.

  • Display Name Field

  • Display Name - Full Name and Initial

    • enterprise.defaults.fullname.middleasinitial

    • When a user's middle name is supplied, the True and False options toggle the display of the middle name in full or as an initial.

    True results in...

    Figure 16-16 Full Name and Initial

    Description of Figure 16-16 follows
    Description of "Figure 16-16 Full Name and Initial"

    False results in..

    Figure 16-17 Full Name and Initial

    Description of Figure 16-17 follows
    Description of "Figure 16-17 Full Name and Initial"

16.5.2 Search

Figure 16-18 Search

Description of Figure 16-18 follows
Description of "Figure 16-18 Search"

Properties

  • Save Searches

    • cmee.asset.registry.saved.searches

    • The True and False options toggle the Save Searches feature. This feature allows search criteria to be saved and reused.

      True displays the Saved Searches section in the sidebar on the Assets screen, as illustrated below.

      Figure 16-19 Saved Searches

      Description of Figure 16-19 follows
      Description of "Figure 16-19 Saved Searches"

  • Search Indexed Fields

    • cmee.search.general.include.indexedfields

    • The True and False options toggle the inclusion of indexed fields in general asset searches.

  • Search Categorizations

    • cmee.search.general.include.categorizations

    • The True and False options toggle the inclusion of categorizations in general asset searches.

  • More Search Options Categorization Default Visibility

    • cmee.search.advanced.categorizations.visible

    • The True and False options toggle the default display of the Categorizations tree in the More Search Options dialog.

    False results in..

    Figure 16-20 System Settings

    Description of Figure 16-20 follows
    Description of "Figure 16-20 System Settings"

    True results in..

    Figure 16-21 More Search Options

    Description of Figure 16-21 follows
    Description of "Figure 16-21 More Search Options"

  • Search Specific Field

    • cmee.search.specific.field

    • The True and False options toggle the ability to search specific fields during Standard Searches by identifying the field to be searched in the Keyword text box.

      As illustrated below, the string description:MyAsset will search for the keyword the MyAsset in the Description field of every asset in the Repository.

      Figure 16-22 Search

      Description of Figure 16-22 follows
      Description of "Figure 16-22 Search"

  • Confirm Empty Search

    • cmee.empty.search.confirm

    • The True and False options toggle the display of a warning message when a user performs a search on a blank string.

      True displays a warning message.

  • Minimum Number of Characters for User Search

    • cmee.users.min.text.search

    • The numerical value entered in the text box determines the minimum number of characters required to perform a search to locate user information.

      Attempts to perform a user search with fewer than the minimum number of characters results in a warning message.

16.5.3 Policy Management

Figure 16-23 Policy Management

Description of Figure 16-23 follows
Description of "Figure 16-23 Policy Management"

Properties

  • Enable Compliance Templates

    • cmee.compliance-template.enable

    • Enables the Compliance Template System.

  • Enable Asset Policies

    • cmee.asset-policy.enable

    • Enables the Policy Management System.

  • Collapse Policy Assertions

    • cmee.asset-policy.collapse.assertions

    • Collapse the display of assertions by default when showing applied policies in the Asset detail.

  • Asset Policy Relationship

    • cmee.asset-policy.relationship

    • Defines the relationship type within the system to use for policy assignment - it should be a Two-way, Order Matters relationship.

16.5.4 Open API

Figure 16-24 Open API

Description of Figure 16-24 follows
Description of "Figure 16-24 Open API"

Properties

  • Open API

    • cmee.extframework.enabled

    • Enables the Open API.

  • Testing Capabilities of the Open API

    • cmee.extframework.test.enabled

    • Enables the testing Functions built into the Open API.

  • Open API - Max Assets

    • cmee.extframework.assets.max

    • Maximum number of assets returned by queries through the Open API..

  • Open API - Max Projects

    • cmee.extframework.projects.max

    • Maximum number of projects returned by queries through the Open API.

  • Open API - Max Users

    • cmee.extframework.users.max

    • Maximum number of users returned by queries through the Open API.

  • Open API - Location for temporary export file

    • cmee.extframework.export.tempfile

    • Path of temporary export file.

16.5.5 Print Asset Detail via PDF

Figure 16-25 Print Asset Detail via PDF

Description of Figure 16-25 follows
Description of "Figure 16-25 Print Asset Detail via PDF"

Properties

  • Use default XSLT for asset types

    • cmee.asset.pdf.xslt.default

    • The True and False options specifies that when exporting an asset to PDF, a default asset type is used. Failing its existence, an error is shown.

  • PDF Asset Export Destination

    • cmee.asset.xml.paths.export-destination

    • Text entered in the text box identifies the PDF asset export destination.

  • PDF Asset Export Destination URL

    • cmee.asset.xml.paths.export-destination-url

    • Text entered in the text box identifies the PDF asset export destination URL.

  • PDF Asset XSL Directory

    • cmee.asset.xml.paths.xsl-source

    • Text entered in the text box identifies the PDF asset XSL directory.

  • PDF Asset Generated PDF Destination

    • cmee.asset.xml.paths.out-destination

    • Text entered in the text box identifies the PDF asset generated PDF destination.

  • PDF Asset Generated PDF Destination URL

    • cmee.asset.xml.paths.out-destination-url

    • Text entered in the text box identifies the PDF asset generated PDF destination URL.

  • PDF Asset Export WebApp URL

    • cmee.asset.xml.paths.webapp-url

    • Text entered in the text box identifies the PDF asset export WebApp URL.

16.5.6 Projects and Navigator

Figure 16-26 Projects and Navigator

Description of Figure 16-26 follows
Description of "Figure 16-26 Projects and Navigator"

Properties

  • Enable Projects

    • cmee.projects.enabled

    • The True and False options toggle the support of multiple projects.

  • Navigator and Project Hierarchy

    • cmee.projecttool.advanced

    • The True and False options toggle advanced project options including the Navigator and project hierarchy.

  • Navigator Support for Microsoft JDK

    • cmee.navigator.force-msjdk-support

    • The True and False options toggle the use of an alternative Navigator applet that is compatible with Microsoft's applet plugin for Internet Explorer.

  • User Defined Projects

    • cmee.extraction.user-projects.enable

    • The True and False options toggle the feature that allows users to create a project on the fly during the asset Use/Download process.

    True results in...

    Figure 16-27 Use - Download

    Description of Figure 16-27 follows
    Description of "Figure 16-27 Use - Download"

    False results in...

    Figure 16-28 Use - Download

    Description of Figure 16-28 follows
    Description of "Figure 16-28 Use - Download"

  • User Defined Projects - Prefix

    • cmee.extraction.user-projects.prefix

    • As illustrated below, text entered in the property text box becomes the prefix for any user-defined projects. This is useful for visual grouping in reports. (User-defined Projects must be enabled.)

    Figure 16-29 Example

    Description of Figure 16-29 follows
    Description of "Figure 16-29 Example"

    Results in..

    Figure 16-30 Use - Download

    Description of Figure 16-30 follows
    Description of "Figure 16-30 Use - Download"

  • Producing Projects

    • cmee.project.producing.enabled

    • The True and False options toggle the display of the Producing Projects section in the Asset Submission dialog (Standard Submission via the Submit and Asset link on the Oracle Enterprise Repository Assets screen.)

    True results in...

    Figure 16-31 Asset Submission

    Description of Figure 16-31 follows
    Description of "Figure 16-31 Asset Submission"

    False results in...

    Figure 16-32 Asset Submission

    Description of Figure 16-32 follows
    Description of "Figure 16-32 Asset Submission"

  • Advanced Project Option - Categorization

    • cmee.projecttool.categorizations

    • The True and False options toggle the assignment of categorizations to projects.

  • Enable Project Reported Asset Value

    • cmee.projecttool.assetvalue.enabled

    • The True and False options toggle the metrics of the Reported Asset Value for projects.

16.5.7 Assets in Progress

Figure 16-33 Assets in Progress

Description of Figure 16-33 follows
Description of "Figure 16-33 Assets in Progress"

Properties

  • View Assets in Progress

    • cmee.asset.in-progress.visible

    • Select True to enable the ability to see assets in progress outside the Asset Editor.

16.5.8 Notifications

Figure 16-34 Notifications

Description of Figure 16-34 follows
Description of "Figure 16-34 Notifications"

Properties

  • Asset Use Notification

    • cmee.extraction.notify-maintainer

    • The True and False options toggle the feature that automatically sends an email to the notification address listed for an asset when that asset is used.

      Figure 16-35 Miscellaneous

      Description of Figure 16-35 follows
      Description of "Figure 16-35 Miscellaneous"

    • When an email is sent, the following algorithm is used to determine the destination address:

      • If the asset has a notification address, use that as the email destination,

      • else, if the system setting cmee.extraction.default.maintainer.email has a value, use that value as the destination address,

      • else, if there is a "submitted-by" user that has an email address, use that email address,

      • else, if there is a "created-by" user that has an email address, use that email address,

      • else, do not send a usage notification email.

  • Default Email Address for Asset Use Notification

    • cmee.extraction.default.maintainer.email

    • This system setting is used to specify the default destination email address for notifications related to usage sent by the system.

  • System Registrar Email

    • cmee.registrar.email

    • Fill in the text box with the registrar's email address, to be used in auto-generated email messages.

  • System Registrar Alternate Notification

    • cmee.registrar.email.enable

    • Allows notification emails to be sent to the System Registrar email address when the notification email has not been set on an asset.

  • Access Administrator Email Address

    • cmee.security-admin.email

    • Fill in the text box with the email address of the individual(s) to whom user- and access-related auto-generated emails are to be sent. This includes notifications sent when unapproved LDAP users are added to the user directory.

  • Enable Reminder Email

    • cmee.extraction.notification.enabled

    • Enables notification via email to update the status of asset usage and value metrics.

  • Reminder Delay

    • cmee.extraction.initial.delay

    • Fill in the text box with a numeric value indicating the number of days to wait after a user downloads an asset before sending a reminder to complete the Update Status form (see below).

      Figure 16-36 Update Status

      Description of Figure 16-36 follows
      Description of "Figure 16-36 Update Status"

  • Reminder Delay - Subsequent

    • cmee.extraction.subsequent.delay

    • Fill in the text box with a numeric value indicating the number of days to wait after the initial usage status reminder message before sending subsequent reminders.

16.5.9 Access Control

Properties

  • Custom Access Settings

    • cmee.customaccesssettings.enabled

    • Enables advanced custom access settings.

  • Custom Access Settings on Assets

    • cmee.customaccesssettings.asset

    • Enables advanced custom access settings on assets.

  • Custom Access Settings on Files

    • cmee.customaccesssettings.file

    • Enables custom access settings on files.

  • Ability to toggle all permissions

16.5.10 Software File Identification (SFID)

Properties

  • Enable Automated Usage Detection

    • cmee.usagedetection.enable

    • Enables the Automated Usage Detection plug-in to manage SFIDs, and allow automated detection of possible usage.

  • Enable Harvesting of Unrecognized SFIDs

    • cmee.sfid.harvesting.enable

    • Enables the collection of information related to detected SFIDs that are not yet registered in the system.

    Figure 16-38 Software File Identification (SFID)

    Description of Figure 16-38 follows
    Description of "Figure 16-38 Software File Identification (SFID)"

16.5.11 Use - Download

Properties

  • Asset Usage Custom Field List

    • cmee.extraction.exported-custom-field

    • This unique setting allows the creation of Custom Asset Usage Fields.

Create Custom Usage Fields

  1. Enter a name for the Custom Usage Field in the text box.

  2. As necesary, click Add to open additional text boxes.

    Figure 16-39 Use - Download

    Description of Figure 16-39 follows
    Description of "Figure 16-39 Use - Download"

  3. Enter a name for each additional Custom Usage Field in the corresponding text box.

  4. Click Save when finished. The new Custom Usage Fields appear in the Use - Download dialog.

    Figure 16-40 Use - Download

    Description of Figure 16-40 follows
    Description of "Figure 16-40 Use - Download"

16.5.12 Custom Links

Figure 16-41 Custom Links

Description of Figure 16-41 follows
Description of "Figure 16-41 Custom Links"

This group of settings controls the configuration and display of custom links on the right side of the Oracle Enterprise Repository menu bar.

Properties

  • Custom Link 1

    • cmee.tool.show-marketplace

    • The True and False options toggle the display of Custom Link 1.

    Figure 16-42 Custom Link

    Description of Figure 16-42 follows
    Description of "Figure 16-42 Custom Link "

    Figure 16-43 Custom Link 1 and Custom Link 2

    Description of Figure 16-43 follows
    Description of "Figure 16-43 Custom Link 1 and Custom Link 2"

    (Illustrates both Custom 1 Link and Custom 2 Link set to True.)

  • Custom Link 1 Label

    • cmee.tool.marketplace.label

    • Text entered in the text box will appear as the label for Custom Link 1 on the Oracle Enterprise Repository menu bar.

  • Custom Link 1 URL

    • cmee.tool.marketplace.url

    • Enter the URL for Custom Link 1.

  • Custom Link 1 Target Frame

    • cmee.tool.marketplace.target

    • Specifies the frame in which to open Custom Link 1

  • Custom Link 2

    • cmee.tool.show-marketplace

    • The True and False options toggle the display of Custom Link 2.

  • Custom Link 2 Label

    • cmee.tool.marketplace.label

    • Text entered in the text box will appear as the label for Custom Link 2 on the Oracle Enterprise Repository menu bar.

  • Custom Link 2 URL

    • cmee.tool.marketplace.url

    • Enter the URL for Custom Link 2.

  • Custom Link 2 Target Frame

    • cmee.tool.marketplace.target

    • Specifies the frame in which to open Custom Link 2.

  • Custom Help URL

    • cmee.tool.help.url

    • Specifies a custom URL for the Help link.

      Note: Oracle Enterprise Repository help files are hosted remotely by default. If necessary, Help files can be hosted in your local environment. Change this setting to reflect the location of the Help files.

16.5.13 Reports

Figure 16-44 Reports

Description of Figure 16-44 follows
Description of "Figure 16-44 Reports"

Properties

  • Report Server URL

    • oracle.reports.server.url

    • Specifies a custom URL for the report server link.

  • Report Server Endpoint URL

    • oracle.reports.server.endpoint.url

    • Specifies a custom URL for the Web Service endpoint to authenticate against the report server.

  • Report Server Username

    • oracle.reports.server.username

    • Specifies the username credential for the report server.

  • Report Server Password

    • oracle.reports.server.password

    • Specifies the password credential for the report server.

  • Enable PDF Output for Reports

    • oracle.reports.pdf.enable

    • Enables PDF Output for Reports.

  • Enable Excel Output for Reports

    • oracle.reports.excel.enable

    • Enables Excel Output for Reports.

16.5.14 Miscellaneous

Figure 16-45 Miscellaneous

Description of Figure 16-45 follows
Description of "Figure 16-45 Miscellaneous"

Properties

  • Asset Submission File Requirement

    • cmee.submission.file.required.enable

    • When enabled, a user performing a Standard Asset Submission is required to provide a file location URL or upload files.

  • Consumer Survey

  • Default Usage Rejection Reason

    • cmee.default.usage.rejection.reason

    • Use the list to select the default asset rejection reason that is recorded when an asset is rejected when updating the status of the asset usage in the My Stuff section.

    Figure 16-48 Default Usage Rejection Reason

    Description of Figure 16-48 follows
    Description of "Figure 16-48 Default Usage Rejection Reason"

    Figure 16-49 Consumed Assets

    Description of Figure 16-49 follows
    Description of "Figure 16-49 Consumed Assets"

  • Export Assets into a Microsoft Excel spreadsheet

    • cmee.asset.registry.export.excel

    • The True and False options toggle the ability to to export asset detail information to an external Microsoft Excel spreadsheet.

    True displays the Export to Excel menu selection in the asset search results frame and the Excel button in the asset detail.

    Figure 16-50 Export Assets

    Description of Figure 16-50 follows
    Description of "Figure 16-50 Export Assets"

    False removes the menu selection and button.

Affinity Settings

Within the context of Oracle Enterprise Repository, Affinity is the condition that occurs when two or more assets are deployed in the same project. The Affinity element will appear in the asset detail for each asset that meets this condition, and will list other assets that have (deployed) projects in common.

The following Affinity System Settings determine the specific behaviour of the Affinity element and its contents.

  • Affinity Threshold

    • cmee.assettab.affinity.threshold

    • If the number of affinity matches exceeds the numerical value entered for this setting, a View All Affinity Assets" link appears in the Affinity element in the asset detail.

  • Affinity Minimum Project Count

    • cmee.assettab.affinity.minimum

    • The numerical value entered in this field determines the minimum number of projects to which an asset is deployed in order to be displayed in the Affinity element in the asset detail.

    Figure 16-51 Affinity

    Description of Figure 16-51 follows
    Description of "Figure 16-51 Affinity"

    If the number of projects that have consumed the asset is less than the supplied numerical value, the Affinity element will indicate that the display criteria have not been met.

16.6 Server Settings

This section contains the following topics:

16.6.1 General

Figure 16-52 General

Description of Figure 16-52 follows
Description of "Figure 16-52 General"

  • Company Name

    • cmee.server.companyname

    • Enter the name of your company in the text box.

  • Homepage

    • cmee.enterprisetab.homepage

    • The default URL points to the default Oracle Enterprise Repository homepage, as it appears in the main (right) frame.

    Figure 16-53 SOA Governance

    Description of Figure 16-53 follows
    Description of "Figure 16-53 SOA Governance"

    Change this URL as necessary to load a different page as the Oracle Enterprise Repository homepage.

  • Default Character Encoding

    • cmee.server.defaultencoding

    • The default character encoding to use in the system (defaults to the JVM default).

    • Examples are UTF-8 and ISO-8859-1. UTF-16 is not supported.

  • Admin Role

    • enterprise.security.roletype.admin

    • The text entered in this box designates the name applied to the role that has unlimited administrative rights and permissions within Oracle Enterprise Repository.

16.6.2 Server Resources

Figure 16-54 Server Resources

Description of Figure 16-54 follows
Description of "Figure 16-54 Server Resources"

Properties

  • Web Resource Path

    • cmee.server.paths.resource

    • The filepath to the location on the Web server Web resources are stored.

  • Web Image Path

    • cmee.server.paths.image

    • The filepath to the location on the Web server where product images are stored. This setting must include the *images subdirectory of the Web Resource Path.

  • Web JNLP Path

    • cmee.server.paths.jnlp-tool

    • The filepath to the location on the Web server where JNLP tool jars are stored. Due to Java Web Start compatibility issues, this path must not point to an SSL-enabled service.

  • WebApp JSP Path

    • cmee.server.paths.jsp

    • The filepath to the location on the application server where JSPs are stored.

  • WebApp Servlet Path

    • cmee.server.paths.servlet

    • The filepath to the location on the application server where product servlets are stored.

  • Asset Detail Path

    • cmee.assettab.asset-detail-page

    • The application server path used by integrations to load asset details.

  • Database Connection Name

    • enterprise.dbaccess.connectionname

    • The name assigned to the database connection.

  • WebApp JSP Path

    • enterprise.server.paths.jsp

    • The filepath to the location on the application server where JSPs are stored.

  • WebApp Servlet Path

    • enterprise.server.paths.servlet

    • The filepath to the location on the application server where product servlets are stored.

16.6.3 Email

Figure 16-55 Email

Description of Figure 16-55 follows
Description of "Figure 16-55 Email"

Properties

  • Allow Distribution List Email

    • cmee.email.cc

    • The True and False options toggle the availability of the email distribution list feature. This allows users to create distribution lists so that the list members are automatically copied on certain email notifications that are sent as part of the asset registration process.

  • Allow External Emails in a Distribution List

    • cmee.email.nonuser.cc

    • The True and False options determine the ability for a user to specify external email addresses in distribution lists. True allows external email addresses in distribution lists. False restricts distribution lists to only internal Oracle Enterprise Repository users.

  • SMTP Server

    • cmee.server.smtp

    • The hostname or IP address of the SMTP server used for auto-generated email messages.

  • Use External Email

    • cmee.server.smtp.send-with-cron

    • True and False options determine the selection of the email mechanisms for automated Oracle Enterprise Repository messages. True enables the external mechanism. False enables Oracle Enterprise Repository's internal email send mechanism.

      Note: Changes to this setting require server restart.

  • Send Email Interval

    • cmee.server.smtp.send-interval

    • This setting determines the number of minutes between automatic Oracle Enterprise Repository email messages.

  • Send System Email as HTML

    • cmee.server.smtp.send.format-html

    • The True and False options toggle the selection of HTML or plain-text formating of automatic Oracle Enterprise Repository messages.

      • True enables HTML formating.

      • False enables plain text formating.

  • Send System Email with Reply-To Header

    • cmee.server.smtp.send.replyto-required

    • The True and False options toggle the option to include a Reply-to header in automated Oracle Enterprise Repository messages. The Reply-to header includes the From address.

      True enables the Reply-to header.

  • Notification Email Delimiter

    • cmee.email.delimiter

    • Use the list to select the appropriate delimiter (comma or semi-colon) for multiple email addresses as determined by the default email client. (For example, Microsoft Outlook uses the semi-colon, while Outlook Express uses the comma).

  • Send Diagnostic Email to Oracle

    • cmee.server.smtp.senddiag

    • The True and False options toggle an automatic monthly diagnostic email to Oracle, for internal informational purposes only.

  • Default Email Suffix

    • enterprise.defaults.email.suffix

    • The information supplied in this text box is automatically suffixed to usernames to form the default user email address.

16.6.4 Upload Area

Figure 16-56 Upload Area

Description of Figure 16-56 follows
Description of "Figure 16-56 Upload Area"

Properties

  • Submission Upload Directory

    • cmee.server.paths.upload

    • Defines a locally referenced operating system path to upload files onto the application server directly via an HTTP file upload process. This property enables the following features:

      • Enables the Add Attachment Now option in the Asset Submission form. (Required if files are to be attached to assets during the submission process.)

      • Enables Uploaded Submission Files option in the Asset Editor.

  • Registrar Submission Upload Path

    • cmee.server.paths.upload-registrar

    • Enables file browsing through the Asset Editor (Optional).

      • The path, when hosted by UNC, requires Windows OS or Samba/Sharity.

      • Enables the appearance of the Browse button in Uploaded Submission Files in the Asset Editor.

  • Submission Upload Artifact Store

    • cmee.server.paths.upload-repository

    • Sets a configured artifact store to allow direct public access to the submitted files. Used for one-step acceptance of submitted files in the Asset Editor. When this property is set:

      • Asset files that available for use/download are visible.

      • The Accept button is visible in the uploaded submission files section of the Asset Editor.

Proxy Downloads

Oracle Enterprise Repository includes an additional option that allows the Repository application server to act as a repository proxy for the user. This feature automatically removes username and password text that is supplied in the HTTP URL during file downloads. This feature is applicable to any artifact store providing that Oracle Enterprise Repository can have network connectivity to resources in that store. Contact Oracle Enterprise Repository support for details.

Examples of Artifact Store Configurations

For instructions on configuring one of the following artifact stores, see Creating and Configuring an Artifact Store.

  • UNC

    • Hostname: unc.oer.com

    • Path: upload/

    • Username: user_oer

    • Password: flash

    • URL: file:////unc.oer.com/upload/

  • HTTP

    • Hostname: http.oer.com

    • Path: oer-web/upload

    • Username: user_oer

    • Password: flash

    • URL: http://user_oer:[email protected]/oer-web/upload/

  • FTP

    • Hostname: meta.oer.com

    • Path: upload

    • Username: user_oer

    • Password: flash

    • URL: ftp://user_oer:[email protected]/upload/

  • ClearCase

    • Hostname: clearcase.oer.com

    • Path: ccaseweb/bin/ccweb

    • Username: user_oer

    • Password: flash

    • URL: http://clearcase.oer.com/ccaseweb/bin/ccweb/?dir=/&elem=&cmd=view&user=user_oer&password=flash

  • PVCS

    • Hostname: pvcs.oer.com

    • Path: dav

    • Username: user_oer

    • Password: flash

    • URL: http://user_oer:[email protected]/dav/

  • Raw URI

    • Name: Example RAW URI

    • RAW URI: http://www.example.com/path1/path2?parameter1&parameter2

    • URL: http://www.example.com/path1/path2?parameter1&parameter2

16.6.5 Audit

Figure 16-57 Audit

Description of Figure 16-57 follows
Description of "Figure 16-57 Audit"

Properties

  • Asset Save Export Filename

    • cmee.asset.logging.filenamep

    • Text entered in the text box identifies the filename used to save asset data at every save (for archival and audit purposes).

  • Asset Save Export Fail on Error

    • cmee.asset.logging.failonerror

    • Select the True option to enable the ability to abort the save of the audit if unable to write to the asset export filename for any reason.

16.6.6 Caching

Figure 16-58 Caching

Description of Figure 16-58 follows
Description of "Figure 16-58 Caching"

Properties

  • Preload Asset Cache at Start-up

    • cmee.assets.preload.at-startup

    • Select the True option to preload the asset cache on application server start-up.

      True preloads the asset cache.

  • Preload Asset Cache as Seperate Thread

    • cmee.assets.preload.as-seperate-thread

    • Select the True option to spawn the preloaded asset cache as a separate thread on application server startup.

16.7 Enterprise Authentication Settings

This section contains the following topics:

16.7.1 General

Figure 16-59 General

Description of Figure 16-59 follows
Description of "Figure 16-59 General"

  • Unapproved User Login

    • enterprise.security.unapproveduser.allowlogin

    • The True and False options toggle the ability for unapproved users to log in to the system. This is useful when using LDAP or container-managed authentication.

  • Display Login dialog

  • Maximum Failed Login Attempts

  • Concurrent Logins Per User

    • enterprise.security.concurrentuser.max

    • The numerical value entered in the text box determines the maximum number of concurrent logins each user is permitted. A value of less than or equal to zero permits infinite concurrent user logins.

  • Grace Logins

    • enterprise.security.password.expiration.gracelogins

    • The numerical value entered in the text box determines the number of times a user is allowed to log in after his/her password has expired.

  • Enable LDAP Login

    • enterprise.authentication.ldap.enabled

    • Enables the LDAP Login Module for authentication.

  • Enable Container Login

    • enterprise.authentication.container.enabled

    • Enables the Container Login Module for authentication.

  • Enable Advanced Container Login

    • enterprise.authentication.advancedcontainer.enabled

    • Select the True option to enable the Advanced Container Login Module for authentication.

  • Synchronize Container Roles

    • enterprise.authentication.container.synchroles.enabled

    • Enables the synchronization of existing Java EE container roles.

  • Default Email Suffix

    • enterprise.defaults.email.suffix

    • Suffix added to a username to determine their default email address.

  • New Unapproved User Notification

    • cmee.new.unapproved.users.notify

    • The True and False options toggle the feature that automatically sends an email to the security administrator when a new user is created via external authentication, such as LDAP or a Java EE container.

LDAP Settings and its description are as follows:

LDAP Settings Description
ldap.ssl.enabled Enables an SSL Connection for LDAP; defaults to false
ldap.host Host name for the LDAP server; required
ldap.port LDAP server port number; defaults to 389; optional
ldap.mask The LDAP mask, either the authentication bind or search criteria; required
ldap.allow-user-creation Determines if unapproved user accounts can be created; defaults to true; optional
ldap.version The LDAP version used, which can be either 2 or 3; defaults to 2; optional
ldap.bindDN The distinguished name of the administrator account; optional
ldap.bindPassword The password for the administrator account; optional
ldap.baseDN Start location for a search, works with ldap.mask and ldap.scope to define the search; optional
ldap.scope Determines the scope of the search; optional
ldap.uniqueIDAttrib Attribute Name that Identifies a Found Entry
ldap.emailAttrib Found Entry Email Attribute Name
ldap.givennameAttrib Found Entry First Name Attribute Name
ldap.surnameAttrib Found Entry Last Name Attribute Name
ldap.telephoneAttrib Found Entry Telephone Number Attribute Name
ldap.middlenameAttrib Found Entry Middle Name Attribute Name
ldap.enable-sync-depts If true, get user departments from LDAP upon login
ldap.enable-synch-roles If true, get user roles from LDAP upon login
ldap.deptAttrib Name of attribute of the departments of the entry found
ldap.rbac.roleAttrib Name of attribute of the roles of the entry found
ldap.redirectDnAttrib Attribute which identifies a second level lookup to retrieve user info; must be a dn(distinguished name); optional
ldap.retrieve-data-as-admin Retrieve data using the admin account
ldap.assign-default-roles If true, users shall be assigned default roles
ldap.follow-referrals If true, follow referral
ldap.auto-create-missing-roles If true, auto create missing roles
ldap.auto-create-missing-depts If true, auto create missing departments

16.7.2 Authentication Token

Figure 16-62 Authentication Token

Description of Figure 16-62 follows
Description of "Figure 16-62 Authentication Token"

  • Authentication Token Expiration

    • enterprise.defaults.authtokens.expiration.value

    • The numerical value entered in the text box determines the period of time (in units determined by the Authentication Token Expiration Units menu selection) until an authentication token expires and is eligible to be purged.

  • Authentication Token Expiration Units

  • Authentication Token Purge Expired Frequency

    • enterprise.defaults.authtokens.purgefrequency.value

    • The numerical value entered in the text box determines the period of time (in units determined by the Authentication Token Purge Expired Frequency Units menu selection) between purges of expired authentication tokens.

  • Authentication Token Purge Expired Frequency Units

    • enterprise.defaults.authtokens.purgefrequency.period

    • Use the list to select the units of time to be used in conjunction with the Authentication Token Purge Expired Frequency setting.

16.7.3 Password Settings

Figure 16-64 Password Settings

Description of Figure 16-64 follows
Description of "Figure 16-64 Password Settings"

  • Password - Minimum Length

    • enterprise.security.password.composition.minimumlength

    • The numerical value entered in the text box determines the minimum number of characters required for a valid password.

      Note: This setting does not apply to passwords created by individuals in the Admin role.

  • Password - Alpha Character Required

    • enterprise.security.password.composition.require.alpha

    • Select the True option to set the requirement that passwords contain at least one alphabetic character.

      Note: This setting does not apply to passwords created by individuals in the Admin role.

  • Password - Numeric Character Required

    • enterprise.security.password.composition.require.numeric

    • Select the True option to set the requirement that passwords contain at least one numeric character.

      Note: This setting does not apply to passwords created by individuals in the Admin role.

  • Password - Special Character Required

    • enterprise.security.password.composition.require.special

    • Select the True option to set the requirement that passwords contain at least one special character.

      Note: This setting does not apply to passwords created by individuals in the Admin role.

  • Password Expiration

    • enterprise.security.password.expiration.days

    • The numerical value entered in the text box determines the number of days until password expiration.

      A value of zero or less disables password expiration.

  • Password History Tracking

    • enterprise.security.password.history.count

    • The numerical value entered in the text box determines the number of prior passwords remembered by the system. The password history is used to prevent the reuse of passwords.

  • Password History - Minimum Tracking Age

    • enterprise.security.password.history.minagehours

    • The numerical value entered in the text box determines the minimum number of hours a password must be in effect before it is added to the password history. This feature is useful for preventing circumvention of the password history by repeatedly changing passwords.

16.7.4 Plugin Login Settings

Figure 16-65 Plugin Login Settings

Description of Figure 16-65 follows
Description of "Figure 16-65 Plugin Login Settings"

  • Plug-in Login Module Class Name

    • enterprise.loginmodules.pluggableloginmodule.classname

    • Text entered in the text box identifies the class name for the plug-in login module.

      Click +Add as necessary to add class names for additional plug-in login modules.

  • Plug-in Login Module Display Name

    • enterprise.loginmodules.pluggableloginmodule.displayname

    • Text entered in the text box appears as the display name of the plug-in login module.

      Click +Add as necessary to add display names for additional plug-in modules.

  • Plug-in Login Module

    • enterprise.loginmodules.pluggableloginmodule.enabled

    • Enter true in the text box to enable the plug-in login module.

      Click +Add as necessary to add and enable/disable additional plug-in modules..

  • Plug-in Login Module - Internal Checking

    • enterprise.loginmodules.pluggableloginmodule.internalchecking

    • Enter true in the text box to enable internal checking of password expiration and grace logins for the configured plug-in login module.

      Enter false in the text box when using LDAP-based, SSO-based, Container Managed or other external login modules to defer these types of checks to the external authentication system.

      Click +Add as necessary to add and enable/disable internal checking for additional plug-in modules.

  • Password Expiration

    • enterprise.security.password.expiration.days

    • The numerical value entered in the text box determines the number of days until password expiration.

      A value of zero or less disables password expiration.

  • Password History Tracking

    • enterprise.security.password.history.count

    • The numerical value entered in the text box determines the number of prior passwords remembered by the system. The password history is used to prevent the reuse of passwords.

  • Password History - Minimum Tracking Age

    • enterprise.security.password.history.minagehours

    • The numerical value entered in the text box determines the minimum number of hours a password must be in effect before it is added to the password history. This feature is useful for preventing circumvention of the password history by repeatedly changing passwords.

16.7.5 LDAP and Active Directory Settings

Figure 16-66 LDAP and Active Directory Settings

Description of Figure 16-66 follows
Description of "Figure 16-66 LDAP and Active Directory Settings"

  • LDAP Server Host Name

    • ldap.host

    • Enter the host name for the LDAP server. This is a mandatory field.

  • LDAP Server Port Number

    • ldap.port

    • Enter the LDAP server port number. The default is 389. This is an optional field.

  • LDAP Mask

    • ldap.mask

    • Enter the LDAP mask, either the authentication bind or search criteria. This is a mandatory field.

  • Creation of Unapproved User Accounts

    • ldap.allow-user-creation

    • Select True to determine, if unapproved user accounts can be created. The default value is true. This is an optional field.

  • Assign default roles to users

    • ldap.assign-default-roles

    • Select true to determine, if users shall be assigned default roles.

  • Auto create missing roles

    • ldap.auto-create-missing-roles

    • Select true to determine, if auto create missing roles is enabled.

  • Auto create missing departments

    • ldap.auto-create-missing-depts

    • Select true to determine, if auto create missing departments is enabled.

  • LDAP Version

    • ldap.version

    • The LDAP version used, which can be either 2 or 3. The default value is 2. This is an optional field.

  • Administrator Account Distinguished Name

    • ldap.bindDN

    • The distinguished name of the administrator account. This is an optional field.

  • Administrator Account Password

    • ldap.bindPassword

    • The password for the administrator account. This is an optional field.

  • Use SSL Connection

    • ldap.ssl.enabled

    • Enables an SSL Connection for LDAP. The default is false.

  • Follow referrals

    • ldap.follow-referrals

    • If true, follow referrals.

  • Retrieve data using the admin account

    • ldap.retrieve-data-as-admin

    • If true, then bindDN must be set. The default is false.

  • Search Start Location

    • ldap.baseDN

    • Start location for a search, works with ldap.mask and ldap.scope to define the search. This is an optional field.

  • Search Scope

    • ldap.scope

    • Determines the scope of the search. This is an optional field.

  • Attribute Name that Identifies a Found Entry

    • ldap.uniqueIDAttrib

    • Attribute name that identifies a found entry beyond the use of the distinguished name, if not specified, then defaults to uid. This is a mandatory field.

  • Found Entry Email Attribute Name

    • ldap.emailAttrib

    • Email attribute name of a found entry. This is an optional field.

  • Found Entry First Name Attribute Name

    • ldap.givennameAttrib

    • First name attribute name of a found entry. This is an optional field.

  • Found Entry Middle Name Attribute Name

    • ldap.middlenameAttrib

    • Middle name attribute name of a found entry. This is an optional field.

  • Found Entry Last Name Attribute Name

    • ldap.surnameAttrib

    • Last name attribute name of a found entry. This is an optional field.

  • Found Entry Telephone Number Attribute Name

    • ldap.telephoneAttrib

    • Telephone number attribute name of a found entry. This is an optional field.

  • Use LDAP Departments

    • ldap.enable-synch-depts

    • If true, get user departments from LDAP upon login.

  • Department Attribute

    • ldap.deptAttrib

    • Name of attribute of the departments of the entry found.

  • Use LDAP Roles

    • ldap.enable-synch-roles

    • If true, get user roles from LDAP upon login.

  • Role Attribute

    • ldap.rbac.roleAttrib

    • Name of attribute of the roles of the entry found.

  • Second Level Lookup Attribute

    • ldap.redirectDnAttrib

    • Attribute which identifies a second level lookup to retrieve user info; must be a dn(distinguished name). This is an optional field.

16.7.6 Single Sign-On (SSO) Settings

Figure 16-67 Single Sign-On (SSO) Settings

Description of Figure 16-67 follows
Description of "Figure 16-67 Single Sign-On (SSO) Settings"

  • Pass All Cookies - JWS

    • cmee.jws.pass-all-cookies

    • Select the True option to pass all of the current cookies from the user's browser to Java Web Start for the Asset Editor to use.

  • Suppress Authorization Header - JWS

    • cmee.jws.suppress-authorization-header

    • Select the True option to prevent authorization header from being propagated by JWS launched utilities.

    SSO Settings and its description are as follows:

    SSO Settings Description
    enterprise.container.auth.username Name of the header which contains the user's username
    enterprise.container.auth.firstname Name of the header which contains the user's firstname
    enterprise.container.auth.middlename Name of the header which contains the user's middlename
    enterprise.container.auth.lastname Name of the header which contains the user's lastname
    enterprise.container.auth.status Name of the header which contains the user's status. Values may be 0=ACTIVE, 10=UNAPPROVED, 20=LOCKED_OUT, 30=INACTIVE
    enterprise.container.auth.email Name of the header which contains the user's email
    enterprise.container.auth.phone Name of the header which contains the user's phonenumber
    enterprise.container.auth.roles Name of the header which contains the user's roles
    enterprise.container.auth.depts Name of the header which contains the user's departments
    enterprise.container.auth.enable-synch-depts If true, get user departments from the container
    enterprise.container.auth.enable-synch-roles If true, get user roles from the container
    enterprise.container.auth.assign-default-roles If true, users shall be assigned default roles
    enterprise.container.auth.auto-create-missing-roles If true, the system will auto create missing roles
    enterprise.container.auth.auto-create-missing-depts If true, the system will auto create missing departments
    enterprise.container.auth.roles-single-header If true, roles are passed within a single header
    enterprise.container.auth.roles-delimiter The delimiter between roles names
    enterprise.container.auth.depts-single-header If true, departments are passed within a single header
    enterprise.container.auth.depts-delimiter The delimiter between department names

16.7.7 Container Login Settings

Figure 16-68 Container Login Settings

Description of Figure 16-68 follows
Description of "Figure 16-68 Container Login Settings"

  • Fallback Authentication

    • enterprise.loginmodules.fallbackauthentication

    • Enables fallback authentication.

  • Container Login Module Class Name

    • enterprise.loginmodules.containerloginmodule.classname

    • Text entered in the text box identifies the class name of the container login module.

  • Container Login Module Display Name

    • enterprise.loginmodules.containerloginmodule.displayname

    • Text entered in the text box appears as the display name of the container login module.

  • Container Login Module

    • enterprise.loginmodules.containerloginmodule.enabled

    • Select the True option to enable the container login module.

  • Container Login Module - Internal Checking

    • enterprise.loginmodules.containerloginmodule.internalchecking

    • Select the True option to enable internal checking for the container login module.

16.7.8 Cookie Login Settings

Figure 16-69 Cookie Login Settings

Description of Figure 16-69 follows
Description of "Figure 16-69 Cookie Login Settings"

  • Allow Cookie Login

    • enterprise.security.cookielogin.allow

    • Select the True option to enable automatic login using a cookie. If disabled, manual login is required.

  • Default to Cookie Login

  • Cookie Login Module Class Name

    • enterprise.loginmodules.cookieloginmodule.classname

    • Text entered in the text box identifies the class name of the coookie login module.

  • Cookie Login Module Display Name

    • enterprise.loginmodules.cookieloginmodule.displayname

    • Text entered in the text box appears as the display name of the cookie login module.

  • Cookie Login Module

    • enterprise.loginmodules.cookieloginmodule.enabled

    • Select the True option to enable the cookie login module.

  • Cookie Login Module - Internal Checking

    • enterprise.loginmodules.cookieloginmodule.internalchecking

    • Select the True option to enable internal checking for the cookie login module.

16.8 External Integration Settings

This section contains the following topics:

16.8.1 General

Figure 16-71 General

Description of Figure 16-71 follows
Description of "Figure 16-71 General"

  • UDDI

    • cmee.uddi.enabled

    • Enables the UDDI Web Service Plugin.

  • UDDI - Default Business

    • cmee.uddi.default.business

    • Use the list to select the default business entity to be assigned to any UDDI services to which no business has been assigned.

  • Default UDDI User Name

    • cmee.uddi.user

    • The text in entered in the text box provides the default user name for UDDI searches when no user has been supplied.

  • Business Service Relationship Name

    • cmee.uddi.business.service.relationship

    • Use the list to select the relationship that will link UDDI Business Services to UDDI Business Entities.

  • UDDI

    • cmee.uddi.server.enabled

    • Select the True option to allow Oracle Enterprise Repository to act as a UDDI registry for selected applications.

  • UDDI - Suppress Instance Details

    • cmee.uddi.server.suppress.instdet

    • Some UDDI clients cannot properly process the instanceDetails element in a bindingTemplate response. Select the True option to suppress the instanceDetails element in the response to a get_serviceDetail request to the built-in UDDI server.

  • UDDI - AccessPoint Mapping

    • cmee.uddi.server.accesspoint.mapping

    • For asset types that are exposed through UDDI as services, this property specifies the asset type element that is to be used for the access point of the service in the UDDI model.

  • UDDI - AccessPointType Mapping

    • cmee.uddi.server.accesspointtype.mapping

    • For asset types that are exposed through UDDI as services, this property specifies the asset type element that is to be used for for the protocol type of the access point of the service in the UDDI model.

  • UDDI - WSDL Location Mapping

    • cmee.uddi.server.wsdl.mapping

    • For asset types that are exposed through UDDI as services, this property specifies the asset type element that is to be used for for the location ocation of the WSDL.

      If this value is left undefined, the system will inspect each relevant asset's associated files in an attempt to discover WSDL that has been specified as part of the asset payload.

  • Import - Enable UDDI Import

    • cmee.import.uddi.enabled

    • Select the True option to display Import from UDDI link in the Import Export section in the Admin sidebar. This setting allows the import of assets from an external UDDI registry.

  • Import - Default UDDI Service Type

    • cmee.import.uddi.service.assettype

    • Use the list to specify the default asset type to be assigned to imported UDDI services.

16.8.2 UDDI

Figure 16-72 UDDI

Description of Figure 16-72 follows
Description of "Figure 16-72 UDDI"

  • UDDI

    • cmee.uddi.enabled

    • Enables the UDDI Web Service Plugin.

  • UDDI - Default Business

    • cmee.uddi.default.business

    • Use the list to select the default business entity to be assigned to any UDDI services to which no business has been assigned.

  • Business Service Relationship Name

    • cmee.uddi.business.service.relationship

    • Use the list to select the relationship that will link UDDI Business Services to UDDI Business Entities.

  • UDDI

    • cmee.uddi.server.enabled

    • Select the True option to allow Oracle Enterprise Repository to act as a UDDI registry for selected applications.

  • Import - Default UDDI Service Type

    • cmee.import.uddi.service.assettype

    • Use the list to specify the default asset type to be assigned to imported UDDI services.

16.8.3 File Stores

Figure 16-73 File Stores

Description of Figure 16-73 follows
Description of "Figure 16-73 File Stores"

  • Advanced Access File Stores

    • registry.advanced.filestores.enabled

    • Sets advanced file store options.

16.8.4 Rational ClearCase

Figure 16-74 Rational ClearCase

Description of Figure 16-74 follows
Description of "Figure 16-74 Rational ClearCase"

  • Configuration Specification

    • cmee.config-spec.enabled

    • Enables attachment of configuration specification files to assets.

16.8.5 Eventing

Figure 16-75 Eventing

Description of Figure 16-75 follows
Description of "Figure 16-75 Eventing"

  • Enable Event Manager

    • cmee.eventframework.enabled

    • Select the True option to enable the Advanced Registration Flow subsystem.

  • Event Manager Notifier Thread Sleep (seconds)

    • cmee.eventframework.notifier.sleep

    • Specifies in seconds how long the notifier should wait, if an endpoint is unavailable, before retrying to send an event.

  • Event Manager Store Thread Sleep (seconds)

    • cmee.eventframework.store.sleep

    • Specifies in seconds how long the Event Manager's Store Manager thread should sleep before polling for the next available event stored in memory.

  • Event Manager Delivery Thread Sleep (seconds)

    • cmee.eventframework.delivery.sleep

    • Specifies in seconds how long the Event Manager's Delivery Manager thread should sleep before selecting the next available event from the JMS server.

  • Event Manager Embedded JMS Enable

    • cmee.eventframework.embedded.jms.enabled

    • Select the False option to disable the Event Manager's Embedded ActiveMQ JMS. Disabling this property will force the Event Manager to use an external JMS server. If this setting is disabled, all the JNDI properties should be configured.

  • JNDI URL

    • cmee.eventframework.jndi.provider.url

    • Specifies the JNDI URL.

  • JNDI User Name

    • cmee.eventframework.jndi.user

    • Specifies the JNDI user name.

  • JNDI Password

    • cmee.eventframework.jndi.password

    • Specifies the JNDI password.

  • JNDI Context Factory

    • cmee.eventframework.jndi.context.factory

    • Specifies the JNDI context factory.

      If this value is left undefined, the system will inspect each relevant asset's associated files in an attempt to discover WSDL that has been specified as part of the asset payload.

  • JNDI Connection Factory

    • cmee.eventframework.jms.connection.factory

    • Specifies the JMS connection factory to enable JMS clients to create JMS connections.

  • JNDI Topic

    • cmee.eventframework.jms.topic

    • Specifies the JMS topic, which is a pub/sub destination type for a JMS server.

  • JNDI Subscribers Client ID

    • cmee.eventframework.jms.subscribers.client.id

    • Specifies the JMS subscriber's client ID. The purpose of the subscriber client identifier is to associate a connection and its objects with a state maintained on behalf of the client by a provider. By definition, the client state identified by a client identifier can be in use by only one client at a time.

  • JNDI Producers Client ID

    • cmee.eventframework.jms.producers.client.id

    • Specifies the JMS producer's client ID. The purpose of the producer client identifier is to associate a connection and its objects with a state maintained on behalf of the client by a provider. By definition, the client state identified by a client identifier can be in use by only one client at a time.

  • Event Manager JMS Subscribers Enabled

    • cmee.eventframework.jms.subscribers.enable

    • If set the False option is selected, then the internal JMS subscribers will not be enabled. This is to make sure that the embedded JMS server is started. However, an external JMS tool can be used to connect to the embedded JMS server using the specified JMS Subscriber Client ID name. Once connected, the external tool can also be used to clean up events stored by the Event Manager.

  • JNDI Delivery Mode

    • cmee.eventframework.jms.deliverymode

    • Specifies the JMS delivery mode of PERSISTENT or NON-PERSISTENT. Although more reliable, persisting events to a store can affect performance.

  • JNDI Message Expiration

    • cmee.eventframework.jms.expiration

    • Specifies the message expiration time in seconds. If set, unprocessed events will expire in the specified number of seconds. The default value of 0 means that messages will never expire.

  • Lazy Initialize Event Manager

    • cmee.eventframework.lazy.load

    • Select the True option to "lazily" initialize the Event Manager only when an event is produced for the first time.

16.9 Email Templates

Certain specific events within Oracle Enterprise Repository trigger automated email responses. For instance, when a new asset is submitted, an email notification is sent to the registrar. The various templates are described below.

  • All Asset Tabs Approved: Notifies the registrar and the users assigned to the asset that all tabs have been approved.

    An asset's tabs can be approved in the Asset Editor. Each tab, with the exception of the Administration tab, has an Approve button. This button will not be available until the asset is has been accepted, which can be done under the Administration tab.

  • Asset Accepted: Notifies the submitter that the asset has been accepted.

    An asset can be accepted in the Asset Editor under the Administration tab. The Accept option is not available until the asset has been submitted.

  • Asset Active: Notifies the submitter and subscribers that the asset has been marked active.

    An asset can be marked as Active in the Asset Editor under the Administration tab under the Status section.

  • Asset Assign: Notifies users that the asset has been assigned to them for processing.

    An asset can be assigned to a user in the Asset Editor under the Administration tab within the Assign Users section.

  • Asset Deletion: Notifies the submitter and subscribers that the asset has been deleted.

    An asset can be deleted in the Asset Editor under the Administration tab within the Status section.

  • Asset Editor Submission: Notifies the registrar of an asset submission via the Asset Editor.

    Assets can be submitted within the Asset Editor by either selecting File->New or File->Copy/Migrate.

  • Asset Inactive: Notifies the submitter and subscribers that the asset has been marked inactive.

    An asset can be marked inactive in the Asset Editor under the Administration tab within the Status section.

  • Asset Registered: Notifies the submitter that an asset has been registered.

    An asset can be registered in the Asset Editor under the Administration tab. Assets must be submitted and accepted before they can be registered.

  • Asset Retired: Notifies the submitter and subscribers that the asset has been retired.

    An asset can be retired in the Asset Editor under the Administration tab within the Status section.

  • Asset Submission Rejection: Notifies the submitter that the asset has been rejected.

    An asset can be rejected by the Registrar in the Asset Editor.

  • Asset Tab Approved: Notifies the Registrar that a specific tab has been approved.

    An asset's tabs can be approved in the Asset Editor. Each tab, with the exception of the Administration tab, has an Approve button. This button will not be available until the asset is has been accepted, which can be done under the Administration tab.

  • Asset Tab Unapproved: Notifies the Registrar that a specific tab has been unapproved. For unregistered assets, the users assigned to the asset are also notified.

    An asset's tabs can be unapproved in the Asset Editor. Each tab, with the exception of the Administration tab, has an Approve or Unapprove button, depending on the state. This button will not be available until the asset has been accepted, which can be done under the Administration tab.

  • Asset Unaccepted: Notifies the submitter that the asset has been unaccepted.

    An asset can be unaccepted in the Asset Editor under the Administration tab. An asset must have been submitted before the accept/unaccept option is made available.

  • Asset Unassign: Notifies users that were previously assigned to an asset that they have been unassigned.

    A user can be unassigned to an asset in the Asset Editor under the Administration tab within the Assign Users section.

  • Asset Unregistered: Notifies the submitter that an asset has been unregistered.

    An asset can be unregistered in the Asset Editor under the Administration tab. Assets must be submitted and accepted before they can be registered/unregistered.

  • Asset Unsubmitted: Notifies the submitter that the asset has been sent to the Unsubmitted queue.

    An asset can be unsubmitted in the Asset Editor under the Administration tab. An asset must be unaccepted before it can be unsubmitted.

  • Repository Submission: Notifies the registrar of an asset submission.

    An asset can be submitted from the Web Tool under the Assets tab by selecting Submit an Asset.

  • Usage Query 1: Queries the asset consumer regarding the intended user off an asset.

    This is a notification to remind the user to submit a survey regarding this asset. The survey can be found in the Web Tool under the My Stuff tab within the Consumed Assets section. In the detail of the given asset is a button called Update Survey Status. This button will only be available if the Consumer Survey system setting is enabled. The setting is cmee.extraction.consumer-survey.enable.

  • Usage Query 2: Depending on the response to Usage Query 1, asset consumers may receive a second query regarding the intended use of the asset.

    This is a notification to remind the user to submit the survey regarding this asset. The survey can be found in the Web Tool under the My Stuff tab within the Consumed Assets section. In the detail of the given asset is a button called Update Survey Status. This button will only be available if the Consumer Survey system setting is enabled. The setting is cmee.extraction.consumer-survey.enable.

16.9.1 Editing Email Templates

The procedure begins on the Oracle Enterprise Repository Admin screen.

  1. Click Email Templates in the Admin sidebar. The list of email templates appears in the upper frame of the main pane.

    Figure 16-76 List of Email Templates

    Description of Figure 16-76 follows
    Description of "Figure 16-76 List of Email Templates"

  2. Select the email template to be edited from the list. The Email Template edit screen opens in the bottom frame.

    Figure 16-77 Email Template: All Asset Tabs Approved

    Description of Figure 16-77 follows
    Description of "Figure 16-77 Email Template: All Asset Tabs Approved"

  3. Use the Status list to activate/deactivate the email message.

  4. Edit the template information as necessary.

Notes on editing

  • The Status field can be set to Active or Inactive. When inactive, no email notification is sent for the specified event. Active is the default status.

  • Substitutions are dynamic variables that can be placed within the subject, message, and Mail From email address. When the notification is sent, these variables is replaced with the appropriate values. The following example demonstrates the syntax for entering a substitution for the name of the asset:

    You have submitted the asset called <%asset.name%>

    A list of acceptable substitutions is displayed with each email notification on the Email Templates screen.