Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Objectives

The new learning objectives of this exercise are to generate a table in a MySQL database from a collection of blocks in Rhapsody and then update that table when values change in the SysML model.

Preparation

This exercise assumes the student has

  • IBM Rational Rhapsody 8.2 installed correctly on his or her machine with a valid license for use, and

  • Syndeia 3.3 installed as a plugin for Rhapsody with a valid license for use

  • Syndeia MySQL interface, correctly installed with a valid license for user.

  • A MySQL repository network connection in the Syndeia Repository Manager, where you have write privileges to MySQL

  • MySQL Workbench, a direct interface to the user's MySQL database

The specific instructions call for a schema named AV_Tutorial, but any other schema available to the user would work. For users unfamiliar with MySQL databases, Appendix 1 describes how to access the databases directly using the MySQL Workbench, where the user can create, modify, and view schemas, tables and table rows directly.
Caution: Rhapsody has, by default, restrictions on the naming of SysML elements, which can create problems when Syndeia tries to create Rhapsody model elements that violate these restriction, e.g. beginning a SysML block name with a number. We recommend modifying any Rhapsody models you create to relax these restrictions. Modify the properties of the top-level package of the model under General::Model::NamesRegExp with the following string and save.
^(([a-zA-Z0-9_][a-zA-Z0-9_ ():-]*)|(operator.+))$

Exercise

  1. We will use the collection of blocks in the MySQL_Tutorial Part 1 package in the MagicDraw model supplied, Syndeia_Tutorial_Testbed.rpy (Get it here - SysML Models, Profiles and Mappings.). In Figure 1, we see a component block with 12 specializations. We will use the parent component block to generate the table structure, using the value properties as column headers, and the specialized blocks to generate the table rows, with the default values as the column entries in each row.

    Caution: component.name is given a special stereotype, <<MySQLTable_PrimaryKey>>. This stereotype should be assigned to a parameter that will not have duplicate values within the MySQL table, unlike mass or cost.

    Figure 1 Contents of MySQL_Tutorial Part 1 package in Syndeia Tutorial Testbed.mdzip

  2. Launch the Syndeia dashboard from the MySQL_Tutorial Part 1 package in the SysML model. Select a Syndeia Cloud project, if necessary.

    Figure 2 Contents of MySQL_Tutorial Part 1 package in Syndeia Tutorial Testbed.rpy

  3. The first step is to create the table in MySQL. Go to the Connection Manager tab. Set the Connection Type to Model Transform, as shown in Figure 2. Drag the parent block, component, from SysML to AV_Tutorial in MySQL

  4. Confirm table generation, as shown in Figure 3.

    Figure 3 Confirming table generation

  5. When complete, the Connection Manager should show a new table, component, under demo_tutorial _Rhp, as shown in Figure 4.

    Figure 4 Connection Manager after generation of new table, component

  6. The Connection Search tab, as shown in Figure 5, shows the connection created between the SysML block and the MySQL table after Get All is clicked.

    Figure 5 Connection Search tab shows link between SysML block and MySQL table

  7. The next step is to create a row in the table in MySQL. Set the Connection Type to Data Map. Drag the child block, Atmospheric Sensor, from SysML to component in MySQL and a new table row is created, as shown in Figure 6.

    Figure 6 Generating a table row from the Atmospheric Sensor block

  8. The table viewed in the MySQL database through the MySQL Workbench appear as in Figure 7.

    Figure 7 Generating a table row from the Atmospheric Sensor block

  9. Before completing the table, we will demonstrate how to compare and synchronize the parameter values between the SysML model and the MySQL database. In Rhapsody, modify the default value of the cost value property of the Atmospheric Sensor block, from 100 to 50. In the Connection Browser tab, right click on the connection from the Atmospheric Sensor block and select Compare Source & Target, as shown in Figure 8.

    Figure 8 Generating a comparison across the Atmospheric Sensor data map connection

  10. The Comparison Result is shown in Figure 9. The changed value of Atmospheric Sensor.Mass can also be observed directly using the MySQL Workbench. To update the parameter value in MySQL, right-click on the same connection and select Sync Source -> Target and confirm.

    Figure 9 Comparison Result before updating SysML value to MySQL table

  11. The remaining SysML specialized blocks can be dragged over in one step by selecting the blocks (singly or multiple-select) on the left side of the Connection Manager tab and dragging them onto the component table on the right. When complete, the Connection Manager will appear as shown in Figure 10. The changed value of Atmospheric Sensor.Mass can also be observed in the right column.

APPENDIX 1: CREATING A TABLE IN MYSQL

The purpose of this appendix is to familiarize the reader with the MySQL Workbench, enabling him or her to create, display, edit and delete MySQL database tables independent of Syndeia. This may be useful in carrying out the Exercise 3.1 and 3.2 tutorials

A1.1 Connecting to a MySQL Database through MySQL Workbench

  1. In order to connect to a MySQL repository directly, install the MySQL Workbench client on your local computer and contact the MySQL server administrator for a user name, password and the server hostname.

  2. Launch MySQL Workbench from your local computer and select Database → Connect to Database (see Figure A 1)

    Figure A 1  Connect to Database from MySQL Workbench

  3. Entering the information provided by the administrator into the window in Figure A 2, create a quick connection path on the workbench desktop. The Stored Connection field should contain a nickname assigned by the user for easy identification.

    Figure A 2  Provide your credentials to setup a connection to your MySQL server

  4. There should now be an icon on the MySQL Workbench desktop label with the Stored Connection name. Click it to open the SQL Editor window, as shown in Figure A 3.

    Figure A 3  SQL Editor, existing schemas circled in red, Create New Schema icon circled in green

A1.2 Creating a MySQL Database Schema

  1. It is possible to create a table in one of the existing schemas shown in the lower left corner of Figure A 3, skipping this section. Alternatively, a new schema can be created by clicking the Create New Schema icon, shown in green in the same figure. This opens the Schema tab (Figure A 4)

    Figure A 4  Creating a new schema in MySQL, Step 1

  2. Assign the new schema a name and click Apply. A new window will appear (Figure A 5) that shows the SQL commands that create the new schema. Review and click Apply again. A final window (Figure A 6) prepares to execute the commands. Click Finish to complete.

    Figure A 5  Creating a new schema in MySQL, Step 2

    Figure A 6 Creating a new schema in MySQL, Step 3

A1.3 Creating a MySQL Database Table

  1. To create a new table, begin by selecting which of the available schemas to create the table in. Right-click on the desired schema in the lower left corner of Figure A 7 and select Set as Default Schema. The selections should now appear in bold font.

  2. Click on the Create New Table icon (see yellow highlight in Figure A 7).

    Figure A 7 Table Editor, available schemas circled in red, Create New Table icon circled in yellow

  3. Enter the new table's name in the first field. Check that the Schema to the right is correct.

  4. Expand the Window vertically, if necessary, to see several rows of the table headed Column Name…Datatype and enter column header information for the new table, as shown in Figure A 8. Generally, the first column entered will be set as primary key, but this can be changed by checking the PK and NN (Not Null) columns. When finished, click Apply. Respond to windows similar to Figure A 5 and Figure A 6 with Apply and Finish, respectively.

    Figure A 8  Table Editor, with column info entered (red highlight)

  5. To display and edit the contents of the table, enter the command shown is Figure A 9 in the Query 1 tab (shown for table Staff in schema test_demo) and click on the Execute icon.

    Figure A 9 Query 1 tab, display contents of table, red highlight around Execute icon

  6. As shown in Figure A 10, enter the data into the table in the lower pane. In this example, we show a table with two columns (employee and desk) and four rows. When all data has been entered, click Apply, Apply and Finish as before.

    Figure A 10 Table entry in lower pane

  • No labels