Monitor Agile PLM Performance Is your Agile PLM environment starting to slow down or are you looking to monitor its performance? There are a number of tools out there to help with this, including the Java Console that comes with the Java Development Kit (JDK). This blog will provide basic instructions on how to enable the Agile PLM server deployment for remote monitoring.

1. Monitoring Agile PLM
with JConsole

2. About Us
 PLM Mechanic specializes in the technical
aspects of Oracle’s Agile PLM solution
 We offer the following service:
– Agile PLM installations and upgrades
– Agile PLM maintenance and help desk functions
– Agile PLM hosting
– Customization
 PLM Mechanic also has several product
offerings

3. Introduction
Is your Agile PLM environment starting to slow
down or are you looking to monitor its
performance? There are a number of tools out
there to help with this, including the Java Console
that comes with the Java Development Kit (JDK).
This blog will provide basic instructions on how to
enable the Agile PLM server deployment for remote
monitoring. Once you have this basic knowledge,
you will be capable of finding additional resources
online to add features like authentication for the
monitoring connection.

4. Setting up the Agile PLM Weblogic Server
1. Log into the Agile PLM host via RDP
2. Identify monitoring ports
3. From the command window execute: netstat –a
4. Find a port that is not being used: I will use port 9000 for
this blog
5. Navigate to AGILE_HOMEagileDomainbin
6. Open the install service file
7. We are interested in the “set CMDLINE” line.
8. Make a copy of the “set CMDLINE” line in the install service
file and comment it out (put rem in front of the line)

5. Setting up the Agile PLM Weblogic Server
(continued)
9. Go to the end of the active “set CMDLINE” line and paste
the following line before the very end (weblogic.Server)
-Dcom.sun.management.jmxremote.port=<port>
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

6. Setting up the Agile PLM Weblogic Server
(continued)
10. Replace port with the port identified in above. Here is an
example line after modification. Do not copy this line, it is
from a local dev server and will not offer the java
performance needed for a production environment!
set CMDLINE="-server -XX:MaxPermSize=256M -ms1280M -mx1280M -XX:NewSize=256M
-XX:MaxNewSize=256M -Dweblogic.Stdout=%STDOUT% -Dweblogic.Stderr=%STDERR%
-classpath "%CLASSPATH%" %JMX_SET% -Dweblogic.Name=dev-agile9312a-AgileServer "-
Dbea.home=C:OracleMiddleware" -Dweblogic.management.username=%WLS_USERNAME%
-Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE
% "-Djava.security.policy==C:oracleMiddlewarewlserver_10.3/server/lib/weblogic.policy"
-Dagile.log.dir=C:AgileAgile931/agileDomain/servers/dev-agile9312a-AgileServer/logs
-Dlog4j.configuration=file:.configlog.xml -Dcom.sun.management.jmxremote.port=9000
-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
weblogic.Server"

7. Setting up the Agile PLM Weblogic Server
(continued)
11. Save and exit InstallService.cmd
12. Stop the Agile services on the host
13. Uninstall the service by executing UninstallService.cmd
14. Reinstall the services by executing InstallService.cmd
15. Start the Agile service

8. Connecting a Client
 On a client machine open jconsole
(JAVA_HOME/bin/jconsole.exe). Mine
happens to be in C:jdk1.6.0_29bin
 Select the remote radio button
 For the host enter host:port – For my
environment, I selected entered dev-
agile9312a:9000
 Do not enter a username or password
 Click connect

9. JConsole Login

10. JConsole

11. Contact Us
 Web: http://www.plmmechanic.com
 Blog: http://www.plmmechanic.com/blog
 Twitter: @PLMMechanic
 Email: sales@plmmechanic.com
 Phone: 512-827-2262
 Fax: 512-582-2932