Request metrics provides build-in instrumentation to monitor transaction flows. The data that is collected by request metrics can be sent to a supported Application Response Measurement (ARM) agent.
The following tables show the ARM application properties when request metrics initializes an ARM 4.0 agent.
Identity property names | Value |
Cell Name | The cell name that the server belongs to. |
Version | The version of WebSphere Application Server. |
Application Properties | Value |
Registered application name | WebSphere:<server_type> The <server_type> can be APPLICATION_SERVER, ONDEMAND_ROUTER, or PROXY_SERVER. |
Application group | <server_name> |
Application instance | <node_name>.<server_name> |
String serverType; // the server type like APPLICATION_SERVER String version; // WebSphere version String sCellName; // the cell name of dMgr String sAppInstance. // <short_node_name>.<short_server_name> String sServerInstance; // short server name String sWasName = "WebSphere:" + serverType; String[] IDNAMES = new String[]{"Cell Name", "Version"}; ArmIdentityProperties appIdentity = txFactory.newArmIdentityProperties(IDNAMES, new String[]{sCellName, version}, null); ArmApplicationDefinition appDef = txFactory.newArmApplicationDefinition( sWasName, appIdentity, null ); ArmApplication app = txFactory.newArmApplication(appDef, sServerInstance, sAppInstance, null );
String[] contextNames; // the names for the context data like Port, QueryString, URI, EJBName String tranIdentityName; // the transaction types shown in the following table like URI, EJB. String appDef; // defined and created in above code snippet under ARM application properties String app; // defined and created in above code snippet under ARM application properties ArmIdentityPropertiesTransaction props = armFactory.newArmIdentityPropertiesTransaction( null, null, contextNames, null ); ArmTransactionDefinition atd = armFactory.newArmTransactionDefinition(appDef, identityName, props, (ArmID)null); ArmTransaction at = txFactory.newArmTransaction(app, atd );
This transaction type is the uniform resource identifier (URI) for servlet and JavaServer Page (JSP) requests. All of the following transaction types and context names are available in all types of servers.
Transaction type: URI |
|
---|---|
Context name | Description |
Port | The TCP/IP port where the request arrived, specified
as a string representation of the decimal value. Example: 9080 |
QueryString | The portion of the dynamic URI that contains the search
parameters of the request in the query segment of the URI string, excluding
the question mark (?) character. Example: selection=EJB&lookup=GBL&trans=CMT |
This EJB transaction type and context names are only available in application servers.
Transaction Type: EJB | |
---|---|
Context name | Description |
EJB name | The fully qualified Enterprise Java™ Bean (EJB) class
name, followed by method name with a period (.) to connect them. For example,
com.mypackge.MyEJBClass.mymethod. Example: com.ibm.defaultapplication.IncrementBean.create |
The Web services provider transaction type is for server-side Web services requests. This transaction type and the Wsdlport and Operation context names are available in all types of servers. The Transport, NameSpace, and InputMessage context names are only available in application servers.
Transaction type: Web Services Provider | |
---|---|
Context name | Description |
WsdlPort | The WSDL port name that is associated with the Web service. Example: AccountManager |
Operation | The operation name that is associated with the Web service. Example: createNewAccount |
Transport | The transport name that is associated with the Web service. Example: http |
NameSpace | The name space that is associated with the Web service. Example: http://accountmanager.mycorp.com |
InputMessage | The input message name that is associated with the Web
service. Example: createNewAccountRequest |
The Web services requestor transaction type is available only at DEBUG trace level. For other levels, Web services requestor is a block call. This transaction type and context names are only available in application servers.
Transaction type: Web Services Requestor | |
---|---|
Context name | Description |
WsdlPort | The Web Services Description Language (WSDL) port name
that is associated with the Web service. Example: AccountManager |
Operation | The operation name that is associated with the Web service. Example: createNewAccount |
Transport | The transport name that is associated with the Web service. Example: http |
Parameters | The parameters for the Web service request. Example: customerName,addressStreet,addressCity,addressState,addressZip |
The JMS transaction type is only for message-driven bean (MDB) scenarios in default messaging, including the System Integration Bus (SIB) layer and MQ. This transaction type and context names are only available in application servers.
Transaction type: JMS | |
---|---|
Context name | Description |
DestinationName | The destination queue name or topic name for the Java
Message Service (JMS). Example: MyBusiness.Topic.Space |
BusName | The service integration bus name for the JMS. |
MethodSelector | The method selector for JMS. |
MdbDiscriminator | The MDB discriminator. |
Topic | The topic name. |
The asynchronous beans transaction type is for asynchronous beans timers, alerts, and deferred starts. This transaction type and context names are only available in application servers.
Transaction type: Asynchronous beans | |
---|---|
Context name | Description |
Type | The type of asynchronous beans task. Example: COMMONJ_TIMER |
ClassName | The class name that executes the asynchronous beans
task. Example: com.mycorp.MyTaskClass |
For HTTP inbound, WebSphere Application Server checks the case sensitive HTTP header “ARM_CORRELATOR” for the incoming ARM correlator. The application server does not allow the flow of ARM correlators via HTTP outbound.
<soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <reqmetrics:arm_correlator soapenv:actor="reqmetricsURI" xmlns:reqmetrics="http://websphere.ibm.com"> 37000000000000000000 </reqmetrics:arm_correlator> </soapenv:Header>