lao%20Application%20Developer%20with%20Rational ...The case study is done using WSAD4.02 with...

file:///C|/Documents%20and%20Settings/avaughan/Desktop/getstart/la...o%20Application%20Developer%20with%20Rational%20ClearCase%20LT.htm

A Case Study of Using IBM WebSphere Studio Application Developer with Rational ClearCase LTBy Ying Zhao and Leying Zhu

The following case study shows a typical scenario for developing Java applications using WebSphere Studio Application Developer (WSAD) with the ClearCase LT plug-in. You will see how team development is empowered by using the ClearCase Unified Change Management (UCM) tools. The same steps also apply to J2EE project development, because after the WSAD project is moved into ClearCase, J2EE files are treated as resources in the software configuration management (SCM) system. ClearCase uses a .cc_meta file to save the identification of the project (for example, whether it's a Java project, Web project, or EJB project). The case study is done using WSAD4.02 with Rational ClearCase 4.2.The screens will be a bit different if you are using the later version but all the steps still apply.

The presented case consists of the following six phases which cover a team development cycle:

1. The project manager sets up a UCM project with a predefined baseline and policies. 2. Developer A joins the project and delivers work to the integration stream. 3. The project integrator makes the baseline for the new version of the project to make it available to

other developers. 4. Developer B joins the project, tests and modifies the project, and delivers the new project version

to the integration stream. 5. The integrator makes another baseline, setting it as the recommended baseline and changing its

promotion level to reflect the quality and stability of the project. 6. Developers bring the new version of the project into their workspaces.

Manager Sets Up Versioned Object Base (VOB) and Unified Change Management (UCM) Project

The development cycle starts with the project manager creating a UCM project. The UCM project should be created on top of an existing Versioned Object Base (VOB), which is the area where all the elements, such as files, directories, and metadata, are stored.

1. Create a VOB

file:///C|/Documents%20and%20Settings/avaughan...veloper%20with%20Rational%20ClearCase%20LT.htm (1 of 21) [4/8/2004 5:04:52 PM]


● From the Start menu, select Programs > Rational ClearCase LT Server > Create VOB. ● Enter "CcTestVOB" for the name of the VOB and "For CC Demo" in the comment field. ● Check the "Create as a VOB level component checkbox ● Click Finish. ● When the confirmation window pops up, click OK. ClearCase will then create the VOB. ● At the end of the process, an information summary window pops up. Click Close to dismiss this

window.

A new VOB has been created. The project manager is ready to build a UCM project on top of it.

2. Create a UCM Project

● From the Start menu, select Programs > Rational ClearCase LT Server > Rational ClearCase LT Project Explorer. Alternatively, you can perform the following steps from WSAD to achieve the same purpose.

❍ From WSAD menu, select ClearCase > Run ClearCase Explorer. ❍ After ClearCase Explorer shows up, select UCM tab on the left pane. ❍ Select Project Explorer after UCM pane is shown.

● From the Project Explorer menu, select File > New > Project. A window entitled New Project — Step 1 pops up.

● Enter "CcTestProject" as the project title and "A project for CC demo" for the description. ● Click Next. ● In the Step 2 window, choose No since you are creating a new project from scratch. ● Click Next. ● In the Step 3 window, click Add to set the initial component baseline for the project. An Add

Baseline window pops up. ● Select "CcTestVOB" as the component from the drop-down list and select

"CcTestVOB_INITIAL" under Baselines. The Promotion Level is always set to "INITIAL" when the project is newly created. Also leave "Allow project to modify the component" checked.

● Click OK.

A component baseline has been successfully added to the project. The result should look like the figure below.



Figure 1: A listing of component baselines

● Click Next ● In the Step 4 window, accept all the default values as shown in the figure below.



Figure 2: Accept all of the default values

● Click Next. ● In the Step 5 window, choose No since you are not using ClearQuest. ● Click Finish

A confirmation window should appear. Click OK to dismiss it. ClearCase then creates the UCM project called "CcTestProject".

NOTE: in ClearCase 5.0, you would have the chance to create UCM projects with read-only VOBs.

The following figure of the Project Explorer shows a new project named "CcTestProject" has been created. There is no development stream yet since a developer stream is created only after a developer joins the project.



Figure 3: What your new project should look like

Developer A Starts Project Development and Delivers Work to ClearCase

To use the UCM tools, the project manager must create a UCM project. Then developers can move the projects created on their workbenches into the UCM project.

Before being able to access team project resources and share work with other team members, a developer has to join the UCM project. ClearCase creates an individual development stream as the developer's own work area. Most interactions between ClearCase and the developer are done through the individual development stream.

1. Join a ClearCase Project

● From the Start menu, select Programs > Rational ClearCase LT Server > Rational ClearCase LT



Project Explorer. ● In Project Explorer, click ToolBox > UCM > Join Project button. The Join Project window pops

up. ● Select "CcTestProject."

NOTE: The previous steps can also be done inside WSAD as following:

● From WSAD menu, select ClearCase > Create New View... ● Click Yes for the radio button to indicate working on a ClearCase project. ● Expand the projects folder and select CcTestProject. ● Click Next. ● In the Create a Development Stream window, the default development stream name is

<hostname>_CcTestProject. You want the corresponding view to be created on the server, so click Advanced Options.

● In the Choose Location for a Snapshot View window, the root of the development view should be <server_views_directory>\<hostname>_CcTestProject, similar to what appears in the figure below. (J: is a network drive that has been mapped to the ClearCase views directory on the server.)



Figure 4: Configuring the root of the development view

● Click Next. ● Correspondingly, in the Create an Integration Stream window, the default name for the

integration stream is <hostname>_CcTestProject_integration. The root of the integration view should be <server_views_directory>\<hostname>_CcTestProject_integration.

● Click Next. ● In the Choose Components window, leave CcTestVOB checked. ● Click Finish. ● The confirmation window comes up as shown in the figure below. Click OK. A development

stream and the corresponding development and integration views are created.

Figure 5: Clicking OK creates the development and integration view, and

developer A will have joined the project

Developer A has joined the UCM project and can start work on a Java project in WSAD.

2. Create a Java Project in WebSphere Studio Application Developer (WSAD)

● Choose the desired directory for the workspace (for example, D:\workspace).

NOTE: To avoid confusion in a parallel development environment (where even an individual developer can work on multiple streams and/or multiple views) the workspace created with the -data switch should have a name that corresponds to the name of the ClearCase view with which it is to be associated.

● From the command prompt, enter the following command to start WSAD with a new workspace:



wsappdev.exe -data D:\workspace

(Use the directory you have chosen if different from the above example of D:\workspace.)

● Create a Java project called JavaDemoProject in WSAD. The project created by the developer is shown in the figure below.

NOTE: You can also create this project directly in the ClearCase View directory where you want the project to reside, not in the default directory offered by WSAD. Then you would select the "Add to Source Control" menu item.

Figure 6: The project in WSAD

The developer can now add this project to source control using ClearCase.

3. Move Work to the Development Stream

● Connect to ClearCase from the WSAD workbench by selecting ClearCase > Connect to Rational ClearCase.

● From the WSAD workbench, right click JavaDemoProject and select ClearCase > Move Project Into ClearCase

● Select the location to move the project to. In the example, the project should be moved to <server_views_directory>\<hostname>_CcTestProject\CcTestVOB as shown in the figure below.



Figure 7: Choosing the destination for moved files

● Click OK. ● The Add Element(s) to Source Control window comes up. Uncheck the Keep checked out option. ● Click OK. ● When the Select Activity window pops up, click New ● Enter "initial_demo" in the New Activity window. ● Click OK to record the new activity on the project. ● In the Project Explorer, select View > Refresh to refresh views. This step is only necessary if

ClearCase LT or the snapshot view is used.

Once the developer is ready to share the project work, it must be added to the integration stream.

4. Deliver Work to the Integration Stream

● Make sure that all files under source control are checked in and not hijacked. A Hijacked file is a version of a file in a snapshot view that is modified but not checked out. Files may be hijacked for the convenience of working offline.

● From the WSAD workbench menu, select ClearCase > Deliver Stream, or from the Project Explorer, right click the development stream and select Deliver from Stream



● In the Deliver from Stream Preview window, accept the default as shown in the figure below.

Figure 8: Again, accept all the program's defaults

● Click OK. ● The Delivering to View window pops up and shows the delivery progress. ● When the Merges Complete window pops up, click OK. ● Dismiss the ClearCase Explorer window if it pops up. ● In the Delivering to View window, click Complete to finish the deliver process. The final

window, as shown in the figure below, shows that the deliver operation succeeded.

file:///C|/Documents%20and%20Settings/avaugha...eloper%20with%20Rational%20ClearCase%20LT.htm (10 of 21) [4/8/2004 5:04:52 PM]


Figure 9: A successful delivery operation

A successful deliver operation ensures that the new development work has been merged into the integration stream.

Project Integrator Creates New Baseline

From time to time, the project integrator needs to consolidate the team's work and approve it for sharing, either for testing or for developers to synchronize to their work areas. In the example, the integrator finds out that a new version of the project has been delivered by developer A and wants to make it available to the rest of the team. The task is accomplished using the Make Baseline operation.

Make New Baseline

● In the Project Explorer, select View > Refresh to refresh views if the ClearCase LT snapshot view is being used.

● Lock the integration stream to prevent developers from delivering their work during the process.



To do this, in the Project Explorer, right click CcTestProject > Integration and select Properties > Lock > Locked.

● To make a new baseline, in project explorer, right click CcTestProject > Integration and select Make Baseline

● The values are set in the Make Baseline window as shown in the figure below. The default baseline title is CcTestProject_<date>.

Figure 10: Creating a baseline in ClearCase

● Click OK. ● After the baseline has been created, click Close to close the Make Baseline window. ● Unlock the integration stream by right clicking CcTestProject > Integration and selecting

Properties > Lock > Unlocked.

By making a new baseline, the project integrator makes the work delivered by developer A available to other team members.

Developer B Tests and Modifies the Project

Now that developer A's work is accessible to the whole team, developer B will test the project. Developer B must first join the project.



1. Join the ClearCase Project and Add the Project to Workspace

The processes for joining the ClearCase project and adding the project to a new workspace are similar to those outlined previously for developer A. The only exception is that, following the example, CcTestProject_2 is used instead of CcTestProject in developer B's development stream name and location. The project location should appear as shown in the figure below.

Figure 11: Locating the correct directory

Once JavaDemoProject is added to the workspace, developer B can work on the project.

2. Test and Modify the Project

● Developer B has to check out the project file before working on it. Do this by right clicking the JavaDemo.java file and selecting Check Out

● When the Check Out Element(s) window comes up, click OK. ● In the Select Activity window, create a new activity by entering "test_demo" to indicate a new

version of the project. ● Click OK to complete the checkout operation. ● Modify the Java class in the file as shown in the figure below.



Figure 12: Making modifications to the Java class

● The green icon on the left side of JavaDemo.java shows that the file is checked out. It has to be checked back in before the Deliver Stream action can be performed. Do this by right clicking the JavaDemo.java file and selecting Check In

● In the Check In Element(s) window, uncheck the Keep checked out box. ● Click OK.

Once developer B has checked the file back in, the changed project must be added to the integration stream.

3. Deliver Work to the Integration Stream

The process for delivering work to the integration stream is similar to that outlined previously for developer A.

The Deliver from Stream Preview window should look like the figure below, showing the name of the new project version to be integrated.



Figure 13: Developer B checks work in to the development stream

Once the process is completed, the final window shows that the deliver operation succeeded, as shown in the figure below.

Figure 14: ClearCase will notify you when delivery is complete


http://www.rational.net/main/cata.html?USE_CASE=viewcontent&SERVICE_NAME=Vignette&SERVICE_SPECIFIC_ID=2222&RESOURCE_ID=227246#


A successful deliver operation ensures that developer B's changes have been merged into the integration stream.

Integrator Makes the New Version the Recommended Baseline

After developer B tests, modifies, and delivers work into the integration stream, a newer version of the project is created. Since the new version of the project has been tested, the project integrator may want to offer it to the whole team as the recommended baseline.

1. Make New Baseline, Promote Baseline, and Change Recommended Baseline

● Follow the steps previously outlined to make a new baseline. ● After the new baseline is created, right click CcTestProject > Integration and select Properties.

The Integration Properties window pops up. ● Click the Baselines tab. ● Select the baseline to promote and click Properties. The Properties window pops up. ● Change the Promotion level to TESTED as shown in the figure below.



Figure 15: Promoting the status of a project

● Click OK to confirm the change.

In the Integration Properties window, the promotion level of baseline has been changed to TESTED, as shown in the figure below. The asterisk to the left means the baseline is the recommended baseline, in this case the newest baseline created.



Figure 16: Note that the Promotion Level now indicates that the project has been tested

The integrator may want to use this tested version as the code base for the team, even if other developers deliver new work and new baselines are been created. To do this, the integrator must change the baseline promotion policy.

2. Change Baseline Promotion Policy

● Right click CcTestProject in the Project Explorer and select Properties. The Properties window will pop up.

● Click the Policy tab. ● Change the value for the project promotion level to TESTED, as shown in the figure below.



Figure 17: Make sure you set the new promotion policy to reflect the promoted project

● Click OK.

By changing the baseline promotion policy to TESTED, only a baseline promoted to TESTED will serve as the recommended baseline. Since all new baselines start with the INITIAL promotion level, any new baselines that are created will not be recommended unless promoted.

NOTE: If the Integrator was already attached to the project when the developer delivered his changes, the integrator would have to do a WSAD refresh to see the new changes that the Developer made. The same steps should be applied if file changes are made outside of WSAD.



Developers Rebase Stream

After the integrator sets the new version of the project as the recommended baseline, it is up to the developers to synchronize their development streams with the integration stream. Then they need to populate the project on their workbenches with the new version to continue working with the new code base.

Following the example, developer A does not have the latest changes to the project and should perform the Rebase Stream operation.

Rebase Stream

● On the WSAD workbench menu, select ClearCase > Rebase Stream The Rebase Stream Preview window pops up, as shown in the figure below.

Figure 18: The Rebase Stream Preview window

● Click OK. ● When the Merges Complete window pops up, click OK. ● In the Rebasing in View window, as shown in the figure below, click Complete.



Figure 19: The Rebasing in View window

● When focus is switched to the WSAD workbench, a File changed window pops up. You will be asked: "The file has been changed on the file system. Do you want to load the changes?" Click Yes to load the change to the workbench. JavaDemo.java is then successfully changed on developer A's workbench. The developer can continue working with the new code base.

End of Cycle

This ends the demonstration of a full team development cycle using WebSphere Studio Application Developer and ClearCase LT. WSAD version 4.0 and ClearCase version 4.2 (2001A.04.00) were used for the case study. Even though in the case study, views are stored in the server, you can also use other machines to store the view content. This test has also been run with WSAD version 4.02, but no change has been made in the plug-in API. Depending on the ClearCase version being used, interfaces may be slightly different from the figures provided.


lao%20Application%20Developer%20with%20Rational ...The case study is done using WSAD4.02 with...

Documents

Transcript of lao%20Application%20Developer%20with%20Rational ...The case study is done using WSAD4.02 with...