{"id":327,"date":"2016-06-26T21:57:42","date_gmt":"2016-06-26T16:27:42","guid":{"rendered":"http:\/\/www.middlewareprimer.com\/blog\/?p=327"},"modified":"2016-06-26T21:57:42","modified_gmt":"2016-06-26T16:27:42","slug":"starting-stopping-message-flows-iib","status":"publish","type":"post","link":"http:\/\/www.middlewareprimer.com\/blog\/2016\/06\/26\/starting-stopping-message-flows-iib\/","title":{"rendered":"Starting Stopping message flows IIB"},"content":{"rendered":"

Starting Stopping message flows IIB listed below for reference (considering IBM Integration Bus v9.0.0.0<\/strong>)<\/p>\n

Starting a message flow<\/strong><\/span><\/p>\n

mqsistartmsgflow command<\/strong> can be used for the following purposes:<\/p>\n

To start a specific message flow in an integration server
\nTo start all message flows in the integration server
\nTo start a specific integration server
\nTo start all integration servers
\nTo start a message flow in a specific application or library or both
\nTo start all message flows in a specific application or library or both
\nTo start a specific application
\nTo start all applications<\/p>\n

mqsistartmsgflow command usage<\/strong><\/p>\n

mqsistartmsgflow <broker name> <attributes><\/p>\n

Where attributes<\/strong> are,<\/p>\n

-e integrationServerName
\nThe name of the integration server for which to start message flows. You must specify either -e or -g.
\n-g
\nThe specified message flow or flows are started on all integration servers on the specified broker. You must specify either -e or -g.
\n-j
\nAll message flows in the specified integration server are started.
\n-k applicationName
\nThe name of an application to which to target a start request.
\n-m flowName
\nThe name of the message flow being started.
\n-v traceFileName
\nThis parameter sends internal debug trace information to the specified file.
\n-w timeoutSecs
\nThis parameter specifies the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
\n-y libraryName
\nThe name of a library to which to target a start request.
\n-z
\nThe -z parameter indicates that all applications in an integration server are to be started.<\/p>\n

mqsistartmsgflow command examples<\/strong> (as mentioned in IBM Knowledge Center)<\/p>\n

Start a named message flow that you have deployed to integration server eg1 on the broker IB9NODE:
\nmqsistartmsgflow IB9NODE -e eg1 -m simpleflow<\/p>\n

Ensure that all message flows are running on the local broker IB9NODE:
\nmqsistartmsgflow IB9NODE -g -j<\/p>\n

Start the message flow myFlow1 in the application myApplication in the default integration server:
\nmqsistartmsgflow IB9NODE -e default -k myApplication -m myFlow1<\/p>\n

Start the message flow myFlow1 in the library myLibrary, which is referenced by the application myApplication, in the default integration server:
\nmqsistartmsgflow IB9NODE -e default -k myApplication -y myLibrary -m myFlow1<\/p>\n

Start all message flows and start all applications in the default integration server:
\nmqsistartmsgflow IB9NODE -e default -z -j<\/p>\n

 <\/p>\n

Stopping a message flow<\/strong><\/span><\/p>\n

mqsistopmsgflow command<\/strong> can be used for the following purposes:<\/p>\n

To stop a specific message flow in an integration server
\nTo stop all message flows in the integration server
\nTo stop a specific integration server
\nTo stop all integration servers
\nTo stop a message flow in a specific application or library or both
\nTo stop all message flows in a specific application or library or both
\nTo stop a specific application
\nTo stop all applications<\/p>\n

mqsistopmsgflow command usage<\/strong><\/p>\n

mqsistopmsgflow <broker name> <attributes><\/p>\n

Attributes are,<\/strong>
\n-e integrationServerName
\nThe name of the integration server for which to stop message flows. You must specify either -e or -g.
\n-f
\nUsed with the \u2013m, \u2013e, and \u2013k parameters to force the named message flow to stop within the named integration server or the named application.
\n-g
\nThe specified message flow or flows are stopped on all integration servers on the specified broker. You must specify either -e or -g.
\n-j
\nAll message flows in the specified integration server are stopped; the integration server is not stopped.
\n-k applicationName
\nThe name of an application to which to target a stop request.
\n-m flowName
\nThe name of the message flow being stopped.
\n-v traceFileName
\nThis parameter sends internal debug trace information to the specified file.
\n-w timeoutSecs
\nThis parameter specifies the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
\n-y libraryName
\nThe name of a library to which to target a stop request.
\n-z
\nThe -z parameter indicates that all applications in an integration server are to be stopped.<\/p>\n

mqsistopmsgflow command examples<\/strong><\/p>\n

Stop a named integration server on broker IB9NODE:
\nmqsistopmsgflow IB9NODE -e eg2<\/p>\n

Stop all integration server processes on the local broker IB9NODE:
\nmqsistopmsgflow IB9NODE -g<\/p>\n

Stop the message flow myFlow1 in the application myApplication in the default integration server:
\nmqsistopmsgflow IB9NODE -e default -k myApplication -m myFlow1<\/p>\n

Stop the message flow myFlow1 in the default integration server and restart the default integration server:
\nmqsistopmsgflow IB9NODE -e default -m myFlow1 -f restartExecutionGroup<\/p>\n

Stop the message flow myFlow1 in the library myLibrary, which is referenced by the application myApplication, in the default integration server:
\nmqsistopmsgflow IB9NODE -e default -k myApplication -y myLibrary -m myFlow1<\/p>\n

Stop all message flows and stop all applications in the default integration server:
\nmqsistopmsgflow IB9NODE -e default -z -j<\/p>\n

 <\/p>\n

Message Flow related IIB v9.0 knowledge center link here<\/a><\/strong><\/span> and Command reference here<\/strong><\/span><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Starting Stopping message flows IIB listed below for reference (considering IBM Integration Bus v9.0.0.0) Starting a message flow mqsistartmsgflow command can be used for the following purposes: To start a specific message flow in an integration server To start all message flows in the integration server To start a specific integration server To start all […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[214,215,146,216,217,218],"class_list":["post-327","post","type-post","status-publish","format-standard","hentry","category-ibm-integration-bus","tag-broker","tag-eg","tag-iib-v9","tag-integration-node","tag-message-flow","tag-start-stop-message-flow"],"_links":{"self":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/327","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/comments?post=327"}],"version-history":[{"count":5,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/327\/revisions"}],"predecessor-version":[{"id":758,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/327\/revisions\/758"}],"wp:attachment":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/media?parent=327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/categories?post=327"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/tags?post=327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}