Overview

TIBCO Designer allows you to create alias to resources that are to be reused in other projects. Alias are used in two resources, the AliasLibrary and the LibraryBuilder. The AliasLibrary resource allows you to load files stored in the file system into your project. The LibraryBuilder resource allows you to build a design-time library that includes resources defined in one project that can be shared with other projects.

AliasLibrary Overview

The AliasLibrary resource allows you to specify aliases to file system resources (such as a jar file) that need to be included in your project. To use a file system resource, a project needs to know where to find it. Since projects are exported or deployed to different machines and different environments, Designer uses aliases to specify file locations. Before including a file, an alias is created that specifies the file’s location. An alias is part of your preferences and is common to all of your projects. Aliases are created and managed under the File Alias tab in the Preferences dialog.

LibraryBuilder Overview

The LibraryBuilder resource allows you to share resources you have defined in a project with other project developers. This allows you to create shareable resources once, then allow other project developers to use them in their projects. LibraryBuilder resources are used as part of design-time libraries, which are explained later in this chapter.

For example, the following resources can be part of a LibraryBuilder resource:

•

Schemas (AE or XSD)

•

Identities and SSL Certificates

•

TIBCO ActiveMatrix BusinessWorks Processes

•

TIBCO Rendezvous, JDBC, JMS or other TIBCO ActiveMatrix BusinessWorks shared configurations

A LibraryBuilder resource can be maintained using a revision control system or placed in a shared directory. If a LibraryBuilder resource is to be shared by many project developers, the resource should be managed in a revision control system where users can sync regularly to get updates. In a smaller environment, LibraryBuilder resources can be placed in a shared directory and developers can use email to update each other when there is a change.

If the LibraryBuilder resource changes, the resource must be reloaded into your project. The best practice is to minimize changes to the resource. It should be built and tested, then updated infrequently.

To use a LibraryBuilder resource, a project needs to know where to find it. Since projects are exported or deployed to different machines and different environments Designer uses aliases to specify libraries locations. Before using a library an alias is created that specifies its location. An alias is part of a user’s preferences and is common to all of that user’s projects. Aliases are created and managed under the File Alias tab in the Preferences dialog.

When you build an enterprise archive file from a project that contains a LibraryBuilder resource, all resources referenced in the LibraryBuilder resource are included in the archive, just as resources in your local project are included.