Copyright © 1999-2023. Cloud Software Group, Inc. All Rights Reserved.

Perforce Fast Software Configuration Management System

Perforce has comprehensive software configuration management capabilities built around a scalable client/server architecture. Requiring only TCP/IP, developers can access the Perforce Server through a variety of Perforce clients (Windows GUI, Web, or Command-Line). Perforce can be deployed quickly and easily, and requires minimal administration, even for large or distributed sites.

Perforce is supported on a large number of operating systems.

Prerequisites

Before attempting to use Perforce you must ensure the following procedures have been taken.

•	Install the Perforce software. TIBCO Designer does not include or install this software.

−	The Perforce server must be installed and running.

−	The Perforce client must be installed on your machine. Only the client is necessary on the machine where TIBCO Designer runs.

•	The Perforce server port must be defined.

•	Setup a password for your Perforce account. To do this in Microsoft Windows, select User > Set Password for UserName. Every Perforce port has a unique password. You may need to define a password for all the Perforce ports you access normally.

Assigning user name and passwords may be done by the Perforce administrator at your site.

•	Select the client you use to use or define a new client with any name. You can define a new client in the Perforce clientSpecs >New menu.

•	Be sure that you have the appropriate permissions to access, create, delete, store, and modify the files you wish to work with under Perforce.

Using Perforce

Step 1: User A Starts TIBCO Designer to Create a Perforce Project

To create a Perforce project, User A follows these steps:

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.

If you set your default client in the Perforce native UI you don't need to fill in the user or server type fields when you access Perforce from TIBCO Designer

Figure 20 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:

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.

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.

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.

 

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.

You can add or check in resources recursively.

Copyright © 1999-2023. Cloud Software Group, Inc. All Rights Reserved.