RE: Can an OEM Plug-IN use the JavaWrapper fetchlet ?

Question

Hi:
- Can I create an OEM Plug-In using the JavaWrapper fetchlet for data acquisition ?
- If yes, can I add my own jar files to the OEM Plug-In archive
and call my own classes ?
And, what would be the path to my own jar files in the XML metadata file ?
IE, can I update the CLASSPATH ?
Thanks
John

Answer 1

Can I create an OEM Plug-In using the JavaWrapper fetchlet for data acquisition ?Yes
If yes, can I add my own jar files to the OEM Plug-In archive and call my own classes ?Yes, however, depending on the OEM Agent version, you will have to take different options
If you are using OEM Agent version lesser than 10.2.0.5:
You have two options:
- If you have necessary approval / license clearance to bundle jars as part of plug-in , do so.
- If not, you may need to ask EM/plug-in user to copy these jars to specific location on Agent_home
- In my case (for jdbcdrivers), I recommended the jars to be copied to $AH/sysman/jdbcdriver
- Ask the EM/plug-in user to update the $OH/sysman/admin/config/classpath.lst
(provide absolute path)
- Now, depending on how you have done the coding, i.e.,
- if you depend on JavaWrapperFetchlet - you can document that re-start of agent is required for the new
classpath takes effect
OR
- As you pointed out (reference to one of my earlier post), you need not use JavaWrapperFetchlet,
instead, use OSLineToken to invoke java (custom class) which can handle dynamic class loading.
Advantage in this is - no agent re-start.
Disadvantage - you will be invoking java process for every metric collection (quite an overhead)
However, if you are using OEM Agent version 10.2.0.5, things are much simpler. I believe, 10.2.0.5 Agent supportd additional property (which should reference to the absolute path of the jar location after plug-in deployment ) for JavaWrapperFetchlet and its done ! No agent re-start required. No java process invocation for every metric collection !!