Populating the Repository

You can export client/server interface contracts from the Rose Expert to the Contract Repository, thereby populating the Contract Repository with the data. This gives you the ability to share the BEA TUXEDO services modeled in the Rational Rose paradigm with the rest of the Builder development environment by means of the shared Contract Repository.
 

Prerequisite Tasks

In order to populate the Contract Repository with Rose Expert data, you must have at least one component package in the current Rational Rose model. If there are no component packages in the model, you get an alert message when you choose the Populate Repository menu option.

Figure 3-13 Populate Warning

If you get this warning, go back to the model and create a component package.

For more information on creating component packages, refer to topic Create Component Packages and a Component Diagram in the section Using Rational Rose to Model a TUXEDO Application.
 

What the Populate Repository Process Does

During the "populate repository" process, the Rose Expert creates a text file called PopulateRepository.dat based on the application model for the selected component package. The PopulateRepository.dat file is read automatically by the bulk loader (crbld.java) that connects to the Contract Repository server.

After using the Rose Expert to populate the repository, you can access the objects you created by means of the Contract Repository Editor or any other BEA Builder product that uses the Contract Repository as a data source.

Table 3-5 shows how the Rose Expert data translates to the Contract Repository.

Table 3-5 How Rose Expert Data Translate to Populate the Contract Repository

Rational Rose Entity	Contract Repository Entity
Component Package	No equivalent-used as the unit of movement from the model to the Contract Repository
Task Module	Module
Control Class	Interface
Operations of a Control class	Operations of an interface
Operation parameters	Elements belonging to an operation. Also called operation parameters
Structure class	Struct
Other model classes	No equivalent
No equivalent	Elements

Note: As a part of the populate repository process, the Rose Expert overwrites duplicate entires from previously generated data.
 

How to Populate the Contract Repository with Model Data

To populate the Contract Repository based on your application model:

1. In Rational Rose, make sure the model you want to use to populate the repository is currently displayed (ApplicationName.mdl) and contains at least one component package.

2. Choose Tools->BEA TUXEDO Builder->Populate Repository from the Rational Rose menu bar.

   This brings up the Populate Contract Repository logon window as shown in Figure 3-14.

   Figure 3-14 Populate Contract Repository - Logon

   

   As a first step in populating the Contract Repository with Rose Expert data, you need to provide logon information for Contract Repository logon. (If you have specified default logon settings, the first three fields on this window will be set already. See Specifying Logon Settings.)

   Table 3-6 explains the fields on this window.

   Table 3-6 Populate Contract Repository - Logon

   Field	Description
   Host	Specifies the name of the BEA TUXEDO host machine that is running the Contract Repository server.
   Port	Specifies the port number of the Contract Repository server.
   User	Specifies the BEA TUXEDO user name.
   Application Password	Specifies the BEA TUXEDO application password if needed (8-character limit).
   User Password	Specifies the BEA TUXEDO user name (30-character limit). Must not be left blank.

3. When you have filled in the fields, click OK and continue with the next step in the populate repository process.

   This brings up the Populate Contract Repository select package window as shown in Figure 3-15.

   Figure 3-15 Populate Repository - Select Package

   

4. Select the component package containing the data you want to export to the Contract Repository and click OK.

   This brings up the Populate Repository start window as shown in Figure 3-16. The target host you specified in step 1 is displayed here.

   Figure 3-16 Populate Repository

   

5. Click Start to log on to the Contract Repository and begin the populate repository process.

   The window remains open to show the progress of the populate process. Table 3-7 explains the read-only fields on this window.

   Table 3-7 Populate Contract Repository

   Field	Description
   Host	Indicates the name of the BEA TUXEDO host machine that is running the Contract Repository server. This is the server where the generated data will be placed. For information on specifying the host, refer to step 2. in "Populating the Repository".
   Component Package	Indicates the component package selected for populating the Contract Repository.
   Status	Indicates what objects are being accessed in the model. Results of the populate process are written to the project root directory, which is displayed in the dialog.

   Figure 3-17 Populate Contract Repository - Phases

   

   When the populate repository process is finished, the window indicates this and the Cancel button changes to a Close button as shown in Figure 3-18.

   Figure 3-18 Populate Repository - Complete

   

6. You must click View Log to display the results of the populate process.

   Figure 3-19 View Log

   

7. After you have checked the log, you can click Close on the Populate Contract Repostiory window to close it.

When the populate process completes successfully, the model elements in the chosen component package are available in the Contract Repository. (For information on working with the Contract Repostiory, refer to the online help for that product. Also, refer to Where to Find Related Information.)