1 Basic Configuration

This chapter provides an overview of the basic configurations required to use Oracle Enterprise Repository.

This chapter contains the following sections:

• Section 1.1, "Overview"

• Section 1.2, "Departments"

• Section 1.3, "Users"

• Section 1.4, "Projects"

• Section 1.5, "Roles"

• Section 1.6, "Access Settings"

• Section 1.7, "Sessions"

1.1 Overview

In Oracle Enterprise Repository, all users are assigned roles. Roles define the Oracle Enterprise Repository functionality that can be exercised by each user. In order for a user to access any files associated with assets in Oracle Enterprise Repository, the user must be assigned to a project.

Projects are the primary means of gathering metrics in Oracle Enterprise Repository. Oracle Enterprise Repository tracks assets produced by projects, as well as assets consumed by projects. Oracle Enterprise Repository users are assigned to projects, and when a user submits a new asset, they are prompted for the producing project. Similarly, when a user wants to reuse an asset, they are prompted for the project on which the asset is reused. Both Users and Projects are assigned to Departments. This is convenient from a reporting standpoint, as organizations can then track the production and consumption of reusable assets to a specific department.

Figure 1-1 describes the relationships between Users, Roles, Projects, Assets, and Departments.

Figure 1-1 Relationship Diagram

Description of "Figure 1-1 Relationship Diagram"

1.2 Departments

You need to set up or create departments before creating users and projects. This section contains the following topics:

• Section 1.2.1, "Creating a New Department"

• Section 1.2.2, "Editing Department Information"

1.2.1 Creating a New Department

To create a new department, perform the following steps in the Oracle Enterprise Repository Admin screen:

1. In the left panel, click Departments.

2. Click Create New. The Create New Department dialog is displayed.

3. Enter the appropriate information in each of the text boxes.

   Figure 1-2 Create New Department Dialog

   
   Description of "Figure 1-2 Create New Department Dialog"
   
   

4. When finished, click Save.

1.2.2 Editing Department Information

To edit a department information, perform the following steps in the Oracle Enterprise Repository Admin screen:

1. In the left panel, click Departments.

2. Click List All, or search for a particular department.

3. Select the department to be edited from the list in the right panel. The department's detail is displayed.

4. Click Edit in the department detail. The Edit Department dialog is displayed.

5. Update the text boxes as required.

6. When finished, click Save.

1.3 Users

This section describes the following topics:

• Section 1.3.1, "Creating a New User"

• Section 1.3.2, "Viewing User Information"

• Section 1.3.3, "User Search"

• Section 1.3.4, "Cloning a User"

• Section 1.3.5, "Editing User Information"

1.3.1 Creating a New User

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the left panel, click Users.

2. Click Create New in the Users section. The Create New User dialog is displayed.

3. Enter the appropriate information in each of the text boxes in the Overview section, as shown in Figure 1-3.

   Figure 1-3 Overview Section

   
   Description of "Figure 1-3 Overview Section"
   
   

4. Select Active in the Status list.

5. In the Roles section, assign roles to the new user by using the >> and << buttons to move items from the Available Roles column to the Selected Roles column, as shown in Figure 1-4. (The User role is the default role for all new users.)

   Figure 1-4 Roles Section

   
   Description of "Figure 1-4 Roles Section"
   
   

6. In the Departments section, assign the new user to departments by using the >> and << buttons to move items from the Available Departments column to the Selected Departments column, as shown in Figure 1-5.

   Figure 1-5 Departments Section

   
   Description of "Figure 1-5 Departments Section"
   
   

7. When finished, click Save.

1.3.2 Viewing User Information

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the Users section, use Search or List All to locate the user(s) to be viewed.

   The list of users is displayed in the main pane, as shown in Figure 1-6.

   Figure 1-6 List of Users

   
   Description of "Figure 1-6 List of Users"
   
   

2. Select a user from the list. The user's information is displayed in the lower pane.

3. Click Hide/Display Search Results button to expand the User detail to fill the main pane.

4. Click the first button in Figure 1-6 to switch to the tabbed view of the User detail.

   Figure 1-7 User Details Page

   
   Description of "Figure 1-7 User Details Page"
   
   

5. Click the first button in Figure 1-7 to switch back to the standard view of the User detail.

6. Click the second and third button in Figure 1-7 to scroll through the list of users.

1.3.3 User Search

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. Enter appropriate text in the Name text box.

2. Use the Department, Role, and Status lists as appropriate to narrow the search.

3. Click the Search button. Search results appear in the list in the upper frame of the main pane.

1.3.4 Cloning a User

Cloning a user provides an easy way for administrators to quickly duplicate user accounts.

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the Users section, use Search or List All to locate the user to be cloned.

2. Click the Clone button in the user detail.

   The Clone User dialog is displayed. The Overview section is blank, but information in the Roles and Departments sections duplicates that of the cloned user.

3. Enter the appropriate information in each of the text boxes in the Overview section.

4. If necessary, edit the information in the in the Roles and Departments sections by using the >> and << buttons to move items between the Available and Selected columns.

5. When finished, click Save.

1.3.5 Editing User Information

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the Users section, use Search or List All to locate the user(s) to be edited. The list of users opens in the main pane.

2. Select a user from the list. The user's information is displayed in the lower pane.

3. Click the Edit button in the user detail. The Edit User dialog is displayed (same form as the Create New User and Clone User dialogs).

4. Make changes as necessary in the Overview, Roles, and Departments sections.

5. When finished, click Save.

1.4 Projects

Projects are the primary means of gathering metrics in Oracle Enterprise Repository. Oracle Enterprise Repository tracks assets produced by projects, as well as assets consumed by projects. Oracle Enterprise Repository users are assigned to projects, and when a user submits a new asset, they are prompted for the producing project. Likewise, when a user wants to reuse an asset, they are prompted for the project on which the asset is reused. This allows Oracle Enterprise Repository to generate reports on the reuse savings per project. It also allows Oracle Enterprise Repository to report on the savings generated by asset production teams. Projects are also hierarchical, which allows organizations to, for example, establish a program that may spawn many projects.

Projects are also a channel for governance practices. Oracle Enterprise Repository Compliance Templates (usually taking the form of Architecture Blueprints or Project Profiles) can be applied to projects.

The Oracle Enterprise Repository Projects page provides access to tools for creating and managing projects.

• Section 1.4.1, "Viewing Project Details"

• Section 1.4.2, "Creating a Project"

• Section 1.4.3, "Editing a Project"

• Section 1.4.4, "Reassigning Users/Usage"

• Section 1.4.5, "Locating a Project"

• Section 1.4.6, "Closing a Project"

• Section 1.4.7, "Adding a Relationship to a Project"

1.4.1 Viewing Project Details

Project information may be displayed as a series of portlets or tabs:

Overview

Includes a project Description, and indicates the assigned Department, Start Date, Estimated Hours, and project Status.

Compliance Templates

Displays the Compliance Template(s) assigned to the project.

Figure 1-8 Compliance Templates Tab

Description of "Figure 1-8 Compliance Templates Tab"

Consumed Assets

Lists any assets used in (or under consideration for use in) the project.

Figure 1-9 Consumed Assets Tab

Description of "Figure 1-9 Consumed Assets Tab"

Click the Zoom icon next to any listed asset to display its Reported Asset Value.

• Project members can view the Asset Usage Detail.

• Project leaders can view/edit the Reported Asset Value.

Figure 1-10 Reported Asset Value of Asset

Description of "Figure 1-10 Reported Asset Value of Asset"

Reported Asset Value represents the hours saved by reusing assets on their projects. This value is derived from either the Predicted Value, Consumer Value, or a completely new value determined by the project leader. Only the project leader can set this value.

Produced Assets

Lists any assets produced by the project.

Figure 1-11 Produced Assets Tab

Description of "Figure 1-11 Produced Assets Tab"

Users

Lists all users associated with the project, as well as each user's role on the project (leader/members). Project leaders have the ability to assign a Reported Asset Value value to assets consumed by the project.

Figure 1-12 Users Tab

Description of "Figure 1-12 Users Tab"

Related Projects

When enabled, lists any related projects, and defines the relationships in parent/child terms.

1.4.2 Creating a Project

This procedure is performed in the Projects screen.

1. In the left panel, click Create New. The Create New Project dialog is displayed.

   Figure 1-13 Create New Project

   
   Description of "Figure 1-13 Create New Project"
   
   

2. Enter the appropriate information in the Name, Description, and Estimated Development Hours text boxes.

3. Click the ... button to open the calendar to select a Start Date.

4. Select a department from the Department list.

5. Select the appropriate status in the Status list. There are two options that you can select from - Open and Closed. An Open status indicates that the project is still open for changes. A Closed status would mean that the project is closed and is not open for changes.

6. If necessary, select Automatically Assign to New Users.

7. Click Edit in the Users section. The Add/Remove Users dialog is displayed, as shown in Figure 1-14.

   Figure 1-14 Add/Remove Users Dialog

   
   Description of "Figure 1-14 Add/Remove Users Dialog"
   
   

8. Use Search or List All Users to display a list of users in the Search Results section. Use the Department list to filter search results.

9. Use the >> and << icons to move users between the Search Results, Project Leaders, and Selected Users sections.

10. Click OK. The assigned Project Leaders and Project Members appear in the Users section of the Create New Project dialog is displayed.

    Figure 1-15 User Dialog

    
    Description of "Figure 1-15 User Dialog"
    
    

11. Click Save. The Create New Project dialog closes, and the new project detail appears on the Projects page.

    Figure 1-16 Overview Tab

    
    Description of "Figure 1-16 Overview Tab"
    
    

1.4.3 Editing a Project

This procedure is performed in the Projects page.

1. Use Search or other means to locate the project to be edited.

2. Click Edit in the project detail.

3. Edit the project information as necessary. (See Section 1.4.2, "Creating a Project").

1.4.4 Reassigning Users/Usage

This procedure is performed in the Projects page.

1. Select the Users tab.

   Figure 1-17 Users Tab

   
   Description of "Figure 1-17 Users Tab"
   
   

2. Click Reassign Users/Usage. The Reassign dialog is displayed.

3. Use the options to select the appropriate action.

4. Click Choose a New Project. The Search for a Project dialog is displayed.

   Figure 1-18 Search for a Project

   
   Description of "Figure 1-18 Search for a Project"
   
   

5. Use Search or List All Projects to display a list of projects.

6. Select the project to which the users and/or usages are to be reassigned.

7. Click OK.

8. Click Next. The Select users you wish to reassign dialog is displayed.

   Figure 1-19 Reassign Users

   
   Description of "Figure 1-19 Reassign Users"
   
   

9. Use the >> and << icons to reassign users as Project Leaders and/or Project Members.

10. Click Next. A confirmation message appears.

11. Click Done.

1.4.5 Locating a Project

This procedure is performed on the Projects page.

1. Enter a keyword or search term in the Name text box.

2. Use the Department and Status lists as necessary to filter the search.

3. Click Search. Search results are listed in the main pane.

1.4.6 Closing a Project

This procedure is performed on the Projects page.

1. Select the project to be closed. The project detail is displayed in the bottom frame.

2. Click Edit. The Edit Project dialog is displayed.

3. Select Closed from the Status list in the Overview section of the Edit Project dialog, as shown in Figure 1-20.

   Figure 1-20 Edit Project Dialog

   
   Description of "Figure 1-20 Edit Project Dialog"
   
   

4. Click Save. If the project has consumed assets, the Update Usage Status dialog is displayed, as shown in Figure 1-21. The consumed assets are listed in this dialog, each with a Status list.

   Figure 1-21 Update Status

   
   Description of "Figure 1-21 Update Status"
   
   

5. Update the status of each consumed asset as necessary.

   
   

   Note: Depending on the specific role and permissions assigned to the project leader, certain assets consumed by the project does not appear in the list. If this is the case, an ATTENTION message appears in the Update Usage Status dialog. Be advised: Only the project members listed below the ATTENTION message can reject the asset. Otherwise, clicking OK in the Update Usage Status dialog sets the status of any hidden assets to Deployed.

   
   

6. When the Update Usage Status pop-closes the view returns to the Edit Project dialog.

7. Click Save. The project is closed.

1.4.7 Adding a Relationship to a Project

The Project Relationships feature enables you to map the relationships between projects on a parent/child basis.

This procedure is performed on the Projects page.

1. Click List All on the Projects page, as shown in Figure 1-22.

   Figure 1-22 Projects Page

   
   Description of "Figure 1-22 Projects Page"
   
   

   A list of projects appears in the top section of the main pane, as shown in Figure 1-23.

   Figure 1-23 List of Projects

   
   Description of "Figure 1-23 List of Projects"
   
   

2. Select the project to be edited. The Project Detail pane is displayed in the bottom section of the main pane, as shown in Figure 1-24.

   Figure 1-24 Project Detail Pane

   
   Description of "Figure 1-24 Project Detail Pane"
   
   

3. Click Edit in the Project Detail pane. The Edit Project dialog is displayed, as shown in Figure 1-25.

   Figure 1-25 Edit Project Dialog

   
   Description of "Figure 1-25 Edit Project Dialog"
   
   

4. Click Edit in the Related Projects section of the Edit Projects dialog. The Add/Remove Projects dialog is displayed, as shown in Figure 1-26.

   Figure 1-26 Add / Remove Projects

   
   Description of "Figure 1-26 Add / Remove Projects"
   
   

5. Click List All Projects. A list appears in the Available Projects window.

6. Select the project to be added and use the >> icon to move it to either the Parent Projects or the Child Projects category window, as appropriate. The project appears in the selected window.

7. Click OK to close the Add/Remove Projects dialog. The new project relationship appears in the appropriate list in the Related Projects section of the Edit Project dialog, as shown in Figure 1-27.

   Figure 1-27 Related Projects Section

   
   Description of "Figure 1-27 Related Projects Section"
   
   

8. Click OK to close the Edit Project dialog. The new project relationship appears in the Related Projects section of the Asset Detail, as shown in Figure 1-28.

   Figure 1-28 Related Projects Section

   
   Description of "Figure 1-28 Related Projects Section"
   
   

   Project relationship are also displayed in the Oracle Enterprise Repository Navigator.

1.5 Roles

Clicking the Roles link in the Oracle Enterprise Repository menu bar allows administrators to set up roles for an organization's various functions. Oracle Enterprise Repository access settings are established for each role, and each user is assigned a specific role based on his/her function within the organization.

Users assigned the admin role have unlimited access to all Oracle Enterprise Repository functions. By default, in either a new installation or a migration from a previous version, the user account identified as admin is assigned the admin role in order to facilitate initial installation and configuration. It is highly recommended that you limit the assignment of admin privileges to the original Oracle Enterprise Repository* user account and no more than one additional account. The various default roles established in Oracle Enterprise Repository offer a variety of privileges to satisfy the functions and responsibilities for any and all Oracle Enterprise Repository users. These roles may be customized to suit the particular needs of your organization.

• Section 1.5.1, "User Role Descriptions"

• Section 1.5.2, "Creating a New Role"

• Section 1.5.3, "Editing a Role"

• Section 1.5.4, "Deleting a Role"

1.5.1 User Role Descriptions

The various default roles shipped with Oracle Enterprise Repository are listed below. Users with access to the Admin tab can change role names to suit organizational needs. The permissions granted to these roles can be changed in the Access Settings section.

• User

  Anyone with an Oracle Enterprise Repository user name and password is considered to be a user. This role can be assigned as the default role for any new users at the time the user is created. All Oracle Enterprise Repository users can:

  • View news about the company's reuse initiatives

  • Locate, evaluate, and use/download assets

  • View projects

  • Generate reports

  • Submit assets to the registrar

• Access Administrator

  The access administrator creates all Oracle Enterprise Repository users, and assigns permissions to them. The access administrator must be familiar with the functions of the Admin Tab. Typically, access administrators can:

  • Create, view, and edit users and permissions

  • Generate reports

• Advance Submitter

  The advanced submitter role is typically assigned to asset builders and harvesters. Asset builders focus on building the asset content base. They respond to organization-wide asset needs as well as individual project needs. Harvesters study post-implementation projects for asset reuse potential. Typically, advanced submitters can:

  • Locate, evaluate, and use/download assets

  • View projects

  • Generate reports

  • Submit assets to the registrar

  • Edit asset metadata prior to asset registration

• Registrar

  The registrar is responsible for the acceptance or rejection of any asset. There may be more than one person functioning as a repository registrar, depending on the functions addressed. Typically, registrars can::

  • Locate, evaluate, and use/download assets

  • View projects

  • Generate reports

  • Submit assets to the registrar

  • Edit asset metadata prior to asset registration

  • Accept assets for the registration process

  • Approve tabs

  • Register assets

  • Edit access settings

• Registrar Administrator

  The registrar administrator is able to establish Types within Oracle Enterprise Repository, using the Type Manager. Typically, registrar administrators can:

  • Locate, evaluate, and use/download assets

  • View projects

  • Generate reports

  • Submit assets to the registrar

  • Edit asset metadata prior to asset registration

  • Accept assets for the registration process

  • Approve tabs

  • Register assets

  • Edit access settings

  • Edit Artifact Stores and Types

• Project Administrator

  Oracle Enterprise Repository tracks asset use at the project level in order to maintain a history for maintenance purposes. Project administrators create projects and assign users to projects using the Projects tab. Project administrators can close projects, indicate which assets were deployed, review, validate, and optionally override the predicted and consumer-reported value of assets used in a project through the project-reported asset value user interface. Typically, project administrators can:

  • Create, edit, and View projects

  • Generate reports

• System Administrator

  The system administrator configures Oracle Enterprise Repository for use, including, possibly, installation as well as the post-installation configurations. The system administrator typically can:

  • Enable and edit system settings

  • Generate reports

  (The system administrator role should not be assigned to general users.)

1.5.2 Creating a New Role

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the left panel, click Roles. The Roles section is displayed, as shown in Figure 1-29.

   Figure 1-29 Roles Section

   
   Description of "Figure 1-29 Roles Section"
   
   

2. Click Create New. The Create New Role dialog is displayed, as shown in Figure 1-30.

   Figure 1-30 Create New Role Dialog

   
   Description of "Figure 1-30 Create New Role Dialog"
   
   

3. In Figure 1-30, enter a role name and description in the text fields in the Overview section.

4. If necessary, select the Automatically assign to new users? box.

5. Click the Edit Users in the Users section. The Add New Users dialog is displayed, as shown in Figure 1-31.

   Figure 1-31 Add New Users Dialog

   
   Description of "Figure 1-31 Add New Users Dialog"
   
   

6. Use Search or click List All to locate users.

7. Use the >> and << buttons to move users between the Available Users and Selected Users columns.

8. When finished, click Save.

To add access settings to the role, see Section 1.6.1, "Granting Permissions to a Role".

1.5.3 Editing a Role

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the left panel, click Roles. A list of roles is displayed in the main pane, as shown in Figure 1-32.

   Figure 1-32 List of Roles

   
   Description of "Figure 1-32 List of Roles"
   
   

2. Use Search or browse the list to locate the Role to be edited.

3. Click the role to display its information in the lower pane.

4. Click the Edit button in the role detail (bottom frame). The Edit Role dialog is displayed, as shown in Figure 1-33.

   Figure 1-33 Edit Role: User Dialog

   
   Description of "Figure 1-33 Edit Role: User Dialog"
   
   

5. When finished, click Save.

1.5.4 Deleting a Role

This procedure is performed on the Oracle Enterprise Repository Admin screen.

(Requires the Delete permission. See Access Settings.)

1. In the left panel, click Roles. A list of roles is displayed in the main pane.

2. Use Search or browse the list to locate the role to be deleted.

3. Option 1:

   • In the list in the upper frame, place a check in the box next to each role to be deleted.

   • Click Delete.

4. Option 2:

   • Select the role in the list in the upper pane to display its information in the lower pane.

   • Click the Delete button in the role detail (lower frame).

5. Click OK in the delete confirmation.

   
   

   Note: Deleted roles no longer appear in Access Settings.

   
   

1.6 Access Settings

Access Settings allow the administrator to assign permissions to each role. Access settings identify the functions and responsibilities of a role, and determine each role's level of access to assets and asset management features in Oracle Enterprise Repository.

System safeguards prevent an administrator from inadvertently modifying permissions in such a way that would prevent his/her subsequent access to Access Settings.

• Basic Access Settings (BAS)

  Control the access to assets in Oracle Enterprise Repository across the board, based on the roles to which users are assigned. Access to Oracle Enterprise Repository tools, such as the Asset Editor or the Type Manager, is similarly controlled. Basic Access Settings establish access across the system. For example, permission to view assets applies to all assets; as does permission to Use/Download assets.

• Custom Access Settings (CAS)

  Establish Advanced Role-based Access Control to restrict access to specific assets or groups of assets in Oracle Enterprise Repository to specific user roles.

• Section 1.6.1, "Granting Permissions to a Role"

• Section 1.6.2, "Editing Permissions"

• Section 1.6.3, "Verifying User Permissions"

• Section 1.6.4, "Security Considerations"

1.6.1 Granting Permissions to a Role

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the left panel, click Basic Access Settings.

2. Select the appropriate grouping from the list in the Basic Access Settings section.

   Figure 1-34 Basic Access Settings

   
   Description of "Figure 1-34 Basic Access Settings"
   
   

   The selected grouping's access settings are displayed in the main pane.

   Figure 1-35 Set Permissions

   
   Description of "Figure 1-35 Set Permissions"
   
   

3. Click the Edit button (upper right corner of the main pane.) The Edit Basic Access Settings for:... dialog is displayed.

   Figure 1-36 Set Permissions

   
   Description of "Figure 1-36 Set Permissions"
   
   

   Roles are listed on the left; Permissions are listed along the top.

4. Select the appropriate option to determine which roles are displayed.

   Figure 1-37 Set Permissions

   
   Description of "Figure 1-37 Set Permissions"
   
   

5. Select the role to which permissions are to be granted.

6. Use the check boxes to assign the appropriate permission.

   • One click on an empty box adds a check mark (Granted)

   • A second click adds an X (Denied).

   • A third click clears the box (Not Granted).

7. When finished, click Save.

1.6.2 Editing Permissions

See: Section 1.6.1, "Granting Permissions to a Role"

1.6.3 Verifying User Permissions

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the left panel, click Basic Access Settings.

2. Select the appropriate grouping from the list in the Basic Access Settings section.

   The selected grouping's access settings are displayed in the main pane.

3. Click the View Access button (upper right corner of the main pane). A message dialog is displayed.

   Figure 1-38 View Access for Basic Access Settings for Assets

   
   Description of "Figure 1-38 View Access for Basic Access Settings for Assets"
   
   

4. Click Configure. The Search / Filter Users and Access Settings dialog is displayed.

   Figure 1-39 Search / Filter Users and Access Settings

   
   Description of "Figure 1-39 Search / Filter Users and Access Settings"
   
   

5. Use Search or click List All in the Find Users section to locate the user(s) whose permissions are to be verified.

6. Use the >> button to move user(s) from the Available Users column to the Selected Users column.

7. Click OK. The selected user's access settings are displayed.

   Figure 1-40 User Access Settings

   
   Description of "Figure 1-40 User Access Settings"
   
   

8. If multiple users are selected, clicking the > icon next to a user's name displays information specific to that user.

9. When finished, click Close.

1.6.4 Security Considerations

Role-based Access Control (RBAC) allows Oracle Enterprise Repository to track asset usage and production on a by-user basis and personalizes the presentation of assets, limiting visibility to designated portions of Oracle Enterprise Repository. However, Role-based Access Control is not intended to provide security for asset metadata, nor is it intended to supplement the security of underlying asset repositories.

Oracle Enterprise Repository access settings provide no additional security for otherwise unsecured assets or data. For maximum security, asset metadata should be managed in a manner that prevents access to the metadata via an unsecured repository. Confidential information should be embedded in the asset's payload, or attached as documentation files and hosted in a secure repository.

If you choose to circumvent an authentication and permission challenge from the underlying asset repository, you do so at your own risk.

The following actions also have security implications:

• Configuring SCM systems for access via a single Oracle Enterprise Repository user account

• Allowing system access by unapproved users

• Creating guest account logins

  • Guest accounts are strictly forbidden under the Oracle Enterprise Repository license.

Any of these actions has the potential to open the contents of Oracle Enterprise Repository to anyone with network access to Oracle Enterprise Repository.

1.6.4.1 Access Setting and the Asset Editor

Depending on the Access Settings in use, users with access to the Asset Editor may be able to see relationships to assets that are otherwise invisible to them in the registry. In this situation, the name of the hidden asset is visible, as is the detail of the relationship between that asset and an asset to which the users have access. No other information on the hidden asset is visible in the Asset Editor. In this situation, it is possible to delete the relationship between the visible and the hidden asset. However, given that the invisible asset is inaccessible to the users in question, the relationship cannot be restored by those users.

1.6.4.2 Permissions

Permissions may be:

• Granted (Permission is explicitly granted)

• Denied (Permission is explicitly denied)

• Not Granted (Permission is not explicitly granted nor denied.)

The table below identifies permissions that may be managed within Basic Access Settings.

Access Definitions

Assets: Tools regulated: Oracle Enterprise Repository Asset screen, Asset Editor, Type Manager.

Permission	Description
View	Assets may be viewed in Oracle Enterprise Repository.
Use	Displays/enables the Use - Download button in Oracle Enterprise Repository.
Download	Asset files may be downloaded. Provides visibility to file links after pressing the Use - Download button.
Review	Reviewing assets using Oracle Enterprise Repository.
Edit	Editing assets in the Asset Editor.
Accept	Accepting assets. This button, in the Asset Editor, moves assets from the Submitted -- Pending Review to the Submitted -- Under Review queue.
Approve Tabs	Approving metadata for assets. This button is available at the bottom of each tab in the Asset Editor display of each asset. Approving a tab logs the name of the approver and the date in the metadata, moves the asset out of the Submitted - Under Review queue for that tab, and changes the tab's text label to green.
Register	Registering assets. This permission providers the user with the ability to register all assets in the Asset Editor.
Edit Access Settings	Applicable only with Custom Access Settings. Provides the ability to assign Custom Access Settings to assets and files.
Create/Submit	Gives a user the ability to submit assets through or create new assets through the Asset Editor.
Launch Asset Editor	Gives a user the ability to open the Asset Editor tool. One must use this tool to edit and register assets.
Edit Artifact Store	Gives a user the ability to create and edit artifact stores (through the Asset Editor).
Edit Types	Gives a user the ability to configure asset type/compliance template metadata. Requires the Launch Asset Editor permission.
Notify	Determines if the user is allowed to send an ad-hoc email to users.
Global Permissions	These are permissions that do not apply to individual assets and cannot be overridden by custom access settings.

Access: Tools regulated: Oracle Enterprise Repository Admin screen: Users, Sessions, Roles, Departments, File Stores, Basic Access Settings, Custom Access Settings

Permission	Description
View	Viewing entries in the sections noted above.
Edit	Editing entries in the sections noted above.
Create	Creating users, roles, departments, file stores, and custom access settings.
Delete	Deleting sessions, roles, and custom access settings.

Projects: Tools regulated: Oracle Enterprise Repository Projects screen

Permission	Description
View	Viewing projects on the Projects page.
Edit	Editing projects on the Projects page.
Create	Creating projects on the Projects page.
Apply Template	Apply a compliance template to a project.

Policies: Tools regulated: Oracle Enterprise Repository Asset screen

Permission	Description
Apply Policy	Allows user to apply a policy to other assets.

Reports: Tools regulated: Oracle Enterprise Repository Reports screen

Permission	Description
View	Viewing reports.

System Administration: Tools regulated: Oracle Enterprise Repository Admin screen: System Settings, Email Templates.

Permission	Description
Edit	Ability to edit general, security, authentication, and file store settings.
Enable	Ability to enable new general, security, authentication, and file store settings.

1.7 Sessions

Sessions allows the administrator to see which users are logged in to Oracle Enterprise Repository and, if necessary, shut down a user session.

• Section 1.7.1, "Viewing Sessions"

• Section 1.7.2, "Deleting a Single Session"

• Section 1.7.3, "Deleting Multiple Session"

1.7.1 Viewing Sessions

This procedure is performed on the Oracle Enterprise Repository Admin screen.

1. In the left panel, click Sessions. A list of sessions is displayed in the main pane, as shown in Figure 1-41.

   Figure 1-41 Sessions Pane

   
   Description of "Figure 1-41 Sessions Pane"
   
   

1.7.2 Deleting a Single Session

1. Select the session to be deleted from the list in the main pane. The session's detail opens in the bottom frame.

2. Click the Delete button in the session detail. A confirmation dialog is displayed.

3. Click OK. The session is deleted.

1.7.3 Deleting Multiple Session

1. In the list of session in the main pane, place a checkmark next to each session to be deleted. (Place a checkmark in the check box at the top of the column to select all listed sessions.)

2. Click the Delete button in the session detail. A confirmation dialog is displayed.

3. Click OK. The session is deleted.

(Requires the Delete permission. See Section 1.6, "Access Settings".)