Video: creating a database connection profile

Start video

Click the link below to play the video:

Creating a database connection profile

Transcript

The video starts with the Welcome screen of IBM Db2 Analytics Accelerator Studio.

1. The user clicks the cross-shaped icon on the tab of the Welcome page to close the page.
2. The normally starts with the Accelerator perspective, which is the correct choice for work within IBM Db2 Analytics Accelerator Studio. If the Accelerator perspective is not selected, you can change this by clicking the appropriate button on the very right of the toolbar.
3. The video shows the Accelerator perspective. In the navigation area on the left, the user finds a tabbed notebook consisting of two pages. The Administration Explorer page is in front. This is the right choice.
4. The user in the video clicks a downward-pointing arrow next to the label New on the toolbar of the Administration Explorer.
5. From the menu that unfolds, the user selects New connection to a database.
6. The New Connection window opens. The left side of this window shows a list with the heading Select a database manager. In this list, the user selects Db2 for z/OS.

   This action changes the population of the JDBC Driver drop-down list on the upper right. The drop-down list now shows the default driver selection for Db2 for z/OS®, that is, IBM Data Server Driver for JDBC and SQLJ (JDBC 4.0) Default. This is the correct choice.

7. A tabbed notebook under the heading Properties shows a page labeled General up-front.
   1. In the Location field of this page, the user types the name of the Db2 subsystem that she or he wants to connect to. In the example, the user types STLEC1.
   2. In the Host field directly underneath, the user types the name of the database server that the Db2 subsystem is located on. In the example, this is DTEC534.vmec.svl.ibm.com.
   3. In the User name field, the user types SYSADM. This is the ID of a user with system administrator authority. It is not necessary to choose a user with such extensive authority, but it guarantees that the user can perform all tasks that might come up. This is why such an ID was chosen for the example.
   4. The user types the password of the SYSADM user in the Password field.
   5. The user selects the Save password check box so that the password does not have to entered for each new connection to the same Db2 subsystem.
   6. The user clicks the Test Connection button in the lower right of the window to see whether the connection works.
   7. An small alert window with the title New Connection is displayed. It contains the message Connection succeeded. The user clicks the OK button in the alert window to confirm the message and close the window.
   8. The user returns to the General notebook page in the New Connection window proper.
8. The user clicks the Finish button in the New Connection window to save the connection settings and to return to the Administration Explorer in the Accelerator perspective of IBM Db2 Analytics Accelerator Studio.
9. In the folder hierarchy of the Administration Explorer, the topmost folder labeled All Databases now contains several objects, which are also hierarchically organized.
   • The first entry shows an icon of a server followed by the name of the database server on which the connected Db2 subsystem resides. In front of this entry, the user finds a plus sign, which marks it as an expandable node.
     • On the next level down the hierarchy, the user finds an entry with the name of the connected Db2 subsystem. This is also an expandable node.
       • The next level down the hierarchy shows the objects in the Db2 subsystem, again organized in a folder hierarchy. Each folder in this hierarchy contains Db2 database objects of the same type. The topmost folder is labeled Accelerators and contains the attached accelerators.

   All this confirms that the connection to the Db2 subsystem has been established successfully. The video continues and shows how the user explores a few of the functions that have become available through the connection.

10. The user selects the Accelerator folder, which opens the Object List Editor in the right pane of the Accelerator perspective.

    The Object List Editor shows a list of the available accelerators.

    In the example, the first accelerator in this list is called SIM16. It is a regular accelerator, meaning that it can be used to accelerate queries.

    The second accelerator in the list is a virtual accelerator called VIRTBED. Virtual accelerators cannot accelerate queries, but can be used to extract valuable Db2 EXPLAIN information about queries, such as:

    • Can the query be accelerated?
    • Does the query contain errors, for example, is the SQL syntax wrong?
    • What will be the approximate response time if the query is accelerated?
11. The user double-clicks the entry for the SIM16 accelerator in the Object List Editor. This action opens the Accelerator view for that particular accelerator. The Accelerator view shows a list of the tables on the accelerator.

    On the toolbar of the Accelerator view, you find a filter field next to an icon (a large green plus sign). This field allows you to limit the number of tables that are displayed. This is especially useful if the Db2 subsystem contains numerous tables.

12. The user types EMP in this field to show just the tables whose name starts with the string EMP.

The video ends at this point.