Page History

...

Table 11-1 File system permissions

J2EE Collector network ports

...

1. Click the drop-down menu to select the server where the JVM is running. If you want to add a new server, click Add. For more information, see see see Adding a new server on page 44.

   Info
   This is the name or IP address of the server where you want to install the J2EE Tier Collector. The server name appears in the list only if you previously defined it as a Precise Server. In upgrade mode, the list contains all servers that were installed or upgraded. Choose a server that was upgraded.

2. Select an auto-detected JVM from the "Detected JVMs" list. The remaining text boxes are auto-filled, but may be edited as needed.
3. If the JVM you want to monitor is not detected then proceed as follows:

   1. Click the drop-down menu to select the application server type.

      Info
      This is the type of the J2EE application server. Precise supports several J2EE application server types, including Oracle WebLogic, IBM WebSphere, Oracle AS, and Apache Tomcat.

   2. Click the drop-down menu to select the application server version.

      Info
      The next two items are optional, but are required to enable automatic execution of post-installation action items.

   3. Enter the full path to the Java executable.

   4. Mark the “WebLogic instance configured through admin console” check box.

      Info
      For Precise to instrument the JVM, it must modify its startup configuration. A WebLogic instance is configured using either a local file on the instance machine, or settings configured in the WebLogic admin console. Select this option if installing a WebLogic instance that is configured through the WebLogic admin console.

4. Enter the instance (JVM) name.

   Info
   The instance name should be an alphanumeric string to be used by J2EE, Insight, Alerts, and Report Manager to identify the monitored application server instance. The instance name must be unique to the monitored host.

5. Click Next. A preview of the planned installation will be displayed for approval at the beginning of the installation process.

...

1. 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"

   • 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.

2. Follow the apladmin instructions.
3. Add the -DisClustered=false flag to the arguments from apladmin. For a cluster, specify 'true' for this flag.

4. 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.

5. Enable Application Server Metrics by performing the following steps:
   1. 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.
   2. Verify that the initial specification level is "Basic" or "Custom."
   3. After Performance Monitoring Service is confirmed to be enabled at startup, perform the following steps to configure the Application Server Metrics collection:
      1. Select Servers > Application Servers > <SERVER_NAME> > Server Infrastructure > Administration > Custom Services.
      2. Click New.
      3. Mark the "Enable service at service startup" check box.
      4. Leave the External Configuration URL blank.
      5. Set the "Classname" to com.precise.javaperf.extensions.websphere.PreciseMetricPluginLoader
      6. Set the "Display Name" to PreciseMetricPluginLoader
      7. Set the "Classpath" to: <precise_root>/products/j2ee/lib/indepthmetric.jar
      8. Save the changes.
6. Update the security policy.

   1. 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 '/'.

7. Restart the Application server.

   Info
   For clustered applications, the user must verify that the rt.jar generated in step 1, and pointed to by the Xbootclasspath, is located in all the servers that are running as part of the WebSphere cluster. The user can copy the rt.jar to any central location, and update the Xbootclasspath accordingly.

...

IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal