Using Perforce
Step 1: User A Starts TIBCO Designer to Create a Perforce Project
To create a Perforce project, User A follows these steps:
Procedure
|
1.
|
User A opens TIBCO Designer and chooses New Empty Project. |
|
2.
|
In the dialog that appears, User A specifies the following information: |
|
—
|
Project Directory —Location of the project on the local drive, that is, location where the project is placed by Perforce when you synchronize. |
|
—
|
Encoding —This field is used to determine the wire encoding that TIBCO Rendezvous should use for sending and receiving data in this project. This is a project-wide preference. See TIBCO Adapter Concepts for a discussion of how TIBCO adapters support Unicode. |
ISO8859-1
—Default value. Use this option if you ONLY intend to use TIBCO Rendezvous for English and Western European data.
UTF-8
— Select this option if you want to use TIBCO Rendezvous activities for processing non-Western European data, such as Japanese.
|
—
|
Multi-User System —Perforce — This selection also enables the Test Configuration option. Use this option to test the validity of the information you are using to access Perforce. |
|
—
|
User Name —Name of the current user. This is the same as Owner entered in Perforce Client Specification. |
|
—
|
Password —Password for the current user, as specified during the Perforce client installation. |
|
—
|
Perforce Client —This is the same as Client entered in Perforce Client Specification. |
|
—
|
Server —The port on which you access the Perforce server. |
|
—
|
Perforce Command —Click Browse to point to the P4.EXE executable on your machine. |
|
—
|
Timeout (seconds) —Amount of time available to connect with the Perforce server before a timeout occurs. |
Note: If you set your default client in the Perforce native UI you don't need to fill in the user/server type fields when you access Perforce from Designer.
Save Project Options for Perforce Version Control System
Step 2: User A Makes Changes to Project and Checks In the Project
User A can now make changes to the project and check them in as follows:
Procedure
|
1.
|
Using the TIBCO Designer GUI, User A adds resources to the project and configures them. |
|
2.
|
User A saves the project, then chooses Multi-User > Add Resource to RCS. |
If a resource has never been added to RCS, you must add. If you make additional changes, you check in the resource.
After User A has supplied a label for this version, the check-in console, which shows the check-in information, is displayed.
Note: All resources are now locked and can be checked out by other users as needed.
Step 3: User B Checks Out Resources and Makes Changes
After User A has checked the whole project into Perforce for the first time, each resource can be checked out by each user that has access to Perforce.
Procedure
|
1.
|
User B opens the project from TIBCO Designer, using the Perforce as the Revision Control system and providing a username and password, and other required information. |
|
2.
|
User B chooses Multi-User > Project > Synchronize Project to make sure all resources are loaded. |
|
3.
|
User B selects a resource to be checked out in the project tree, then chooses Check Out Resource from the right-button menu of the resource. |
Note: If you check out a resource that contains other resources, they may be checked out when you check out the top-level resource. Whether this happens depends on the directory structure TIBCO Designer creates.
|
4.
|
User B can now make changes to the checked-out resource. After all changes have been made, User B can choose Multi-User > Check In Changes. If User B adds new resource, each resource must first be added to the RCS using the Add Resource to RCS menu. |
Tip: You can add or check in resources recursively.