Getting Started

Familiarize yourself with the Oracle Health Check Collections Manager Application.

Incident Ticket System Lookup Lists and Seed Data

Oracle Health Check Collections Manager provides a basic incident ticket system for tracking and managing incidents.

The application includes seed data for the lookup lists used when entering incident ticket information. The lookup lists include:

Products
Category
Customer Contacts
Notifications
Status Codes
Incident Severity
Incident Urgency

The predefined seed data contains commonly used values. Administrators can add new values or modify the seed data to meet organizational requirements.

You must have administrator privileges to manage seed data.

To access the seed data configuration:

Log in to Oracle Health Check Collections Manager with administrator privileges.
Click the gear icon in the upper-right corner.
Select the Administration tab.
Add or modify the required lookup list values.

Access Control System

Use the Access Control system to manage access to Oracle Health Check Collections Manager features based on functional roles.

Access Control is disabled by default. When Access Control is disabled, all authenticated users are granted administrator privileges and can access all application features.

Enable Access Control to assign one or more functional roles to users and restrict their access based on their responsibilities. Manage Access Control and user roles from the Administration tab.

The following functional roles are available:

Role	Access and Responsibilities
Admin	Has administrative access to Oracle Health Check Collections Manager. An Admin can also be a Workspace Administrator, depending on your functional role requirements.
DBA Manager	Can edit user roles and assign systems to other users within the DBA Manager's business unit (BU). A DBA Manager can be responsible for one or more BUs.
DBA	Has read-only access and can work with systems within one or more BUs when those systems are assigned by the corresponding DBA Managers. A DBA can also manage incidents assigned to them.
Read Only	Has monitoring-only access regardless of BU administrative roles.

Note:

The Read Only role takes precedence over other assigned roles. It restricts access to the Administration tab and limits the activities that the user can perform in Upload Collections.

Note:

All users must authenticate successfully before accessing Oracle Health Check Collections Manager, regardless of whether Access Control is enabled or disabled.

After configuring the Access Control system, assign the appropriate functional roles to users.

Oracle Health Check Collections Manager Application Administration

Use role-based administration to restrict Oracle Health Check Collections Manager features and data to authorized users.

The application provides different administrative capabilities based on the functional role assigned to a user.

Admin

An end user who is assigned the Admin role has administrator privileges within Oracle Health Check Collections Manager.

http://hostname:port/apex/f?p=<ApplicationID>

or:

http://hostname:port/pls/apex/f?p=<ApplicationID>

For example:

http://dbserver.domain.com:8080/apex/f?p=103

After logging in as an Admin, the Administration menu appears in the upper-right corner of the application.

An Admin can:

Grant or revoke administrative privileges.
Define Business Units (BUs).
Assign the DBA Manager role to users.
Assign DBA Managers to one or more BUs.
Assign systems to BUs. A system can belong to only one BU.
Assign DBAs to DBA Managers.
Assign systems to DBAs.
Ignore a check for a collection, BU, or system.
Create incidents and assign them to any user.
Manage all incidents.

Only users with the Admin role can modify all sections available under the Administration menu.

Before making Oracle Health Check Collections Manager available for wider use, an administrator should configure the application according to organizational requirements. Although most initial configuration is a one-time activity, administrators can modify the configuration as requirements change.

Configuration can include:

Products
Customers, which can represent internal workgroups
Categories
Notifications
Status codes
Email server and job settings
Notification settings
Incident severity
Incident urgency
User roles and system assignments
Business Units (BUs)
System-to-BU assignments

DBA Manager

A user assigned the DBA Manager role can administer users, systems, and incidents within the Business Units assigned to them.

http://hostname:port/apex/f?p=<ApplicationID>

or:

http://hostname:port/pls/apex/f?p=<ApplicationID>

After logging in, the Administration menu appears in the upper-right corner of the application.

Click Users and Roles to manage users and system assignments.

The scope of a DBA Manager can include one or more BUs.

A DBA Manager can:

Assign DBAs to the BUs that the DBA Manager manages.
Assign DBAs to one or more systems.
Ignore a check for a collection, BU, or system.
Create incidents for systems.
Assign incidents to DBAs who manage systems within the DBA Manager's assigned BUs.
Manage incidents associated with systems in the assigned BUs.

DBA

A user assigned the DBA role has read-only administrative access and can work with systems and incidents assigned to them.

http://hostname:port/apex/f?p=<ApplicationID>

or:

http://hostname:port/pls/apex/f?p=<ApplicationID>

After logging in, the Administration menu appears in the upper-right corner of the application.

Click Users and Roles to view the applicable user and role information.

A DBA can:

Manage systems within one or more BUs when those systems are assigned by the corresponding DBA Managers.
Ignore a check for a collection or system that the DBA manages.
Manage incidents assigned to the DBA.

A DBA cannot manage the Access Control List.

By default, Oracle Health Check Collections Manager automatically captures the details of users who log in using LDAP authentication and assigns them the DBA role.

You can disable automatic user capture if you want to control user creation and role assignment manually. You can re-enable automatic user capture at any time.

When automatic user capture is disabled, you must manually create users and assign the appropriate roles.

Click Administration, and then select Users and Roles.
To disable automatic capture of user details during login, click Don't Capture User Details (When Login).
After this option is enabled, Oracle Health Check Collections Manager no longer automatically creates user details when users authenticate through LDAP. Create the required users and assign their roles manually.
To re-enable automatic capture of user details during login, click Capture User Details (When Login).

Bulk Mapping Systems to Business Units

Use an XML file to map multiple systems to Business Units (BUs) in Oracle Health Check Collections Manager. Bulk mapping is useful when you need to create or update assignments for a large number of systems.

Click Administration > Business Unit > Assign System to BU.
Click Bulk Mapping.
Generate an XML file containing the current system-to-BU mappings:
1. Click Generate XML File (Current Mapping).
2. Download the generated XML file.
Edit the downloaded XML file to define the required system-to-BU mappings.
Click Upload Mapping (XML File) and upload the modified XML file to apply the new mappings.

Purging Old Collections

By default, Oracle Health Check Collections Manager runs a purge job daily and removes collection data that is older than three months.

You can change the purge frequency, disable automatic purging, or re-enable it when required.

Click Administration > Configure Email > Configure Mail Server/Notification/Purge Job.
Configure the purge settings as required:
- To change the purge frequency, specify the required value in Purge Frequency, and then click Click To Purge Every.
- To disable automatic purging, click Click To Disable Purging.
- To re-enable automatic purging, click Click To Enable Purging.