MySQL tables_rows → SysML Blocks_Instances

The objective of this exercise is to generate Rhapsody SysML blocks and instances from a MySQL database. Many organizations store data about products in such databases and it is desirable to be able to import this data into the SysML model. In this exercise, we will use the MySQL table created in the previous example and import this information back into an empty model in Rhapsody.

1. As in tutorials 2.3 and 2.5, create a new Rhapsody SysML project with an empty package and the Syndeia profile.
2. Name the empty package Tutorial_2_07.
3. Right-click on Tutorial_2_07 and open the Syndeia dashboard.

4. Expand Component database in the Connection Manager tab to show the databases and tables within the database. In this example, we are using the component table in the test_demo database, as shown in Figure 59.
   
   Image Added
   
    Figure 59 Syndeia Dashboard, Connection Manager tab, showing MySQl repository Component

   Image Added
   
   Figure 60 Dialog box

5. In the first exercise, we will Create a block in SysML linked to the table component in MySQL. Set the Connection Type to Model Transform. Drag the table component (see red arrow in Figure 59) into the Tutorial_2_07 package in the SysML model. Click Yes on the dialog box (Figure 60). When complete, component appears as a block in the SysML model panel as in Figure 61. Note that while the component block contains the structure of the component table (this can be seen in Rhapsody), it does not contain any of the data about specific components. This is the object of the next step.
   
    Image Added
   
   

   Figure 61 Syndeia Dashboard, Connection Manager tab, showing MySQl table component and the SysML block component
   
   Image Added 

   Figure 62 Instance generation dialog box
   
   

6. Set the Connection Type to Data Map. Select several of the individual records under the component table in the right-hand panel. Drag them into the Tutorial_2_07 package in the left panel. A dialog box as in Figure 62 will appear. Leave the "As Specialization" checkbox unchecked and click Yes. The new SysML instances are shown in Figure 63.
   
   Image Added 
   Figure 63 Syndeia Dashboard, Connection Manager tab, showing new SysML instance created 
   
   

7. Explore other options for creating transferring MySQL records to the SysML model
   1. Create a new package in the SysML project and drag some MySQL records into it. They will still be treated as instances (or specializations) of the component block even if they are not in the same package.
   2. In the Filter query box (upper left corner) of the Connection Manager., enter a valid MySQL syntax query, for example, Select * from test_demo.component where Mass < '3'. Only those records satisfying the query will be displayed and can be dragged into the SysML model.
   3. Erase the current contents of the Tutorial_2_07 package in Rhapsody, including all connections. Drag some MySQL records into it. Note that a component block is created automatically, along with the specializations corresponding to the individual records.
8. In the next part of the exercise, we will make change to the data in the database and update the SysML model from MySQL. Go to the MySQL Workbench and modify some details of the connected rows. For example, see Figure 64 where the left side shows the components table before making changes and the right side show the changes. The cost of the Communication Controller was increased from 25 to 50 and the mass of the Payload Controller was increased from 1.5 to 2.5.
   
   

   Image Added
   Figure 64 Modify contents of database in MySQL Workbench

    

9. Now multiple select (using Ctrl key) connections C2 and C6 that correspond to the 2 modified rows. Right click and select Sync Target → SysML, as shown in Figure 65.
   
   Image Added
   Figure 65Multiple select connections, right click, and select Sync Target → SysML
   
   

10. The Syndeia log window will show messages similar to below:
    
    

    16:57:19] INFO Processing 2 connections...
    [16:57:19] INFO Updating SysML block from MySQL table row for connection C2.
    [16:57:19] DEBUG GID of source: GUID 9e4c94e6-6344-4ea5-a8dd-25f28a3ddc0d | GUID a2f00ea8-6d04-44f1-bdae-cd993895cd41
    [16:57:19] DEBUG GID of target: Component database | {"database":"test_demo","table":"component","row":"Payload Controller","column":null}
    [16:57:19] DEBUG Setting real number 2.5 as the default value for property Mass. Creating a LiteralReal.
    [16:57:19] INFO Default value of value property Mass is changed from 1.5 to 2.5
    [16:57:19] INFO C2 connected sources (SysML) updated.
    [16:57:19] INFO Updating SysML block from MySQL table row for connection C6.
    
    Image Added 

    Figure 66 Updated values from MySQL

     
11. In the Rhapsody Features windows, you can see that the appropriate initial values have been updated, as shown in Figure 66.
12. Similarly, you can change the SysML instance slot value or block (default) value in Rhapsody and sync to MySQL by right-clicking the appropriate connection and selecting Sync SysML → Target.