Adapter Microagents

You can use TIBCO Hawk microagents to supplement the monitoring information provided by the standard logging levels capability. Examples of supplemental information that you can obtain with microagents include the repository URL, command line arguments used to start the adapter, and so on.

Each adapter has three microagents, with different capabilities and names. The same microagent follows different naming conventions, depending on how an adapter is started: from TIBCO Designer, or from TIBCO Administrator.

  • Standard Microagent  Predefined in TIBCO Adapter SDK. You can use the microagent to perform queries on all running adapters, regardless of their class or application.

    • Naming in TIBCO Designer:

      COM.TIBCO.ADAPTER.adr3.%%Deployment%%.%%InstanceId%%

    • Naming in TIBCO Administrator:

      COM.TIBCO.ADAPTER.adr3.domainName.%%Deployment%%.%%InstanceId%%

    • Naming in TIBCO Administrator:

  • Class Microagent  Predefined in TIBCO Adapter SDK. You can use the microagent to perform queries on one class of the adapter.

    • Naming in TIBCO Designer:

      COM.TIBCO.adr3.%%Deployment%%.%%InstanceId%%

    • Naming in TIBCO Administrator:

      COM.TIBCO.ADAPTER.adr3.%%Deployment%%.%%InstanceId%%

  • Custom Microagent  Predefined in TIBCO ActiveMatrix Adapter for SAP. You can use the microagent to perform the adapter specific queries.

    • Naming in TIBCO Designer:

      SAPAdapterMicroAgent

    • Naming in TIBCO Administrator:

SAPAdapterMicroAgent