Page History

...

It is highly recommended to specify the JVM name in the JVM arguments as described in JVM arguments! If you did not follow the recommendation, the JVM name will be resolved automatically in the following way:•    For

• For WebLogic and WebSphere JVMs running as WebLogic/WebSphere console managed servers correspondingly, the JVM name will be set to the server name if it was not specified explicitly.

...

• For the rest of the JVMs the JVM name will be set to <server_name>_<running_number>,

...

• where <server_name> is the name of the server on which the JVM runs,

...

• while <running_number> will help to distinguish between different JVMs running on the same server, but using different extracted Precise folders.

...

• ***(Requires testing and decision if we support this case!!!!)***If more than one JVM will be run on the same server using the same extracted Precise folder and for none of them the JVM name argument is supplied, the activity of both JVMs will be presented in the same invocations tree and the metrics values will be displayed as average values between all the JVMs.

Shared script JVMs

If several JVMs are sharing the startup script where Precise JVM arguments were added, all of them will be started up with the same JVM name, whether it was specified or not. In such case all the data of the JVMs will be presented in the same way as described in the third bullet of JVM naming.

Advanced installation notes

This section contains advanced installation notes.•    If

• If you have uninstalled a remote J2EE instance, and you want to install it again, on the Precise FocalPoint remove the products/infra/var/<INSTANCE_NAME>_id.txt file from the local extraction folder, and restart the JVM.

...

• By default, the reinstalled instance includes history data from the previously uninstalled instance. If the server name or instance name has changed and you want the newly installed instance to include the history data of the previously uninstalled instance, you can add the following property after the removal of

...

• the products/infra/var/<INSTANCE_NAME>_id.txt file and before restarting of the JVM:
  -DPRECISE_SSL_RECOVERED_ID=<PREVIOUS_ID>

The find the related instance ID, use the get-instance-id command, see Installing a new instance while keeping historical data from an old instance on page 82.

...

This section describes the installation procedure for WebSphere and if Java 2 Security is enabled.

Installation procedure for WebSphere

For J9, add the following to the JVM argument:

-javaagent:<PRECISE<PRECISE_LIB>LIB>\products\j2ee\lib\indepth\indepthj2eej2ee-agent.jar=com.precise.javaperf.javaagent.agents.IBMJavaAgent

For example:

-javaagent:E:\Precise\products\j2ee\lib\indepth\indepthj2eej2ee-agent.jar=com.precise.javaperf.jav aagentjavaagent.agents.IBMJavaAgent

For all the others, add the following to the JVM argument:

-javaagent:<LOCAL<LOCAL-LIB>LIB>/products/j2ee/lib/indepth/indepthj2eej2ee-agent.jar

Alternatively, you can run the displayParams script, which will generate the JVMparameter.

Java 2 Security is enabled

Perform the following procedure.

To determine whether or not Java 2 Security is enabled1.    Connect

1. Connect to the WebSphere admin console with a user that has administration rights.

...

1. In Admin Console>Security>Global Security, check if the Java 2 Security check box is checked.

   ...

   1. 1. If Java 2 Security is enabled, certain permissions need to be explicitly granted in a server.policy file.

      ...

      1. 1. 1. Determine the location of the server.policy file. This can be found by examining the JVM startup command and locating the

      ...

      1. 1. 1. Djava.security.policy argument. It typically looks like this:
               -Djava.security.policy=

      ...

      1. 1. 1. <IBM Installation

      ...

      1. 1. 1. folder>\WebSphere\AppServer\profiles\

      ...

      1. 1. 1. <PROFILE>\properties\server.policy

      ...

      1. 1. 1. where <PROFILE> is the profile name.

      ...

      1. 1. If no such argument is found, add one using the above example.

      ...

      1. Add the following to

      ...

      1. the server.policy file:
         grant {
         permission java.util.PropertyPermission "indepth.j2ee.classLoaderHandle", "read";
         };
         grant codeBase "file:

      ...

      1. <PRECISE_

      ...

      1. LIB>/-" {
         permission java.security.AllPermission;
         };

      ...

      1. Info
         The <PRECISE_LIB> inside the server.policy file needs to be specified using URL format. For example: Windows grant codeBase "file:/E:/Precise/-" { permission java.security.AllPermission; }; UNIX grant codeBase "file:/opt/precise/-" { permission java.security.AllPermission; };

      ...

      Anchor
      #Additionalinformation #Additionalinformation

      Additional information

      For information on uninstallation of the remote J2EE instance, see the Deleting a Tier instance or cluster and Uninstalling a J2EE remote instance sections in the Precise Installation Guide.

      For information on monitoring settings for a remote J2EE instance, see the About monitoring settings for a remote J2EE instance section in the Administration Guide.

      Precise. Performance intelligence from click to storage. Learn more > >

      ...