Specifying dependencies for a multi-user project
When Software AG Designer 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, Software AG Designer 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 Software AG Designer menu, choose Project > Properties.
3. In the Properties dialog that appears, expand Apama.
4. Click MonitorScript Build Path.
5. Display the External Dependencies tab.
6. Click Add Variable.
7. In the New Variable Dependency Entry dialog, 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; Software AG Designer 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.
