Page History
...
If the application server is running on an IBM AIX version 5.x computer, and you want to enable Precise for J2EE to report CPU numbers for each method invocation, set and export the AIXTHREAD_ENRUSG parameter as follows:
AIXTHREAD_ENRUSG=ON
export AIXTHREAD_ENRUSG
Anchor | ||||
---|---|---|---|---|
|
...
- For Java 1.5
- Add the following arguments to the Java command line of the JVM to be monitored:
- For an instance
-javaagent:<precise_root>\products\j2ee\lib\indepthj2ee-agent.jar=com. precise.javaperf.javaagent.agents.DefaultJavaAgent
-Dindepth.j2ee.server=<precise_root>\products\j2ee\config\<INSTANCE_NAME> -DisClustered=false For a cluster
-javaagent:<precise_root>\products\j2ee\lib\indepthj2ee-agent.jar=com. precise.javaperf.javaagent.agents.DefaultJavaAgent
-Dindepth.j2ee.server=<precise_root>\products\j2ee\config\<CLUSTER_NAME> -DisClustered=true
Info Be sure to use the
<JAVA_HOME>
that the application server uses, not the<JAVA_HOME>
located in the Precise product installation folder. The apladmin program will attempt to prevent any use of a JVM located under<precise_root>
.- For Java 1.4
- Configure instrumentation by executing the following command from the
<precise_root>
folder, replacing<JAVA_HOME>
with the path to the Java home of the application to be monitored:- Windows.
products\j2ee\bin\apladmin modrt --jvm-id=<instance (jvm)_name/cluster_name> "<JAVA_HOME>\bin\java.exe"
For example:
products\j2ee\bin\apladmin modrt --jvm-id=<instance (jvm)_name/cluster_name> "c:\j2sdk1.4.2_08\bin\java.exe"
UNIX.
products/j2ee/bin/apladmin.sh modrt --jvm-id=<instance (jvm)_name/cluster_name> "<JAVA_HOME>/bin/java"
For example:
products/j2ee/bin/apladmin.sh modrt --jvm-id=<instance (jvm)_name/cluster_name> "/opt/j2sdk1.4.2_08/bin/java"
Info Be sure to use the
<JAVA_HOME>
that the application server uses, not the<JAVA_HOME>
located in the Precise product installation folder. The apladmin program will attempt to prevent any use of a JVM located under<precise_root>
.
- Windows.
- Follow the instructions in the command output to modify the Java command line of the JVM to be monitored.
- Add the
-DisClustered=false
flag to the arguments from apladmin. For a clustered installation, specify 'true' for this flag. - After executing the apladmin.modrt, add the parameters to the JVM startup command line.
For example:
-Xbootclasspath/p:C:\Precise\products\j2ee\etc\apl\jvms\java-vm-TestApp\lib\rt.jar
-Xbootclasspath/p: C:\Precise\products\j2ee\lib\indepthj2eeboot.jar
-Xbootclasspath/p: C:\Precise\products\j2ee\classes
-Dindepth.j2ee.server= C:\Precise\products\j2ee\config\TestApp
-DisClustered=false
- Configure instrumentation by executing the following command from the
- For an instance
- Add the following arguments to the Java command line of the JVM to be monitored:
...
To manually execute the action items1. Start
- Start the cluster with Precise instrumentation by adding the following parameters to the Java command:
-javaagent:
...
<precise_
...
root>\products\j2ee\lib\indepthj2ee-agent.jar=com.precise.javaperf.javaagent.agents.DefaultJavaAgent
-Dindepth.j2ee.server=
...
<precise_
...
root>\products\j2ee\config\
...
<cluster_
...
name>
-DisClustered=true
...
- Repeat for each cluster started by the startup script.
Anchor | ||||
---|---|---|---|---|
|
...
To manually instrument a WebSphere instance/cluster1. Configure
- Configure instrumentation by executing the following command from the
<precise_root>
folder, replacing<JAVA_HOME>
with the path to the Java home of the application to be monitored.
...
- Windows.
products\j2ee\bin\apladmin modrt --jvm-id=
- Windows.
...
<instance (jvm)_name/cluster_
...
name> "
...
<JAVA_
...
HOME>\bin\java.exe"
...
UNIX.
./products/j2ee/bin/apladmin.sh modrt --jvm-id=
...
<instance (jvm)_name/cluster_
...
name> "
...
<JAVA_
...
HOME>\bin\java.exe"
Info
...
Be sure to use the
...
<JAVA_
...
HOME>
that the application server uses, not the
...
<JAVA_
...
HOME>
located in the Precise product installation folder.
...
- Follow the apladmin instructions.
...
- Add the
-DisClustered=false
flag to the arguments from apladmin. For a cluster, specify 'true' for this flag.
...
To enable RMI transaction monitoring, add the following text:
Dorg.omg.PortableInterceptor.ORBInitializerClass.com.precise.javaperf.lib.smartlink.PreciseSmartlinkORBInitializer
For example, the user will add the following arguments to WAS java arguments:-Xbootclasspath/p:C:\Precise\products\j2ee\etc\apl\jvms\java-vm-TestApp\lib\rt.jar
-Xbootclasspath/p: C:\Precise\products\j2ee\lib\indepthj2eeboot.jar
-Xbootclasspath/p: C:\Precise\products\j2ee\classes
-Dindepth.j2ee.server= C:\Precise\products\j2ee\config\TestApp
-DisClustered=false
...
Info Generally the
<JAVA_HOME>
for WebSphere installations can be found in the Application
...
> WebSphere variables section in the WebSphere Administrative Console.
...
- Enable Application Server Metrics by performing the following steps:
...
- Verify that the Performance Monitoring Service is enabled by marking the "Enable Performance Monitoring Infrastructure (PMI)" setting located on the Application Servers >
...
<SERVER_
...
NAME>
> Performance Monitoring Infrastructure (PMI) page.
...
- Verify that the initial specification level is "Basic" or "Custom."
...
...
- After Performance Monitoring Service is confirmed to be enabled at startup, perform the following steps to configure the Application Server Metrics collection:
- After Performance Monitoring Service is confirmed to be enabled at startup, perform the following steps to configure the Application Server Metrics collection:
...
- Select Servers > Application Servers >
...
<SERVER_
...
NAME>
> Server Infrastructure > Administration > Custom Services.
...
- Click New.
...
- Mark the "Enable service at service startup" check box.
...
- Leave the External Configuration URL blank.
...
- Set the "Classname" to
com.precise.javaperf.extensions.websphere.PreciseMetricPluginLoader
- Set the "Classname" to
...
- Set the "Display Name" to
PreciseMetricPluginLoader
- Set the "Display Name" to
...
- Set the "Classpath" to:
...
<precise_
...
root>/products/j2ee/lib/indepthmetric.jar
...
- Save the changes.
...
- Update the security policy.
...
Edit the
<WAS_INSTALL_
...
ROOT>/profiles/<SERVER>/properties/server.policy
file to include the following:grant codeBase "file:
...
<precise_
...
root>/-" {
permission java.security.AllPermission;
};Info
...
In Windows, change the PATH separator from '\' to the UNIX style separator '/'.
...
Restart the Application server.
...
Info For clustered applications, the user must verify that the
rt.jar
generated in step 1, and pointed to by theXbootclasspath
, is located in all the servers that are running as part of the WebSphere cluster. The user can copy thert.jar
to any central location, and update theXbootclasspath
accordingly.
Precise. Performance intelligence from click to storage. Learn more > >