always.use.commander.registrar.url = true
The commander.registrar.url property specifies the Commander Server in the deployment. This is the Commander Server to which the mediators available for auto-assignment report.
The always.use.commander.registrar.url property set to "true" enables auto-registration for this probe. Note that when auto-auto-registration is enabled, the registrar.url setting in dispatcher.properties is ignored.
For details, see the comments for these properties in the etc/dispatcher.properties file.
Adjusting the Heap Size for the Java Agent in the Application Server
The size of the heap can impact the performance of the Java Agent and the application server. The default value for the heap size is 64 MB, but an application server usually increases it to a larger amount. When you add the Java Agent to an application server, you may need to increase the heap size to accommodate the memory used by the Java Agent. For details, see "Requirements for the Diagnostics Java Agent Host in theDiagnostics System Requirements and Support Matrixes Guidelocated on the HP Software Support Online Product Manuals site. Access requires an HP Passport login (registerfor an HP Passport).
The heap size is set in the application server JVM configuration using the following JVM argument:
-Xmx<size>
You can increase the heap size by updating the value specified in the -Xmx<size> option. See your JVM documentation for help on setting this parameter.
Configuring the SOAP Message Handler
The Diagnostics SOAP message handler is required for Java probes to support the following features:
l Collect payload for SOAP faults.
l Determine SOA consumer ID from SOAP header, body, or envelope.
For most application servers, the instrumentation points and code snippets are written to automatically configure the Diagnostics handlers for web services being monitored.
Note: For some application servers, special instrumentation is provided in Diagnostics to
automatically load the Diagnostics SOAP message handler.
However, some manual configuration is required for WebSphere 5.1 JAX-RPC and Oracle 10g JAX-RPC. See"Loading the Diagnostics SOAP Message Handler " below.
In addition, the Diagnostics SOAP message handler is not available for all application servers, nor is custom instrumentation available to capture SOAP faults or consumer IDs from SOAP payloads. Therefore, this feature is not available on all versions of all application servers. For the most recent information on Diagnostics SOAP message handler support, see the Diagnostics Support Matrix at
http://support.openview.hp.com/sc/support_matrices.jsp.
This section includes the following:
l "Disabling the SOAP Message Handler" below
l "Loading the Diagnostics SOAP Message Handler " below Disabling the SOAP Message Handler
By default, the SOAP message handler is enabled. You can disable the handler as follows:
In the <agent_install_dir>/etc/inst.properties file edit the details.conditional.properties property to include mercury.enable.autoLoadSOAPHandler = false.
If the SOAP message handler is disabled, you must manually configure where in the chain the handler gets installed.
Loading the Diagnostics SOAP Message Handler
The SOAP message handler is loaded automatically on most application servers but requires manual configuration on these application servers:
WebSphere 5.1 JAX-RPC
To configure the SOAP message handler on WebSphere 5.1 JAX-RPC, follow these steps:
Note: For WebSphere 6.1 JAX-WS web services, Diagnostics handlers are not supported.
You must recompile the application with the Diagnostics SOAP handler classes.
1. Locate the Web service deployment descriptor (webservices.xml) for the application. The directory path should look similar to the following:
<install_root>\config\cell\<Server>\applications\<WebServiceEAR>\deployme nts\<WebServiceName>\<WebServiceJAR|WARName>\WEB-INF
Here is an example:
C:\Program Files\WebSphere\AppServer\config\cells\MyServer1\application\WebS ervicesSamples.ear\deployments\WebServicesSamplea\AddressBookJ2WB.war\WEB-INF 2. Edit the webservices.xml and add the Diagnostics handler for each <port-component>:
<port-component>
...
<handler>
<handler-name>Diagnostics RPC Handler</handler-name>
<handler-class>
com.mercury.opal.javaprobe.handler.soap.ProbeRPCHandler
</handler-class>
</handler>
...
</port-component>
3. Copy the Diagnostics handler jar (<agent_install_dir>\lib\probeSOAPHandler.jar) to the WebSphere lib directory.
Here is an example:
cp C:\MercuryDiagnostics\JavaAgent\DiagnosticsAgent\ lib\probeSOAPHandler .jar C:\Program Files\WebSphere\AppServer\lib
These steps were developed with IBM WebSphere 5.1.0 Application Server on Windows.
Oracle 10g JAX-RPC
To configure the SOAP message handler on Oracle 10g JAX-RPC, follow these steps.
1. Locate the Web service deployment descriptor (webservices.xml) for the application. The directory path should look similar to the following:
<OC4J_install_root>\j2ee\home\applications\<app name>\ <deployment name>\
WEB-INF\webservices.xml
2. Edit the webservices.xml and add the Diagnostics handler for each <port-component>:
<port-component>
...
<handler>
<handler-name>Diagnostics RPC Handler</handler-name>
<handler-class>
com.mercury.opal.javaprobe.handler.soap.ProbeRPCHandler
</handler-class>
</handler>
...
</port-component>
3. Copy the Diagnostics handler jar (<agent_install_dir>\lib\probeSOAPHandler.jar) to the
<OC4J_install_root>\j2ee\home\applib directory.
These steps were developed with Oracle Containers for J2EE (OC4J) 10g Release 3 (10.1.3.3) on Windows.