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


mqsireportbluemixreporting command

Use the mqsireportbluemixreporting command to report the current status and configuration of the Bluemix™ reporting function for a specified integration server or for all integration servers on the specified integration node.

Supported platforms

Purpose

Use the mqsireportbluemixreporting command to display the current status and configuration of the Bluemix reporting function, either for a specific integration server or for all integration servers on the specified integration node.

Start of changeThe mqsireportbluemixreporting command displays the current reporting status and configuration, including the parameters that have been set for reporting startup and usage information to a Product Insights service, and parameters that have been set for sending logging, statistics, and accounting data to the Logmet service in IBM® Bluemix.End of change

IBM Cloud Product Insights is a Bluemix service that is part of IBM Connect to Cloud. Ensure that your version and fix pack level of IBM Integration Bus is compatible with the level of the Product Insights service before you enable IBM Integration Bus to connect to it.

The output of the mqsireportbluemixreporting command shows the values set by the mqsichangebluemixreporting command, and includes the following information:
  • The current state (active or inactive) for the reporting of startup and usage information to a Product Insights service
  • The API host for the startup and usage service in Product Insights
  • The API key for the startup and usage service in Product Insights
  • Start of changeThe URL of the HTTP proxy server (if any) through which the connection is made to the startup and usage service in Product Insights.End of change
  • The optional group name for the startup and usage service in Product Insights
  • The reporting interval for the usage service in Product Insights, in minutes
  • Start of changeThe current state (active or inactive) for the reporting of logging, statistics, and accounting data to the Logmet serviceEnd of change
  • Start of changeThe host name and port number for the logging, statistics, and accounting servicesEnd of change
  • Start of changeThe Bluemix space identifier for logging, statistics, and accounting servicesEnd of change
  • Start of change The tenant logging token for logging, statistics, and accounting servicesEnd of change
  • Start of changeThe interval, in seconds, for sending information to the logging, statistics, and accounting service.End of change
  • If the integration server has been configured with the option to provide the user's Bluemix details, these details (with the exception of the password) are reported.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-mqsireportbluemixreporting--integrationNodeName-------------->

>--+-----------------------------+-----------------------------><
   +- -e --integrationServerName-+   
   '- -g ------------------------'   

Parameters

integrationNodeName
(Required) The name of the integration node.
-e integrationServerName
(Optional) Specifies a single integration server for which the status and configuration information will be displayed. If you specify this parameter, you cannot specify the -g parameter.
-g
(Optional) Specifies that the status and configuration information will be displayed for all integration servers in the specified integration node. If you set this parameter, you cannot specify an integration server name by using the -e parameter.

If you specify neither the -e nor -g parameter, the -g parameter is set by default.

Responses

In addition to standard command responses, the following responses are returned by this command.
  • BIP8374I: Shows the Bluemix startup and usage reporting state and configuration.
  • BIP8375I: Shows the Bluemix logging state and configuration.
  • BIP8378I: Shows the Bluemix details, apart from the password, used to obtain the logging tokens.

Authorization

The command must be run by a host operating system user ID that is a member of the mqbrkrs group.

Examples

Always enter the command on a single line; in some examples, line breaks have been added to enhance readability.

In the following example, status and configuration information will be displayed for all integration servers in the integration node called myIntegrationNode1 (in this case, there is only a single integration server called is01):
mqsireportbluemixreporting myIntegrationNode1
The output from the command is similar in format to that shown in the following example:
BIP8374I: Server = 'is01', Bluemix startup and usage reporting mode = 'active',
apihost = 'https://productinsights-api.ng.bluemix.net', apikey = '03d54174-c4fe-3g2h-b9ad-52683e893c8f'
report interval minutes = '15', group name = 'Dev', proxy = ''

BIP8375I: Server = 'is01', Bluemix log reporting mode = 'active', 
host = 'logs.opvis.bluemix.net', port = '9091', report interval seconds = '120', 
tenantSpaceId = 'ab6d4fe4-4d75-3ek7-8a2g-5793affef363', tenantLogToken = 'JEsmPj9ehUvQ'
BIP8378I: Server = 'is01', Bluemix tenant SpaceId and LogToken obtained for region = 'us-south', 
organization = 'a.user@a.com', space = 'dev', user= 'a.user@a.com'
Start of changeIn the following example, status and configuration information will be displayed for integration server is02 in the integration node called myIntegrationNode1:
mqsireportbluemixreporting myIntegrationNode1 -e is02
The output from the command, which in this case includes the name of an HTTP proxy server, is similar in format to the following example:
BIP8374I: Server = 'is02', Bluemix startup and usage reporting mode = 'active',
apihost = 'https://productinsights-api.eu-gb.bluemix.net', 
apikey = '5g6d017a-82ef-479d-af92-82c470e2731b', report interval minutes = '10', 
group name = '', proxy = 'localhost:3128'
End of change

bz91110_.htm | Last updated 2017-07-17 12:46:56