Tutorial: Exploring the Engineering Workflow Management JUnit example project

To create the JUnit example project, you must have JazzAdmin permissions and be assigned a Developer Client Access License.

The JUnit example project includes eight users. You can log in to the JUnit project as any of these team members to get different perspectives on roles and assignments. However, to fully explore the JUnit project as one of these users, the user must be assigned a Developer Client Access License. The number of licenses you can assign for this example is limited by the number of licenses remaining on your server.

1. Log in to the JUnit project area as a user who has administrator privileges (ADMIN/ADMIN on a new server installation).
2. In the Team Organization view (Window > Show View > Team Organization), in the upper-right corner, click the View Menu icon; then click Show Users.
3. Right-click Markus Kent; then click Open.
4. In the User editor under Client Access Licenses, select Engineering Workflow Management - Developer and click Save.

Results

The Team Organization view only shows the users who are part of the JUnit project. To assign client access licenses for other users, use the Jazz® Team Server web interface: navigate to Administration > Manage Users. The Active Users interface appears; use it to manage user accounts and licenses. This interface lists all users on the server:

Tip:

To log in as a different user, modify the properties of your repository connection and specify a different user ID:

The JUnit project uses the scrum process. The scrum process is an approach to managing projects in an agile way. For each iteration, called a sprint, the team has created a plan document, and has defined work items for that sprint iteration.

1. You can see the Process sprints by opening the JUnit project in the Project Area editor:
   Note: Plans can be accessed in the Engineering Workflow Management application's web interface from the Plans menu on the action bar.
   
2. To examine the iteration plans, from the Team Artifacts view, open a plan:
   

   Tip: Plans open in the web client only. You can choose to open plans in an internal or external browser by setting the web browser preferences in Eclipse client. For more information, see Web Browser preferences in the Eclipse documentation.
3. Look at the JUnit 4.4 s2 Sprint Backlog plan. On the Planned Items tab, the Plan Details section has a view that gives you an inline work item editor that shows planning attributes.
   

   Tip: From the Planned Items tab, you can quickly change certain attributes of work items by clicking on one of those work item's attributes.
4. To see the details of a work item, from the Planned Items page, click the item. It opens in the work item editor, where you can make changes, depending on your role and the process configuration.

   For example, if you are logged in as JUnit project member Markus Kent, try using the Discussion section to add a comment to the work item:

   

The JUnit files are under source control in the Engineering Workflow Management repository. Markus and other project members (to whom you assigned a Developer Client Access License) are able to deliver changes to the stream.

About this task

In the Team Artifacts view, you can see that the JUnit project includes a single source control stream called JUnit. The stream includes a single component, also called JUnit. In the following screen capture, the JUnit component is at the initial baseline.

The current user loads a repository workspace called JUnit. You can search for other user repository workspaces, then duplicate and load them; or you can create your own repository workspace.

When a repository workspace is loaded, the projects that are part of the loaded components are available for you to work on within your development environment. In the JUnit component, there are two projects:

Learn more about Jazz source control: After you have explored a bit, you might want to learn more about some of the Jazz source control concepts and tasks.

Read the Overview of Engineering Workflow Management source control section to learn more about streams, components, repository workspaces, and other concepts.

Experiment by making a change to a file (note that there is no source code in this example project) and delivering that change in the Pending Changes view. You can associate your change with a related work item.

The JUnit project includes one build definition and one build engine. To explore and experiment with the JUnit builds, you must set up and start a build engine using the separately installed build toolkit.

1. From a command line, navigate to installdir/buildsystem/buildengine/eclipse, where installdir is the installation directory.
2. Enter the following command:

   jbe -repository https://hostname.example.com:9443/ccm -userId bill -pass bill -engineId junit -sleeptime 5

   where hostname.example.com is the path to your repository URL.

   When you successfully start the engine with the build toolkit, it waits for build requests. Only build definitions that are defined to run on this particular build engine are supported.

   
3. Request a junit build:
   
4. When the build has completed, from the Builds view, open the build results. View the Overview, Compilation, and JUnit tabs of the build result to learn about the types of information that you can view from a build result.
5. Optional: To schedule the junit build to automatically run every 30 minutes:
   1. In the Team Artifacts view, right-click the junit build; then click Open Build Definition.
   2. In the Build Definition editor, click the Schedule tab.
   3. Select the Enabled check box.
   4. In the Continuous interval in minutes field, type 30.
   5. Click the Jazz Source Control tab.
   6. At the bottom of the Jazz Source Control page, to ensure that a build runs even if there are no changes since the previous build, clear the Build only if there are changes accepted check box.
   7. Click Save.
   

If you plan to explore the JUnit project in depth, you can use reports to track the progress and monitor the JUnit project areas and teams. However, because reports require historical, aggregated data, the JUnit project does not have any initial data points to start building reports.

1. Ensure that Markus Kent has JazzAdmin permissions, then log in to the Engineering Workflow Management Application Administration web interface as Markus.
   Note: If you gave Markus Kent the JazzAdmin permission, he can assign himself the JazzAdmin permission. Otherwise, you must log in with your own user ID to assign JazzAdmin permission to Markus.
2. On the action bar, click Reports.
3. In the Data Warehouse Collection Jobs section, click Run all data warehouse collection jobs.

Most of this guide has taken you through the Eclipse client. The Engineering Workflow Management web interface also provides a rich environment where you can meet many of the same goals of collaborating with your team.

About this task

To explore the JUnit project area in the web interface:

1. Open a browser to the web interface. If you are running locally, the default URL is the following:

   https://localhost:9443/ccm/web/projects/JUnit Project

2. Navigate through the web interface. For example:
   • On the Work Items page, find, edit, and create work items.
   • On the Source Control page, browse the files in the repository.
   • On the Plans page, create and review project plans.
   • On the Dashboards page, work with team and personal dashboards.
   • On the Builds page, view build definitions and results, and request builds.
   • On the Reports page, create and view project status and progress.