Installation and Start Up
1. While installing the
bin files in Linux machines, the installation program quits abruptly
without any message.
Reason: This occurs when the DISPLAY
variable is not set.
Solution 1: If you are installing the
product in a non-GUI environment, execute the bin file as given below:
./AdventNet_ManageEngine_ApplicationsManager_8_0_0_linux.bin
-console
Solution 2: If you are installing the
product in a GUI environment, set the DISPLAY variable and then install
the product.
Example:
export DISPLAY=localhost:0.0 [To set the
DISPLAY variable]
xhost + [To provide permission for the remote hosts to open the GUI]
./AdventNet_ManageEngine_ApplicationsManager_8_0_0_linux.bin
[Question]
2. Applications Manager
displays "Enter a proper AdventNet license file" during
installation.
Reason1: If your system date is set to a future or a past
date, you will get this error message.
Solution: Uninstall Applications Manager,
set the system date settings to current date and time, and re-install
it.
Reason2: You might have have applied the Professional
Edition License in the Enterprise Edition Server.
Solution: You can check in AppManager_Home/conf/install.txt or AppManager_Home/conf/AMServer.properties
file. Here check for serverType. If you have got License for
professional Edition, you need to choose Applications Manager as
Professional Edition instead of Enterprise Edition while installing the
product.
Also, make sure that the license file is not corrupted. If
the problem persists, contact support@appmanager.com
with your licensing and contact information.
[Question]
3. I started Applications Manager,
but it quits stating "Port :9090 needed by Applications Manager
is being used by some other application. Please free the port
and restart Applications Manager."
Reason 1: When the Applications Manager is
started, its Web Server (Apache) starts in port 9090 by default. If the
port is occupied by other applications, you will not be able to start
Applications Manager.
Reason 2: You have shutdown Applications
Manager and tried to restart it but it's MySQL or Apache server
are still running.
Solution: Check if any other application
is using the same port number and/or MySQL and Apache are running even
after shutting down Applications Manager. If so,
Shutdown the MySQL, execute the file stopMySQL.bat located in <Applications Manager Home>/working/bin> directory.
Kill Applications Manager and restart it. (To kill Applications Manager -
Execute command : "shutdownApplicationsManager.sh/.bat -force" under Applications Manager Home directory)
If still not starting up,
For versions 8 and above,
Change the WEBSERVER PORT NUMBER (am.webserver.port) in AMServer.properties file under <Applications Manager Home>/conf> directory.
For versions below 8
To shutdown the webserver, execute the file ShutdownWebSvr.bat/.sh located in <Applications Manager Home>/working/apache directory.
To shutdown the MySQL, execute the file stopMySQL.bat located in <Applications Manager Home>/working/bin directory.
Try to restart AppManager
[Question]
4. After running 'startApplicationsManager.sh', an
error message "Failed to establish connection with web server.
Gracefully shutting down Applications Manager" is shown.
Reason 1: This happens in Linux if a library file
named libdb-3.2.so or libgdbm.so.2 is not available or
if it is available in another name. Apache Web Server requires this
file for it to start. To confirm this as the reason, open the stderr.txt
log file located in <Applications Manager>/logs directory
which should have the message "bin/httpd: error while loading
shared libraries: libdb.so.3 (or libgdbm.so.2):
cannot open shared object file: No such file or directory".
Solution1: If the log file has the below
error message
AppManager-Home/working/apache/bin/httpd:/lib/i686/libc.so.6:
version`GLIBC_2.3' not found (required by
Appmanager-Home/working/apache/lib/libdb-3.2.so or (libgdbm.so.2))
Then the library libdb-3.2.so or libgdbm.so.2, bundled in Applications
Manager may not be compatible with your version of Linux. Hence, remove
the file AppManager-Home/working/apache/lib/libdb-3.2.so (or
libgdbm.so.2) and try to restart the server.
Solution 2: As a workaround for this problem, you
can give the soft links for the libdb-3.2.so file or libgdbm.so.2
To do so,
- Login as root user in the machine.
- Go the /lib directory. In Linux Mandrake, go to
/usr/lib/
- Execute the command
ls -latr libdb* ( if it is for libdb-3.2.so)
or
ls -latr libgdbm* ( if it is for libgdbm.so.2)
-
The above command will return the files that are
starting with the name libdb (or libgdb).
- Check whether the file libdb-3.2.so (or libgdbm.so.2)
exists. If this is not present,
-- for libdb-3.2.so
Check whether the file libdb2.so.3 or any
higher version exists. If it exists then give the softlinks by
executing the following command in the /lib directory or /usr/lib
ln -s /lib/libdb2.so.3 libdb-3.2.so
If it is not present, then check for any other libdb file (libdb*). If
the file exists then give the softlinks by executing the following
command.
ln -s /lib/<libdb filename>
libdb-3.2.so
-- for libgdbm.so.2
- Check for any other higher version libgdbm file
(libgdbm*). If the file exists then give the soft links by executing
the following command from the /lib directory,
ln -s /lib/<libgdbm filename>
libgdbm.so.2 ( eg: ln -s /lib/libgdbm.so.3 libgdbm.so.2 )
- Exit from the root user and start the
Applications Manager.
- If you are still having problems, contact us at support@appmanager.com.
Also, go to <AppManager/working/apache/bin>
directory and execute the following command and let us know
the output of the command
ldd httpd
Note: If the host is not having the library
files, copy it from another linux host
Reason 2 : If it is not reason1, then in
some Linux machines, there is the problem of apache and tomcat having
started properly. But when a request is made, apache is not able to
communicate to tomcat
Solution:
Edit the workers.properties present in the Appmanager/working/apache/tomcat/conf/backup
directory
- Change the value of worker.ajp13.host to the
hostname or ipaddress of that machine. By default this value is
localhost.
- Then start the Applications Manager.
- Also before starting the Applications Manager, if
you have previously started the Apache alone by executing the
StartWebSvr.sh present in Appmanager/working/apache. Kindly stop the
same by executing the ShutdownWebSvr.sh present in the same directory.
[Question]
5. Having problems while starting Applications
Manager in Debian machines.
For Applications Manager to run in Debian machines,
Ensure if the following configurations are done.
# 1 Check whether the libdb3.so
file is located in /lib/ directory. For more information,
refer to answer 6.
# 2 Uncomment the following line in the
<Applications Manager Home>/working/apache/conf/backup/httpd.conf
file.
ScoreBoardFile logs/apache_runtime_status
# 3 Check whether the /tmp
directory in the Debian system has permissions for all the users. This
directory should have permissions for all the users. This can be
checked by creating a new dummy file.
# 4 Change the following property in AMServer.properties
file located in <Applications Manager Home>/conf
directory.
Default value is commented and it looks like
this.
#am.pingtest.command=/bin/ping -c 1 -w 1
Modify (uncomment) it as given below.
am.pingtest.command=/bin/ping -c 1 -i 1
[Question]
6. When trying to connect to
the web client using http://hostname:9090, I get "Forbidden. You don't
have permission to access / on this server." message. I've installed
the product under /root.
Reason: As the product is installed in
/root directory, you need to provide execute permission to /root to
access the web client.
Solution: To execute permission use the
following command (as superuser)
chmod +x root from /directory
[Question]
7. If Applications Manager is installed in a directory
that contains non-english characters then product is not getting
started.
Reason: This is because the absolute path
of the working directory will be updated in server.xml and tomcat wont
start if non-english charaters are present in server.xml.
Solution: As of now, Applications Manager
should be installed in a directory that has english characters only.
[Question]
8. When I try and start the server from the dos prompt,
I get the following message. "Could Not Find C:\ProgramFiles\AdventNet\ME\Appmanager\working\mysql\data\AMDB\STATSDATA*.*"
The system cannot find the file specified.
Solution: It is a simple warning message.
You can ignore it.
[Question]
9. When I try to start Applications Manager, it says
' Applications Manager is already running'. This happens even
after, I have verified that Applications Manager is not running.
Reason: The system in which the
Applications Manager has been installed would have been accidentally
restarted or shutdown. The file <am.lock> will remain in
the folder <AppManager_Home\working> to say that
Applications Manager is running.
Solution: If you are sure that
Applications Manager is not running, then delete the file <am.lock>
in <AppManager_Home>/working/> directory. Restart
Applications Manager.
[Question]
10. When the Server is started in Linux Machines with
root user and then after two three days when it is started as
normal user , the Server doesn't get started.
Reason: This is because the files in <working/mysql/data/AMDB>
will have permissions for the root user only.
Solution: Give all permissions for all the folders
in Applications Manager for normal user by using chmod
[Question]
11. If you get the message "The server is currently starting
up. This page will reload itself in 30 seconds, or you can click
here to reload it now to display the login page. If this problem
persists, please refer the troubleshooting section"
Reason: For the Applications manager to
run, Apache and an another main process should start. Only Apache used
by Applications Manager has started, in this case
Solution: Linux System:
Use shutdownApplicationsManager.sh with -force option found under
Applications Manager home (Execute command : "sh
shutdownApplicationsManager.sh -force" ) and use startApplicationsManager.sh.
Windows System : Use
shutdownApplicationsManager.bat with -force option found under
Applications Manager home. If Applications Manager is installed as
service, stop the Apache server in the services list
(ApacheApplicationsManager) and use startApplicationsManager.bat.
If none of the above options are working send Support Information
File to support@appmanager.com
[Question]
12. When I try to access Applications Manager
web client, I am getting the Error "The Page cannot be displayed".
I am not able to access any page in Applications Manager.
Reason: Apache uses the sendfile
syscall on platforms where it is available in order to increase the
speed of sending responses. Unfortunately, on some systems, Apache will
detect the presence sendfile at compile time, even when it does not
work properly. This happens most frequently when using network or other
non-standard file-system.
Confirmation: You can find the error message "core_output_filter:
writing data to the network" in the Apache logs.
Solution: Uncomment the line #EnableSendfile
off ( by removing # ) in AppManager_Home/working/conf/apache/backup/httpd.conf
file and save the changes. Then restart Applications Manager.
[Question]
13. While updating a service pack
or a patch, I get a message "The ppm file that you have specified
is not compatible with this product".
Reason: Service packs from Applications
Manager are in the form of a .ppm file. The Update Manager has some
useful validation incorporated related to this. This validation
includes compatibility checks. You cannot use update manager to install
an incompatible service pack. For example, you cannot install a service
pack of another product in Applications Manager or a service pack
of one version of Applications Manager in another version.
Note: If you have downloaded full build, do
not install Service pack of the same version. For eg, if the full build
no. is 6600, you will have SP6 in the service pack page. That service
pack is for customers who have downloaded previous versions of full
build like 6050, 6055 etc., By applying service pack SP6, the customers
can upgrade themselves to 6600.
[Question]
14. How to update the Service Pack if Applications Manager's
Server is a GUI-less linux server.
Solution: Use the following option in
UpdateManager script
updateManager.sh -c
[Question]
15. I am not able to perform any activity
in Applications Manager Web Client. Why?
Reason: You might have logged in to
Applications Manager with user access as 'Operator' where you can only
view the Monitor details. You will not have the privilege to configure
or edit the different components of the product.
Solution: To work with or configure the
product, log in as 'Admin' user. For more information on user access,
refer to the User
Administration section in the User Guide.
[Question]
16. Clicking on any link in Applications Manager
goes back to Login Screen.
Reason: DNS name of the machine would not
have been configured in their DNS Server.
Solution: Use the machines' IP Address to
connect to the client.
[Question]
17. Applications Manager's time is different
from my local time. How to reset it to my time?.
Reason: Your PC's time zone ( eg:
Brazil/DeNoronha ) is different from Applications Manager's java time
zone (eg: GMT ).
Solution: In startApplicationsManager.bat/startApplicationsManager.sh
file, add -Duser.timezone=Brazil/DeNoronha to the start
/B %JAVA_HOME%\bin\javaw line
If installed as service, add wrapper.java.additional.4=-Duser.timezone=Brazil/DeNoronha
in wrapper.conf file
Note: For Chennai, it should not be set as -Duser.timezone=India/Chennai.
Set it as -Duser.timezone=IST
See Forum
Link for more details on what needs to be set.
[Question]
18. In Linux, under Reports
tab, I try to check the health details of all monitors. I get the
following Java Exception: ErrorDispatcherValve[localhost]: Exception
Processing
ErrorPage[exceptionType=java.lang.Throwable,
location=/jsp/ErrorPage.jsp]
java.lang.ClassCastException: java.lang.NoClassDefFoundError
Solution: The display variable is not properly
set. Edit the the file under
<Appmanger8\ startApplicationManager.sh>
comment the following lines
# if [ "$DISPLAY" = "" ]; then
AWT_HEADLESS=-Djava.awt.headless=true
# fi
[Question]
19. Where do I find the log files that I
need to send to technical support team for analysis?
The log files are located in <Applications
Manager Home>/logs directory. You can send the Logs as Support
Information File (to create Support Information File - go to Support
tab in the product -> Applications Manager Support -> Click on Support
Information File)
To create Support Information File via Command Prompt, execute
createSupportFile.bat / createSupportFile.sh present under <Applications
Manager Home>/bin directory
If the size is less than 2MB, you can send the Support Information
File to support@appmanager.com
If the Support Information file is above 2MB and less than
100MB, Upload it to AdventNet site -
http://bonitas.adventnet.com/upload/index.jsp?to=support@appmanager.com
If the size of the file is larger than 100MB, you can ftp the
same to our ftp site. You will be provided details of the ftp
service usage when you connect to our ftp server using "ftp
ftp.adventnet.com"
Details of ftp site :
Server Name = ftp.adventnet.com
user account = anonymous
password = <<your email address >>
Once you have uploaded the file you can contact us with the
name/location of the file at support@appmanager.com
Note: You can also make use of the automatic HTTP upload
by selecting the option 'Create and upload to AdventNet Support
Center', while creating the Support Information File in the
Applications Manager Web Client.
[Question]
20. The ManageEngine® Applications Manager
service is setup Automatic but not started. When I'm trying
to start it up the following error message appears:
"Could not start the ManageEngine® Applications Manager
service on local computer. Error 1075: The dependency service
does not exist or has been marked for deletion".
Check whether the service "ApacheApplicationsManager"
is present under the services menu and also whether its Startup
Type is not Manual.
If not then navigate to the <AppManager8>/bin folder
in command prompt.
1. Execute the uninstallService.bat
2. Execute the installService.bat
Check whether two services ApacheApplicationsManager
and ManageEngineApplicationsManager are present in the
services menu and then start the ManageEngine Applications Manager
in the services menu.
[Question]
Monitoring - General
1. I
deleted a monitor from my Monitor Group, still the Monitor is
monitored.
Reason: Deleting a monitor from the monitor
group will only remove its association with the monitor group. This
will not stop its monitoring.
Solution: To delete the monitor also,
click 'Monitors' tab, select the monitor and click Delete. This will
remove the monitor completely.
[Question]
2. While adding a new monitor, it says
"Unable to get the Interface details. The IPAddress of the
given system is ..".
Reason: This is because the IP address of
the system returned by the SNMP Agent is wrong.
Solution:
1)Stop Applications Manager
2)Go to <Applications Manager Home>/working/conf>
directory
3)Edit the seed.file present there, change <ENABLE_SNMP_DISCOVERY="true">
entry to <ENABLE_SNMP_DISCOVERY="false">
4)Restart the Applications Manager and add the monitor again.
[Question]
3. While adding a new monitor the following
message is shown "Unable to add the system. Kindly check
whether it is reachable..".
Reason: This is because you are not able to reach
the system in any one of the following ways .
1)ICMP ping. Execute the below command in the command prompt and check
if ICMP ping is working.
ping <hostname>
2)SNMP ping.
Check whether SNMP Agent is running in the remote system you are trying
to monitor.
3)Native ping. This is disabled by default.
Solution: Enable any one of the
above 3, so that you would be able to reach the system.
To enable native ping, Edit <Appmanager/conf/AvailabilityTests.conf>
and Change <am.enablenativeping=false>
to <am.enablenativeping=true> [if you change the option
as true then start Applications manager as root in linux and admin user
in Windows ]
[Question]
4. When I click on 'View Monitor Details'
link after creating a new monitor, sometimes I am asked to reconfigure
the details of the monitor though I have created them successfully.
Reason: Polling is not yet started.
Solution: Wait for 30 seconds and then it
will display the monitor information. Here the data collection will not
be started. You can view the information only in the next polling
interval.
[Question]
5. Problem during Data Collection
or no performance data is displayed in my screens. Why?
Reason 1: Details such as user name and
password of the monitor may be incorrect.
Reason 2: In host resource, there are a few
requirements to be checked before starting its discovery.
Solution: To know details on the
prerequisites to monitor a system or host, refer to the Data
Collection - Host Resource section in the User
Guide.
Reason 3: Data collection may also be
hindered, if your system date is set to a future or a past date.
Solution: Check the Last and Next Polling
Interval time with your system time.
[Question]
6. No reports generated for icons
representing 7 and 30 days. Also, in Reports screen, on clicking
on any attribute for reports, it displays a message, "No
Data available to generate Reports for the specified time period".
Reason: Applications Manager archives the
data for every one hour. Though the monitoring of the monitors is
started, the reports are generated only after an hour.
Solution: Wait for a minimum of 1hour to
view the report.
[Question]
7. Scripts containing Java Programs, vbs
scripts and other executable files works fine while running
from the command prompt but gives error while monitoring them
from applications manager.
Reason: Applications Manager on executing
the script does not know the path for the java, cscript and other
executable files.
Solution: So, to monitor the script, the
path should be set within the script. If java is used inside the
script,make sure that the classpath is set for the java.
Add the below as the first line:
for linux :-
export path=<path>
for windows :-
set path=<path>
Where <path> is the full path that you get
when you type echo $path in linux and echo %path% for windows in the
command prompt.
[Question]
8. Not able to add monitors when the machine
has a different locale and is not SNMP enabled
Reason: To add a system as a Monitor to
Applications Manager, the following methods are used
1. Do a "ping " through code
2. If SNMP is enabled, check the SNMP agent and use data from it
3. Use Native Ping (ICMP Ping).
In this particular case, since the machine has a
different locale, normal ping method is ruled out. SNMP is also
disabled. If logged in as a normal user, Native ping will also not
work.
Solution: Native ping requires
Administrative privileges to work. So the user should be logged in as
Administrator while starting Applications Manager to solve this problem
and enable monitoring of the system.
[Question]
9. How do I set up a monitor for our Websphere
instance running on an iSeries (as/400) using the OS/400 operating
system?
Solution: You can add the websphere
servers directly for monitoring by choosing "WebSphere Server" from the
"Add Monitor of type" drop down box in New Monitor screen. The OS/400
will appear as unknown under the Servers category.
[Question]
10. I get the following message, "Authentication
failed. Kindly verify the username and password provided" while
adding server, Microsoft .NET, Exchange server through WMI
Solution: Kindly enter the username as <domainname>\<username>
[Question]
11. While monitoring windows applications
like Microsoft .NET, Microsoft Exchange, I get "Error # The
RPC server is unavailable". What should I do?
Reason: WMI or RPC server might not be
available in the remote machine
Solution: Check if the WMI and RPC services are
running in the remote machine.This you can check in the Services
window. If these services are not started , Start them and try adding
the monitors.
If there is a firewall in between Applications
Manager and the remote machine, Open the ports 135, 443 & 1025 in
the firewall, to enable access.
Also refer to server troubleshooting
question
Even after the above steps, if you get the error, send the Support
Information File with the details of your setup to support@appmanager.com
[Question]
12. Applications Manager is not adding the
monitor that has SSH2 running
Reason: SSH Key based authenication is
supported only for SSH2. Applications Manager will not add the monitor
(even though SSH2 is running) if the entry in
</etc/ssh/sshd_config> is 'Protocol 2,1'
Solution: Change the entry to 'protocol 2'.
Restart SSH2 deamon.
[Question]
WebLogic Monitoring
1. On discovering WebLogic server, a
message is displayed stating, "Data collection yet to start.
Please refresh this page after the data collection interval
has elapsed".
Reason: The MBean Authorization for
WebLogic 6.1 and 7.x is enabled that does not allow Applications
Manager to connect to the WebLogic Server.
Solution: Disable the authorization.
Refer to Creating
New Monitor - WebLogic Server in the User Guide for more
information.
[Question]
2. When I try to monitor WebLogic I get "Data
collection yet to start" even after I added -Dweblogic.disableMBeanAuthorization=true
to the WebLogic startup script.
Reason 1
Adding attribute AnonymousAdminLookupEnabled="false"
in SecurityConfiguration tag of Weblogic 8.1 config.xml
restricts MBean details from getting accessed from remote machines
without authentication.
Solution
Set the attribute value as false. For more
information:
http://e-docs.bea.com/wls/docs81/config_xml/SecurityConfiguration.html
#AnonymousAdminLookupEnabled
Reason 2
In Evaluation version of Weblogic, connection is
restricted to maximum 5. So request from Applicatoins Manager might be
blocked.
Solution
Try restarting your WebLogic instance and ensure
that Applications Manager collects data before the limit of 5
connections is reached.
Reason 3
Proxy Server blocking the connection to Weblogic
Server. Proxy Server might have been configured to allow only HTTP
requests.
Solution
Contact your system administrator.
[Question]
3. When I monitor weblogic server, I get the
message "Applications Manager could not register to the Weblogic
server for Data Collection" at the top. What should I do?
Reason
For monitoring the weblogic server, Applications
Manager tries to register a MBean in the Weblogic server. But for some
reason, the MBean could not be registered.
Solution
Ping Applications Manager server name from the machine
in which Applications Manager is running. check if the IP address is
not 127.0.0.1. If so, check the entry in the system's <hosts>
file[Windows: <C:\Windows\system32\drivers\etc\hosts>;
Linux: /etc/hosts]. If ping <AppManager hostname> returns
127.0.0.1 then, WebLogic will not be able to get the required
configuration from Applications Manager.
Check whether weblogic server host was able to connect to the
Applications Manager as we connect in the browser. ie for eg, http://<ApplicationsManager
hostname>:<portNumber>. This should be reachable.
Also check whether any error or exceptions are thrown on the weblogic
logs.
[Question]
4. When I monitor the weblogic server, I
get the message "Access to the weblogic MBean server is denied.
Enable "-Dweblogic.management.anonymousAdminLookupEnabled=true
-Dweblogic.disableMBeanAuthorization=true" in the weblogic startup
file." What should I do?
Reason 1
The mbean authorization is enabled and hence these
two properties must be enabled in the weblogic 7.x, 8.x and 9.x.
Solution
Disable the authorization. Refer to Creating
New Monitor - WebLogic Server in the User Guide for more
information.
Reason 2
In Evaluation version of Weblogic, connection is restricted
to maximum 5. So request from Applications Manager might be
blocked.
Solution
Try restarting your WebLogic instance and ensure
that Applications Manager collects data before the limit of 5
connections is reached.
[Question]
5. When I monitor the Weblogic server, I get
the message, "Data Collection in progress. Please wait till
the next poll interval".
Solution 1
Check whether weblogic server host was able to connect
to the Applications Manager as we connect in the browser. ie for eg,
http://<ApplicationsManager hostname>:<portNumber>. This
should be reachable. Also check whether any error or exceptions are
thrown on the weblogic logs.
Solution 2
Disable the authorization. Refer to Creating
New Monitor - WebLogic Server in the User Guide for more
information.
Solution 3
If you are using Free Edition, try restarting your
WebLogic instance and ensure that Applications Manager collects data
before the limit of 5 connections is reached.
[Question]
6. I'm not able to add Weblogic Monitor. What
could be the reason?
Solution 1
Check if there is any firewall between the Weblogic host
and Applications Manager machine. If this is the case, then open the
Weblogic host and the port in the Applications Manager side. Also note
that Weblogic should be able to contact Applications Manager in
Applications Manager's webserver port. By default this will be 9090.
[Question]
7. Applications Manager says, "There are
no JMS servers deployed in this Weblogic Server." but JMS data
is present in WebLogic Server. what is the problem?
Reason
JMS and SAF support is added to Applications Manager
only from version 7200. If an older version Applications Manager agent
is deployed in WebLogic server, then you need to restart the WebLogic
Server to get the JMS and SAF details.
[Question]
WebSphere Monitoring
1. I'm trying to monitor Websphere
6.X. I'm facing problem while adding the Websphere monitor".
Check whether Websphere admin user is added to the
monitor group of the perfservletApp, if global security is
enabled in Websphere.
Check whether you have deployed perfservlet in the
correct server.
And also, try to access any one of the below url and
send us the output along with the support information file.
Base Deployment
http://<WebSphereHost>:<WebSpherePort>/wasPerfTool/servlet/perfservlet?connector=SOAP&port=
SOAP-PORT
where
WebSphere Host -> Host in which WebSphere Application
Server is running
WebSphere Port -> HTTP Transport port of the
WebSphere Application server
SOAP Port -> SOAP Port of WebSphere
or
Network Deployment
http://WebSphereHost:Port/wasPerfTool/servlet/perfservlet?connector=SOAP&port=NetworkDeployerSOAP
-PORT&HOST=NetworkDeployerHost
WebSphere Host -> The host of the websphere
application server in which the perf servlet application is installed
Websphere Port -> HTTP Transport port of the
Websphere server in which the perf servlet application is installed
NetworkDeployer SOAP PORT -> The SOAP port of the
domain manager (DMGR)
Network Deployer Host -> The host in which the domain
manager is running.
Detailed information can be obtained from Prerequisites
for monitoring WebSphere Application Server Help.
Let us know if you are using a proxy server to connect
to websphere.
Else you can try this option:[ as suggested by a customer]
Instead of trying to reuse any existing ports which seem to be having some conflicts, you can define some new ports and transport chains.
1) In WebSphere Admin Console, Navigate to Application Servers -> Server Name -> Web Container Settings -> Web Container Transport Chains
2) In this view which shows current transport chains, click on New Button
3) In the resulting wizard at step 1, Give a new name to this chain (I gave it WC_CacheMonitor_Inbound) , and from the template Drop Down box select Webcontainer (Chain 1) and click on Next
4) In Step 2 , give this a new port name to identify it , and the host , port values, For the Port I gave 9030 when creating on instance 1 and 9032 when creating on instance 2. Click on Next.
5) In Step 3, Click on Finish button.
6) Repeat the above steps for each server in Cluster (I got 4 servers)
7) Save Configuration Changes.
8) Navigate to Environment -> Virtual Hosts, Click on New button
9) In the Wizard, give a new name and click on OK button.
10) In the resulting window click on the new Virtual Host created and click on Host Aliases for that Virtual Host.
11) Add the Virtual Host by making sure to reflect the Host and Port numbers (like 9030, 9032 etc) which have been already been created in the previous steps for Web Container Transport chains.
12) Save the Configuration Changes.
13) Navigate to Applications -> Enterprise Applications -> perfServletApp --> Map virtual hosts for Web modules
14) Select the newly created Virtual Host from the Drop Down.
15) Save the Configuration Changes, and restart all Servers.
16) The perfservlet is now accessible though ports 9030 and 9032 against the hosts configured
[Question]
2. Applications Manager says, perfservlet
is not installed, but perfservlet is present. What could be
the problem?
Solution
Check whether you are able to get the perfservlet.xml
while invoking the url with ipaddress. For eg.,
http://192.168.23.41:9080/wasPerfTool/servlet/perfservlet?connector=SOAP&port=8880
Check whether you have deployed perfservlet in the
correct server.
If it doesnot respond, then check whether the virtual
host is configured in the WebSphere Server. This you can check as
follows
1) Login to the admin console of the WebSphere Server.
2) Expand the Environment node and click Virtual Hosts.
3) Click "default_host" and click Host Aliases.
4) Now check whether the Host Name for the port 9080 is given as "*" or
hostname. If the hostname is given then you can change it to * , save
the configurations and restart the WebSphere Server.
5) Then add it in Applications Manager. If it is not able to change the
hostname in the existing entry, then you can add new entry for port as *
[Question]
3. When I try to add the Websphere server,
it gave an error message "service is not running" and monitor
is not added?
Solution
When Global Security is enabled the default transport
port may be disabled.
Please check the same in the following location and
enable it.
From administration console
Application servers > <server name> >Communications
>Ports> WC_defaulthost>
For WC_defaulthost, click on "View associated
transports" link then click on WCInboundDefault and check whether it is
enabled or not. If it is not enabled please enable it and restart the
websphere server.
Also check whether transport port of APPserver where
Perfservlet is installed is accessible from the browser.
Now try to add the monitor again.
[Question]
4. Why some of the tables don't have any
data or some of the fields have the value "NA" in the Websphere
details page?
Solution
1) Check whether you have set the PMI level to
"Standard" for version 5.x and "All" for version 6.x
2) Restart the Websphere server (all the Appservers in the Network
Deployement for ND) after the above change.
3) For version 6-
Go to servers->application servers -> <Appserver> ->
Performance -> Performance Monitoring Infrastructure
(PMI)
i) Enable the option Enable Performance Monitoring Infrastructure(PMI)
ii) Set the PMI level to "ALL" and restart the
particular Appserver.
For version 5-
Go to servers ->application servers -> <Appserver> ->
Additional properties -> Performance Monitoring Service
i) Set the PMI level to "Standard"
ii) Enable the option "server should start the service automatically at
startup" with the field name "startup".
iii) Restart the Appserver after the above configuration changes.
[Question]
JBoss Monitoring
1. While trying to monitor JBoss, I
get the message "No JBDC Connection pools are configured
for this Server".
Reason: No Database Connection Pools are
configured in JBoss server, i.e., no *-ds.xml file is present
in the JBoss deployed folder.
[Question]
2. While trying to monitor JBoss I
get error such as 'Unable to collect Data for <host name>'
and I do not get JVM and EJB details.
Reason 1: Applications Manager collects
JBoss MBean details by directly connecting to the JBoss JNDI Naming
service. The application http-invoker.sar which comes by
default with JBoss installation is used to access the JBoss JNDI
service. Ideally jbossagent.sar should have automatically been
deployed by the Applications Manager in the JBoss server as soon as it
is discovered. If this does not happen, you will get the 'Unable to
collect Data' message.
The Applications Manager should be able to access
the host where JBoss server runs and vice versa. If you suspect
accessbility issue, perform the following tests to ensure the same.
To ensure if the system where JBoss is installed
can be accessed, invoke the below URL from the system where JBoss is
installed: http://<Applications Manager
Host>:9090/classes/jbossagent.sar
To test whether the AdventNet Agent is deployed
properly in JBoss, go to the JMX Console in the JBoss server and check
if there is a domain named 'AdventNet'. Example: Go to the URL
http://<JBoss Server Host>:8080/jmx-console/ and check for
'AdventNet' domain. If each of the hosts is not accessible, then we
infer that the agent is not deployed.
Solution: To deploy the agent manually,
copy the file jbossagent.sar from <Applications Manager Home>/working/resources> directory and place it in the deploy
folder of the respective JBoss server and restart the JBoss server.
Reason 2: Using a customized version of
JBoss.
Solution: If you are using a customized
version of JBoss, the http-invoker.sar should be deployed in
the JBoss Server for Applications Manager to discover and manage it.
The application (http-invoker.sar) is by default deployed in the JBoss
server.
Reason 3 : The http port of the JBoss
server is changed.
Solution: If the http port of the JBoss
server is changed then the port number in the attribute InvokerURLSuffix
should also be modified in jboss-3.2.0\server\<jboss_server_name>\deploy\http-invoker.sar\META-INF\jboss-service.xml
file.
Make sure that the port number in the
<JBoss
home\server\<servername>\deploy\jbossweb-tomcat55.sar\server.xml>
file and
<JBoss
home\server\<servername>\deploy\http-invoker.sar\META-INF\jboss-service.xml>
file are same. If they are different, change the port number in
<jboss-service.xml file>
Note: InvokerURLSuffix occurs in many
places in the XML, wherever InvokerURLSuffix occurs, all the port
numbers should be changed. See a sample file - Sample_http_invoker_sar.html
which highlights all the ports that need to be changed.
Reason 4: When there are multiple IPs for
the machine in which JBoss is running.
Solution: To start JBoss with proper
bindaddress, use the command run.bat -b <ip address of the
machine> to start the JBoss server. To obtain the <ipaddress
of the machine>, execute the command ping <hostname>
in the host where Applications Manager is running.
Reason 5 : JBoss is installed in a different
network. Applications Manager can connect only to the JBoss server's
ipaddress and could not resolve its hostname
Solution: Add an entry for
jbosshostname/jbossip in <WINDOWS SYSTEM DIR>\drivers\etc\hosts
in the machine in which Applications Manager is installed so that
AppManager can resolve the JBoss host name. For linux add the entry in
/etc/hosts file. For AppManager to monitor jboss, both ip and hostname
should be accessible to Applications Manager.
Reason 5 : There is a firewall between JBoss and
Applications Manager.
Solution: Port in which JBoss is running (for
eg., 8080) and also, the Hostname should be accessible.
Also, try opening up RMI Object port (eg., 4444).
Refer http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall
[Question]
3. While trying to monitor JBoss, I do
not get JVM and EJB details, and a message "Select the JBoss
version. Edit Monitor to change the version." appears in the
top
Reason: JBoss is discovered automatically
and version of JBoss is not updated
Solution: Click the image for Configure to
get EJB, JDBC, JVM details and enter the version(3.2.x, 4.x) of the
JBoss.
[Question]
Tomcat Monitoring
1. Discovering Tomcat server fails
and it displays "AdventNet Agent has to be deployed for collecting
the data from Tomcat Server".
Reason: Tomcat 3.x and 4.x cannot be
discovered if AdventNet Agents are not deployed in it.
Solution: To discover Tomcat 3.x and 4.x,
download AdventNet agents, Tomcat3Agent.zip and Tomcat4Agent.zip
respectively, that are bundled with Applications Manager, into the
Tomcat server. For more information, refer to the Creating
New Monitor -Tomcat Server section in the User
Guide.
[Question]
2. Some Tomcat Web applications are
not monitored.
Reason: In Tomcat server 4.x, a deployed
Web application can be monitored only when web application responds to
any query. If there are no requests sent to the Web application, the
web application and its servlets cannot be identified and monitored.
Solution: Query the web applications of
Tomcat server 4.x. Note that, you have to do this only for Tomcat
server 4.x.
[Question]
3. I do not see the "Threads Availability"
graph for my Tomcat Monitor.
Reason: The data for the "Threads
Availability" will be shown only for 5.x versions of the Tomcat Server.
This data is not available for 3.x and 4.x version of Tomcat Server.
[Question]
4. When I try to monitor a Tomcat 5.x
server, I get the message "Authentication details are wrong".
Reason: Tomcat 5.x, an application named Manager
must be running in it for Applications Manager to monitor the Tomcat
server. By default, this application will be running in the server.
Moreover, the user role to access the server must also be manager.
Solution: To add a role as "manager"
for any of the users such as tomcat, role1, or both,
you need make changes in tomcat-users.xml file located in the <TOMCAT-HOME>/conf
directory.
Example:
Default configurations in tomcat-users.xml in
Tomcat Server.
<tomcat-users>
<user name="tomcat" password="tomcat" roles="tomcat" />
<user name="role1" password="tomcat" roles="role1" />
<user name="both" password="tomcat" roles="tomcat,role1" />
</tomcat-users>
After adding the roles for the "tomcat" user,
the modified entries will be as follows:
<tomcat-users>
<user name="tomcat" password="tomcat" roles="tomcat,manager"
/>
<user name="role1" password="tomcat" roles="role1" />
<user name="both" password="tomcat" roles="tomcat,role1" />
</tomcat-users>
On making the configuration, restart the Tomcat
Server.
Now, when adding a new Tomcat (5.x) monitor,
specify the username/password as tomcat/tomcat when discovering the
Tomcat Server.
[Question]
5. In Tomcat monitoring, some URLs/applications
that are not present in my Tomcat are shown. Why does this occur?
Reason: In 4.x and 3.x versions of Tomcat
Servers, we track all the requests that comes to the Tomcat Server and
from the requests we add the applications for Tomcat Server. Hence the
random URLs are shown.
