Making the D3 connection

1. The easiest way to define a new D3 connection is to use the Multivalue Connection Wizard. It can be found from the OpenInsight 10 IDE by clicking, NEW, Database Components, Multivalue DataSource.

mv_007.jpg

2. From the New Data Source dialog box choose Connection Class: MVBFS and enter your Connection Name: MVDEMO_BOB-T500.

mv_008.jpg

3. When the Wizard is first started, the user is presented with a Welcome screen. Enter a name for this connection. The name of the connection is used by OpenInsight to attach to the data. Below you can see that we have named this connection MVDEMO_BOB-T500.

mv_009.jpg

4. Choose the Multivalue platform you want to connect to (e.g. D3, QM, Universe or Unidata).

Enter the Server Name or IP Address of the system that hosts your Multivalue database. The IP Address lets OpenInsight know the address of the server, either on the local machine, the local network, or the world wide web.

The Server Port is required for D3 or QM connections. The default value is usually acceptable.

mv_010.jpg

5. The Account is where the user enters the name of the account where the D3 files are stored, or the directory that holds the D3 files the user wants to work with.

For the purposes of this exercise we will use the MVDEMO account. Enter that name and click on the ‘Next’ button.

mv_011.jpg

6. This will bring up the Server Credentials form. The Server Credentials screen is where the user enters the information needed for OpenInsight to connect to the D3 Server.

The Username is a username accepted on the server

The Password is the password required by the Username.

mv_012.jpg

7. The Logon Procedure is the name of a procedure that will run on the D3 server when OpenInsight connects using the Username specified.

mv_013.jpg

8. Clicking on the ‘Next’ button brings up a panel that prompts for the location of the Shadow Dictionary location. Shadow Dictionaries are OpenInsight versions of the column definitions that define the D3 table. OpenInsight does not want to affect the column definitions on the D3 data source, so a local copy is made. There are a number of advantages to this, including formatting for OpenInsight reports.

The Wizard offers a default folder location where the shadow dictionaries will be created. If a full path is not specified a directory will be created within your OpenInsight folder. We will accept this default, and then click on the ‘Next’ button.

mv_014.jpg

9. The next screen is the MultiValue Linking Wizard. This wizard will allow you to attach specific files from your D3 server to OpenInsight.

mv_015.jpg

10. Choose the Connection Name that was previously defined to connect to a specific account on your D3 server.

mv_016.jpg

11. Choose the D3 files you want to attach to OpenInsight.

mv_017.jpg

mv_018.jpg

12. In most cases you do not need to scan. Only use this option if your D3 system has multi-level data files.

mv_019.jpg

13. The Wizard is now complete and you can manage your connection from the screen below. Connection details can be maintained via the Property Panel.

mv_020.jpg

14. Right click on a table to build your OpenInsight shadow dictionaries.

mv_021.jpg

15. Right click on a table to view the data dictionaries in the Table Designer.

mv_022.jpg

16. Below are the converted shadow dictionaries that can be maintained via the Table Designer.

mv_023.jpg

17. From the OpenInsight 10 IDE, go to View, Tool Panels, Database to open the Database Manager.

mv_024.jpg

18. The Database Manager will display in the left tool panel. You can see we have attached MV Tables from the MVDEMO_BOB-T500 volume.

mv_025.jpg

19. Now that the files from our D3 system are attached to OpenInsight they are seen as native tables. From the TCL command prompt we can type the following:

LIST CUSTOMERS BY STATE ID-SUPP BREAK-ON STATE CUSTOMERID ORGANIZATIONNAME CITY

mv_026.jpg

20. Click the Execute button to run the command. The report will output to the Print Preview window.

mv_027.jpg

  • bfs/mv/making_the_d3_connection.txt
  • Last modified: 2023/10/25 10:49
  • by 127.0.0.1