Beruflich Dokumente
Kultur Dokumente
Scenarios
1) Schedule monitoring probes to run periodically 2) Create a watch based on a probe output 3) Analyse the probes execution over time from the monitoring dashboards 4) Handle alerts generated by the system and based on the watch defined earlier 5) Report from the trending derby database
Objectives
In this lab, you will learn how to: Schedule monitoring probes and analyze their execution data Define thresholds based on probes execution output or metrics, and alerts based on these thresholds Use the Monitoring dashboard available from the CMC Handle Alerts from the CMC Create a universe from the trending derby database
4. When the Schedule options appear, set the probe to run every 3 minutes from the current time to 24 hours later. We want the CMS Logon Logoff probe to run every 3 minutes while we are working on other exercises and generating some activity on the BOE cluster. We will analyze this monitoring data later on.
5. Select the Crystal Reports Service (Processing Server) probe, and click Properties Verify that the probe input parameters are as follows CUID should be from a Crystal Report from Public Folders > Report Samples > Demonstration (Launch BI Launchpad and get the CUID of this report)
6. Go to the Schedule section and set it to run every 5 minutes for the next 24 hours. 7. Select the InfoView probe and set it to run every 5 minutes for the next 24 hours. 8. You should now see 3 probes set as scheduled from the Probes dashboard. Notice the icon from the Schedule Status column.
9. If the Infoview probe shows a failure, it is probably because the username/password it is using is not correct. 10. Right-click on the probe and select Properties 11. Edit the username/password by inputting one of the train-xx users (e.g. train-01, or train-02) 12. Click Save and Close 13. Right-click on the probe and select Run Now 14. Click the refresh icon ( ) next to the Enable Auto-Refresh button. 15. If you wish the probe screen to automatically update, select the Enable Auto-Refresh button.
Create a watch
The CMS probe is now scheduled and you want to base a watch on it so it generates an alert if the Logon Logoff action takes longer than 200 milliseconds. 1. Go to Monitoring > Watchlist
2. Click on New and define a name, description for your new watch as showed in the screenshot Set the number of states to Two (OK, Danger) and check the 2 options Show on Dashboard and Write to Trending Database
3. Click on Next Browse the available metrics and select Probes > BI40SIA.CMSLogonLogoff > executiontime On the right panel, set the Danger operator to >= and value to 200 (or choose a value that appears just above the current average so that you get some alerts)
4. Click on Next Leave the settings to default: alert notifications will be sent every time the threshold is reached and notifications will be sent to the Administrator user.
Get notified when the threshold is reached When your CMS probe has been running for a few hours you may have sent alerts to the Administrator. 1. Log on to BI Launch Pad
2. From the Home Page, notice the new Alerts from the Alerts module if you have alerts you will see something similar to this.
4. Log on to the CMC and go to Monitoring > Dashboard Notice the alerts on the right panel
Click on More Alerts at the bottom of the panel (or to the Alerts tab)
6. Select one of the alerts from the CMS probe, view the details and confirm it (in reality you will confirm it once youve taken action). You will use the Confirm button for this and also notice how the icon changes from Unread to Read to Confirmed . ,
2. Select one of the probes you scheduled earlier, for instance CMS Logon Logoff
3. From the bottom right graph, select the time window during which the probe has been running
4. Observe the chart being updated with the historic values stored in the trending database, feel free to use the time slider to select a different time window and zoom in and out. If you dont have much data at the moment, we will look again in 24 hours.
3. Locate the following lines in the jdbc.sbo <DataBase Active=Yes Name=Generic JDBC datasource> <JDBCDriver>
4. Add the following lines right after <JDBCDriver>, save and close the file <ClassPath> <Path>C:\RKT\Monitoring\\derby.jar</Path> </ClassPath> <Parameter Name="JDBC Class">org.apache.derby.jdbc.EmbeddedDriver</Parameter>
you are ready to launch Universe Design Tool or Information Design Tool. In this example we will use the Universe Design Tool. If you have extra time you could also try the steps on the Information Design tool.
1.
Login into BI4.0 Universe Design Tool and create Generic JDBC connection
2.
Define Login Parameters for UNV universe and point Database URL to Derby DB backup that you just created
Database URL= jdbc:derby:C:\DerbyDBBackup\Derby;create=false JDBC Class= org.apache.derby.jdbc.EmbeddedDriver
3.
4.
Create universe
6. Publish UNV universe, close Universe designer and now you can create a Webi report.
2.
Define connection Parameters and make sure that Server parameter points to Derby DB on Windows Server (<host>:<port>)= C:\DerbyDBBackup\Derby;create=false
3. Create single source Data Foundation (DFX) and use connection created in the first step
4.
From Table Browser of DF select three tables from APP scheme and move them to Master. Create joins
5. Create Derive table for each table from APP scheme (Define derived table SELECT as: select * from <table_name>) (This step is necessary if table columns are not visible when trying to create joins in previous step)
(Name Deriva table as original table name and add _DT. Example: MANAGED_ENTITY_STATUS_DETAILS_DT) 6. Create joins between derive tables
7.
Create Relational Business Layer by using Data Foundation created in previous steps
8.
9.
Go to Data Foundation to change the connection. Choose the shortcut to the secure connection (connection has extension cns)
10.
11. Now you are ready to create a Webi or Crystal Reports using this universe.
End of lab