The Team Productivity Center is a downloadable JDeveloper extension that provides access to a set of application lifecycle management (ALM) tools and technologies. This tutorial uses Oracle JDeveloper 11g Version 11.1.1.2.0 to guide you through setting up a Team Productivity Center and shows how you can use some of its features to maximize your organization's investment in skills, processes and technologies.
1 hour
The tutorial covers the following topics:
Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: This action loads all screenshots simultaneously, so response time
may be slow depending on your Internet connection.)
Note: Alternatively,
you can place the cursor over an individual icon in the following steps to load
and view only the screenshot associated with that step. You can hide an individual
screenshot by clicking it.
Oracle Team Productivity Center is an Application Lifecycle Management tool that enables software development teams to collaborate and work productively together when developing applications using JDeveloper.
It provides you with tools for communicating with team members, tracking data in team repositories and accessing team data such as bug tools and feature databases, all from within JDeveloper. This tutorial introduces you to the main features of TPC from both the administrator perspective, and the team member perspective.
The first three topics in this tutorial assume a situation
where you have been provided with administrator permissions in order to set
up a Team Productivity Center.
The fourth topic assumes that you have been given a team member role in TPC
and you need to discover how TPC can help with your project work.
Important Note: In order to demonstrate
the features of the Team Productivity Center, this OBE uses a team server that
has been pre-populated with data, and many of the steps of the OBE use this
sample data. If you are just starting out with TPC, or if you are using a database
populated with your own data, the screenshots shown here will not reflect what
you see as you work through the steps on your own machine.
Before starting this tutorial, you should have completed the following:
1. | Install Oracle JDeveloper 11g Version 11.1.1.2.0. You can download it from Oracle Technology Network.
|
2. | Install the Team Productivity Center server instance.
|
3. | Start JDeveloper by selecting Start > All Programs > Oracle Fusion Middleware > JDeveloper Studio 11.1.1.2.0
|
4. | If the Migrate User Settings dialog box opens, click No. If prompted for a User Role, choose Default Role.
Close the Tip of the Day window.
|
5. |
The JDeveloper IDE should now be displayed.
|
The Oracle Team Productivity Center provides a connector framework to enable third party ALM tools to be integrated with JDeveloper. There are a number of connectors available, including those to integrate Team Productivity Center with Atlassian JIRA, Microsoft Project and Rally Software. With this release TPC has a connector to its own Task management system. You can also create your own connectors.
To download TPC client files and connectors, perform these steps:
1. | Choose Help-->Check for Updates from the JDeveloper menubar. The Check for Updates wizard is invoked.
|
2. | In the Welcome to the Check for Updates Wizard page click Next, and in the Source page check the Internal Automatic Updates checkbox. Click Next.
|
3. | In the Available Updates pane, scroll through the list of updates to locate the Oracle Team Productivity Center updates. For this tutorial select the Jira Connector, the Task Connector, and Team Productivity Center Integration. Click Next.
|
4. | When the download has finished, the Summary page displays a list of the extensions you have downloaded. Click Finish to close the wizard. Restart JDeveloper after the install.
|
5. | In the Confirm Exit box, click Yes to restart JDeveloper. Restart JDeveloper after the install.
|
The Team Productivity Center provides team members
with access to repositories so that they can integrate with, and interface to,
internal and external data that is of value to their work. A Team Productivity
Center repository might be a database for tracking bugs and feature requests,
a library of customer feedback from a usability study or beta program, or some
other structured organized information set used by the team.
A key job of the administrator is to provide and maintain references to the
various repositories available to TPC users. To experience what is involved
in setting up a connection to a repository, perform the following steps:
1. | In JDeveloper choose View-->Team-->Team Navigator. |
2. | In the Team Navigator, click Connect to Team Server. Then in the Connect window input your credentials and click Connect. Note the following points about credentials: - If the administrator has set you up as a TPC administrator, then you should use the credentials you have been given. Note: Check the Use SSL Connection box if your team server is using SSL.
|
3. | From the Team Navigator menu choose Team Administration. Note that this option is only available to users with administrator permissions. The Team Administration console displays. As an administrator, you should be able to see all four tabs in the Team Administration console - Users, Teams, Repositories, Roles. If you don't see them all, then you haven't been granted full administrator privileges. You need to get a login that has full privileges in order to follow the steps in this part of the OBE.
|
4. | Click the Repositories tab. The TPC used in this OBE is already populated with sample data. If you expand the Work Item node you see examples of repositories associated with work items used by teams. If yours is a completely new installation there will not yet be any data visible in the Work Item node.
|
5. | In this example a connection to the Public JIRA repository has been defined. Selecting JIRA Public displays details of the connection to the Public JIRA repository. The JIRA connector is one of the connectors that was downloaded in the previous topic. Notice too the reference to Task. A connector for this repository type was also downloaded in the previous topic.
|
6. | When adding a new repository reference, you first need to determine whether you wish to add a Work Item or a Document (Documents contain references to the file-store repositories used by teams.) For this example, select Work Item and click the green + .
|
7. | To define a new repository, you need to select a connector
from the dropdown list, provide a name, and optionally a description.
Click the green + to add a new repository server; provide a name and URL
for the server. Click OK to create the new repository.
|
8. | Notice the Versioning node in the Repositories page. This feature allows you to specify a connection to a source control repository for team members to use to version their work. Expand the Versioning node.
|
9. | Selecting the Test connection in the example data, reveals that Test is using the ADE connector to connect to an ADE source code repository.
|
10. | To add a new connection to a versioning repository, select Versioning and click the green +. Use the down arrow to the right of the Connector field to select the type of versioning system you want to connect to. Provide a name for the connection and (optionally) a description. Note that there is no option to add a server name or location at this point; this is done at the team level, as you will see in a later section of this OBE.
|
11. | To delete the connection, click the red X and confirm. However note that a repository connection that is being used by a team cannot be deleted.
|
A major part of the administrator's job involves managing users and teams. The following subtopics take you through creating users and teams and configuring teams.
![]() |
Create a New User | |
![]() |
Create a New Team | |
![]() |
Configure the Team | |
To add a new user to the Team Productivity Center, perform the following steps:
1. | In the Team Administration console, click the Users tab.
|
2. | You have already seen
that the TPC used in this OBE is populated with sample data. If you are
starting from scratch with setting up your Team Productivity Center, the
Users tab will only contain details of the administrator created in the
server install.
|
3. | If you have multiple users in your Users tab, select another user and see the teams and permissions he/she has. In this example Irene Mikkili is a member of more than one team and has different roles in each one.
|
4. | Click the green plus (+) to add a new user.
|
5. | Provide name and login information for the new user. Here is an example: Kevin Mourgos, (login) kmourgos, (email) kevin.mourgos@example.com (password) kev. Notice that the new user's name is added to the Users roster on the left.
|
6. | You need to define any special
permissions that the user may have.
|
7. | Add three more new users: Trenna Rajs, (login) trajs, (email) trenna.rajs@example.com (password) tren Curtis Davies, (login) cdavies, (email) curtis.davies@example.com (password) curt Peter Vargas, (login) pvargas,
(email) peter.vargas@example.com (password) pete
|
1. | Click the Teams tab.
|
2. | The Teams page displays the teams and sub-teams that exist in the Team Productivity Center, along with the members of each team, and their roles in the teams. Clicking the PSR team in this example shows the members of that team.
|
3. | Notice too the subteams in the DEV_ORG team hierarchy. Teams and subteams can have any number of subteams.
|
4. | Click the green plus (+) to add a new team.
|
5. | In this example the new team appears by default, as a subteam of DEV_ORG since DEV_ORG was selected when the new team was created. However, since this is not what is required here, you can change it by modifying the value in the Parent Team field.
|
6. | Name the new team, Curriculum Development. From the dropdown list in the Parent Team field select ALM. The new team is created as a subteam of the ALM team.
|
7. | Create a subteam of Curriculum Development, called OBE. Select Curriculum Development and click the green +; name the subteam OBE. The Parent Team field is automatically populated with the value Curriculum Development.
|
Configuring the team involves adding users to it, and defining their roles in it. It also involves providing the team with access to the repositories that it needs. To configure the Curriculum Development and OBE teams, perform the following steps:
1. | Select Curriculum Development (or the team you created in Step 6 above if you used a different name) in the Teams pane, and click the green + in the Team Members area.
|
2. | The Select Team Members dialog offers a list of all users
that have been created in the TPC.
|
3. | Back in the Teams tab, you see that the user has been
added to the Curriculum Development team.
|
4. | Add Trenna Rajs, Curtis Davies
and Peter Vargas to the OBE team (or
the users you created in the Creating a New User topic above,
if you used different names).
|
5. | Add Kevin Mourgos to
the OBE team. Although he is a Group Administrator for
the Curriculum Development team and will therefore have admin rights for
the OBE team in terms of adding users etc, if he is to participate fully
in the work of the team, he needs to be added to it as a member.
|
6. | Three of the roles you have seen in the Roles column - Team Member, Team Administrator and Group Administrator - are the default roles that ship with TPC. It is important that you, as an administrator check that these roles 'fit' with your organization, and then create additional roles as necessary. To add a new role, click the Roles tab.
|
7. | The three default roles display in the Roles pane along with the TestRole, created for this organization.Click each of the default roles in turn to see the privileges that each role has: the Team Member role is only able to manage team tags; the Team Administrator role has all privileges except that of being able to gain privilege over child teams. The Group Administrator has the full set of privileges.To create a new role, click the green +.
|
8. | Supply a name and (optional) description for the role, and select privileges by checking the appropriate check box(es) in the Role Privileges pane. Note that these roles are team-based i.e they define the role a user has in a team. None have privileges that allow a user to access either the Repositories or Roles tabs. Only a user with administrator privileges (set in the Users tab - see Step 6 in the Creating a New User topic above) - or the default TPC admin users can access all four tabs.
|
9. | Check that the new role has been created by returning to the Teams tab, and clicking the drop down list in the Role column in the Team Members pane. The new role should be available for selection.
|
10. | To define the repositories that a team needs to be able
to access, click the Team Repositories tab.
|
11. | The Team Repositories tab displays a list of the repositories that were set up in the Repositories tab. In this example the OBE team needs to have access to the QA Scenario JIRA, BugDB, and Task repositories. To specify this, you check the appropriate check boxes in the Select Team Repositories pane.
|
This topic pre-supposes that you have been input in TPC as a user of the system. As a member of a team in the Team Productivity Center, you can use TPC facilities to communicate with your fellow team members, to track data in team repositories and access team data such as bug tools and feature databases. To explore some of the team member facilities in TPC, perform the following steps:
![]() |
Connect to theTeam Productivity Center | |
![]() |
Explore the Team Accordion | |
![]() |
Access Team Data | |
![]() |
||
![]() |
In order to connect to a Team Productivity Center server, you must have been added as a user of the system, by an administrator.
1. | In JDeveloper chooseView-->Team-->Team Navigator.
|
2. | In the Team Navigator, click Connect to Team Server. Then in the Connect window input the credentials you have been given by the administrator, and click Connect.
|
3. | Once connected to the TPC server, you see the name of a team to which your administrator has added you and below it, a Team Members accordion that provides data about the other members of the team, and Work Items, Team Documents and Versioning accordions, each of which will provide access to information repositories needed by your team.
|
1. | Notice that the name of a team of which you are a member is displayed at the top of the Team Navigator. If you have been assigned to more than one team, click in the team name box to see the other teams that you belong to. In this example Irene Mikkili has been assigned to the ALM, Business Services and the DemoStore Services teams.
|
2. | Selecting a team (in this example, the ALM team) displays the accordions containing information relevant to that team. Clicking the Team Members accordion opens it to display team member information.
|
3. | A list of all your fellow team members for the currently selected team is displayed. If you 'mouse over' the name of a team member, you can see his/her email address, role in the team and 'Chat' status if you are connected to Chat.
|
4. | To chat with a fellow team member, double-click the name in the list. If the team member icon to the left of the name is 'lit', the team member is currently logged into Chat. The first time you log into the Team Member chat panel you may be asked for some configuration information needed by TPC. Such information typically includes the host chat server URL and port number, as well as your user name and password.
|
5. | The Chat window opens, ready for you to begin a conversation.
|
6. | Notice the tabs at the bottom of the Chat window. You can chat with buddies from any currently available XMPP/Jabber protocol, and in addition you can start a chat with a team member directly from the team members accordion.
|
1. | Before being able to
access data in any of the team repositories, a team member must add his
login for the repositories that he/she needs to access.
|
2. | In this OBE example, the ALM team is working on the DemoStore project, and needs to have access to the JIRA repository and the Task repository. Using this data you would need to select JIRA in the Accounts pane of the Manage Accounts dialog and add Irene Mikkili's login (imikkili/tpc). Click Test Connection. The login is successful. Note: If the Test Connection is not successful, then it might be because you are trying to access a server that is outside your firewall - for instance, if you are connecting to the Public JIRA repository. In this case, check that you have your proxy set: Tools--> Preferences--> Web Browser and Proxy.
|
3. | You follow the same steps to set up an account for imikkili for the Task repository.
|
4. | Open the Work Items accordion. Expanding the JIRA node and the Task node in the sample data, reveals that the team uses the JIRA repository for managing requirements for the DemoStore project and the Task repository for ALM tasks.
|
As you have seen in previous topics, TPC provides a
great resource for team members in terms of the team data stored in the various
repositories. Team members can create user queries and team queries
to run against this data.
User queries are queries you can create to solve a specific problem that
you are facing—for example, to find bugs in a specific date range, or
filed by an individual team member if you are taking over another member's tasks.
A team query represents a more general query that may need to be used
by multiple team members. For example, the entire team might want to view bugs
filed as a result of a usability session or beta program.
1. | As you have seen, the ALM team in the sample data is working on the DemoStore project. The screenshot below shows that two team queries have been created in the JIRA repository. To run a team query, you double-click it..
|
2. | The result of the DemoStore Open Requirements query is
returned. You can customize query results in a number of ways, for example
all columns are sortable in ascending or descending order.
|
3. | You can reorder columns, using drag and drop. In the sample data, clicking in the Priority column and dragging it to the left allows you to move it in that direction.
|
4. | Clicking the Customize Columns button at the top right of the report allows you to select the columns you want to display.
|
5. | The Customize Columns dialog allows you to add or remove columns from the display. For example, in the sample data, all issues relate to the DemoStore project, so there is no need to display the project name. Selecting the Project column and shuttling it from the Selected Columns list into the Available Columns list, and clicking OK, removes it from the report.
|
6. | You can also use the Search Criteria dropdown lists at the top of the report to formulate more specific queries. Click the + (plus sign) next to Search Criteria at the top left of the report to open up the Search area. The example shows the first line of a two-line search query: Assignee is selected from the first dropdown list, Equals from the second dropdown list and the name, imikkili is input in the third box. Clicking the green + allows you to add more search criteria.
|
7. | The second line of the query adds the additional filter to only search on Priority = Major. Clicking Search runs the query. A list of only the major requirements assigned to Irene Mikkili is returned.
|
8. | Our sample user, Irene needs to save the query so that she can monitor her tasks list. She saves it as a user query with the name, DS - Tasks. To save a user query, click the More Actions button, and choose Save As from the dropdown list. Provide an appropriate name for the query in the Save Query dialog, ensure that the User Query radio button is selected and click OK.
|
9. | Notice the DS -Tasks query saved under the My Queries node in the JIRA repository.
|
10. | Irene needs to refamiliarize herself with the Calculate Order Discount work item. Double-click it to display details of it.
|
11. | Update the work item. In the screenshot below you see that the Due Date field has been changed to 2009-07-31 to give Irene another month to work on the bug. You make the change in the Detail finger tab, by clicking the calendar on the right of the Due Date field. Clicking the Save icon in the JDeveloper toolbar saves the update back to the JIRA repository.
|
12. | Clicking the Relationships finger tab indicates whether this work item has any relationships with other work items.
|
13. | The Calculate Order Discount work item has relationships with bugs in the BugDB and Bugzilla repositories, and with a task in the Task repository.
|
14. | Double-clicking on the task opens the work item at the other end of the relationship - in this example, in the Task repository. You can add the revised due date to the task in this repository: use the calendar in the End Date field to input a date of 2009-07-31. Save the change.
|
15. | Clicking the Relationships finger tab in the Task repository also displays the reference to the other end of the relationship, in this example, the JIRA repository. Our sample user, Irene, uses the Task repository for task planning and management and the JIRA repository for tracking project requirements and bugs, but TPC makes a direct relationship between the two, so that a work item can be accessed from either repository.
|
You can attach tags to work items. The tags that you create may be to suit the general needs of the team or the personal needs of the team member. For example, bugs in a product under development may be tagged by a project manager as Hot, Warm, EOD (end-of-day), or Deferable. To see how you might use tags to enhance query results, perform the following steps:
1. | In the Calculate Order Discounts task in the Task repository, you use the Tags finger tab to see any existing tags or to create new ones.
|
2. | No tags have yet been defined for this work item.
|
3. | Create a tag for the Calculate Order Discounts work item. Click the green + in the top right of the Tags finger tab, and in the Apply Tags dialog, click Manage Tags.
|
4. | Check the checkbox next to the use case needed tag, to apply this existing tag to the Calculate Order Discounts work item. Click OK.
|
5. | The use case needed tag has now been applied to the Calculate Order Discounts work item.
|
6. | To apply the new tag to the related SSTORE-9 work item in the JIRA repository, you need to click the SSTORE-9 tab to display it, and then click the Tags finger tab.
|
7. | In the Tags tab click the green + to add a tag and in the Apply Tags dialog again check the check box next to the use case needed tag. Click OK.
|
8. | Close all the open tabs by right-clicking one of them and choosing Close All from the context menu.
|
9. | Run a query to find the work items that are tagged with the tag you just created. In the Work Items accordion, click the Tags icon and from the dropdown list, select Query By Team Tag-->use case needed.
|
10. | A list of work items with the use case needed tag is returned. Notice that the list is cross-repository i.e using the sample data, it displays work items from the BugDB repository as well as those from the JIRA and Task repository that you have worked with in this tutorial.
|
11. | You can also run the same query for a specific repository. This example uses the JIRA repository. Right-click the repository node and from the context menu, choose Query By Team Tag-->use case needed..
|
12. | This time only the work item tagged with the use case needed tag in the JIRA repository is returned.
|
13. | The screenshot below shows the results of the two queries one below the other: the top one shows all the information held in TPC about work items tagged with the specified tag, and so the work item in JIRA and the related work item in the Task repository are both displayed (as well as unrelated work items in the BugDB repository). The bottom screenshot is repository-specific, showing TPC has returned the data from the JIRA repository for the only work item from that repository tagged with the specified tag.
|
14. | Right-click the repository node (JIRA in the OBE example)) in the Work Items accordion again to explore the other available options on the context menu. The New Query option allows you to create a new query on the selected repository. The New Issue option allows you to create a new issue and save it back to the repository. (Note that if you don't see New Issue, it's because this functionality was not available to the connector writer i.e the API used to communicate with the repository doesn't support the creation of issues.) The Query By ID option allows you to search for a work item by its ID. In the Query By ID dialog, type a valid ID (SSTORE-8 in this example) in the Key field and click OK.
|
15. | The requested work item (SSTORE-8 in this example) opens. Position your mouse over the right-most icon on the top left of the work item tab - Make Active. Click the icon to make the current work item the 'Active Work Item' in the Work Items accordion.
|
16. | The three icons to the left of the Active icon all refer to 'context'. Context allows you to save (or restore or delete) details of what the JDeveloper IDE is currently showing i.e the current set of open windows. To demonstrate this, open a project and some files in JDeveloper's Application Navigator. In this example, User Interface project files search.jspx and query.jspx, as well as the DS -Tasks user query provide the context for the SSTORE-8 work item. Click the Save Context icon. Click OK in the Save Context information box.
|
17. | Close the context files, leaving just the SSTORE-8 work item open. Click the Restore Context icon.
|
18. | The files search.jspx, query.jspx and the DS - Tasks user query are all opened automatically, thus restoring the context for the work item.
|
This tutorial introduced you to the Oracle Team Productivity Center from the perspective of an administrator setting up TPC and from the perspective of a team member needing to understand how the features of the product might help with day to day project work. You've seen how to:
![]() |
Get Started With Team Productivity Center (Administrator Role) |
![]() |
Make Repositories Available to the Team Productivity Center (Administrator Role) |
![]() |
Manage Users and Teams in the Team Productivity Center (Administrator Role) |
![]() |
Use the Facilities of the Team Productivity Center (User Role) |
![]() |
|
![]() |
|
![]() |
Oracle Team Productivity Center Overview (Oracle White Paper) |
![]() |
|
![]() |