1 Getting Started with Plug-in Development

1.1 About the Plug-in Creation Process

Creating a plug-in involves the following steps, all of which are covered in this book:

1. Designing your plug-in.

2. Developing the plug-in, which includes creating the requisite metadata files that enable the plug-in functionality.

3. Staging the plug-in.

4. Validating the plug-in.

5. Packaging the plug-in as an archive (.opar) file.

6. Importing the plug-in into Enterprise Manager Cloud Control.

7. Deploying the plug-in to Oracle Management Service.

8. Adding a target from your environment to initiate target monitoring. The plug-in files required by the Management Agent to monitor the target will be pushed to the Agent at this time.

9. Testing the plug-in to verify that it is behaving as expected.

As you continue to modify your plug-in metadata, you can upload your new metadata files to Enterprise Manager without re-deploying the plug-in archive using the Metadata Registration Service. See Section 13.7, "Updating Deployed Metadata Files Using the Metadata Registration Service (MRS)" for instructions on using this service.

In addition, to keep track of each updated version of your plug-in, you should incrementally update the plug-in version as follows in the following plug-in metadata files:

• In the PluginVersion attribute in the plugin.xml file that describes the plug-in to Oracle Management Service the plug-in is deployed to. See Section 2.4, "Creating the plugin.xml File".

• In the Version attribute in the plugin_registry.xml file that describes the plug-in to Management Agents the plug-in is deployed to. See Section 2.5, "Creating the plugin_registry.xml File".

1.2 About the Extensibility Development Kit (EDK)

A key component of the Enterprise Manager Cloud Control architecture is the Extensibility framework. To enable Oracle partners to extend the Enterprise Manager platform, an Extensibility Development Kit (EDK) is provided with the product.

The EDK is a collection of tools, utilities, and documentation, including:

• Enterprise Manager Extensibility documentation: Provide general guidelines for programming Enterprise Manager plug-ins

• Reference Implementation: Provides a reference code implementation, code snippets, and so on for various Enterprise Manager features

• Build time tools to verify EDK conformance: A tool that you can use to validate and report any violations, with respect to Enterprise Manager Extensibility guidelines

• Packaging Tool: A tool to package the plug-in components tool (empdk)

• Verification Tool: A tool to validate plug-in code components and to report violations (if any).

Enterprise Manager EDK includes a command line utility called empdk. Use this utility to package or validate a plug-in archive. For information associated with the empdk commands and their options, see Section 13.3, "Validating the Plug-in".

After you download the EDK, unzip it on your local system, and change your current directory to the location where you unpacked the EDK. The EDK contains reference documentation and guides to help you with plug-in development as well as the API reference you might need to integrate while developing plug-ins.

For information about downloading the EDK, see Section 1.3, "Installing the Extensibility Development Kit (EDK)".

1.3 Installing the Extensibility Development Kit (EDK)

Before you begin developing plug-ins, install the Extensibility Development Kit (EDK).

To install the EDK:

1. Download the EDK ZIP archive to your local system using one of the following options:

   • Enterprise Manager Cloud Control

     1. Log in to Enterprise Manager Cloud Control.

     2. From the Setup menu, select Extensibility, then select Development Kit.

        The Extensibility Development Kit (EDK) page appears.

     3. Under Installing the EDK, select Download the Extensibility Development Kit to your workstation.

     4. Save 12.1.0.2.0_edk_partner.zip to your local system.

   • Enterprise Manager Command Line Utility (EM CLI)

     Note:

     For information about setting up EM CLI, see Section 13.5.1.2, "Setting Up the EM CLI Utility".

     Open a command prompt and run the following command:

     emcli get_ext_dev_kit
     

     This command downloads the EDK zip archive to the same directory from where you ran the command and does not require any parameters.

2. Set your JAVA_HOME environment variable and ensure that it is part of your PATH. For example:

   setenv JAVA_HOME /usr/local/packages/j2sdk1.6.0_24
   
   setenv PATH $JAVA_HOME/bin:$PATH
   

3. Unpackage the downloaded EDK ZIP archive to a directory on your local system. For example:

   Unzip 12.1.0.2.0_edk_partner.zip
   

   This command creates the following directories under the directory (release_edk_partner) where you unpackaged the EDK ZIP archive:

   release_edk_partner
                      |
                       bin
                       doc
                       lib
                       oui
                       samples
                       README
   

   For more information about the directory contents, see Section 1.2.1, "Contents of the EDK".

1.4 Designing the Plug-in

Before creating your plug-in, you must first determine what information needs to be collected to monitor and manage the target type. This involves:

• Identifying performance and configuration metrics that should be collected.

• Determining how often each metric should be collected. Oracle recommends that the collection frequency for any metric should not be less than once every five minutes.

• Based on customer-specific operational practices, specifying default warnings and critical thresholds on these metrics. Whenever a threshold is crossed, Enterprise Manager generates an alert, informing administrators of potential problems.

1.5 Creating a Basic Plug-in

Ideally, begin by creating a basic monitoring plug-in that includes the basic required metadata:

• The target type definition file, which defines:

  • A required "Response" metric group, which includes a status metric and a performance metric.

  • Credentials needed to authenticate with the target.

  For more information, see Chapter 3, "Creating Target Metadata Files".

• A default collection file defining the frequency at which metrics and configuration data will be collected. For more information, see Section 3.5, "Creating the Default Collection File".

• Developing Oracle Business Intelligence Publisher (BI Publisher) reports to display collected target data.

  For more information, see Chapter 5, "Developing BI Publisher Reports".

Once created, you will validate and package your plug-in. See Chapter 13, "Validating, Packaging, and Deploying the Plug-in" for instructions.

As the final step, deploy your plug-in to Enterprise Manager Cloud Control and begin testing to ensure that data for the Response metric is being returned.

1.6 Creating an Intermediate Plug-in

When you have created a basic plug-in, you might want to enhance the plug-in's capabilities by adding more complex functionality.

• Add more complex metrics.

  For more information, see Section 3.4.3, "Defining Advanced Metrics".

• Provide the ability to collect configuration data for the target, which is used to create a "snapshot" of the target's configuration at a specific point in time.

  For more information, see Chapter 6, "Collecting Target Configuration Data".

• Create a metadata-based metadata custom user interface, which will essentially add a custom target home page for displaying target metrics to Enterprise Manager.

  For more information, see Chapter 8, "Defining a Management User Interface".

• Defining target associations, which can be used to create topology models of the targets managed by the plug-in.

  For more information, see Chapter 10, "Using Derived Associations".

• Define a job type that executes specific tasks specific to the target type.

  For more information, see Chapter 7, "Adding Job Types".

1.7 Creating an Advanced Plug-in

When you have successfully created and validated your basic or intermediate plug-in, you might want to enhance it with advanced features. Among the enhancements to consider:

• Adding the ability to automatically discover newly-added instances of the target type managed by the plug-in.

  For more information, see Chapter 11, "Defining Target Discovery".

• Building a Flex-based custom management user interface. This page will be accessed with other target home pages through the Cloud Control console.

  For more information, see Chapter 8, "Defining a Management User Interface".

• Define compliance standards and monitoring rules specific to the target type.

  For more information, see Chapter 12, "Adding Compliance Standards".