Apama 10.3 | Apama Documentation | Using Apama with Software AG Designer | Working with Projects | Building Apama projects | Configuring the project EPL build path | Specifying external dependencies | Specifying dependencies for a multi-user project
Specifying dependencies for a multi-user project
When Software AG Designer builds a project, it defines any dependencies in an XML file that hard codes the path to the external files. 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. Right-click the project and click Properties.
2. In the Properties dialog, expand Apama.
3. Click MonitorScript Build Path.
4. Click External Dependencies.
5. Click Add Variable.
6. 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. Click OK. You can skip the remaining steps.
*If you select a variable that represents a directory, click Extend to specify an EPL file that completes file dependency path that starts with a variable. The Variable Extension dialog appears. Navigate to the EPL file that your project is dependent on. Double-click the EPL file.
*To define a new variable that identifies the required file, click Configure Variables and click New.
i. In the New Variable Entry dialog, in the Name field, enter the name of the new variable. Use upper case names for build path variables.
ii. Click File or Folder and navigate to the appropriate folder or EPL file.
iii. 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.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.