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.
Procedure
Result
The two methods using which you can specify where to find the JAR files during deploy time are:
- Using classpath (-cp) option - In the command-line specify the path of the JAR files in the
-cp command line option for the classpath. For example:
studio-tools.exe -cp c:\logs\677138\cf-logger51.jar -core buildEar -o c:\temp\hello.ear -p C:\Logs\677138\HelloWorld_with_CustomFunction
- Using the
studio-tools.tra file - In the
studio-tools.tra file, which is used to build the EAR file on the build machine, add the following property for each defined variable:
java.property.CUSTOM_HOME=C:/Logs/677138/
where, CUSTOM_HOME is the name of the variable.
Now you can build EAR without specifying classpath in the command, for example:studio-tools.exe -core buildEar -o c:\temp\hello.ear -p C:\Logs\677138\HelloWorld_with_CustomFunction
Copyright © TIBCO Software Inc. All rights reserved.