Test 896: IBM Tivoli Compliance Insight Manager V8.0 Implementation

Section 1: Planning

1. Given the customer reporting needs, determine which report requirements can be supported by IBM Tivoli Compliance Insight Manager so that a reporting plan can be established for the implementation.
1. Identify the customer report needs.
2. Analyze the reports requested by the customer.
3. Determine which of these reports can be generated by IBM Tivoli Compliance Insight Manager.
4. Categorize the reports per platform.
5. Deliver a list of reports that can be produced.
6. Discuss with the customer how the reports should be distributed – per platform, per department, with or without scoping.


2. Given the customer report needs, review the requirements and assess which event sources will be required so that a list of event sources needed for the IBM Tivoli Compliance Insight Manager environment is delivered.
1. Review the reporting requirements determined during the assessment of the customer reporting needs.
2. Assess which event sources will be required to support the reporting requirements.
3. Deliver a list of event sources that need to be deployed.


3. Given the list of event sources needed to support the customer reporting needs, determine the best collection option for each event source so that the appropriate collection method for each event source is identified.
1. Review the list of event sources determined during the assessment of the customer reporting needs.
2. Discuss the collection options for each event source with the customer.
3. Discuss the advantages and disadvantages of each collection mechanism (per event source).
4. Determine the best collection option for each event source based on the customer feedback.


4. Given each target platform and the specific procedures, determine and configure the audit settings so that the desired events can be logged and ready for collection.
1. Identify the Event Source.
2. Identify the audit setting configuration procedure for the particular target platform.
3. Specify audit events desired from target platform based on the customer reporting needs.
4. Specify audit settings for desired platform.
5. Assess impact of desired settings.
6. Configure audit settings for desired platform.
7. Enable auditing on desired platform.
8. Verify desired events are being logged.


5. Given hardware and software prerequisites, verify processors' speed, the RAM and hard disk space amounts, available ports and hard disk space partitions so that it is determined that the system meets prerequisites and server is ready to be configured for IBM Tivoli Compliance Insight Manager.
1. Verify the required hardware and software is available.
2. Determine the rate of flow of collected data.
3. Verify CD-ROM drive is available on all IBM Tivoli Compliance Insight Manager Servers included in installation.
4. Verify servers and production network are available.
5. Verify TCP/IP connectivity between monitored servers and IBM Tivoli Compliance Insight Manager Standard Server(s) is ensured.
6. Identify the ports to be used by the installation.

-Determine which port will be used for server and actuator communications; by default this is port 5992.
-Verify that TCP port 139 is open to allow communication with Windows event sources.
-Verify that the TCP port 22 is open to allow communications with UNIX SSH event sources.
7. Verify that SSH is utilized.
8. Verify that the server’s hard disk drives are partitioned in a RAID level 5 configuration.
9. Determine the appropriate hard disk space, depending on the amount of daily log data that is collected on monitored platforms and applications.


6. Given the event sources, processors, audited logs, hard drive partitions, memory, GEM databases and delivered reports, determine the number of servers required so that IBM Tivoli Compliance Insight Manager can be implemented.
1. Define What Platform types will be audited.
2. Define Number of Machines Per each Platform type will be audited.
3. Determine the size of the audit files to be collected at a given rate for each Target Platform.
4. Determine the number of event sources the environment will handle.
5. Determine the number of GEM databases that will support the reporting requirements.
6. Determine the amount of events that will be generated by syslog.


7. Given the main components of IBM Tivoli Compliance Insight Manager, describe the purpose of the components so that key components are identified.
1. Describe the purpose of the standard server.
2. Describe the purpose of the management console.
3. Describe the purpose of the Web portal.

-Describe iView.
-Describe log manager.
-Describe policy generator.
-Describe scoping.
-Describe regulatory compliance.
4. Describe the purpose of the enterprise server.
5. Describe the actuator.


8. Given the collection, load, restart and backup schedules, plan the scheduled tasks so that continuity and completeness of data is maintained.
1. Determine when the restart task should take place.
2. Determine when the backup should take place.
3. Determine when the collects should take place.
4. Determine when the loads should take place.
5. Determine when the report distribution should take place.


9. Given the GEM database and W7 grammar, explain how event values are mapped to the GEM fields and categorized into W7 groups so that the W7 and GEM models are described.
1. List the W7 dimensions.
2. List the GEM fields.
3. Describe the relationship between the W7 grammar elements and the GEM fields.
4. Explain how the event values are mapped to the GEM fields.
5. Explain how event values are categorized into W7 groups.


10. Given IBM Tivoli Compliance Insight Manager policies, describe how policy exception and attention event are generated so that security rules are identified.
1. Describe with the W7 Model what would be an acceptable behavior of an event.
2. Describe how a policy exception is generated.
3. Describe how an attention event is generated.

Section 2: Installation

1. Given the installation media and a Windows server, install the database engine and the standard server, so that the installation is verified.
1. Log in to the Windows server as a user with administrative privileges.
2. Verify system prerequisites have been met.
3. Load Installation Disk 1.
4. Install the database engine.

-Run setup.exe.
-Define the installation directory.
-Define the database instance name.
-Define the sys user password.
5. Install the database engine upgrade.
6. Install the database engine critical patches.
7. Load Installation Disk 2.
8. Install the standard server.

-Run NTm setup.
-Choose the setup type of Expansion Server or Custom.
-Choose the installation directory.
-Define the Windows user account for the IBM Tivoli Compliance Insight Manager services.
-Select the database instance.
-Define the database user account.
-Define the initial databases.
-Define the datafile location.
-Define the connection information.
-Define the server name.
-Define the timezone for aggregation.
-Define the maintenance schedule.
-Define the collection failure alert configuration.
9. Apply current patches and platform updates.
10. Verify the installation.

-Review installation log files for errors.
-Verify status of IBM Tivoli Compliance Insight Manager services.
-Verify login to the management console succeeds.
-Verify login to the web portal succeeds.
-Verify patches and platform updates were successfully applied.
-Verify the IBM Tivoli Compliance Insight Manager directory structure has been created.


2. Given the installation media, install an enterprise server so that a IBM Tivoli Compliance Insight Manager cluster can be define.
1. Ensure that the database engine has been installed.
2. Launch the server installation.
3. Choose the appropriate setup type.
4. Complete the installation.
5. Subscribe servers to the cluster.


3. Given the installation media, upgrade a standard server to an enterprise server so that a IBM Tivoli Compliance Insight Manager cluster can be defined.
1. Identify the standard server to be upgraded.
2. Launch the server installation.
3. Perform a custom setup.
4. Choose the enterprise components.
5. Complete the installation.
6. Subscribe servers to the cluster.


4. Given the IBM Tivoli Compliance Insight Manager hotfix code on Windows platform, apply the hotfix so that IBM Tivoli Compliance Insight Manager is updated to the desired level.
1. Verify the current hotfix level is installed.
2. Apply hotfix.
3. Verify the hotfix has been successfully applied.


5. Given the IBM Tivoli Compliance Insight Manager hotfix code on the UNIX platform, apply the hotfix to the current environment so that the IBM Tivoli Compliance Insight Manager is updated to the desired level.
1. Apply hotfix.
2. Verify the hotfix has been successfully applied.


6. Given a running IBM Tivoli Compliance Insight Manager installation, verify the ability to log in, and that key processes and services are running so that the successful installation is confirmed.
1. Verify you are able to log in to the Management Console and IBM Tivoli Compliance Insight Manager Web applications.
2. Verify that all IBM Tivoli Compliance Insight Manager services started after successful installation.
3. Review the installation log files.
4. Verify the IBM Tivoli Compliance Insight Manager directory structure has been created.
5. Verify the main processes are running.


7. Given Compliance report media, verify the execution of the compliance setup program so that the compliance module is installed in the iView application.
1. Verify Compliance Reports Media and size.
2. Verify the available space.
3. Copy the compliance reports setup to a temporary directory.
4. Run set up.
5. Verify successful installation.
6. Delete the compliance reports setup from the temporary directory.


8. Given the actuator code and cfg file, install the actuator code on a supported platform so that an actuator is installed and ready to collect audit trails.
1. Log in to the server where the actuator is to be installed.
2. Mount the actuator installation media.
3. Launch the actuator setup program.
4. Install the actuator code.
5. Provide the actuator cfg file to establish the actuator/server configuration.
6. Verify the installation.


9. Given the management console and properly configured actuator and target machine, use the add machine process so that the actuator code is remotely installed.
1. Verify what other applications running on the target system that may interfere with the installation.
2. Launch the management console.
3. Add a new machine.
4. Select the system type.
5. Select the machine or machines to be audited.
6. Select local for the point of presence.
7. Define the communication port.
8. Select automatic for the installation type.
9. Enter the NetBios name for the machine or machines.
10. Enter the operating system credentials for the actuator service.
11. Enter the operating system credentials to be used to complete the installation.
12. Define the event source or sources to be audited.
13. Complete the add machine process.

Section 3: Configuration

1. Given the security compliance reporting requirements for a specific audit platform, configure the audit subsystem so that the collected security audit data can be used to generate the required security compliance reports.
1. Translate the Security Compliance reporting requirements to the required Audit Setting Configurations on the target platform.
2. Review the current audit settings on the target platform.
3. Apply changes to the current audit settings.
4. Verify that the audit settings changes have been committed.
5. Verify that the data collected (after committed the audit setting changes) meet the Security Compliance reporting requirements.


2. Given the management console, use the add machine process so that an audit trail is collected locally.
1. Launch the management console.
2. Add a new machine.
3. Select the system type.
4. Select the machine or machines to be audited.
5. Select local for the point of presence.
6. Define the communication port.
7. Select automatic or manual for the installation type.

-If automatic installation is selected, enter the NetBios name for the machine or machines.
-If automatic installation is selected, enter the operating system credentials for the actuator service.
-If automatic installation is selected, enter the operating system credentials to be used to complete the installation.
8. Define the event source or sources to be audited.
9. Complete the add machine process.


3. Given a Windows target machine, configure the machine so that security audit logs can be successfully collected via remote collection mechanism.
1. Configure or verify the Windows Domain relationship required for the remote collection of the target machine from IBM Tivoli Compliance Insight Manager server (or Windows Actuator).
2. Configure or verify that the Windows Services and network settings on the target machine required for remote collection are properly configured.
3. Configure or verify that the Windows Services and network settings on the IBM Tivoli Compliance Insight Manager server (or Windows Actuator) required for remote collection are properly configured.
4. Configure or verify that the TCP/IP connectivity between IBM Tivoli Compliance Insight Manager server (or Windows Actuator) and the target windows machine required for remote collection are enabled.
5. Configure or verify that the IBM Tivoli Compliance Insight Manager Server (or Windows Actuator) service run account has security privileges to perform a successful remote of the security log data from the target machine.
6. Add the remote collect windows target machine to the management console.
7. Add the corresponding event sources to the remote collect windows target machine.
8. Configure the event source properties of the remote event sources in the management console.
9. Verify that the security log data from the Windows target can be successfully collected.


4. Given SSH is configured, follow the add machine wizard so that remote SSH collection is installed.
1. Determine the SSH daemon is running on the audited system.
2. Ensure PuTTY is installed on the point of presence.
3. Determine the authorization key pair to use.
4. Enable a user account on the audited system.
5. Create the user.

-Ensure that the partition that contains the user home directory has enough free space to store a copy of the collected log data.
-Ensure that the user has all the necessary access to the log files and directories used during collect.
-Ensure that all commands to be run are in the user path and that the user is allowed to execute them.
-Create a special subdirectory in the user home directory to contain its authorized keys.
6. Test the communication between the point of presence and the audited machine.
7. Start the Add Machine wizard to add the audited system.
8. Ensure the collect is successful.


5. Given the network identity of the appliance, add the network appliance to the IBM Tivoli Compliance Insight Manager server so that security logs from the network appliance can be successfully collected.
1. Ensure that the communication path between the IBM Tivoli Compliance Insight Manager server (or Point of Presence) and the appliance allows unblocked transmission of the security events from the appliance.
2. Verify that appliance events are directed to IBM Tivoli Compliance Insight Manager.
3. Add the appliance as an audited machine to the IBM Tivoli Compliance Insight Manager server.
4. Verify that the security events from the appliance can be collected by the IBM Tivoli Compliance Insight Manager server.


6. Given a supported syslog ng environment and remote SSH collection is properly configured, configure the IBM Tivoli Compliance Insight Manager syslog collector so that the syslog events can be collected by IBM Tivoli Compliance Insight Manager.
1. Run configuration scripts on syslog-ng on supported server.
2. Inventory target syslog generator target machines.
3. Verify normalized naming for all target machines at IBM Tivoli Compliance Insight Manager, POP and TARGET.
4. Add syslog-GEM in the Management Console database view.
5. Add target machine in the Management Console.
6. Add the desired syslog event source from syslog host.
7. Set collect schedule to never.
8. Associate event source to syslog-GEM.
9. Set load schedule to never.
10. Verify target machine added in the syslog-ng.config file.
11. Forward syslog events to the syslog-ng server.
12. Verify syslog log folder and audit log file on the syslog-ng server.
13. Collect syslog event for added syslog event source.
14. Manual Load collected syslog events in Syslog-GEM database.
15. Generate events by type report for loaded syslog events.


7. Given the scripts, configurations, mapping definition files, collection and load processes, add an event source so that audit trails can be stored, mapped and loaded into GEM databases.
1. Open the management console.
2. Select the Event Source View.
3. Click Add Event Source.
4. Select Machine from witch to collect from.
5. Select the Event Source Type.
6. Define the Event Source Properties.
7. Define Collect Schedule.
8. Select GEM for data loads.
9. Define Load Schedule.


8. Given the management console, use the add machine process so that a ubiquitous log file is collected.
1. Launch the management console.
2. Add a new machine.
3. Select the system type.
4. Select the machine or machines to be audited.
5. Select local for the point of presence.
6. Define the communication port.
7. Select automatic or manual for the installation type.

-If automatic installation is selected, enter the NetBios name for the machine or machines.
-If automatic installation is selected, enter the operating system credentials for the actuator service.
-If automatic installation is selected, enter the operating system credentials to be used to complete the installation.
8. Define the event source as Ubiquitous Log.
9. Define the event source properties.
10. Complete the add machine process.


9. Given the management console, use the add machine process so that a W7 log file is collected.
1. Define a process that takes the custom log file and converts it to the W7 Log modified format (CSV or XML).
2. Implement the log file conversion process.
3. Launch the management console.
4. Add a new machine.
5. Select the system type.
6. Select the machine or machines to be audited.
7. Select local for the point of presence.
8. Define the communication port.
9. Select automatic or manual for the installation type.

-If automatic installation is selected, enter the NetBios name for the machine or machines.
-If automatic installation is selected, enter the operating system credentials for the actuator service.
-If automatic installation is selected, enter the operating system credentials to be used to complete the installation.
10. Define the event source as W7 Log (choosing the appropriate format of CSV or XML).
11. Define the event source properties.
12. Complete the add machine process.


10. Given the location information of a user and grouping store, configure the user information source to collect the user and grouping information from the store so that the user information source collects the user and grouping information.
1. Configure or verify that the IBM Tivoli Compliance Insight Manager server (or Windows Actuator) service run account has security privileges to perform a successful collection of the user and grouping information from the store.
2. Configure or verify that the user account (provided as part of User Information Source property) has security privileges to successfully collect the user and grouping information from the store.
3. Configure or verify that the Windows Services network settings are properly configured on the store for user and grouping information collection.
4. Configure or verify that the TCP/IP connectivity between IBM Tivoli Compliance Insight Manager server (or Windows Actuator) and the user and grouping store are enabled.
5. Configure or verify that the Windows Services network settings on the IBM Tivoli Compliance Insight Manager server (or Windows Actuator) required for user and grouping information collection are properly configured.
6. Add the User Information Source to the management console.
7. Configure the User Information Source properties in the management console.
8. Verify successful collection from the User Information Source.


11. Given a scheduled report distribution, implement the schedule so that reports are distributed.
1. Configure the general settings for report distribution.
2. Create a test email user in the Management Console.
3. Add the created test email address for this user.
4. Create a distribution task to set off as soon as a related database has loaded.
5. Verify reports are distributed.
6. Add the distribution list.


12. Given the Attention rules, protocol, severity and recipient list, set an alert so that the alert communicates an attention rule to the recipient list.
1. Identify the Attention Rule ID to use in the alert.
2. Select the Alert Maintenance Icon in the Management Console.
3. Create the Alert using the Rule ID, Protocol, Recipient, and Severity.
4. Verify the Alert are received or generated.


13. Given the management console, use the policy explorer and the company security to define a basic policy so that the customer reporting needs are met.
1. Determine which policies in the company security policy can be mapped to an IBM Tivoli Compliance Insight Manager security policy.
2. Launch the management console.
3. Open the policy explorer.
4. Duplicate the latest committed IBM Tivoli Compliance Insight Manager policy.
5. Edit the duplicate IBM Tivoli Compliance Insight Manager policy.
6. Define the appropriate W7 groups to support the company security policy.
7. Define the appropriate policy rules to support the company security policy.
8. Define the appropriate attention rules to support the company security policy.
9. Save and test the new IBM Tivoli Compliance Insight Manager policy.
10. Continue testing until the desired reporting needs are met.
11. Commit the new IBM Tivoli Compliance Insight Manager policy.


14. Given the loaded GEM database with a large number of Windows or firewall events, use the Automatic Policy Generator so that an appropriate policy is generated.
1. Open the application.
2. Define the name of the policy to generate.
3. Select the Data to use(C, K)
4. Generate Automatic Policy file.
5. Test data in a GEM with policy.
6. Extend the existing policy with the newly generated policy.
7. Load the test data again with the extended policy.


15. Given that scoping is required, assign assets so that access can be regulated.
1. Identify assets which require scoping.
2. Configure scoping for unassigned assets.

-On the entry page, click Enable Scoping.
-On the Confirm Status Change page, click Start to enable scoping or Cancel to end your operation.
-If you clicked Start, the Changing Scoping Status page is displayed. Wait till the change of the scoping status is complete.
-Define Scoping groups and assign users to these groups.
-Move a selection of W7 groups to the Scoping groups.
-Create similar Scoping groups for the Who, Where and OnWhat categories
-Reload the test data and logon into iView with one of the users that have restricted viewing capabilities as defined through the Scoping module.


16. Given the list of reports needed to satisfy customer needs, determine which reports will require a custom solution so that the customer reporting needs are met.
1. Review the list of list of reports needed to satisfy customer needs.
2. Determine which reports can be satisfied by the standard reports.
3. Determine which reports will require a custom solution.
4. For each custom report requirement, determine the following criteria:

-Report layout – report type and column selection
-Report criteria – event selection and conditions
5. Use the report wizard or a text editor to create the custom report.


17. Given a set of GEM load schedules, configure the IBM Tivoli Compliance Insight Manager Automated Report Distribution manager such that the GEM database reports are successfully sent on-time to a corresponding set of recipients.
1. Determine a time-line at which GEM database load completes and the GEM reports become available for distribution.
2. Determine the schedule for setting up the report distribution for each GEM database.
3. Configure the Email settings common to all report distribution tasks.
4. Verify with a test report distribution task that the report can be sent successfully to a test recipient.
5. Add the Report Distribution tasks for each GEM database.
6. Verify that the reports are distributed to the correct set of recipients on-time.

Section 4: Performance Tuning and Problem Determination

1. Given IBM Tivoli Compliance Insight Manager activities, identify log files so that troubleshooting can take place for the IBM Tivoli Compliance Insight Manager solution.
1. Identify log file that shows a collection has been successful.
2. Identify log file that shows the progress of a load into a GEM database, as well as the archiving of them.
3. Identify log file that shows the progress of a connection to a remote host and to the IBM Tivoli Compliance Insight Manager server.
4. Identify log file that shows iView reporting errors.
5. Identify the log where the actuator run on the point of presence shows its collection activity.
6. Identify the schedule restart log and sub log of the processes it runs.
7. Identify the Management Console activities events and the log where they can be found.
8. Identify the Consolidation log file.
9. Identify the successful database mount and activity log.
10. Identify the Log Manager activity log.
11. Identify the log file where iView activity can be found.
12. Identify the log file where lost chunks will be shown if they have been transferred to the depot.
13. Identify the log file showing reports have been delivered by the Distribution scheduled task or error occurred.
14. Identify log file indicating authentication to the web portal application.
15. Identify log file where Policy Generator Activity is found.
16. Identify the application that collects most of the log files for troubleshooting.


2. Given a GEM database, investigate the set of activities taking place during the GEM load so that the basic stages of load are described.
1. Identify the type of the GEM database load.
2. Identify the different phases of the GEM load.
3. Identify the type of mapping used by the GEM database.
4. Determine the current stage of the load
5. Determine whether any error occurred during the load, and in which phase of the load.
6. When an error occurs during any phase of the load, determine the set of log files that need to be preserved for further investigation.
7. Determine the duration of each phase of the load.
8. Determine whether the load has completed at any point in time, and the total duration of the load.


3. Given the verification of possible failures, troubleshoot the logon failure so that successful logon is achieved.
1. Verify IBM Tivoli Compliance Insight Manager services are running.
2. Verify correct user name and password are being used.
3. Verify the restart task.
4. Verify the recnotify.
5. Verify the blrec.


4. Given the log files and error message, apply standard problem determination techniques so that the problem can be resolved.
1. Identify the component that is failing (such as server, management console, Web portal, and so on).
2. Determine the type of failure (login, connectivity, and so on).
3. Identify the log file needed to gather additional information on the failure.
4. Review the appropriate log file.
5. Correct the problem or call support.


5. Given a IBM Tivoli Compliance Insight Manager Server or a Windows Point of Presence, generate and deliver diagnostics such that the diagnostics are complete and successfully delivered to the Support recipient.
1. Identify the IBM Tivoli Compliance Insight Manager Server or Windows Point of Presence where the diagnostics needs to be generated.
2. Ensure that there is enough disk space to store the diagnostics.
3. Determine under what situations a diagnostics file may be generated.
4. Locate the Windows program menu for Diagnostics generation and start up the Diagnostics generation task.
5. Choose the path where the Diagnostics file has to be generated.
6. Ensure that the diagnostics file has been generated.
7. Ensure that the diagnostics file is complete.
8. Deliver the diagnostics to the intended support recipient.
9. Verify that the support recipient has successfully received the diagnostics file.


6. Given the management console, test the connectivity, so that there is a successful connection to point of presence.
1. Right-click machine name.
2. Choose the properties option.
3. Click the Network Tab.
4. Click the Test IP and Port button.
5. Verify that message Port is listening appears.

Section 5: Administration

1. Given the management console application, navigate through the different views so that the basic administration activities for audited machines can be performed.
1. Launch the management console.
2. Open the audited machine view or event source view.
3. Determine which machines are being audited.
4. Determine to which machine group each audited machine is assigned.
5. Add a new audited machine.
6. Determine which event sources are being collected for each audited machine.
7. Determine the audit settings applied to each event source.
8. Determine where the event sources are being collected (local or remote).
9. Add a new event source.
10. Determine the state of each point of presence.
11. Determine the last collection date and time.
12. Determine the collection schedule for an event source.
13. Configure the collection schedule for an event source.
14. View the basic settings for a point of presence.
15. Test the connection to a point of presence.
16. Generate a new password when the secure channel between the server and a point of presence is broken.
17. Add a user information source.


2. Given the management console application, navigate through the database view so that the basic administration activities for databases can be performed.
1. Launch the management console.
2. Open the database view.
3. Determine the load schedule for a database.
4. Determine the load status for a database.
5. Associate an event source with an existing database.
6. Add a new database.
7. Manually load a database.


3. Given the management console application, navigate to the alert panel so that the basic administration activities for alerts can be performed.
1. Launch the management console.
2. Open the alerts panel.
3. View or modify existing alerts.
4. Define a new alert.
5. Create an alert rule that is only triggered by the eventid of an attention rule.
6. Verify alerts are sent.


4. Given the management console application, navigate to the user management panel so that the basic administration activities for users can be performed.
1. Launch the management console.
2. Create or modify a user.
3. Assign roles to a user.
4. Define database access for a user.
5. Delete a user.


5. Given the management console application, navigate to the policy explorer so that the basic administration activities for policies can be performed.
1. Launch the management console.
2. Open the policy explorer.
3. List the previously committed policies.
4. List the policies in draft mode.
5. Edit a draft policy.

-Add or modify grouping files.
-Add or modify policy and attention rules.
6. Commit a draft policy.
7. Open a committed policy.
8. Create a new policy based on an existing policy.
9. View an automatic policy.


6. Given the IBM Tivoli Compliance Insight Manager Web portal and IBM Tivoli Compliance Insight Manager user account with access to iView, navigate iView so that the functionalities are described.
1. Access IBM Tivoli Compliance Inisght Manager Portal
2. Access iView
3. Describe Compliance Dashboard

-Describe Enterprise Overview
-Describe Trend graphic
-Configure the trend graphic settings.
-Describe Database overview
-Configure the Dashboard settings.
4. Describe GEM Summary

-Describe Event Information
-Describe Status of the Database
-Describe Data in the Database