Setup Team Projects
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. |