Click here to load reader

Lab 2: Editing a Rhapsody Model in RMM · PDF file Lab 2: Editing a Rhapsody Model in RMM Objectives After completing this lab, you will be able to: Create an RTC repository workspace

  • View
    4

  • Download
    0

Embed Size (px)

Text of Lab 2: Editing a Rhapsody Model in RMM · PDF file Lab 2: Editing a Rhapsody Model in RMM...

  • © Copyright IBM Corp. 2018 2 - 1

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    Lab 2: Editing a Rhapsody Model in RMM

    Objectives

    After completing this lab, you will be able to:

    ► Create an RTC repository workspace and local sandbox

    ► Load a Rhapsody model from RMM into your local sandbox

    ► Modify the model, link a work item to the change set and deliver the change set to a stream

    Scenario

    In general, when teams are working in parallel, there are two approaches:

    Optimistic: Teams work concurrently on the model in their own workspaces, without explicitly locking resources.

    Whilst this is the most flexible solution, when changes are delivered, there is the potential for conflict if two or more

    teams have modified the same artifact – in which case a merge is required.

    Pessimistic: Before editing a part of the model, the team locks that model element – preventing other teams from

    modifying it. Whilst this is a simpler solution (a merge is never* required) – it is also less flexible than the

    optimistic model. Making sure that the model is configured at the lowest level of granularity (‘everything is a unit”)

    helps mitigate this.

    *When an element is locked in Rhapsody – the integration places a lock on that same element in the team stream. If

    another team tries to lock that same element – RTC will check it and declare that it is already locked. However, if

    the other team decided to edit the file without locking it (terribly bad practice if the decision has been made to work

    pessimistically) then there is a chance of a conflict. RTC is not checking that stream in real time so there is a small

    chance that another team could modify a locked element before their RTC client has realized the element is locked.

    In this case, a merge would be required.

    Rational Team Concert may be configured to ‘auto-lock’ elements by declaring specific file types to be

    automatically read-only. In that case engineers must unlock units before working on them. This is outside the scope

    of this workshop however.

    In this Lab, you will start by setting up the Rational Team Concert client to connect to the RMM repository on the

    Jazz Team Server as Pete. You will create a repository workspace and a local sandbox for Pete. You will then load a

    model from RMM into Pete’s sandbox. You will then try out the pessimistic approach by locking a model element

    as Pete and seeing the results as Dan. You will not make any changes to the locked element however since the

    delivery of changes is the same whether you are working optimistically or pessimistically – the only real difference

    is the potential for a conflict.

    You will then create a new task in CCM for the sample user Pete to modify the model. From here on you will work

    optimistically. You will work as Pete, modifying the model and associating the changes with the task created earlier.

    You will publish Pete’s changes back to the team Stream. Finally, you will switch to Dan’s workspace and accept

    Pete’s changes – updating Dan’s version of the model. Note that in this lab there is no conflict – conflict resolution

    will be handled in Lab 4.

    Pete’s Activity:

  • Rhapsody Model Manager Tech Jam

    2 - 2 © Copyright IBM Corp. 2018

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    Task 1: Create a Repository Workspace for Pete

    In this task, you will configure Pete’s workspace (the workspace folder has already been created for you but you will

    import the preferences you created earlier in Dan’s workspace). You will start by creating a new repository

    connection to the architecture management area on Jazz. You will then connect to the Sample Models project and

    create a new repository workspace on the server for Pete. That repository workspace will flow into the default

    stream in RMM (‘Sample Models Stream’). You will then load the only component in that stream (Sample Models

    Default Component) into your local workspace (that is your sandbox).

    1. Open Pete’s Workspace:

    a. Switch to the Rhapsody client

    b. From the Rhapsody menu, select File  Close

    c. Switch to the RTC Client

    d. From the menu, select File  Switch Workspace  C:\Workspaces\pete

    TIP: Rational Team Concert will close and reload. The list of workspaces that appear in the switch menu can be configured in RTC preferences (Window  Preferences) then General  Startup and Shutdown 

    Workspaces

  • Lab 2: Editing a Rhapsody Model in RMM

    © Copyright IBM Corp. 2018 2 - 3

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    2. Create a Repository Connection:

    a. Close the Welcome page if it appears

    b. In the sidebar, click the Create a Repository Connection link:

    c. In the URI field, type https://ibmjazz:9443/am

    d. In the Name field, type RMM

    e. In the User ID field, type pete

    f. In the Password field, type pete

    g. Click Finish

    h. In any Repository Connection Certificate Problems dialogs (there may be several – or none), select Accept this certificate permanently and click OK:

    https://ibmjazz:9443/am

  • Rhapsody Model Manager Tech Jam

    2 - 4 © Copyright IBM Corp. 2018

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    i. If a Secure Storage dialog appears, click No:

    3. Connect to the Sample Models Project Area:

    a. Right-click the [email protected] repository connection and select Manage Connected Project Areas:

    b. Select Sample Models:

  • Lab 2: Editing a Rhapsody Model in RMM

    © Copyright IBM Corp. 2018 2 - 5

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    c. Click Finish

    4. Create a Repository Workspace:

    a. Expand the Sample Models project area:

    b. Expand the Source Control section

    c. Expand the All Streams section

    d. Right-click the Sample Models Stream and select New  Repository Workspace:

    e. In the Repository Workspace Name field, add Pete to the end of the current text:

  • Rhapsody Model Manager Tech Jam

    2 - 6 © Copyright IBM Corp. 2018

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    f. Click Next

    g. Select Use current repository:

    h. Click Next

    i. In the Read Access Permission window, select Project Area:

    TIP: Setting the visibility to Project Area will allow another user to change their flow target to this workspace – effectively allowing collaboration between users without / before publishing those changes into a stream.

    j. Click Next

    k. In the Components to Add window, select the Sample Models Default Component:

  • Lab 2: Editing a Rhapsody Model in RMM

    © Copyright IBM Corp. 2018 2 - 7

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    l. Click Finish

    m. In the Load Repository Workspace window, select Browse the components to select the folders to be loaded:

    n. Click Next

    o. In the Repository folders to load window, select Sample Models Default Component:

    TIP: Make sure this has a tick in it - not a solid fill. If this box is not ticked then a folder will not be created for the component and your sandbox will be out of sync with the team. This is easily corrected however by

    unloading the repository and then reloading it.

    p. Expand the Advanced Options section

    q. Select Load component files into sandbox subfolder

    r. Select Load the selected folders but do not create Eclipse projects:

  • Rhapsody Model Manager Tech Jam

    2 - 8 © Copyright IBM Corp. 2018

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    s. Click Finish

    t. If you receive a confirmation dialog, click OK:

    5. Confirm Folder Creation:

    a. Open Windows Explorer and navigate to C:\Workspaces\pete

    b. Confirm that on the filesystem Pete’s workspace folder contains new folders - one for the stream and another for the component – and the SysML Handset Rhapsody project is also present

    6. Import Preferences:

    a. Switch back to the RTC client

    b. From the menu, select File  Import

    c. In the filter box, type pref

    d. Select the General  Preferences entry in the tree:

  • Lab 2: Editing a Rhapsody Model in RMM

    © Copyright IBM Corp. 2018 2 - 9

    Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

    e. Click Next

    f. Click Browse:

    g. In the left-hand panel, select Desktop

    h. Select the RMMPrefs.epf file as shown below:

    i. Click Open

    j. Click Finish:

  • Rhapsody Model Manager Tech Jam

    2 - 10 © Copyright IBM Corp. 2018

Search related