Client-Server Connection Configuration

Use the client-server mode when the extension and the MQ server reside on different machines.
Authenticate the User
In this mode, you must first authenticate the Infrastructure Agent user who will access the MQ server. Running the
RunMQCommands
script executes a series of commands where you provide the authentication details of the Infrastructure Agent user that is used by the extension to connect with the MQ server.
Follow these steps
:
  1. Navigate to the configuration folder:
    Windows
    :
    <install-directory>\apmia\extensions\ibm-mq-ia-<xxx>\config
    folder and copy the following file:
    RunMQCommands.bat
    Linux
    :
    <install-directory>/apmia\extensions/ibm-mq-ia-<xxx>/config
    folder and copy the following file:
    RunMQCommands.sh
  2. Paste the file on to the MQ server.
  3. Execute the command; you will be prompted to provide the required details to authenticate the user.
Settings to Configure the Client-server Connection
Navigate to the
<install_location>/
apmia/extensions/ibm-mq-ia-<xxx>
directory and configure the bindings mode properties in the
bundle.properties
file.
Restart the Infrastructure Agent after configuring the settings.
  • introscope.agent.mq.monitor.profiles=<queue-manager-profile-name>
    Define the queue manager profile that you want to monitor.
    Example
    : introscope.agent.mq.monitor.profiles=QM1
  • introscope.agent.mq.monitor.profiles.<queue-manager-profile-name>.host=<ip-address-or-hostname>
    Define the IP address or HostName of the given queue manager that you want to monitor.
    Example
    : introscope.agent.mq.monitor.profiles.QM1.host=ibntest001467.bpc.broadcom.net
  • introscope.agent.mq.monitor.profiles.<queue-manager-profile-name>.port=<port-number>
    Define the port of the given queue manager that you want to monitor.
    Example
    : introscope.agent.mq.monitor.profiles.QM1.port=1515
  • introscope.agent.mq.monitor.profiles.<queue-manager-profile-name>.channelname=<channel-name>
    Define the channel name of the given queue manager that you want to monitor.
    Example
    : introscope.agent.mq.monitor.profiles.QM1.channelname=MQIA.CHL
  • introscope.agent.mq.monitor.profiles.<queue-manager-profile-name>.username=<user-name>
    Define the username with which the extension connects with the MQ server.
    Example
    : introscope.agent.mq.monitor.profiles.QM11.username=rm670259
  • introscope.agent.mq.monitor.profiles.<queue-manager-profile-name>.password=<password>
    Define the password corresponding the username.
    Example
    : introscope.agent.mq.monitor.profiles.QM1.password=RGm0U2soMTaYP6kEpZYtoQ==
Troubleshooting
Queue Manager is not connecting with port and Host Name
Symptom
: When trying to connect to the MQ server using the MQ server hostname and port, the connection fails.
The following message appears:
[WARN] [IntroscopeAgent.InfrastructureAgent] MQActivityQueueReader.run Could not connect to configuration instance: QMR|lvnprod009776.bpc.broadcom.net to read the activity reports from activity queue. Will try to connect to the configuration instance after 30 seconds
Solution
: This message appears when you provide the username at the runtime instead of defining it in the
bundle.properties
file. Even if the username has the required permissions, the infrastructure agent sends the
root
user without any permissions, which results in a failed connection.
Follow these steps:
  1. Stop the infrastructure agent by executing one of the following commands:
    • Windows
      :
      ./APMIACtrl.bat stop
    • Linux
      :
      ./APMIACtrl.sh stop
  2. Navigate to
    <install-directory>\apmia\conf
    folder and edit the
    wrapper.conf
    file.
  3. Add the following setting to allow the username at runtime:
    -Duser.name=<user_name>
    Example
    :
    -Duser.name=apmiauser
  4. Save the file and restart infrastructure agent by executing one of the following commands:
    • Windows
      :
      ./APMIACtrl.bat start
    • Linux
      :
      ./APMIACtrl.sh start