Extending Developer Studio

Developer Studio is composed of Eclipse plug-ins, which are modules of code that perform various functions. Some of these plug-ins have public extension points, which are ports through which they expose their functionality to other plug-ins and indicate which class or method to call to use that functionality. To add functionality to Developer Studio, you can create custom plug-ins with extensions that hook into these extension points. Through these connections, custom plug-ins can exchange API calls with Developer Studio and the AR System server.

Important

To create plug-ins for Developer Studio, you must be familiar with Eclipse plug-in development (see http://www.eclipse.org) and Java (see http://www.oracle.com/technetwork/java/index.html). Although BMC Customer Support is available to answer questions about BMC plug-ins and APIs, it cannot provide help with general Eclipse and Java issues that you encounter while developing custom plug-ins.

Related topic

Accessing-and-navigating-Developer-Studio

Installation directory for Developer Studio plug-ins

To integrate a custom plug-in with Developer Studio, put the plug-in's .jar file in the ARSystemInstallDir\DeveloperStudio\plugins directory.

Developer Studio Java API

To incorporate additional functionality (such as information about AR System objects and workflow) into custom plug-ins, use the public Java API calls in the com.bmc.arsys.studio.model plug-in.

These calls are described in the Developer Studio Java API online documentation, which is in the DevStudioInstallDir\files\DevStudioAPIdoc.zip file.

To access the documentation, unzip the file, and open the index.html file.


Action

Reference

Check the prerequisites listed in this topic before creating plug-ins.

Use the public Developer Studio plug-in extension points to create plug-ins that extend its user interface

Refer to the extension points for Developer Studio.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*