Working with External Library and Custom Function Paths
When you work with external libraries or custom functions in your project at design time, and when you run, test, or debug such projects in TIBCO BusinessEvents Studio, ensure that the engine can find all libraries including dependencies on third-party libraries and custom functions, if the project requires any.
For example, if a project uses Rendezvous channels, Java allows the user to set a property, java.library.path, to ensure that the environment path contains a reference to the directory containing Rendezvous DLLs (or on UNIX the SO files).
Similarly, TIBCO BusinessEvents captures the native library path along with the build path information to pass to engines running inside TIBCO BusinessEvents Studio. You can enter this information as described below, or you can enter it when you are configuring a run configuration or a debug configuration.
- Adding an External Library or Custom Function Path
This functionality is also available in the , and the tab, for your convenience. - Specifying an External Library Location Using Build Path Variable
You can use variables (aliases) to specify an external library location in project build path to build a project using studio-tools in TIBCO BusinessEvents. You can store the third party JARs, custom function JARs, and .projlib files in different locations on your local machines and refer to them through aliases. To perform common builds on a build machine, the aliases are used to create the full path to common JAR files.