I am dropping a ManagementModule.jar or .xml in Intrsocpe###/deploy/ directory and the file disappears in a few seconds.
Tried to find the file with name command and I can't find it anywhere on the MOM box.
The file disappears after it is successfully deployed to the ./config/modules directory.
This is by design.
It is not going in ./config/modules
Even, if I run a global search, I can't find this .jar.
To add, if I drop .jar in /modules/ directory and restart MOM, it errors out as "the Supportability is already in use"
You cannot hotdeploy a module that already exists. You need to either stop the EM and overwrite the existing one, or delete the existing while the EM is running before attempting the hotdeploy.
I am not trying to overwrite an existing .jar.
I think that I am missing very basic here.
What are the steps to modify an existing .jar and rename it to use for another ManagementModule alerts?
You do not modify MM jar files directly. You should use the Management Module Editor in the Java workstation to make edits, copy elements, or make a copy of an entire module.
Yes, I didn't directly edit .jar
i copied one, edited managementmodule.xml, saved it as a different .jar and placed it in /deploy/ directory.
is there a knowledge base which can guide me.
this conversation is becoming lengthy and confusing.
We don't support you editing the XML. We don't support customized settings such as this.
You need to use the MM Editor make your edits and saves.
You can go here:
Create and Work With Management Modules - CA Application Performance Management - 10.1 - CA Technologies Documentation
This will tell you everything you need to know about working with. As Hiko_Davis mentioned above, DO NOT edit MM .jar in XML, rather do it in MM Editior which can be access via Java Workstation (for all APM versions) or WebView (for v10.x).
Please reach out to me directly if you have further questions or need help with MM.
This is in response to thread getting too long
Generally if I see new questions arise, I branch to a new topic to ease readability. If something is very lengthy, it may also be a good case candidate. But I agree that long community (or email threads) can take time to understand
I am going to mark this as answered since Hiko has responded to the key questions. You may ask followup questions as needed.