Kbase P109463: How to remove all remote monitoring on the remote containers and the Fathom host
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/07/2008 |
|
Status: Verified
GOAL:
How to remove all remote monitoring on the remote containers and the Fathom host
GOAL:
How do I remove all components installed when enabling remote monitoring
GOAL:
How to manually uninstall remote monitoring
FACT(s) (Environment):
Fathom for Management 3.X
All Supported Operating Systems
FIX:
This is a rather drastic measure so before doing so please ensure that the option -name <containername> in the fmconfig utility has been used on the remote machine. NOTE:fmconfig must be executed as user root on Unix systems and as a user with Administrator permissions in Windows systems.
eg: fmconfig -host <fathom_hostname> -name <container_name> [-enable | -update]
A.) Disable remote monitoring
The details for the Remote machine and Fathom AdminServer are different but the first step for both is to run "fmconfig -disable".
[Fathom machine]:
1) Shutdown the AdminServer
proenv -> proadsv -stop
2) Disable remote monitoring
proenv -> fmconfig -disable
3) cd to $FATHOM/SonicMQ
run uninstall.sh or uninstall.bat
4) cd to $FATHOM
delete the SonicMQ directory
delete smqinstall.log, smqinstall.err and SonicMQ.ini
5) cd to $WORKDIR
delete MFConfigurationElements.xsd, Fathom1.FathomAdminserver1.log
6) Search the whole machine for "vpd.properties", if found delete it:
eg: find / -name vpd.properties -print 2> /dev
ull
[Remote machine]:
1) Disable remote monitoring
proenv -> fmconfig -disable
2) cd to $DLC
delete MFConfigurationElements.xsd, container.xml
3) cd to $DLC/java/ext
delete the following jars:
activation.jar
ant.jar
antconfig.jar
gnu-regexp-1.0.6.jar
jndi.jar
js.jar
mail.jar
mfcontext.jar
mgmt_apps.jar
smq_install.jar
soap.jar
sonic_ASPI.jar
sonic_Client.jar
sonic_Crypto.jar
sonic_HTTP.jar
sonic_mgmt.jar
sonic_mgmt_client.jar
sonic_Selector.jar
sonic_SSL.jar
sonic_XA.jar
sonic_XMessage.jar
xerceslmpl.jar
xmlParserAPls.jar
4) cd to $WORKDIR
delete MFConfigurationElements.xsd, Fathom1.<name>.log and <name>.import
delete Fathom1.<name>.cache directory
NOTE: All the following files listed above may not be found, they are included it for completeness. The fact is that they /should/ be there, which can be checked next time remote monitoring is enabled.
B.) Enable remote monitoring
[Fathom machine]:
Before running fmconfig:
* The vpd.properties file must have been deleted. If it exists, fmconfig will fail to properly execute if there is a pre-existing vpd.properties file.
* fmconfig -update must be executed as user root on Unix systems and as a user with Administrator permissions in Windows systems.
* The correct java version for the Progress/OpenEdge version is in use.
1.) The AdminServer should still be shutdown at this stage
proenv -> proadsv -query
2.) Enable remote monitoring on the Fathom Management server
proenv -> fmconfig -enable [ -debug ]
3.) Start AdminServer, it should start without error. If any errors record th.em.
proenv -> proadsv -start
[Remote machine]:
4.) Stop the AdminServer on the Remote machine
proenv -> proadsv -stop
5.) Enable remote monitoring on the Fathom Management server
proenv -> fmconfig -enable -host <fathom_hostname> -name <container_name> -port 6835 -debug
6.) Restart the AdminServer. If any errors record them.
proenv -> proadsv -start.