To begin monitoring IIB, you must install the IIB agent.
The document guides you on how to integrate Appdynamics IIB Agent on Linux and AIX. The installation steps for IIB agent for IIB v9 and v10 are the same for Linux and AIX. The installation steps for IIB ACE 11 are provided in a separate tab.
ACE is currently supported on Linux and AIX v7.2.
Specify the settings for the agent-controller communication. In the
controller-info.xml file, set the following properties:
account-name: Account name of the controller login.
account-access-key: Access key. This key is used for verification with the controller.
application-name: Name of the application that the IIB server belongs to.
controller-host: Hostname of the controller.
controller-port: Port number of the controller.
controller-proxy-host: Host name or IP address of any proxy required for the agent to connect to the controller.
controller-proxy-port: Port number of any proxy required for the agent to connect to the controller.
controller-proxy-username: Username for authenticating with the proxy.
controller-proxy-password: Password for authenticating with the proxy user.
controller-proxy-passwordfile: Full path name of a file containing the password for authenticating with the proxy user.
controller-ssl-enabled: SSL login. Set
controller-cert-file:Full path to the PEM format X509 certificate for SSL.
log-dir: Path to the directory containing the IIB agent log files. The default path is
/tmp/appd. Logs that are written before this configuration are logged in this path.
log-level: Level of the logs. Set this property to
Error is the highest priority and
trace is the lowest priority.
tier-name: Name of the tier representing the broker.
user-exit: Exit name of the user. This must be in the alphanumeric format, as provided to the
Run the following command to stop the broker. To configure user exits, your broker must be stopped.
Install the IIB agent user exit. Ensure that the IIB agent user exit is enabled by default, for all the flows. Perform the steps based on the version applicable to you.
The agent starts and stops with the broker, if it is installed on the broker.
Run the following command to start the broker.
For IIB 10, you can monitor a subset of your message flows. You can exclude flows that are of less importance from being monitored by running the following command:
mqsichangeflowuserexits <broker_name> -e <integrationServerName> -f <MessageFlow> -k <application_name> -i <user_exit_name>
AppDynamics IIB Agent creates a separate log file for each execution group. Therefore, each log continuously grows, even if the execution group is not instrumented.
Hence, a need to stop pushing the updates to the logs for non-instrumented execution groups arises. AppDynamics IIB Agent now allows you to configure the log file size according to your requirement.
The following setting in the configuration file,
controller-info.xml allows you to configure the log file size of the agent:
<log-settings> <log-setting broker="" execution-group=""> <max-file-size></max-file-size> </log-setting> </log-settings>
The settings are defined as follows:
|<log-setting broker="" execution-group="">||Broker name and the execution group name, which must be strings|
|<max-file-size> </max-file-size>||The maximum size of the log file. The format is |
However, you need to note the following guidelines for the configuration:
If you include the log setting, log-rotation is set to 1, else the default value of 5 is considered as the log rotation.
For example, in the following configuration, there are three instances of log setting:
The order of preference is mentioned in the following table. The preference order is defined as 1 → 2 → 3 → 4. Hence, if an order is invalid or does not match, then the next valid order is considered.
The following are the valid values, for different execution groups when used with the above example configurations.
If you experience any functional issues with the agent, review the following information and supply it to the AppDynamics Support.
/tmp/appdif the configuration has not been read at the time the message is logged. The status information can help diagnose issues with the agent.
If the user-exit name provided in the
If you have an issue with the agent or if you want to disable it, perform the following:
Perform the following based on the version applicable to you.
For IIB Agents that use the MQ mechanism, the MQRFH2 message header is used to provide correlation to downstream tiers. Any applications consuming MQ messages from an upstream IIB agent must support the MQRFH2 header standards to provide end-to-end correlation.
In a situation where the downstream agent reports the error MQRC_HEADER_ERROR (MQRC 2142) while parsing the message from an IIB agent via MQ, you can perform one of the following:
MQRFH2header structure by upgrading the downstream software to a version that supports
MQ PROPCTLproperty to
NONEon the destination queue. See https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.mig.doc/q008230_.htm for more details.
AppDynamics Monitor Agent tool adds an additional RFH header to the MQ message before adding the message to the queue. Because of this additional RFH header, IBM MQ .NET Clients may report an
MQRC_HEADER_ERROR (MQRC 2142) while parsing the message. Following is the sample RFH header that gets added to MQMessage.
RFH ….x…”…3…MQSTR ……..P…<usr><singularityheader
The RFH2 structure begins with <usr><singularityheader dt=”string” >. This RFH header is added by the AppDynamics Monitor Agent tool and not by MQ.
Perform the following steps to disable the additional header on the tool:
1. Go to Configuration -> Instrumentation -> Backend Detection.
2. Click on your application name, go to the .NET tab and click Queues.
3. Click Edit Automatic Discovery and in the popup window, clear the Correlation Enabled checkbox.