AR System Java plug-in API

Overview

The Java plug-in API is a collection of classes, abstarct classes, interfaces, and relationships you can use to implement ARDBC, AREA, aan AR filter plug-ins in Java to run using the AR System 7.1 Java-based plug-in server. See the Integrating with Plug-ins and Third-Party Products guide for information about configuring the plug-in server and about setting up to use the Java plug-in API.

For product related issues or questions, contact Customer Support by e-mail at support@remedy.com.
For questions or comments about this documentation, e-mail us at doc_feedback@bmc.com.

Interfaces and abstract classes

The Java plug-in API includes an interface and an abstract class for each plug-in type. Your Java plug-in program must implement one of the interfaces or extend one of the abstract classes.

Java plug-in API interfaces

Interface
Extends
ARDBCPluggable
ARPluggable
AREAPluggable
ARPluggable
ARFilterAPIPluggable
ARPluggable

Java plug-in API abstract classes

Abstract class Extends Implements
ARDBCPlugin
ARPlugin
ARDBCPluggable
AREAPlugin
ARPlugin
AREAPluggable
ARFilterAPIPlugin
ARPlugin
ARFilterAPIPluggable

Classes, instances, and shared data

Two or more Java plug-in classes can be configured in a plug-in set or group as described in the Integrating with Plug-ins and Third-Party Products guide. When the plug-in server starts, it loads each configured plug-in class or group in a separate class loader and any static initialization in the classes is executed. Each time the AR System server makes a connection to a plug-in server, the plug-in server creates a new thread and, for each new thread, creates an instance of each plug-in class already loaded. Plug-in classes must load classes they depend on.

Different instances of a class can share data in the static class variables. To be thread safe, however, the class implementation must protect this static data. Plug-ins can also share data in a thread safe way by implementing the createInstance method for the plug-in. The server calls this method once for every instance of the plug-in created when a new thread is started. The instance data returned by createInstance is passed to every method. See the Java plug-in API online documentation for details.

The class can use instance variables to store data that is not shared. Because each thread has a separate instance, this data is thread safe.


BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

DB2 is a registered trademark of International Business Machines Corporation.

IBM is a registered trademark of International Business Machines Corporation.

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX is a registered trademark of The Open Group.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.