Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Delivered
Workspace App Connect
Created by Guest
Created on Apr 5, 2012

Provide command to return broker status as an exit code value

Provide a command similar to mqsilist that would return the status of a broker (running, stopped, running as standby, etc..) as an exit code value. This would make it easier when writing scripts that need to determine the status of a broker. Similar commands for execution groups and flows could also be useful.

Idea priority Low
RFE ID 21143
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Reply
    |
    Jul 30, 2021

    Idea / RFE Review. Apologies for the length of time this suggestion has been in status Uncommitted Candidate / Future Consideration. Since this request was initially created, the product has improved in this area. The mqsilist command does now provide a status code which enables you to identify if a node is started or stopped (some examples I just executed on ACEv11.0.0.12 is shown below). Of course, in programmatic circumstances, it is sometimes also much simpler to use a REST API call as this way it is possible to retrieve much more detailed information ... for example querying /apiv2 for an integration node will return the processId (amongst many other node details):


    {

    "hasChildren": true,

    "name": "V12NODENOQM",

    "type": "integrationNode",

    "uri": "/apiv2",

    "properties": {

    "defaultQueueManagerName": "",

    "httpConnectorPort": 7080,

    "httpsConnectorPort": 7083,

    "restAdminListenerPort": 4444,

    "restAdminListenerIPCSocket": "\\\\.\\pipe\\C:\\ProgramData\\IBM\\MQSI\\V12NODENOQM"

    },

    "descriptiveProperties": {

    "productName": "IBM App Connect Enterprise",

    "version": "12.0.1.0",

    "buildLevel": "ib000-L210520.1569 (S000-L210520.10620)",

    "platformName": "Windows 10 Enterprise",

    "platformArchitecture": "AMD64",

    "platformVersion": "6.3 build 19042 "

    },

    "active": {

    "processId": "13052"

    }


    C:\Program Files\IBM\ACE\11.0.0.12>mqsilist

    BIP1326I: Integration node 'ACEFP10NOQM' is stopped.

    BIP1326I: Integration node 'ACEFP9NOQM' is stopped.

    BIP1326I: Integration node 'ACETEST' is stopped.

    BIP1326I: Integration node 'ACETEST1' is stopped.

    BIP1326I: Integration node 'ACEv110010' is stopped.

    BIP1285I: Integration node 'ACEv110010WITHQM' on queue manager 'V11FP10QM' is stopped.

    BIP1326I: Integration node 'ACEv110011' is stopped.

    BIP1326I: Integration node 'ACEv110011NewOne' is stopped.

    BIP1325I: Integration node 'ACEv110012' with administration URI 'http://LAPTOP-HH1E1OQN:4440' is running.

    BIP1326I: Integration node 'ACEv11003' is stopped.

    BIP1326I: Integration node 'ACEv11004' is stopped.

    BIP1326I: Integration node 'ACEv11005' is stopped.

    BIP1326I: Integration node 'ACEv11006' is stopped.

    BIP1326I: Integration node 'ACEv11007' is stopped.

    BIP1325I: Integration node 'ACEv11008' with administration URI 'http://LAPTOP-HH1E1OQN:4433' is running.

    BIP1285I: Integration node 'ACEv11009' on queue manager 'EXAMPLEQM' is stopped.

    BIP1285I: Integration node 'ACHv5000' on queue manager 'ACHQM' is stopped.

    BIP1326I: Integration node 'ben' is stopped.

    BIP1326I: Integration node 'BEN3011' is stopped.

    BIP1326I: Integration node 'bob' is stopped.

    BIP1326I: Integration node 'MyIntegrationNode' is stopped.

    BIP1326I: Integration node 'MY_NODE_V11' is stopped.

    BIP1326I: Integration node 'REDDY_V11' is stopped.

    BIP1326I: Integration node 'wibble' is stopped.

    BIP8071I: Successful command completion.


    C:\Program Files\IBM\ACE\11.0.0.12>mqsilist ACEv110012

    -----------------------------------

    BIP1286I: Integration server 'server1' on integration node 'ACEv110012' is running.

    BIP8071I: Successful command completion.


    C:\Program Files\IBM\ACE\11.0.0.12>echo %ERRORLEVEL%

    0


    C:\Program Files\IBM\ACE\11.0.0.12>mqsilist ACEv11008

    -----------------------------------

    BIP1286I: Integration server 'SecondServer' on integration node 'ACEv11008' is running.

    -----------------------------------

    BIP1286I: Integration server 'ThirdServer' on integration node 'ACEv11008' is running.

    -----------------------------------

    BIP1286I: Integration server 'default' on integration node 'ACEv11008' is running.

    BIP8071I: Successful command completion.


    C:\Program Files\IBM\ACE\11.0.0.12>echo %ERRORLEVEL%

    0


    C:\Program Files\IBM\ACE\11.0.0.12>mqsilist ACEv11007

    BIP8019E: Integration node 'ACEv11007' stopped.

    This integration node is stopped; the command you issued cannot be processed when an integration node is stopped.

    A previous command has been issued to stop this integration node, or this integration node has never been started.

    This integration node can be started, changed, or deleted.


    C:\Program Files\IBM\ACE\11.0.0.12>echo %ERRORLEVEL%

    19


    Given these changes, and the lack of any other votes on this item, we're going to close off the RFE in its current form as delivered ... but if you feel more is still needed in this area with a dedicated status reporting command, then perhaps we could ask you to open a new idea dedicated to the modern ibmint styling and we may be able to gather more interested user feedback that way.

  • Guest
    Reply
    |
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Reply
    |
    Apr 11, 2012

    Thanks! We're continuing to investigate ways to simplify the scripting of operational actions in the broker, and this requirement is consistent with that theme.
    It's worthwhile noting that what you need can be done in WMB today using Java, using precisely one statement using the Message Broker API (CMP). The return value from the static method LocalBrokerUtilities.getLocalBrokerPID(String brokerName) will return zero for stopped brokers or non-zero for running brokers. (And there are similar static methods in the same class for determining the status of multi-instance brokers.) It would be straightforward to incorporate a call to a program that uses any of these methods into a script.
    For more advanced scenarios, you might want to take a look at the BrokerInfo sample included with the product. Alternatively, if you wanted to do this without the dependency of a JVM, you could use the ps command to look for the presence of a bipbroker or DataFlowEngine process, or ping the V8 broker's admin port (if enabled) using standard TCP/IP tools.