Introduction

AWM is a highly extensible framework that you can use in the following ways to customize the behavior of an application:

• Using the AWM modeling capabilities to define the user interface and tool integration. For example, modeling AWM Properties, Element Types, Action Descriptors, Tool Descriptors, and so on.
• Using standard AWM tool descriptors to run Eclipse or Enterprise Developer-based functions or to execute programs or scripts on supported platforms. For example, open a file in the COBOL editor, execute a REXX procedure on the mainframe, or run a Windows batch script.
• Using the AWM plug-in API to access specific AWM functions or interfaces. For example, define a new AWM system type to provide AWM models from custom locations.
• Extend standard modeling capabilities by implementing new function packages using the AWM plug-in API. For example, create a function package to provide new AWM modeling capabilities for a third party or home-grown software configuration management tool.

An AWM administrator can define complex workflows by using the AWM standard modeling capabilities. This needs an understanding of the AWM model and how to attach tools to AWM which is described in detail in the modeling and tool attachment chapters.

This section explains the capabilities and how to use the AWM API to provide Eclipse extension points where the AWM functionality can be extended.

The following sub topics contain tutorials explaining how to make use of the AWM plug-in functionality and how to extend an AWM extension point. The AWM extension is based on the AWM model extension point which is the most important extension point provided by AWM.

This chapter requires basic knowledge about Java programming and Eclipse plug-in development.