Running and Testing the Model

When you first run and test your AWM model you should start Enterprise Developer for Eclipse in debug mode. To do this:

1. Right-click the shortcut for Enterprise Developer for Eclipse.
2. Click Properties.

   This opens the Enterprise Developer for Eclipse Properties dialog box.

3. Click Open File Location.

   This opens Windows Explorer at the Eclipse application location in the Enterprise Developer folder location.

4. Edit the eclipse.ini file.
5. Insert a new first line, type -debug and then save and close the eclipse.ini file.
6. Restart Enterprise Developer for Eclipse.
7. Right-click in the Application Explorer view, then click Add System(s).

   This opens the Add System(s) dialog box.

8. Click Custom System, and then click OK.

   This opens the New Custom AWM System dialog box.

9. In the System Name field, type Issue Tracker.
10. Click Next.
11. In the Location field, click Browse.
12. Navigate to the IssueTracking.model, select it, then click OK.

    The Application Name field is automatically populated with text derived from the application name.

13. Click Finish.

    This adds the Issue Tracker custom system to the Application Explorer view.

14. In the Application Explorer view, expand the Issue Tracker custom system.
    
    
15. Right-click IssueTracking, and then click Load Application.

Expand the IssueTracking application folder. Below are the All Issues and Issues by Priority groups. Click either group to display its children. In the case of the All Issues group it is a list of the ticket numbers with the description next to it. For the Issues by Priority it has children folders for the priorities and within these are the appropriate tickets.

On individual tickets you can right-click, and then click Show Raiser. This opens an Issue Tracking System dialog box containing the ticket raisers name.

If you right-click on a group of tickets, and then click Show Issues in Table it displays the group of tickets and their details in the Table Results view.