Page History

...

• About configuring Precise for J2EE
• About configuring registry settings
• About configuring Precise for J2EE features
• About configuring EJB 3.0 monitoring
• About configuring JMS monitoring
• About configuring findings settings
• About configuring HTTP query parameters and Java method arguments capturing
• About file system security
• About monitoring settings for a J2EE remote instance

...

Precise for J2EE provides default monitoring for EJB 3.0 annotations. Metadata annotations are a key element in the developmental simplification of EJB 3.0 applications. Metadata annotations are used by the developer to specify expected requirements on container behavior, to request the injection of services and resources, and to specify object/relational mappings. Metadata annotations may be used as an alternative to the deployment descriptors that were required by earlier versions of the EJB specification.

While the EJB 3.0 specification allows (and promotes) defining EJBs using annotations, it is also still possible to use an XML deployment descriptor (the previous EJB 2.0 method). Since Because this is not automatically monitored by Precise, the following procedure must be run for the appropriate application server, as follows:•    WebLogic

WebLogic

To monitor EJB3.0 in a WebLogic environment using a XML deployment descriptor file only (no annotations)1.    Add

1. Add the following entry to the <i3_root>/products/i3fp/registry/clusters/j2ee/

...

1. <cluster-

...

1. name>/InstrumenterConfigLis t.xml file:
   <config-file>
        WeblogicEjb3Config-FD.xml
   </config-file>

...

1. Run the relevant CLI command as it appears in step 3 of

...

1. Instance registry or Cluster registry.

WAS

To monitor EJB3.0 in a WAS environment using a XML deployment descriptor file only (no annotations)1.    Add

1. Add the following entry to the <i3_root>/products/i3fp/registry/clusters/j2ee/

...

1. <cluster-

...

1. name>/InstrumenterConfigLis t.xml file:
   <config-file>
        WebSphereEjb3Config-FD.xml
   </config-file>

...

1. Run the relevant CLI command as it appears in step 3 of

...

1. Instance registry or Cluster registry.

Jboss

To monitor EJB3.0 in a Joss environment using a XML deployment descriptor file only (no annotations)1.    Add

1. Add the following entry to the <i3_root>/products/i3fp/registry/clusters/j2ee/

...

1. <cluster-

...

1. name>/InstrumenterConfigLis t.xml file:
   <config-file>
        JbossEjb3Config-FD.xml
   </config-file>

...

1. Run the relevant CLI command as it appears in step 3 of

...

1. Instance registry or Cluster registry.

Anchor
AboutConfigJMS AboutConfigJMS

About configuring JMS monitoring

By default, Precise for J2EE instrumentation of JMS calls is disabled, and must be manually configured to enable monitoring for transactions that use synchronous JMS. Since JMS is an asynchronous API, to configure this functionality the thread that initiates the JMS calls on the client-side must contain a method which calls both the JMS send and receive operations, and represents the bounds of the "synchronous JMS call".

Example    The For example, the following method could be configured as a JMS exit point:

public String sendSyncMessage (Message msg) {
// Do some things... MessageProducer.send(msg);
// Do some things...
Message reply = MessageConsumer.receive();
return reply.getText();

...

1. In the <i3_root>\products\j2ee\config folder of the instances that sample JMS client and server calls, add the following element to the j2ee\config\[instance_id]\instrumenterconfiglist.xml file:
   <config-file>
        JMS_Calls_AOP.xml
   </config-file>

...

1. In the j2ee instrumenter config folder, apply the following change to the j2ee\config\instrumenter\JMS_Calls_AOP.xml file:
   aspect.wrapper.target.class: jms.wrapper
   aspect.wrapper.target.method:
   sendSyncMessage
   aspect.wrapper.target.signature: *

...

1. Stop and restart the monitored JVMs.

Anchor
AboutConfigFindings AboutConfigFindings

About configuring findings settings

...