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 section.
For example, the following resources can be part of a LibraryBuilder
resource:
• | Schemas (AE or XSD) |
• | Identities and SSL Certificates |
• | ActiveMatrix BusinessWorks Processes |
• | TIBCO Rendezvous, JDBC, JMS or other 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.