A number of ALER workspace preferences and project properties are available for workspace connection configuration and automatic usage detection. These are accessible using the standard Eclipse workspace preferences, using the Window > Preferences menu.
For an Eclipse project, you can right-click the project and select Properties from the menu.
Configuring the ALER Connection
If you haven't already entered connection credentials using the Connect to Enterprise Repository wizard, which is automatically invoke when querying or submitting assets before repository connectivity has been established, then you can manually set ALER connection credentials for an Eclipse workspace as follows:
On the Window menu, click Preferences.
Select AquaLogic Enterprise Repository.
Figure 5-1 Preferences - Connection Credentials
In the Credentials area, enter the server location and login credentials, as follows:
Repository URL - the URL of the repository server. The URL must include the host, port, and ALER server name. For example, http://localhost:7001/aler30.
User Name - user name to gain access to the repository.
Password - password to gain access to the repository.
Click the Establish Connection button to ensure enterprise repository connectivity.
If a connection cannot be established, an approrpriate error message will be displayed.
Once connectivity is established, you can specify your workspace preferences:
Enter a Model Namespace to use as a default for your all of your projects. The Namespace provides a means to organize your models, with the Namespace pre-pended to the names of all the assets in the model in the repository. However, you can change the Namespace on a project-by-project basis (such as when submitting assets), and the new Namespace will only be saved for that project, but will not affect the Workspace Preference name.
Select a Repository project in ALER that the submitted model will be associated with. Asset usage is tracked in the repository and attributed to repository projects, which typically represent software development programs, business initiatives, etc.
The Artifact Store area displays the name of a preconfigured Artifact Store that the submitted assets will be associated with. Artifact Stores contain the files relevant to assets in ALER and are configured in the ALER console by an administrator. The Details box may also display some additional information about the Artifact Store.
Click OK to finish.
Configuring Automated Usage Detection
ALER can automatically detect asset reuse within the development environment. This allows development teams to ensure that they get asset reuse credit, regardless of whether the assets have been downloaded through ALER. Automated Usage Detection relies on a fingerprinting process, called Software File Identification (SFID), which tags selected files within an asset with a unique ID. This SFID is then used to detect when and where an asset is used, even if the asset was acquired through means other than the ALER Use - Download process. An instance of usage is recorded by ALER when tagged files within the asset are brought into the developer's IDE, and a new build or build clean occurs.
See the ALER Software File Identification Guide for more information.
Note:
Automated Usage Detection requires the installation of the ALER Plug-in for WorkSpace Studio, and is currently compatible only with Eclipse and Eclipse-based IDEs.
Enter the appropriate information in the File Pattern text boxes:
Include File Pattern - Includes indicated file pattern
Exclude File Pattern - Excludes the indicated file pattern
Specify which project directories will be targets for automatic usage detection by using the individual check boxes or by using the Select All and/or Unselect All buttons.
