How to Setup StarTeam & PowerBuilder-Single User.
Information in this Brief applies to:
This document will cover how to configure and PowerBuilder 8 & 9 with StarTeam. It is not intended as a definitive document on PowerBuilder development. Further information can be found at:
User is familiar with PowerBuilder 7, 8 & 9 and StarTeam.
User has read the documentation for setting up PowerBuilder 7.
The basic difference in the alternative setup of PowerBuilder 8 and 7 is that each object is placed into it?s own folder created in the workspace. When the objects are added to source control they reside only in the child folder and not in the root folder as in PowerBuilder 7.
To set up PowerBuilder and StarTeam for a single user, first open PowerBuilder. No workspace is defined so select File...New, see Fig1, then Fig 2.
You will now define a workspace, select "OK". This will define the folder on your machine that will contain the PowerBuilder project, see Fig3.
Using the folder navigation buttons you can create a folder called "Example" or similar to contain the workspace file, see Fig4.
Open the Example folder and define a workspace name, in the example "StarTeam" will be used...select "Save", see Fig5.
After selecting Save you will return to PowerBuilder, see Fig6.
Select File...New again, select the "Target" tab...Template Applications, then "OK", see Fig7.
The Template Application Wizard appears, select "Next", see Fig8.
Select "Next" at the "What you will do" window, see Fig9.
The next window permits the creation of the Application Name as well as a browse button to define a new folder within the workspace (which will contain the *.pbl), see Fig10.
Select the "Browse" button and create a new folder within the workspace, in this example the Folder will be "pbl_1", see Fig11.
Open the folder pbl_1 and create the *.pbl file, select "Save". In this example the *.pbl file created will be named "pbl_1.pbl", see Fig12.
After "Save" the results will be as seen in Fig13. Note the location of the Library and Target as folders within the workspace, select "Next".
Select "Next", see Fig14.
Adjust your Library search path if needed, select "Next", see Fig15.
Select "Next", see Fig16.
Select "Next", see Fig17.
Select "Next", see Fig18.
Select "Next", see Fig19.
Select "Next", see Fig20.
In this example select the Connectivity Option of "None", the select "Next", see Fig21.
Select "Next", see Fig22.
Select "Finish", see Fig23
PowerBuilder returns with objects added to the library and application, see Fig24.
Repeat the above steps for a second Application Library, in this example a second *.pbl called "pbl_2.pbl" will be created, see Fig25.
Secondary mouse or right click on the workspace and select "Properties", see Fig26.
Select the Version Control Tab, see Fig27 item "A".
You may select "Require Comments on Check-In", in this dialog You should not set the option in StarTeam (Project...Properties...Require comments on check in). PowerBuilder version controls a *.pbg file in the background, if this option (Require comments on check in) is selected in StarTeam. the *.pbg file is not updated correctly. (This check in/check out is transparent and not seen by the developer.) When the option is set in the Workspace properties dialog, the OK button on the CheckIn dialog is disabled until a comment has been provided.
Do select Perform diff on Status update, Item C.
Select the project browse button, see Fig28.
This brings up the window, select Create New, see Fig29.
The create new project wizard appears, verify the information and the appropriate StarTeam server and then select "OK", see Fig30.
Fill in the log on credentials to the StarTeam server, see Fig31.
PowerBuilder returns with new information in the window, select "OK", see Fig32.
When completed PowerBuilder returns as seen in Fig33, note icons next to *.pbl"s.
Secondary mouse or right click on the workspace and select Add to Source Control, see Fig34.
The window as seen in Fig34 appears, select "OK".
Upon completion the following structure is created in StarTeam, see Fig35. Note the workspace file exists in the root folder.
Note the folders associated to a *.pbl, see Fig36. The *.pbl are not under version control (Not in View) while the objects are under version control (Current).
Objects are still checked in and out of the *.pbl that exist locally on the drive. Copies of the objects exist on the drive in depending on options selected by user or the needs of a specific version control system.
User can now check out an object and edit it, see Fig37.
Once completed note the change in the icon, see Fig38.