Creating a dashboard view
A dashboard view is the collection of replication or publishing configurations that you want to monitor. The view enables you to keep close tabs on the status and performance of your replication programs, Q subscriptions, and queues.
After you set up a dashboard view, you can save it to use at any time, and it can be shared by many users.
In this lesson, you will create a view to monitor two configurations: LONDON.ASN > DALLAS.ASN, and LONDON.ASN > TOKYO.ASN.
A replication configuration is the set of replication objects (programs, control tables, queues) that enable Q subscriptions of the same subscription type and are defined in a set of replication control tables. For example, the LONDON.ASN > DALLAS.ASN configuration contains the following objects:
- The control tables with the ASN schema on the LONDON database.
- The control tables with the ASN schema on the DALLAS database.
- Two replication queue maps, LONDON_ASN_TO_DALLAS_ASN and LONDON_ASN_TO_DALLAS_ASN2, which contain the SEND_RECVQ1_LON_DALLAS and SEND_RECVQ1_LON_DALLAS combined send queue-receive queues.
- Four unidirectional Q subscriptions: EMPLOYEE0001, DEPARTMENT0001, STAFF0001, and SALES0001.
The LONDON.ASN > TOKYO.ASN configuration contains the same control tables at the LONDON database, but different queue maps, queues, and Q subscriptions that enable unidirectional replication from LONDON to TOKYO.
- Start the Data Studio Server. From the windows Start menu, select All Programs > IBM Data Studio > IBM Data Studio V1.1.2 > Start Data Studio Server.
- Launch the Data Studio Administration Console. From the windows Start menu, select All Programs > IBM Data Studio > IBM Data Studio V1.1.2 > Data Studio Administration Console.
- On the Welcome page, enter your Windows log-in user ID and password for the
machine where you installed DSAC, and click on Log in:
Figure 4. Log-in page for DSAC
- On the left navigation panel, click on the plus (+) sign next to Q
Replication Dashboard, and select View Health:
Figure 5. View Health link under Q Replication Dashboard
The Q Replication Dashboard opens, with the Add Server window in front. (If you already registered a data server, click Create in the Dashboard Views table and then Add in the Server table). You will add the LONDON database as a server:
Figure 6. Add Server window
- Enter the following values, and click OK:
LONDONin the Database alias field.
- The host name or IP address of your computer in the Host name or IP
address field. If you are running DB2 and DSAC on the same local
computer, you can enter
- Your user ID and password for connecting to the LONDON database.
After the Add Server window closes, the Create Dashboard View wizard opens, showing the Server page with LONDON in the Server table.
Why you registered the LONDON server first
You started building your view with the LONDON server because it is the source for both the DALLAS and TOKYO target servers. By choosing LONDON, you enable the dashboard to discover both DALLAS and TOKYO (the control tables at the LONDON server contain the definitions for both configurations). You could build the view by starting with any of the servers, but because DALLAS and TOKYO are not related, you would have had to bring them into the view by using the wizard twice.
Regardless of which server you register first, the dashboard discovers all other servers that are related to this server through a Q subscription or publication.
- With the LONDON data server selected in the Server table, click Next
in the wizard:
Figure 7. Create Dashboard View wizard
- On the Schema page of the wizard in the Schemas for Server LONDON table, the
schema ASN is selected by default, so you can click Next.
The dashboard reads the control tables on the LONDON server with the ASN schema (LONDON.ASN) and discovers all replication or publishing configurations that are defined in them.
- On the Configurations page, two configurations are displayed in the
Configurations for LONDON.ASN table:
- LONDON.ASN > TOKYO.ASN
- LONDON.ASN > DALLAS.ASN
The two configurations are also displayed visually in the Topology area. In the Connection Information column of the table, an "Add missing information" control is shown:
Figure 8. Configurations page of wizard
The dashboard needs information to connect to the Tokyo and Dallas databases to monitor replication at the target as well as the London source.
- Click Add missing information. Fill in the host name or IP address of
your computer, and the user ID and password for connecting to the Tokyo and
Figure 9. Connection information complete
- Click Next. On the Summary page of the wizard, accept the default
view name of london.asn, the default refresh interval of 10 seconds, and the
default threshold for end-to-end latency:
Figure 10. Summary page of wizard
Here are brief explanations of some of the concepts on the Summary page:
Table 3. Summary page concepts Concept Explanation Dashboard view name By default, views are named after the server.schema on which they are based. Refresh interval This interval determines how often the dashboard updates monitoring information. The dashboard reads monitoring information that the Q Capture and Q Apply program insert into their control tables. If you want very granular monitoring information, you need to also make sure to set a low monitor_interval for the programs to ensure that they update performance information frequently enough to justify repeated refreshes by the dashboard. Threshold for end-to-end latency You can tell the dashboard to set an alert icon when end-to-end latency rises above a threshold. End-to-end latency is the time between the Q Capture program reading a transaction in the recovery log and the Q Apply program applying the transaction at a target table. The default threshold is 3 seconds. You can choose different thresholds for individual configurations within your view.
After you click Finish on the wizard, the dashboard displays its health summary page:
Figure 11. Health summary page of dashboard
In the next section, you will learn how to use the summary page to monitor replication performance.