Hi Syed ,
Did you try the steps mentioned in the following KB article :
[url]https://empower.softwareag.com/sl24sec/SecuredServices/KCFullTextASP/viewing/view.asp?prdfamily=IBO&KEY=116632-4465756&DSN=PIVOTAL&DST=TCD[/url]
Mentioning the steps here in case you don’t have access to empower.
The steps are as follows:
-
Ensure EnableJMX is set to true for the realm to be monitored. Open the realm in Enterprise Manager and go to Config tab. Ensure EnableJMX under JVM Management is set to true.
-
Edit the UM config file. In v9.7, edit nserverdaemon.conf (if running realm as a Windows service) or nserver.conf if running as an application.
In v9.8, edit Server_Common.conf.
Look for the following existing line:
wrapper.java.additional.?=-Dcom.sun.management.jmxremote
Then add the following lines:
wrapper.java.additional.?=-Dcom.sun.management.jmxremote.port=X (this is the JMX port used to monitor the realm, eg. 8999)
wrapper.java.additional.?=-Dcom.sun.management.jmxremote.authenticate=false (this will disable password authentication ? see Note below)
wrapper.java.additional.?=-Dcom.sun.management.jmxremote.ssl=false
Replace ?? with a number that?s in sequence with the other numbers.
Note: This configuration is insecure. Any remote user who knows (or guesses) the JMX port number and host name will be able to monitor and control your Java application and platform. While it may be acceptable for development, it is not recommended for production systems.
-
Run Java VisualVM, i.e. a JMX tool.
-
First, add a JMX Connection.
-
Then, enter the UM realm host name and JMX port. Credentials are not required.
#webMethods#Universal-Messaging-Broker#Integration-Server-and-ESB