Developing Apama Applications > Using Apama Studio > Working with Projects > Building Apama projects > Configuring the project build path > Specifying external dependencies > Specifying dependencies for a multi-user project
Specifying dependencies for a multi-user project
When Apama Studio builds a project, it defines any dependencies in an XML file that hardcodes the path to the external file(s). This works correctly if you do not share projects among multiple users. However, if two or more users share a project, they might not store external files in the same location.
If you are sharing projects among two or more users, you should use a variable to define an external file on which your EPL file depends. For example, Apama Studio automatically defines APAMA_HOME and APAMA_WORK variables that can be used to locate files under either of those directories in a way that is independent of exactly where Apama has been installed on the current machine. To use a variable to define a dependency:
1. Select the project, or a file in the project, for which you want to define a dependency.
2. In the Apama Studio menu, choose Project > Properties .
3. In the Properties dialog that appears, expand Apama.
4. Click MonitorScriptBuild Path.
5. Display the External Dependencies tab.
6. Click Add Variable.
7. In the New Variable Dependency Entry dialog that appears, do one of the following:
*If a variable already exists that identifies the required file, double-click that variable. Then click OK. You are done and can skip the remaining steps.
*To define a new variable that identifies the required file, click Configure Variables.
8. In the New Variable Entry dialog, in the Name field, enter the name of the new variable. The convention is to use UPPER_CASE names for build path variables (for example, APAMA_HOME).
9. Click File... or Folder... according to which one you want the variable to represent.
10. Navigate to the appropriate folder or EPL file and double-click it.
11. Click OK twice.
12. Click OK in the Preferences dialog; Apama Studio confirms that the classpath variables have changed, and prompts you to indicate whether you want to rebuild your project so that it can use the new variable. Click Yes.
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.