WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Setting the start mode of flows and applications at run time

You can configure the run state of message flows and applications when you deploy or when you restart an execution group.

Before you start:
This topic assumes that a broker archive (BAR) file has been created and contains a message flow or application. For more information, see the following topics:

In previous versions of WebSphere® Message Broker, when you deploy a new message flow to an execution group, the flow is started automatically. If you deploy an existing message flow to an execution group, the existing run state of the flow is maintained. Therefore, if the flow was stopped before you deployed it, it remains stopped when you deploy it. This run state is also maintained when you restart the execution group.

From WebSphere Message Broker Version 8.0 onwards, you can set the default behavior of message flows and applications when you deploy or restart an execution group. For example, you might have a message flow that creates resources that are required by other message flows. Therefore, you might want to start one message flow before all others when the flows are deployed, or when the broker, execution group, or containing application are started. You can set one message flow to start automatically, then set other message flows to require a manual restart.

You can configure the run state by using the startMode property on the mqsiapplybaroverride command. You can also specify the default behavior by setting the Start Mode property on the broker archive BAR file. For instructions, see Configuring the start mode of flows and applications at development time. Use the mqsireadbar command to view the current values of configurable properties in the BAR file. You can set the startMode property to one of the following values:
Maintained
This value is the default, and indicates that the flow or application is started when deployment is complete, and remains running until a stop command is issued. After a stop command has been issued, the flow or application remains stopped until a start command is issued. The state of the flow or application remains unchanged after redeployment, or after the broker, execution group, or containing application has been restarted.
Manual
This value indicates that the flow or application must always be started manually after deployment or after the broker, execution group, or containing application has been restarted. The flow or application is in stopped state after deployment or redeployment, and after the broker, execution group, or containing application is restarted, even if the flow or application was running before the deployment or restart.
Automatic
This value indicates that the flow or application is always started automatically after deployment, redeployment, or after the broker, execution group, or containing application is restarted.

You can set this property for message flows and applications. The state of an application overrides the state of any message flows that it contains. For example, if an application is stopped, no flows in that application can run, even if they have been set to start automatically.

To find out how to use the mqsiapplybaroverride command to set the startMode property, see mqsiapplybaroverride command.

Next: Deploy the BAR file by following the instructions in Deploying a broker archive file.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:19


Task topicTask topic | Version 8.0.0.7 | bn23605_