Importing a Metric Extension
Metric extensions can be converted to portable, self-contained packages that allow you to move the metric extension to other Enterprise Manager installations, or for storage/backup. These packages are called Metric Extension Archives (MEA) files.
MEA files are zip files containing all components that make up the metric extension: metric metadata, collections, and associated scripts/jar files. Each MEA file can contain only one metric extension. To add the metric extension back to your Enterprise Manager installation, you must import the metric extension from the MEA.
To import a metric extension from an MEA file:
- From the Enterprise menu, select Monitoring, then select Metric Extensions.
- Click Import.
- Browse to file location, and select the MEA file. Enterprise Manager checks if the target type and metric extension name combination is already used in the system. If not, the system will create a new metric extension. If the extension name is already in use, the system will attempt to create a new version of the existing extension using the MEA contents. This will require the MEA to contain a superset of all the existing metric extension's metric columns. You also have the option to rename the metric extension.
- Clicking on OK creates the new metric extension or the new version of an existing metric extension.
- From the Actions menu, select Edit to verify the entries.
- From the Test page, add available test targets.
- Click Run Test to validate the metric extension. The extension is deployed to the test targets specified by the user and a real-time collection is executed. Afterwards, the metric extension is automatically undeployed. The results and any errors are added to the Test Results region.
- Repeat the edit /test cycle until the metric extension returns data as expected.
- Click Finish.