XML file syntax

The XML file that you create for request mapper configuration must be valid XML and must remain available when the configuration is in use. Place the XML file in the dc_home/runtime/custom directory to use it for all application server instances, or in the dc_home/runtime/appserver_version.node_name.profile_name.server_name/custom directory to use it for one application server instance.

Top level

The top-level tag is <gpe>. Within this tag, use the <runtimeConfiguration> tag. These tags have no attributes.

Within the <runtimeConfiguration> tag, create a <requestMapperDefinition> tag. This tag must have a type attribute. Set it to the request mapper type name for the required request type. For more information, see Table 1.

Within the <requestMapperDefinition> tag, the following two tags must be present:

<symbolDefinitions>: Contains all definitions of symbols. Symbols represent values that the agent calculates every time a request of this type is detected.
<selection>: Contains the mapping of context keys to values. The keys represent the custom data that is passed to the agent. They are predefined for each request type. The mapping can be conditional.; For more information about request mapper enabling properties and type names, see Table 1.

Also, within the <runtimeConfiguration> tag, you can create a <requestMapperClassPath> tag. Within this tag, you can define JAR files. You can reference Java™ classes in these JAR files within Request Mapper definitions.