IBM Integration Bus, Version 10.0.0.9 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Configuring an integration server and loading the IBM Integration Bus Kibana dashboard manually

Start of changeYou can use the curl command and the mqsichangebluemixreporting command to configure integration servers to send logging information to the Logmet service in IBM® Bluemix™, and then use the mqsichangeflowstats command to enable accounting and statistics data to be reported to Logmet. You can then view the reported data in the IBM Integration Bus Kibana dashboard.End of change

Before you begin

About this task

This topic explains how to configure an integration server to report logging, statistics, and accounting data to Logmet, and load the IBM Integration Bus Kibana dashboard manually. However, you can use an alternative method, in which you use the mqsichangebluemixreporting command to specify your Bluemix service credentials directly, so that it can configure the server and load the IBM Integration Bus Kibana dashboard into your Bluemix space automatically. For information about how to use this method, see Configuring an integration server to send logging, statistics, and accounting data to a Kibana dashboard in IBM Bluemix.
Start of changeYou can configure your integration servers to report the following information to the Logmet service in Bluemix:
  • Logging, statistics, and accounting data
  • Logging data only
End of change

You can use the mqsichangebluemixreporting command to configure either a specified integration server or all integration servers on a specified integration node.

Start of changeTo enable the reporting of logging information to Logmet, you must use the mqsichangebluemixreporting command to enable your IBM Integration Bus integration servers to send the logging information to the Logmet host. If you also want to send statistics and accounting data in addition to the logging information, you must then configure the collection and reporting of statistics and accounting data by using the mqsichangeflowstats command.End of change

Procedure

Start of changeComplete the following steps to configure an integration server to send logging information to the Logmet service in IBM Bluemix:End of change

  1. Run the following curl command to obtain the logging token and Bluemix space identifier:
    curl -k -XPOST -d 'user= <BLUEMIX_USER>&passwd=<BLUEMIX_PASSWORD>&space=<BLUEMIX_SPACE>&organization=<BLUEMIX_ORGANIZATION>' <BLUEMIX_LOGIN_URL>
    where the BLUEMIX_LOGIN_URL for us-south is https://logmet.ng.bluemix.net/login, and for eu-gb is https://logmet.eu-gb.bluemix.net/login. You must specify the following Bluemix credentials in the command to obtain the logging token and Bluemix space identifier:
    BLUEMIX_USER
    Bluemix user name
    BLUEMIX_PASSWORD
    Bluemix password
    BLUEMIX_SPACE
    Bluemix space
    BLUEMIX_ORGANIZATION
    Bluemix organization
  2. Start of changeRun the mqsichangebluemixreporting command from the host machine that is running your integration node (typically on-premise) to configure and activate the logging, statistics, and accounting feature. For example, the following command specifies that all integration servers (as specified by the -g parameter) on integration node myIntegrationNode1, will report to Logmet using the results obtained from the output of the curl command:
    mqsichangebluemixreporting myIntegrationNode1 -g -l active -x logs.opvis.bluemix.net 
      -i b651725a-3af6-6718-1531-396ab8782dbc -t 1f7hYBjUxvMk
    You can set the logging status to active only if valid values are specified (or have been specified previously) for the following parameters: Start of change
    -x hostName:portNumber
    Sets the host name and, optionally, the port number for logging, statistics, and accounting services.
    For -x hostname, specify the following values:
    • If you are using IBM Bluemix region us_south, specify logs.opvis.bluemix.net
    • If you are using IBM Bluemix region eu_gb, specify logs.eu-gb.opvis.bluemix.net
    -i spaceID
    Sets the Bluemix space identifier for logging, statistics, and accounting services. Take this value from the output returned from the curl command in step 1.
    -t token
    Sets the Bluemix logging token for logging, statistics, and accounting services. Take this value from the output returned from the curl command in step 1.
    End of change

    For more information about required and optional parameters, see mqsichangebluemixreporting command.

    End of change

Start of changeWhen you have enabled your integration servers to send logging information to Logmet, you can enable them to also send message flow statistics and accounting data:End of change

  1. Start of changeRun the mqsichangeflowstats command, specifying bluemix as the output format in the -o parameter, and setting either the -a or -s parameter to active. For example, the following command turns on the collection of snapshot statistics data for all message flows in all integration servers for myIntegrationNode, and emits the data in bluemix format to the Logmet service:
    mqsichangeflowstats myIntegrationNode -s -g -j -c active -o bluemix  
    End of change
  2. Start of changeRestart the integration node (or all the integration servers that you have configured), for the changes to take effect. When the reporting status is active, data for all integration servers on the specified integration node will be sent to Logmet. Alternatively, if you specified a named integration server (by using the -e parameter), data will be reported for that integration server only.

    The default interval for sending events to Logmet is 60 seconds, so there can be a delay of up to 60 seconds before you see events in the Kibana dashboard.

    End of change
  3. Manually import the IBM Integration Bus Kibana dashboard into the Logmet service, by completing the following steps:
    1. Start your IBM Integration Bus integration servers.
    2. Login to your Logmet service using the same Bluemix credentials as used in Step 1 and, if necessary, switch to the same Bluemix organization and space. The Logmet URLs are:
      • For the us_south region: https://logmet.ng.bluemix.net/app/#/kibana4/
      • For the eu_gb region: https://logmet.eu-gb.bluemix.net/app/#/kibana4/
    3. Use the default Kibana views to ensure that logging events have been received from your configured servers. If there are no events, check your IBM Integration Bus local event log to see if there are any error messages. If there are errors, resolve them before continuing to the next step. The default interval for sending events to Logmet is 60 seconds, so there can be a delay of up to 60 seconds before you see events in the Kibana dashboard. By default, the Kibana dashboard shows events that it has received during the previous 15 minutes; if you do not see any events, you might consider increasing this time limit.
    4. Click the Kibana 4 tab, then click Settings.
    5. Click the first entry in the Index Pattern list, in the upper left corner of the window, to show the full index and reveal the action buttons.
    6. Click Reload field list and then click OK.
    7. Review the field list and ensure that it contains entries prefixed with iib_. These fields are IBM Integration Bus data that has been sent from your integration servers; for example, ibm_messageId.
    8. Select the Discover tab under Kibana 4.
    9. Click the Load saved search (open folder) button, then Manage searches. Navigate to the BluemixReporting subdirectory of the work path directory (as defined by the MQSI_WORKPATH environment variable), and then the integration node subdirectory. For example, C:\ProgramData\IBM\MQSI\BluemixReporting\myIntegrationNode. This folder contains your prepared IBM Integration Bus dashboard files.
    10. Select the file IIB_K4_query_< Bluemix space identifier >.json and import it.
    11. Select the Visualize tab under Kibana 4.
    12. Click Manage searches and navigate to the folder contains your prepared IBM Integration Bus dashboard files. To find these files, go to the BluemixReporting subdirectory of the work path directory (defined by the MQSI_WORKPATH environment variable), and then the integration node subdirectory. For example, C:\ProgramData\IBM\MQSI\BluemixReporting\myIntegrationNode. This folder contains your prepared IBM Integration Bus dashboard files.
    13. Select the file IIB_K4_visuals_< Bluemix space identifier >.json and import it.
    14. Select the Dashboard tab under Kibana 4.
    15. Click Manage searches and navigate to the folder contains your prepared IBM Integration Bus dashboard files. To find these files, go to the BluemixReporting subdirectory of the work path directory (defined by the MQSI_WORKPATH environment variable), and then the integration node subdirectory. For example, C:\ProgramData\IBM\MQSI\BluemixReporting\myIntegrationNode. This folder contains your prepared IBM Integration Bus dashboard files.
    16. Select the file IIB_K4_dashboard_< Bluemix space identifier >.json and import it.
  4. Start of changeYou can now view data from your configured and restarted integration servers, by logging into the Logmet service and opening the IBM Integration Bus Kibana dashboard. For more information, see Viewing logging information in the IBM Integration Bus Kibana dashboard in IBM Bluemix.End of change

What to do next

Start of changeYou can stop sending logging, statistics, and accounting information at any time by setting the -l parameter to inactive and then restarting the integration server.End of change

You can view the current configuration that has been set for reporting data, by using the mqsireportbluemixreporting command.


bz91188_.htm | Last updated 2017-07-17 12:46:57