The naming logic varies depending on the application technology. For example:

• For web-oriented technologies that have URI entry points such as Java Servlets, detection rules name the transaction using the first two segments of the URI by default. See URI Based Entry Points.
• For message-oriented technologies such as an asynchronous message listener or message-driven bean (JMS), the agent names the business transaction for the destination name (the queue name) or the listener class name (if the destination name is not available.)
• For Web services, the agent names the business transaction for the Web service name plus the operation name.