Team Projects determine which objects are controlled by Team Coding. If you are a Team Coding Administrator (meaning that you have the TC_ADMIN_ROLE) you can create one or more Team Projects to group the controlled objects into logical work units, based on your organization's workflow requirements. To use Team Coding there must be at least one Team Project.
When a version control system (VCS) is being used in Team Coding, you can link a Team Project to a project in the VCS. This linking determines where the object source revisions of the Team Project are managed in the VCS.
SQL Navigator enables you to create one or more sub-directories in a VCS project at the same time that you create a Team Project. This feature is helpful if, for example:
- You plan to use multiple Team Projects and want to mirror each one to its own VCS directory under a common root VCS project.
- You have multiple developers or development teams working on the same Team Project, and you want to isolate their objects into dedicated directories within a common root project.
Use Team Projects page of Team Coding Administration to administer your Team Projects. Only a Team Coding Administrator can administer Team Projects.
- If using a version control system with Team Coding, log into the VCS from Team Coding | VCS Logon.
- Go to Team Coding | Administer.
- Select the Team Projects tab.
To Create a Team Project
See Setup Team Projects.
To change a Team Project
Under the Team Project that you want to change, do one of the following:
- To change the name of the project, right click the name and then select Rename Team Project.
- To edit the controlled database objects, click in the field next to Database Objects, then click the arrow to select the schema that you want to edit. Refer to Setup Team Projects for information about how to complete these fields and apply the changes.
- To make a project active (meaning Team Coding is active for the objects specified in the project) or inactive (deactivate Team Coding for those objects), select or deselect the Active box.
To delete a Team Project
- Select the Team Project to delete.
- Click
to delete the project, or right-click the project and select Delete Team Project.
- Click Apply.
To freeze a Team Project
- Select the Team Project to freeze.
- Click
to freeze the project, or right click the project and select Freeze Team Project.
- Click Apply.
Note: In the Team Projects list, the project is now marked (Frozen) rather than (Active)
. Click 
to unfreeze the project.
To work with revisions
The Team Coding Administrator can perform the following actions for a project:
|
(Disabled if a VCS is not being used) |
Synchronize Changes |
Synchronize differences between the version in the database and the version in the VCS. Select the objects that you want to synchronize.
Synchronize resolves the following issues:
- Differences between the VCS source code and the object in the database. Any differences are resolved by the global setting of the "When differences in source versions exist" option in the Team Coding Administrator window (as configured by a Team Coding Administrator). If the option is set to Prompt User (user chooses between opening the database version or the VCS version) a non-administrator user can make that choice. Otherwise, either the database or VCS version is opened, depending on the global setting. See Set Team Coding Global Settings for more information.
- Objects in the database but not in the VCS are added to the VCS.
- Objects in the VCS but not in the database are added to the database.
|
|
(Disabled if a VCS is not being used) |
Create New Revision in the VCS |
Create a new revision in the VCS for all controlled objects. This action loads all of the objects for a Team Project into the Synchronize window. Select the ones for which you want to make a new revision. |
 |
Compile PL/SQL Objects in DB |
Compile the selected object in the database. |
The Team Coding Administrator must create at least one Team Project before users begin to use Team Coding. A Team Project is linked to specific controlled objects and a version control system (VCS), if one is being used with Team Coding.
Team Coding must be installed and set up before Team Projects can be created. For more information, see Install Team Coding.
To create a Team Project
- If using a version control system with Team Coding, log into the VCS from Team Coding | VCS Login.
- Select Team Coding | Administer.
- Select the Team Projects tab.
- Click
in the Team Coding Administration toolbar.
- Assign a name to the Team Project. Note: You can rename a project at any time: Right-click the name and then select Rename Team Project.
- Do one of the following:
- If you are not using a VCS with Team Coding, leave the VCS area set to the default (blank).
- If you are using a VCS with Team Coding, click
next to VCS Project to specify a project (and sub-project as needed) in the VCS. The selected project will contain the revisions made to the source objects that this Team Project will control. You have the following options when selecting this directory:
| New... |
Specify a nested sub-project for SQL Navigator to create under the selected VCS project.
- Click New, then type a name for the sub-project.
- Click OK to return to the Select Project window.
- (Optional) To create a nested sub-directory under the new sub-directory, select the new sub-directory in the tree, and then click New.
|
|
Sub-Projects |
Store each object type in a separate sub-directory under the VCS directory that you created in the previous steps:
- Select the check box.
- To create the sub-projects in the VCS now, click Create Sub-Folders. Otherwise, SQL Navigator will create them when the objects are checked out for the first time.
|
- Click
to do one of the following:
- Select All Schemas to include all of the user schemas in the database in this Team Project.
- Select an individual schema from the list.
- To add another schema, click and then select a schema.
- To remove a schema, click .
- To filter the objects that are controlled with this project, expand the schema node and then refer to the following table. By default, all objects of all object types are included in the project.
|
Enable |
Clear the check box for any object type in this schema that you do not want to control with Team Coding.
For tables, you can control how tables and their associated objects are checked out:
- Select the box at the Tables node to check out tables with their associated indexes, triggers, and constraints.
- Select the individual Triggers, Constraints and Indexes nodes to check out those object types separately from their associated tables.
|
|
Filters
() |
Double-click to create filters that control which objects of each object type are controlled. You can add one or more filters. Use standard Oracle filtering such as string% or string_.
Use Filter to specify the objects that you want to control with this project.
Use Exclude to exclude objects from being controlled by this project. |
- Click OK.
- (Optional) Create additional Team Projects.
- Click Apply to direct SQL Navigator to create the Team Project(s) and the associated projects in the VCS, if applicable. The objects are added to Team Coding, but not to the VCS.
|
|
Note: By default, a Team Project is marked as active when it is created. A status of (Active) means that the objects in the project are controlled through Team Coding. |
Team Coding only has one defined role, that of the Team Coding Administrator: TC_ADMIN_ROLE. This role is automatically granted to the user who creates the Team Coding objects. This user can set up or remove Team Coding, set up global rules for the Team Coding environment, and set up Team Projects.
If necessary, you can grant the TC_ADMIN_ROLE to additional users. Be sure to select the Default checkbox when you grant the role to additional users.
You do not need to assign a role to other Team Coding users. By default, all users in the database can:
- View the status of objects with the Team Coding Viewer
- Lock and unlock database objects
- Check items in and out of source control (if a VCS is in use)
- Mirror their schema to a Team Project
Administer Team Coding
Use the Configure Team Coding Options page to configure the following local settings that are unique to your local SQL Navigator installation:
To set local Team Coding options
Options
|
VCS |
Select a version control system to use with Team Coding. Select None to use Team Coding without a VCS.
|
|
Note: If the database you are connected to is controlled by Team Coding, this selection is read-only and cannot be changed. | |
|
Settings |
Configure connection settings to the selected VCS.
Configure Concurrent Version Systems (CVS)
Configure Git
Configure IBM Rational ClearCase
Configure Perforce (P4)
Configure Serena PVCS Version Manager
Configure Subversion (SVN)
Configure Microsoft Team Foundation Server
(Not required for Microsoft Visual Source Safe.)
|
|
Note: If the database you are using is controlled by Team coding, these settings are read-only and are controlled by the Team Coding Administrator. | |
|
Prompt for check-in comment
Prompt for check-out comment |
Force users to enter comments when checking controlled objects in or out.
If the Force check-in comments or Force check-out comments option is set globally by the Team Coding Administrator, that option is read only on this page. |
| Prompt for check-in all on exit |
Prompt users to check in their work when they close SQL Navigator. |
| Prompt for changes to VCS server config |
Prompt to alert you of changes made to the VCS configuration. |
| Check-out object on opening |
Automatically check out a controlled object when it is opened in SQL Navigator. |
| Check-in object on closing |
Automatically check in a controlled object when it is closed in SQL Navigator. |
| Force new revision on check-in |
Force a new VCS revision when a controlled object is checked in, even if no changes are made. Not all VCS systems support this feature. |
| VCS Logging |
Description |
| Show VCS command output window |
Display Team Coding VCS commands and responses in the Output Window. |
| Enable VCS debug logging |
Save VCS commands and responses to the VCS debug log. To view this log, click Open log file. |
