Configure the NeoLoad module for AppDynamics

When the AppDynamics integration module is enabled, the context for the Transaction names are made of the User Path names, Transaction names, and other action names by default. In the AppDynamics preferences panel, the Business Transactions group box makes it possible to select which element must be included in the Transaction names.

Transaction names can be composed of:

• User Path names
• Transaction names.
  For pages with multiple levels of Transactions or Sub-Transactions, the path consists of all of the Transaction names, for example Actions/Transaction1/Sub-Transaction.
  A page without a Transaction is associated with the default Container to which it belongs (Init, Actions, or End).
• Other action names to include Transactions like Loop, If...Then...Else, and so on.
  Conditional elements such as MyCondition...Then and MyCondition...Else are separated into different Transactions.

Before running any test, the Preview panel provides a summary of the information that NeoLoad includes in the requests headers for AppDynamics to read them. In AppDynamics, the elements of the Transaction names are separated with dots, as described in Read NeoLoad information in AppDynamics.