Database Reference
In-Depth Information
Deploying the plug-in on the Enterprise Manager system : EM12c administrators import a plug-in
from the OPAR file and deploy it on the OMS, making it available for end users. End users can
then add new targets to monitor and manage.
As you go through the examples in this chapter, you will see how to iterate through this cycle during plug-in
development. First we'll cover how to set up your development environment.
Development Environment
I recommend that you have a dedicated EM12c plug-in development environment. It's easier to analyze the logs
during troubleshooting and to fully isolate the issues you might encounter. Some of your activities as a plug-in
developer might cause disruption to the environment, so it's safer to have a development environment than to
develop on a shared EM12c system and risk affecting other users.
A single virtual machine (VM) works very well for that purpose. I use two virtual processor cores and 6GB of RAM
for my virtual machine on my laptop. You can get away with a single core and 3-4GB of RAM, but make sure you have
a reasonable swap size, as you will be using some Java tools in addition to running the EM12c environment itself. If
you don't have enough memory or swap, you might experience weird failures while using the empdk command-line
tool for packaging a plug-in, for example.
My development VM with Oracle Enterprise Linux hosts the EM repository, OMS, and the agent. I also installed
and configured the Extensibility Development Kit (EDK) in that same VM. This way, I have a complete development
environment on a single VM. It pays to keep backups of your development VM in case you cause any inconsistencies
to your EM12c repository, as you will be creating and deleting objects in the SYSMAN schema as well as some metadata
records.
You might want to do the development on your workstation where you have your favorite development tools and
editors (mine is vi, so I'm all set on the VM). In this case, you should install the Enterprise Manager Command Line
Interface (EMCLI) there before installing the EDK. For detailed instructions on installing EMCLI, refer to Chapter 1 or
navigate to Setup Command Line Interface in your EM12c console.
Extensibility Development Kit
The Extensibility Development Kit (EDK) has several components:
Plug-in development tool used to verify and package plug-ins.
Reference documentation that includes PDF versions of the two extensibility guides noted
earlier and XML Schema Definition documentation that contains all possible XML elements
much more than described in the PDF but description of most of the elements is either
missing or very brief so you would be experimenting a lot if you want to use undocumented
options.
Plug-in samples. As of EDK release 12.1.0.2, multiple variations of the same plug-in are
provided: the Host Sample plug-in. The versions differ in the functionality they implement,
becoming progressively more complex and feature rich. The previous EDK version had only
one sample plug-in, and the amount of files, code, and features implemented was simply
overwhelming for beginners, so it was really difficult to use it as an example.
The best way to install the EDK is to navigate to the EM12c console: choose Setup Extensibility Development
Kit, and follow the instructions. In a nutshell, you download a zipped distribution, uncompress it in a folder of your
liking, and having set a proper environment, you can call the empdk utility. I usually make sure I have both empdk and
emcli in my path. I will refer to the location of EDK as <EDK> when I need to make it part of the path.
 
Search WWH ::




Custom Search