Copyright © Cloud Software Group, Inc. All Rights Reserved

Creating an AliasLibrary

The AliasLibrary resource is crucial for resources that depend on external files, such as the Java Activity in TIBCO ActiveMatrix BusinessWorks. Resources in your project can reference aliases in the AliasLibrary to resolve external file dependencies that they may have at runtime or debug time.

When you build an enterprise archive file, the files referenced by the aliases defined in an AliasLibrary that you include in your project are included in your archive file. The next diagram shows the AliasLibrary resource.

To Create an AliasLibrary

1.	Select the top-level folder and locate the AliasLibrary resource.

In palette mode, this resource is in the General palette.

2.	Drag the AliasLibrary resource into the design panel.

The AliasLibrary is displayed in the design panel, and the configuration panel now allows you to supply information about the library.

3.	Under the Configuration tab, provide a name and description for the AliasLibrary.

4.	Click the Aliases tab.

Click the icon to select a file or directory to add to your list of aliases. The dialog allows you to pick a Folder or All Files.

Note that if you select a folder, all files in the folder become part of the alias, as well as any sub folders. This means that all files and directories under the folder become part of the enterprise archive file when you build it. If you have a large number of files in the folder, your enterprise archive file will be also be large. When the archive file is deployed, all files in the archive are moved across the network to the remote machines, without regard to which are actually required for the deployment. It is good practice to include only the files required for your project.

A warning appears if the folder of file you select exceeds a certain size. The warning can be customized. See TIBCO ActiveMatrix BusinessWorks Administration for more information.

Click the icon to select a previously defined Alias entry to add to the library. Aliases are managed under the File Aliases tab in the TIBCO Designer Preferences dialog. Click Edit > Preferences to access the dialog.

The icon allows you to delete selected entries in the AliasLibrary. Note that the entry is removed from the AliasLibrary. The alias is still available from the preferences dialog.

5.	You can specify whether aliases within the AliasLibrary should be included in the CLASSPATH, deployed with the enterprise archive file, or both. This may be required for a TIBCO ActiveMatrix BusinessWorks Java Activity that loads a jar file in order to find its executable or supporting code.

−

If you select the Classpath check box, the jar file or file represented by the alias is placed in the CLASSPATH when the enterprise archive file is built. Note that, at design-time, the referring resource is responsible for loading these entries itself. Designer does not perform anything with the configuration other than building the enterprise archive file.

−

If you select the Deploy check box, the associated file is deployed. If the deploy check box is clear, the file is not deployed. This allows a Java Activity to specify that a support jar file is required in the CLASSPATH, but should not be deployed (the jar may already be available as part of a separate configuration at runtime, but may be required during debug time).

6.	Click Apply.

Copyright © Cloud Software Group, Inc. All Rights Reserved