work items, software configuration management, and team...

IBM Software

Work Items, Software Configuration Management, and Team Collaboration Platform for RPG and COBOL Development

Rational Team Concert for Power Systems Software

By Claus Weiss

Advisory Software Consultant IBM Corporation

By Don Yantzi IBM Corporation

March 2010

Rational Team Concert for Power Systems


Table of Contents

Table of Contents INTRODUCTION TO LABS IN THIS TUTORIAL ..................... 6

LAB 1 SETTING UP THE TEAM.........................................................................................7

1.1.1 STARTING THE RDP WORKBENCH.......................................................................................................................... 7

1.1.2 SWITCH TO THE RSE PERSPECTIVE ...................................................................................................................... 8

1.1.3 CREATE A CONNECTION TO THE IBM I SERVER................................................................................................. 10

1.1.4 FIND THE TEAM INVITATION EMAIL ON IBM I IN YOUR TEAM LIBRARY ........................................................... 12

1.1.5 USE THE ACCEPT TEAM INVITATION LINK TO ADD YOURSELF AS A PAYROLL TEAM MEMBER TO RTCP 15

1.2 MEET THE TEAM ..................................................... 20

LAB 2 PLANNING YOUR WORK .....................................................................................21

2.1 WORKING WITH WORK ITEMS............................... 21

2.2 TAKE A TOUR OF THE EXISTING ITERATION PLAN22

2.2.2 CREATE A NEW ENHANCEMENT WORK ITEM TO IMPLEMENT A NEW VIEW OPTION ................................... 25

2.2.3 SPECIFY WORK ITEMS DETAILS............................................................................................................................ 26

2.3 TAKE ANOTHER LOOK THE ITERATION PLAN..... 35

LAB 3 PERFORMING AND SHARING YOUR WORK .....................................................39

3.1 CHANGE THE STATUS OF YOUR WORK ITEM TO ALLOW TRACKING OF YOUR WORK 40

3.2 CREATING YOUR REPOSITORY WORKSPACES FROM THE 1.1 DEV STREAM 42

3.2.1 ENABLE AUTOMATIC CHECK-INS .......................................................................................................................... 42

3.2.2 CREATE YOUR REPOSITORY WORKSPACE FROM THE 1.1 DEV STREAM ...................................................... 42

3.3 SETTING UP YOUR I PROJECT.............................. 47

3.3.1 ASSOCIATE A REMOTE SYSTEM CONNECTION.................................................................................................. 47

3.4 MODIFYING DISPLAY FILE TO ADD VIEW OPTION55

3.4.2 MAKE SOURCE MODIFICATIONS TO ADD VIEW OPTION.................................................................................... 58

3.4.3 COMPILE THE MODIFIED DISPLAY FILE................................................................................................................ 65

3.4.4 MODIFY AND COMPILE THE RPG SOURCE .......................................................................................................... 68

3.4.5 TESTING THE CHANGES......................................................................................................................................... 72

3.4.6 SHORT RECAP OF THIS LAB SO FAR.................................................................................................................... 74

3.4.7 DELIVERING YOUR CHANGED SOURCE CODE AND RESOLVING YOUR WORK ITEM ................................... 75

3.5 RESOLVING THE WORK ITEM................................ 80

3.6 ACCEPTING CHANGES FROM OTHER MEMBERS OF YOUR TEAM 83

3.7 CONCLUSION........................................................... 84

Overview

The RTCp (IBM Rational Team Concert for Power Systems Software) tutorial for the IBM i developers provides a hands-on experience for those needing to understand how developers would work with their source code in the RTCp/RDp environments.

Using Rational Developer for Power Systems Software (RDp) developers can work with RTCp in a controlled team environment.

Introduction

This tutorial demonstrates how an IBM i developer will join a team in RTCp. It introduces the concept of work items to identify the work at hand. Work items are an integral concept of RTCp. They allow project managers to easily get an overview of workloads and project status. Work items also allow developers to annotate the work to be done and keep track of changes in the project. Work items easily help identify who has implemented changes and they can be used to get the status of individual pieces of work at any time during a project.

The developer will pick up the source available at the current level and copy it into a personal workspace. Using RDp and the i projects perspective the changes for an enhancement in the current PAYROLL application will be applied. The changes will be tested and then delivered back to the team so the team has access to the changed source.

The objective of this session is to explore how IBM can help applications development shops control the process of application development on IBM i or in a multi platform environment.

The target of RTCp is any IBM i development shop or multi platform development shop with IBM Power systems.

This tutorial is targeting IBM i developers, and to some degree team leads.

Requirements

You have two choices as to how to run this tutorial for the workstation part:

1. You use RDp installed on your workstation.

2. You use the provided VMware image to run the labs.

For the server you will use the IBM demo IBM i system. You need a valid userid for this IBM i demo system iseriesd.demos.ibm.com. Instructions to obtain a userid for this tutorial are as follows.


First you open a Mozilla Firefox or Internet Explorer session using the icons on our desktop

__a.

__b. Copy and paste in this address: http://iseriesd.demos.ibm.com:59900/getuserid/index.faces

__c. Fill out the form


__d. Press Get UserID button

__e. Write down your Assigned User ID

__f. End your browser session

The userid name will be WLAB<N> and password W<N> (replace <N> with the number assigned to you).


Introduction to Labs in this tutorial

1. In the first lab you will set up your RTCp environment as you join the PAYROLL team.

2. In the second lab you will learn about the concept of work items in RTCp, and create your own work item that your team lead assigned to you. The work that is assigned to you is to implement an enhancement that adds a menu option to an existing display file, and then enable the change in an existing RPG program. (Don't worry. No deep DDS or RPG programming skills are needed). You'll also learn how to use the work item perspective and the work item editor.

3. In the third lab you will implement the enhancement. You will get the current up-to-date source members from the RTCp Jazz repository, and copy them into your personal workspaces. You will switch to the i project perspective and work with the DDS and RPG source. You will push the changed source to an IBM i scratch library and compile and test it. After you tested your enhancement you will deliver the changed source to the Jazz repository so your team members can pick up these changes and work with them. You will also indicate that you finished working on the work item, so everybody in your team knows that this work item is done. This information will be used by your team lead and project manager to monitor the overall project status. The last step in this Lab will guide you thru accepting changed source members from other team members that they have delivered to the Jazz repository and that you need to pick up to do other work.

Enjoy the labs


Lab 1 Setting up the Team

This Lab is assuming that you are an IBM i developer and that you are a new team member of the Payroll project team. You are starting the day and checking your email and find that you got an invitation to join the team. A part of the email contains information on how to join the team using RDp .

You have a quick look at the team organization and then you get ready to start working on your first assignment.

Important! Ensure that you carry out this Lab assuming with the identity of the user you have been assigned. The instructions for all labs will denote WLAB<N>, which you should replace <N> with your assigned id number. Sample screenshots in all labs will the use the id WLAB01. This is the userid for the IBM i system iseriesd.demos.ibm.com.

1.1.1 Starting the RDp workbench

First you start the Rational Developer for Power Systems Software client (RDp)

__1. Start -> All Programs -> IBM Software Delivery Platform -> IBM Rational Developer for Power Systems Software 7.5 -> IBM Rational Developer for Power Systems Software.

__2. In the Workspace Launcher window type C:\Workspaces\WLAB<N> (replacing <N> with your id number). Note: RDp might be configured to open a default workspace, you can select File->Switch Workspace->Other to bring up the Workspace Launcher Dialog box and change the workspace name.

__3. Click OK.


__4. On the Welcome page, you might want to explore this page by reading thru the RTC topics.

__5. On the tab click the X on the tab vthe tab to close the view.

Note: The tabs on Workbench views behave similar to Windows dialog title bars

In the following steps you create a connection to the IBM i server iseriesd, access a file and a member containing the team invitation to the Payroll development team. Normally you would get an email with the team invitation and copy and paste the invitation text to the workbench to create a connection to the RTC repository.

Since we don't have an email account for the Lab students, we are storing the email invitation text in a source file member on the IBM i system. This allows us to mimic the real RTCp environment as close as possible and might save you from typing mistakes.

1.1.2 Switch to the RSE perspective

To create a new IBM i connection, switch to the RSE perspective and then use the Remote Systems view. Here are the steps.

If you are not in the RSE perspective already, the title on the workbench window will tell you.


__1. Switch to the RSE perspective, click on the Open Perspective button, located on the top right corner in the workbench.

__2. Select Remoter Systems Explorer from the drop down.

__3. If Remote Systems Explorer doesn't appear on the menu drop down. Click Other... on the drop down menu and

__a. In the Open Perspective dialog, scroll down until you see the Remote Systems Explorer perspective.

__b. Select it, by double clicking


The Remote Systems Explorer perspective opens and you will see the Remote Systems view on the left side of the workbench.

1.1.3 Create a connection to the IBM i server

In order to work with the IBM i system you will now create a connection that allows you to work with the objects on that system.


__1. Expand the New Connection node in the tree-view and double click on IBM i.

Note: If you don't see a New Connection node, click on the Define a connection icon

__2. In the New Connection dialog, enter iseriesd.demos.ibm.com for Host name and IBM i server connection for Connection name.

__3. Click Finish.


The new IBM i server connection is created and shown in Remote Systems view.

1.1.4 Find the team invitation email on IBM i in your team library

As mentioned before, in a regular RTCp environment with known email addresses, an email with an invitation to join the Payroll team would have been sent to you. You would then copy the email text and use it to set up the RTCp connection from your workbench. In this lab we simulate this email and you will copy the text from a file on the IBM i server.

Note: If you are working in your own server environment, you will not have the file simulating an email on IBM i. In this case please enter the information in the next section of this lab by hand, or copy and paste from this document at that point.

The following steps allow you to find the invitation text and copy it. You will access this file using the Remote Systems Explorer (RSE) in RDp.


__1. Expand the connection node IBM i server connection you just created

__2. Right click on Objects and select action Open Member....

In the Open member dialog

__3. Make sure the correct connection is shown, if not change to the correct connection name.

__4. Browse to or enter library name RTCLAB<N>, <n> is your team number, if you were assigned userid WLAB01, 01 is your team number.

__5. Browse to or enter file name TEAMINFO

__6. Browse to or enter member name NOTE<N> , <N> being your team number.

__7. Select the open for Browse radio button.

__8. Click the OK button


You will be prompted for userid and password

__9. For userid enter WLAB<N>, again <N> being your assigned team number

Note: Use the assigned userid and password to sign on

__10. For password enter W<N>

__11. Make sure that you check to save this information if it is selectable

__12. Click the OK button.

The editor view opens in the workbench.

Copy the highlighted text in the file, as shown in the picture below.


__13. Right click on the highlighted text and select the copy action to copy it to the clipboard. You will paste it into the team invitation panel during the next steps

Note: Make sure you don't copy trailing blanks on the last line of the text.

1.1.5 Use the Accept Team Invitation Link to add yourself as a Payroll team member to RTCp

Now you can use the copied text to set up your workspace to connect as a member of the Payroll team to RTCp. You will use one of the Links in the Team Artifacts view on the Work Item perspective to do this.

To get to the Work Items perspective use the Open Perspective button,

__1. On the workbench menu click the Open Perspectives button

__2. From the drop down menu click Work Items. If Work Items doesn't show in the drop down menu, use the Others action and select Work Items from the list of perspectives


__3. In the Team Artifacts view, click Accept an invitation to join a Jazz™ team area.

__4. In the Accept Team Invitation window, paste the text that you copied before (right click, paste)

The information in the copied text allows Rational Team Concert for Power System Software to connect to the PAYROLL Project and the Team Areas you are a member of. You could enter this information by hand if in case the information didn't arrive by email:

teamRepository=https://<hostname>:<port>/jazz/ userId=WLAB<N> userName=WLAB<N> projectAreaName=PAYROLL teamAreaPath=/PAYROLL Team


Note: If you work on your own server please replace the server information and userid, user name with the correct data for your environment.

__5. Ensure that the values for userId and username match your assigned student id.

__6. Click Finish

__7. If prompted for a login and password:

__a. Type W<N> (replace <N> with your id number) for the Password,

Note: This dialog is case sensitive, make sure this is a capital W.

__b. Select Save password and Automatic login,


__c. and Click OK.


__8. You will be connected to your project and see a screen similar to the following. Ensure that you are connected to the PAYROLL Project area as WLAB<N>.

If you don’t see this view of the workbench, click Open Perspective->Work Items


You have now joined the project. You have access to the team area and artifacts for the teams to which you have been assigned. Note there are tasks in the Work Items view. These are automatically generated by your development process to help you get started.

1.2 Meet the team

Open the Team Organization View

__a. Click Window -> Show View -> (other->Team->) Team Organization ->OK

__1. Expand PAYROLL --> Expand PAYROLL Team.

Here you see all team members for the Payroll team. Notice above the green icon next to the names that are currently connected to an instant messaging server. Jazz can integrate with popular instant messaging servers to allow team members to chat about projects they are working on.

What have you done so far?

You connected to the Jazz server as a team member of the PAYROLL project. This allows you to see who else belongs to the team. It also


enables you to see what tasks have been assigned to yourself and other team members.

Work Items are one of the important concepts in Rational Team Concert (RTC). The next Lab introduces work items and how developers access and modify them.

Lab 2 Planning Your Work

Lab Scenario You want to know what task you and your team members have to work on. All this work (tasks, defects, enhancements) is based around the concept of Work Items. Work Items are fundamental to Rational Team Concert for Power Systems Software and you learn how to use these work items to track the work you do. You prioritize your work so that you can do the right things at the right time in the plan.

In Team Concert for Power Systems Software all the work for enhancements or defects in a project will be planned and tracked using work items. You have the task to add a new feature that implements a view option to an existing application. You will create a new work item, set the priority, estimate how long the work will take and assign the work to the current iteration 1.1 M2. An iteration is a short step in your overall development plan.

Important! For this Lab you are in the role of a developer, use the userid you have obtained before that you used in the previous Lab. The instructions for all labs will denote WLAB<N>, which you should replace <N> with your assigned id number. Sample screenshots in all labs will the use the id WLAB01.

2.1 Working With Work Items In this Lab you will be looking at the iteration plan and see what work items have been created so far for the iteration you will be working in. Work items can be created by the project/team leader, developers or other members of the team.

The work item you will implement adds new view option to enhance the current PAYROLL application. You plan to deliver this enhancement in the 1.1 M2 iteration and your estimate to finish this work is one day.


__1. Ensure that you are using the Work Items perspective (it should be open by default). It will be visible on the top right-hand corner of Team Concert for i

__2. If the Work Items perspective is not open, click the open perspective button and select Work Items

2.2 First look at the Team Artifacts view

The Team Artifacts view shows a list of artifacts or items that are related to your project. Depending on the setup of your project structure you see different high level areas in the project. The way this project is set up you see the following categories: Builds, Plans, Reports, Source Control, and Work Items. You will later have a brief look into the plan for the current iteration of the project.

You are going to implement a new view option to the PAYROLL application. Two work item related to this task already exists that have been created by the teamleader. Later you will look at the work items related to the Add View Option to Payroll app user interface in the list of work items. This is the parent work item to your task. Your View Project Master File WLAB<nn> Implementation item will be a child of the Add View Option work item.


2.2.1 Create a new Enhancement work item to implement a new View Option

__1. Select the Team Artifacts tab


__3. Expand the PAYROLL project

__4. Right click the Work items folder then select New->Work Item.

__5. Select Work item type Enhancement and click Finish

2.2.2 Specify work Items details

The Work Item editor contains the new enhancement with default values. You will now specify the detailed information for this work item:


In the work item editor you specify the detailed information for this new work item.

A short summary of the work item:

__1. Type: View Project Master File WLAB<N> Implementation in the Summary (replace WLAB<N> with your student id)

A detailed description of the work item:

__6. Type: Implement the view project master file option in the Description.

Several pieces of information are already filled in, you could change the severity to a different level, your userid has been applied to the Created by field, and the information about the team area. If you want more information about the team and the PAYROLL project, click on the links provided for the team area.

You have to identify the category this work item belongs to;(heading: Filed Against) These categories could be for example GUI, business logic, documentation, Build. In this Lab it is the File Maintenance category in the Time Reporting System (TRS).


__7. Set Filed Against to PAYROLL/TRS/File Maintenance

Since you will be working on this enhancement and have the responsibility to deliver it in this iteration it is owned by you.

__8. Set Owned By to WLAB<N>

The priority, the iteration you plan to deliver this work item in, and the estimated duration of this activity can be set in this panel as well.

In this development shop the way the planning works is as follows:

• The team leader creates the high level tasks for the project. You will see how to link your work items to these high level tasks in a moment.

• The developer creates the low level work items for the task he is assigned to. In this Lab we just have one work item.

Creation of low level work items for a project could also be done by the development lead. The development lead would fill in some of the required detail data and you as a developer would then pick up the work item and fill in the remaining details. There is a lot of flexibility built into RTCp to accommodate your particular requirements.

__9. Set Priority to Medium

__10. Set Planned For to ->1.1 M2 (may have to choose More to find)

__11. Type 1 day in the Estimate entry field

__12. Click Save in the top right corner of the Work Item editor view.

Your enhancement request should look similar to this:


Now you associate your enhancement with the tasks (high level work items) set by the Team Lead. This will allow the project manager to understand what high level tasks are being worked on and who has been assigned to what tasks. This kind of information is needed to keep the project under control and to be able to understand workloads of developers. As changes occur during the project it allows Team Leads to see bottle necks and if necessary re-assign tasks.


__13. Click on the Links tab of the Enhancement request in the work item editor


__14. Click the Add button in the Links area of the Enhancement work item and select Set parent…


__15. This will open up the Select Work Item dialog that will be used to create a link to a parent task.


You use the Select Work Item dialog to find the parent task your team leader has already created to build the association between this high level task and the work item that implements it. There might be other work items linked to the parent like testing this enhancement. The person performing the test would create a work item and also link it to this parent.

For this Lab the Team Lead has created the high level work item Add View Option .

__16. Deselect Show my assignments only to allow you to search across all work items, not just your own.

__17. Enter add view option in the Containing id or text: field to find the parent work item the Team Lead created.

__18. Select Add View Option task,

__19. Click OK to set this task as the parent of your new enhancement

You can now see this link on the Links page of the work item editor


__20. Click Save to save your work item for implementing this enhancement.


Let’s take a look at the iteration plan for the 1.1 M2 iteration. Remember iterations are short time frames (one to four weeks) that the team will use to implement a complete set of sub functions. For example you might create, review and test the user interface for a new application in one iteration. Then in the next iteration or multiple iterations the team adds the logic behind the UI and again in each iteration fully tests the items added. The team also checks with the stakeholders at the end of each iteration to make sure that the implementation so far fits their needs. During an iteration the team works thru a full development cycle. (From planning, design, etc. to a working product).

2.3 Take a look at the iteration plan

Now have brief look into the plan for the current iteration of the project. To view your work item in the iteration plan:

__1. Select PAYROLL->Plans->1.1 M2 [Main Development Line]->M2 Iteration Plan (1.1 M2).

__2. Double-click to open the M2 Iteration Plan.

__3. Select the Planned Items tab.

__4. Select the Team Folders radio button in the View as area on the right side of the workbench

__21. In M2 Iteration Plan editor, expand the Add view option to Payroll app user interface and Add New View Option work items

__5.


You will see your task (like View Project Master File WLAB01 Implementation task in the screenshot).

You may also see other tasks from the other students, you might have to scroll down to see your work item.

2.4 Working with the configuration wizard

You can work with the configuration wizard for iteration plans, in case you are wondering how to configure an iteration plan. It allows you to determine which projects, teams, and iterations are part of a specific plan,

Have a look at the configuration wizard before you start doing some real development work.


__1. On the M2 Iteration Plan title in the plan editor, right click the menu icon

__2. Select Configure Plan… to open the selection criteria for the plan

Note the selection criteria for the plan: the Project Area, the Team Area and the Iteration. This controls what work items appear in the plan, and why your work items appear in this particular plan.


__3. Click Cancel to dismiss this dialog

2.4.2

You have now completed this section.

Conclusion

This concludes Lab 2. You now know how work items are created. Work items are part of plans and they are an integral part of RTCp. You will now use the new work item you created in this Lab and start working on your assignment.


Lab 3 Performing and Sharing Your Work

In this lab you will learn how to work with the source related to the enhancement that you have to implement.

You are working with artifacts that are stored in the Jazz repository. This is different than working with source files on the IBM i system. You will go thru a couple of steps to get the source files to your workstation from the repository. 1. The source you work with in your assignment is stored in the Jazz repository. It is stored in a stream.

A stream is a set of your source code used in a project by all team members. Instead of working with native libraries and accessing source members in these libraries directly, you now always retrieve the source you work with from the repository. Streams in the Jazz repository contain all the artifacts (files) for your development shop. Development projects have associated streams. You can define multiple streams. Each stream is snapshot of your development assets. For example you could have created a stream for Release 1 of a product that contains every artifact making up your product at the Release 1 level. This will allow you to always go back and compare an artifact at a current level with any previous level. In this Lab you are dealing with four streams for the PAYROLL application that we have already set up: a) The Baseline 1.0, that reflects the state of the source files when they got added to the repository

b) The Development stream 1.1, that contains artifacts (source files) that belong to the 1.1 release of the application with all changes applied to the source by the development team

c) The QA team has its own stream. It is based on the development stream but allows the QA team members to control the level of changes they work with.

d) The System test team has its own stream to control the changes they work with.

In this Lab you will use the 1.1 development stream to get your initial source members from and to deliver your changes to. Other team members can then work with them by getting them from the stream.

You will copy the artifacts from the stream into your own repository workspace, which is located on the IBM i server. A copy of the content of the repository workspace is also created in your local workspace on your workstation

2. You work with the files in this workspace using the i Projects perspective. This perspective lets you work with the LPEX editor to make the required changes to the source. You can check in your changes into the repository workspace and use it as a backup for your local work.

3. You use the remote options to compile the source into IBM i objects. In this Lab that is a compile of the display file DDS and a compile of an RPG program.

4. You test your changes using an emulation window,

5. After completing your tests and the removal of defects that you might have introduced, you check in your source and deliver it to the stream. Now other developers can pick up your changes from the stream. In this part of the Lab you will also be introduced to the concept of change sets. They are a collection of related changes to make it easy to work with a set of changes instead of separate single changes.

Here are some terms that are used in Jazz and their definition.


Some Jazz Terms Defined:

Project Area

The project area is the system's representation of a software project. The project area provides definition for the project deliverables, team structure, process, and schedule. Team Area

The structure of the project teams is defined by one or more team areas. A team area serves these functions:

• Defines the users (team members) on the team and specifies their roles.

• Defines the development line in which the team is participating.

• Customizes the project process for the team.

Streams and Components

A stream is a repository object that includes one or more components. A component is a collection of related artifacts, such as an Eclipse plug-in or a group of documents that comprise Web site content.

Change Set

A change set is a repository object that collects a related group of changes so that they can be applied to a flow target (workspace or stream) in a single operation.

The change set is the fundamental unit of change in Jazz source control. The contents of any workspace, component, or stream can be expressed as a collection of change sets, beginning with the one created when the initial set of projects was checked in. A change set can include changes to the contents of individual files and changes to a component namespace (such as delete, rename, and move operations).

3.1 Change the status of your work item to allow tracking of your work

__1. Click the Work Items tab, at the center bottom part of the workbench

__22. Press the Refresh button to populate the view


To indicate that you are starting to work on this item you will change the work item status. Now other team members, the team leader, or project manager will be able to see the changed status and work with this information without the need for you to explicitly update them.

__23. Right click on your work item and select Start working


3.2 Creating your repository workspaces from the 1.1 Dev stream

3.2.1 Enable automatic check-ins

Once a change is made to a versioned file, its corresponding change-set must be checked in to commit the change to your repository workspace. By default, check-ins must be initiated by the user. However, Rational Team Concert provides the option for making check-ins occur automatically. You will enable this feature now to simplify the steps in the workshop.

__1. Select Window -> Preferences to open the Preferences settings.

__24. Expand Team -> Jazz Source Control and select Check-in Policies

__25. Check Auto check-in local changes

__26. OK

3.2.2 Create your Repository Workspace from the 1.1 Dev stream

Remember you will now get the source from the stream in the Team Repository and copy it into your Personal Repository Workspace on the server.


__1. In the Team Artifacts view (Window -> Show View -> Team ->Team Artifacts), ensure that you are connected to the PAYROLL Project area as WLAB<N>

__a. Expand the PAYROLL project area and then expand Source Control, to show the 1.1 Dev (PAYROLL Team) stream.

__b. Right click the 1.1 Dev stream and select New -> Repository Workspace….

__27. In the New Repository Workspace window modify the Repository Workspace name to reflect your identity. For example type 1.1 Dev(Payroll Team) WLAB<N> Workspace. Click


Next.

Now make sure the correct component is selected and specify to also directly load the source into your local workspace:

__28. Click Next > on the Read Access Permission dialog


__29. On the Components to Add window verify that the PAYROLL component is selected (Initial Baseline number may differ from picture).

__30. Check Load repository workspace after creation. Click Finish.

__31. On the Load Repository Workspace window, select Find and load Eclipse projects

__32. Click Finish.


Loaded Workspaces Loaded repository workspaces are special in that whenever you change a loaded file or folder in your Eclipse workspace, the changes are tracked and shown in the Pending Changes view. Here you can manage your changes and perform common tasks such as:

* Check-in changes to your repository workspace.

* Organize changes into change-sets.

* Undo changes you've made.

* Associate change-sets with work items.

Your repository workspace should now be visible under My Repository Workspaces in the Team Artifacts view.


You now have a loaded workspace and are ready to begin work that has been assigned to you in the IBM i Project perspective

Some Jazz terms reviewed You use a personal Repository Workspace to work on project files under Source Control. You Load the repository workspace to copy the files and folders into your local workspace (Eclipse) on your computer.

Jazz tracks all changes made to source-controlled files with Change-Sets. Each change-set itemizes the changes to one or more individual files or folders, carries a comment, and references the relevant work item motivating the changes. You Check-in your change-sets to upload copies of the modified files from your local workspace to the repository workspace.

3.3 Setting up your i Project

3.3.1 Associate a Remote System connection

The IBM i Projects need to be associated with an RSE connection that allows you to download objects to


the IBM i system, and for example, compile and test changes you worked on. In these steps you will associate with the RSE connection that you created earlier in this tutorial.

The Payroll TRS File Maintenance project and its artifacts should be loaded in your local workspace and are visible in the i Project Navigator view

__1. Switch to the i Projects perspective, go to Window-> Open Perspective -> i Projects or Open Perspective Other...

You should see a red x mark beside your Payroll TRS File Maintenance project in the i Project Navigator view. This indicates an error, because the project needs to be associated with a Remote Systems Explorer (RSE) connection and IBM i library.

The associated RSE connection needs to be setup for your project so the properties list for this connection are set correct. In your case you need to set library list for this project.

Since the RSE view allows setting up the connection you will use it to adjust the library list. The Remote Systems view is located underneath the Project Navigator view.


__33. Expand your connection node and navigate to IBM i server connection -> Objects -> Library list.

Library List When you compile from your i Project, it uses the library list from the associated Remote System Explorer Connection.

__34. Double click on the Library list node to expand it.

You might be prompted to enter your User ID and Password to connect to IBM i if the connection has been disconnected in the meantime and you haven't saved this information.


__35. If the Enter password dialog appears, enter WLAB<N> for User ID and W<N> for Password and click OK.

__36. Look through the library names showing up in your Library list.

If your environment is setup correctly you should not have libraries starting with RTC in the library list.

Like in the picture below.


You need to setup your RSE job on the IBM i to be able to test the changes that you apply to the Time Reporting System in the Payroll application. You have to add two libraries to the library list.

1. The application library RTCLABxx containing all the files and programs needed for the application. It needs to be added to the end of the library list, so when you compile the changed display file and program, the compilers pick up the correct external descriptions.

2. Your scratch library RTCLAB<N> that will contain the changed source and the new display file and program object. It has to be added to the start of the library list.

To add the scratch library to the library list:


__37. Right click on Library list and select Add Library List Entry...


__38. Enter RTCLAB<N> into Additional library ,

__39. make sure Start of list is selected

__40. Click OK.

To add the application library to the library list::


__41. Right click on Library list and select Add Library List Entry...

__42. Library RTCLABXX should be added to your Library list

__43. Select End of list

__44. Click OK.

The library list should now look similar to the one in the figure below

To associate the scratch library with your i Project, so it will act as the target library for all remote


commands issued from the project, go thru the following steps.

__45. Right click on Payroll TRS File Maintenance project in the i Project Navigator view and click on Properties

__46. In the Properties for Payroll TRS File Maintenance dialog, click on i Project page on the left.

__47. Select IBM i server connection from the Connection drop-down box

__48. Enter RTCLAB<N> into Associated library

__49. Click OK.


You should see the red x mark gone from the Payroll TRS File Maintenance project in the i Project Navigator view.

You have setup your connection to the IBM i server and your development environment. You are ready to start working on your enhancement for the Payroll TRS File Maintenance project.

3.4 Modifying display file to add view option

Important! To ensure that the application files you are about to modify inside your Payroll TRS File Maintenance i Project don’t conflict with other files modified by your team members. Please make sure that you are modifying only those files that


have your student id appended at the end (Ex. MSTDSP_<N>.DSPF)

First run the original Payroll application to see what is involved in the planned enhancement.

__1. Double click on the PCOMM emulator icon on the Windows desktop with the IBM i host name iseriesd.demos.ibm.com. This will start an IBM i emulator session.

__50. Sign-on with your WLAB<N> user ID and W<N> password.

__51. On the command line in the emulation window, type addlible rtclab<N> to add this library to the start of your Library list

__52. Press Enter.


__53. Type addlible RTCLABxx *last, to add this library to the end of the library list

__54. Press Enter

__55. Type call payrort_<N> to invoke the Payroll program.

__56. Press Enter to invoke the Payroll application.


__57. Take notice of the three options available in the user interface. You are about to add a fourth option called “View Project Master File”

__58. Hit F3 to exit the program.

After you are done with your modifications and recompile the program in the next section, your Payroll application user interface will look like this.


Leave the emulator open and don’t sign off, you will need it to test the changes to the display file and program.

3.4.1 Make source modifications to add view option

Now you are going to change the source and test your changes


__1. Open the i Project Navigator view (you should already be in the the i Projects perspective, if not you will need to switch to it), go to Window-> Open Perspective -> i Projects).

__59. Expand the Payroll TRS File Maintenance project, then expand the QDDSSRC (source physical file) and find the MSTDSP_<N>.DSPF member.

__60. Right click on the MSTDSP_<N>.DSPF source member and select Open with Screen Designer


__61. MSTDSP_<N>.DSPF source member is opened in the Screen Designer editor.

You should have the SELECT record selected in the Records list on top of the editor. The SELECT record contains the definitions for the Maintenance Selection menu that you are about to change. The Design area shows the layout of the record on 5250 screen.


__62. Click the Select record, if it is not selected already in the Records list,

__63. Make sure the Palette is visible on the right hand side, if not click on the Palette tab.

__64. Select Text Constant from the Constants drawer in the Palette (click on grey triangle to scroll down if it’s not visible in the Constants drawer).

__65. Click under Reason Code Master Maintenance in the Design area of the editor to insert the new text constant.


__66. Click on the constant to edit its label.

__67. Type View Project Master File in the constant’s label.


__68. Select Named Field from the Fields drawer in the Palette.

__69. Click on the left of View Project Master File text constant to insert the new named field.


__70. Open the Properties view for the named field (go to Window -> Show View -> Properties).

__71. Change Name to PRJVIEW and set Length to 1 (see window in lower left of the workbench. Scroll right to find the length field)

__72. Click Ctrl + S to save the modified file.

Note: You could also move the Properties view underneath the Design editor to give it more space to show all property elements. There is also a DDS Designer perspective you could use to work with screen designer, it by default positions the Properties view underneath the Design editor.

You should see the modified file showing up as an outgoing change in the i Project Navigator view. The black arrow pointing right indicates you have changed this member locally in the i Project but have not yet delivered it to the SCM stream to share with your team members.


3.4.2 Compile the modified display file

Before delivering your changes to the stream and sharing them with others, you want to make sure that the changes you have introduced will not cause any errors or build problems.

First you will change the build preference to use the RSE server job instead of sending the compiles to a batch job queue. Then you will use the i projects Remote Actions to compile the display file. The Remote Action will actually first push the changed DDS source to your scratch library RTCLAB<N>, then it will execute the CRTDSPF command and create the new display file in library RTCLAB<N>.

__1. Setup project preferences by modifying Build and Compile options in the workbench Preferences (go to Window -> Preferences ->iProjects ->Build and Compile).

__73. Uncheck Run compiles as batch job option

__74. Select Push selected resources if there are any changes,

__75. Click OK to apply the changes.


__76. In the i Projects Navigator view, expand the Payroll TRS File Maintenance project,

__77. expand QDDSSRC source physical file

__78. Right-click on MSTDSP_<N>.DSPF member.

__79. Select Remote Actions -> Compile -> CRTDSPF menu option.

If you get an error, the error list will come into focus after the compile is completed. You will need to double click on any severity 20 or 30 error. This will bring the source editor panel into focus with the cursor positioned on the line in error. Fix the error, save the source, and compile again until all errors have been eliminated.

To make sure the display file object has been created you can check the scratch library on the IBM i


server that is attached to you project. Follow these steps to check for the display file object.

__80. Check the scratch library in the Remote Systems view for the display file object MSTDSP<N>.

__81. Refresh the library, right click on RTCLAB<N> and click the Refresh action

If the MSTDSP_<N> dspf object does not appear in the library even after refreshing the view, you will need to issue the Remote Action again and check for errors.

3.4.3 Modify and compile the RPG source

As a last step you will modify and compile the RPG source file member, which uses the modified DDS display file.


In the RPG program you have to enable the PRJVIEW input field so the program can invoke the Project Master program that somebody else implemented. Don't worry if you don't know RPG, we have commented out the correct lines of code you only have to remove “*” for the RPG comments.

__1. In the i Projects Navigator view, expand the Payroll TRS File Maintenance project, and expand QRPGLESRC source physical file.

__82. Double click on the PAYRORT_<N>.RPGLE source member.

__83. The source editor is opened for this member

__84. Scroll down to line 67

__85. Blank out the Asterisk '*' after the calc spec 'c' to un-comment the line. This line ensures that the new entry field PRJVIEW is filled with blank when the program starts.

Note: The RPG code is column sensitive don’t use the delete key to remove the Asterisk, make sure the EVAL statement, line up with the EVAL statements above.

__86. Scroll down to line 109

__87. Blank out both Asterisk '*' from line 110 and line 111. These lines will invoke subroutine PRJSUB when the enduser enters an X in field PRJVIEW

Note: The RPG code is column sensitive don’t use the delete key to remove the Asterisk, make sure the WHEN and EXSR statements line up with the EXSR statement above.


__88. Press CRTL+S to save the change

Now you will compile the changed RPG source. As with the DDS compile you use a Remote action in i Projects. The remote action will do a push of the changed source to your scratch library RTCLAB<N> and then the CRTBNDRPG command will be run and the new program object gets created in library RTCLAB<N>.


__89. Select QRPGLESRC ->Payroll_XX.RPGLE ->Remote Actions -> Compile -> CRTBNDRPG menu option.

If you get an error, the error list will come into focus after the compile is completed.

Don't worry about informational or warning messages.

You will need to double click on any severity 20 or 30 error. This will bring the source editor panel into focus with the cursor positioned on the line in error. Fix the error, save the source, and compile again until all errors have been eliminated.


Note: If you encounter problems with the error list, instead of a compiling remote, use the Verify option. On the workbench menu use Source Verify

To make sure the program object has been created you can check the scratch library on the IBM i server that is attached to you project. Follow these steps to check for the display file object.

You might get a severity 0 error don’t worry about this error as long as the program object is created you are good to go ahead.

__90. Check the scratch library in the Remote Systems view for the program object PAYRORT_<N>.

__91. Refresh the library, right click on RTCLAB<N> and click the Refresh action

If the PAYRORT_<N> pgm.rpgle object does not appear in the library even after refreshing the view, you will need to issue the Remote Action again and check for errors.

After you see the display file and program object in your scratch library you're done with your enhancement implementation. You still have to test it to make sure it has the expected functionality.

3.4.4 Testing the changes

You have just compiled the modified RPG and DDS files on the IBM i host. You are now ready to run the updated application again to verify your changes.

Repeat steps in section 1 - (Run the original Payroll application) to run the updated application.


__1. Go to your emulation window, if you didn't sign off in the mean time, the library list is still OK, if you have to sign on again, remember to add RTCLAB<N> to the start and RTCLABXX to the end of the library list.

__92. Enter call payrort_<N>

You will see the changed panel with the added menu option,

__93. Enter an X in View Project Master File <N> to try the new option

__94. Press Enter

You see a new panel which eventually will be completed by another team.


__95. Press F4 to go back to the main panel

__96. Press F3 to leave the application

3.4.5 Short recap of this Lab so far

Let's recap what you have done so far and where the changed source for the display file and program resides.

1. You created an i project in your local workspace

2. You copied the source files of the stream for this iteration into your personal workspace on the IBM i system.

3. You specified to load the content of the repository workspace into your local i project, in order to work with the source and apply the changes

4. You edited and saved the source. The save action for i projects will save the source to your local workstation disk.

5. You specified auto check in for your Jazz source control, which means that any change in your local


workspace will be automatically reflected in the personal repository workspace. This means all changes you have made in i projects are already checked to your repository workspace.

6. You attached a connection and scratch library to your i projects, so you can push your changes to a native library and compile the source with i project remote commands. In the i projects preferences you specified to push the changed selected sources when doing remote compiles. This means the changed source member gets downloaded into the scratch library and then compiled there.

7. You tested the enhancement you applied by running it in the scratch library.

Non of the changed source members and none of the compiled objects are available to your team members. All objects you have changed so far are in your personal workspace, personal repository workspace and scratch library.

The next step will make the changes available to the team.

3.4.6 Delivering your changed source code and resolving your work item

Now you will copy the changed source members from the repository workspace to the integration stream. This task is called deliver.

In this step of the Lab you will deliver your display file and RPG source code to make it accessible to the rest of the team.

You don't have to check your changes into the repository workspace since they have been automatically copied over by RTCp. You can directly go to your repository workspace and deliver your changes to the stream.

Switch back to the Work Items perspective,

__1. Click on the >> button, in the right upper corner of the workbench, to expand the perspective selection

__97. Select Work Items

In the Pending Changes view


__98. To add the view, use these menu items (Window -> Show View -> Other -> Jazz Source Control -> Pending Changes),

Your repository workspace should show outgoing changes (indicated by the icon) for the PAYROLL component.

__99. Expand the tree under your repository workspace name and confirm that you have outgoing changes for your source files.

__100. Right click on Payroll 1.1 Dev repository workspace and select Deliver to send your changes to the 1.1 Dev stream.

If you followed the steps in this Lab so far, this Deliver action will fail, which gives us the chance to introduce the RTC Team Advisor.

Note: RTC will sometimes associate work items with change sets when the work item status gets changed to In Progress. If you don’t get a message: That means the change set has already been associated with a work item. In this case skip the next steps f to k that explain how to use the Team


advisor to fix the problem. You can check in the change set view whether your change set has an association with a work item.

The Team Advisor view which gets automatically added will display a message: Missing work item or comment

If you don't see the Team Advisor view, use (Window -> Show View -> Other -> Team Advisor) to display it

The Team advisor tells you that the changes are not associated with a work item, and it will suggest action to fix this problem.

One of the options in the Team Advisor will help you associate an existing work item or a new work item with your delivery by clicking on one of the Solutions links.

Process enactment and enforcement Though it has not been discussed yet, when a project area is created a Jazz process template is required. When the Payroll project area was created, it was configured to follow the Eclipse Way process which requires a work item or a comment to be included during a deliver operation. It could be changed to require both or either one.


__101. In the Team Advisor view, click the Associate Existing Work Item link.

__102. In the Select Work Items window:

__103. Type your student id WLAB<N> into the Containing id or text field.

__104. The work items assigned to you will appear in the list.

__105. Select the implementation work item and click OK.

Finding work items As you type characters into the Containing id or text field, the list of work items will change to display only those work items that have the typed characters in their Summary. Entering a single space into the Containing id or text field will list all the work items that match the settings of the two check boxes.


__106. Right-click the Missing work item or comment failure message and select Retry “Deliver”.

It should succeed this time. If it does fail for some reason, the Team Advisor view will appear again to remind you of the team’s process rules.

__107. The Pending Changes view should now show no incoming or outgoing changes.


Other change-set operations:

Suspending a change set ( ) There might be times when you need to begin working on a new change set for a given set of items before you are finished with one that is in progress in your workspace. When in this situation, you can suspend the current change set, which removes it from your workspace but preserves it in the repository. The files in a suspended change set revert to the state they were in before the change set started, and the change set itself is moved to a special Suspended folder so that you can resume the work when you are ready.

Discarding a change set ( ) There are two basic scenarios for discarding a change set:

• If you have accepted an incoming change set but decide later that you don't want it in your workspace, you can discard it to undo the accept and return the change set to the component's Incoming folder.

• You can also discard a change set that you created but have not yet delivered. Discarded change sets of this type remain in the repository but are not placed in any special folder. To make it easier to retrieve a discarded change set that does not exist in any other stream or workspace, you can associate it with a work item before you discard it and then accept it from the work item later.

Reversing a change set ( ) If you want to undo the delivery of a change set, you can create a new change set that reverses all the changes in it and then deliver the reversed change set.

You now delivered your enhancements to the stream, other team members can pick up the changes and move them into their personal workspaces to see how your changes work in their specific environment, or complete work that depended on your changes.

Also the Quality assurance team or the build team can now work with your enhancement and use it in


their environments to, for example, test the changes in the overall application environment.

You need to let your team leader and other members of the team know that you have finished this work item.

3.5 Resolving the work item

In RTC you indicate that you finished a work item by moving into a state of resolved/fixed. There are only a couple more steps involved and you will have completed implementing your enhancement.

Resolve your View Project Master File implementation Work Item.

__1. In the My Work view (Window -> Show View -> Other -> Work Items -> My Work), double-click your implementation work item.


__108. In the Overview tab change the Work Item state to Revolved/Fixed.

__109. Optionally, add a comment (you will need to click on the Add Comment/Hide Comment Field link to add the comment).

__110. Save ( ) the Work Item.

Congratulations! You have successfully implemented, and delivered your modifications to add a new View option to the Payroll application user interface. You will now proceed to learn how to accept incoming changes from your team members.


Currently active Work Item The area at the bottom right of the Team Concert window indicates which work item Jazz thinks you are currently working on. Once you have a work item that you are currently working on, any change-sets you create now will automatically be associated with this work item and the pop-up menu for this area will have several interesting entries. If you had an active work item, try the Stop Working action. Now Jazz does not consider any particular work item as active (i.e. <No Current Work>).

Working on a work item There are several ways to designate a work item as the active work item:

• Open the work item, set its status to Start Working and click Save.

• From the Work Items view, drag the work item into the lower right-hand corner of the Eclipse main frame.

• Right-click the <no current work> string lower right-hand corner of the Eclipse main frame and select Start Working or Recent Work to see a list of work items to work on.

There are several ways to deactivate an active work item:

• Open the work item and set its status to Stop Working and click Save.

• Right-click the work item in the lower right-hand corner of the Eclipse main frame and select Stop Working.

When you resolve an active work item, you are prompted to deliver the associated change sets. If you stop working on a work item or start a new change set while a work item is active, you will be prompted to suspend the changes associated with the active work item.


3.6 Accepting changes from other members of your team

Incoming change-sets ( ) As other teammates deliver their updated display files to the Dev 1.1 stream, these changes are made available to you as incoming changes. Later on in this lab you will accept all incoming changes.

If you yourself need to get changes from other team members that have delivered their changes to the stream you need to Accept these changes in order to get them into your repository workspace.

You have not been the only one working on the Payroll component. Your teammates have been delivering their modified display files to the streams also. These changes should be showing up as notifications in real time in the bottom right of the Team Concert for i window.

__1. You can also see these notifications in the Event Log section of the Team Central view (Window -> Show View -> (Other -> Collaboration ->) Team Central) .

__111. Back to the Pending Changes view (Window -> Show View -> Other -> Jazz Source Control -> Pending Changes), verify that there is a number of incoming changes. Expand the folders to locate the changes.


__112. In the Pending Changes view, click Accept All Incoming Baselines and Change-sets ( ) icon to load changes from other teammates into your Repository Workspace(s).

Your personal Repository Workspace is now up to date with the Dev 1.1 stream.

You may need to do this repeatedly as each of your teammates completes his/her work.

3.7 Conclusion

Congratulations, you have just passed Jazz source control 101. You have made changes, tested them, delivered them to your teammates on the streams, and picked up their changes as well. This is the mainline path for performing source control in Jazz. Later on, you will experience other situations like code conflicts and work interruptions. Also, notice once again how the Pending Changes view is central to how you interact with Jazz Source Control.

We hope you got an idea how the RTCp and RDp development environments work and we hope you enjoyed this tutorial.

There are other members in your development team that might have different role, like the team lead or the project manager. If you are interested in working thru some of the RTCp tasks for these folks, please stay tuned. We are working on adding more tutorials that cover tasks in RTCp for people in these roles as well, including project dashboards.


Appendix A. Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Asset title goes here

IBM Software

Appendix

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

[ This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. All references to fictitious companies or individuals are used for illustration purposes only.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Appendix B. Trademarks and copyrights

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

IBM AIX CICS ClearCase ClearQuest Cloudscape

Cube Views DB2 developerWorks DRDA IMS IMS/ESA

Informix Lotus Lotus Workflow MQSeries OmniFind

Rational Redbooks Red Brick RequisitePro System i

System z Tivoli WebSphere Workplace System p

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. See Java Guidelines

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

Other company, product and service names may be trademarks or service marks of others


work items, software configuration management, and team...

Documents