How CAN I execute jbossDebug.bat / jbossDebug.sh file?
This file is used to check if the connectivity and the Discovery of the Jboss Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the Jboss Server monitor. The usage to run this file is as below.
Via command prompt go to AppManager/bin/troubleshooting directory and execute the Jbossdebug file with the usage below.
Usage : jbossDebug.bat [HostName / Ip] [Port Number] [version] [ssl] [username] [password]
[HostName / Ip] HostName or Ipaddress of machine where jboss server is running
[Port Number] Port number of the jboss server (For 7.x versions, provide management native port(Default: 9999) or remoting port(Default: 4447).
For 6.x versions, provide rmiRegistryPort(Default:1090). For 5.x versions and below, provide web server port(Default: 8080))
For 6.x versions, provide rmiRegistryPort(Default:1090). For 5.x versions and below, provide web server port(Default: 8080))
[version] Version of jboss server ( 3.x / 4.0 / 4.0.1 / 4.0.2 - for 4.0.2 and 5.x versions / 6.x - for 6.x versions / 7.x for 7.x versions)
[ssl] If ssl is enabled, enter true. If no ssl and authentication enabled, enter false. If no ssl and no authentication enabled, leave it as blank
[username] User name for connecting to jboss. If no authentication enabled, leave it as blank
[password] Password for connecting to jboss. If no authentication enabled, leave it as blank
This will initiate the process to discover the Jboss Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this you will be able to find If discovery is possible, If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the Jboss installed server.
New to ADSelfService Plus?
Related Articles
How to execute runWLSMbean.bat or sh file?
Execute the runWLSMbean.bat or sh file from the <AppManager_home>\bin\troubleshooting folder via command prompt or terminal. Eg. ~/Zoho/ManageEngine/ManagedServer/AppManager15/bin/troubleshooting$ ./runWLSMbean.sh It will prompt for the details to ...How to execute ServerSSHTroubleshoot.bat or sh file ?
Solution: Execute the file ServerSSHTroubleshoot.bat or sh from the <AppManager_home>\bin\troubleshooting folder (<AppManager_home>\bin in older versions of Applications Manager). Via command Prompt Execute the ServerSSHTroubleshoot.bat or sh file. ...How can I execute the GlassFishDebug.bat / GlassFishDebug.sh file?
Note: Although the script name mentions GlassFish Server, the script file can be used for troubleshooting any monitor connectivity issues, that comes under JMX mode of monitoring like JMXApplications, Apache Zookeeper, Apache Geronimo etc., This file ...How can I execute UpdateHostnameandIP.bat/sh ?
Here are the steps to execute UpdateHostnameandIP.bat/sh: 1) Execute <AppManager_Home>\bin\troubleshooting\UpdateHostaneandIP.bat/sh file. For example, updateHostNameAndIp.bat/sh [Previous HostName/IpAddress] [new HostName/IpAddress] ...How to execute WebsphereMQDebug.bat / WebsphereMQDebug.sh?
This file is used to check if the connectivity and the Discovery of the Websphere MQ Server is possible from the Applications Manager server. This standalone program is an excerpt of the same process we use to add the Websphere MQ Server monitor. The ...