About this task
In WebSphere® Message
Broker Version 7.0, 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 integration server. 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 integration node, integration server, 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
specify the default behavior by setting the
Start Mode property
on the
BAR file. You can also
configure the run state by using the
startMode property
on the
mqsiapplybaroverride command.
For more information, see
Setting the start mode of message flows and applications at run time. You
can set the
Start Mode 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 integration node, integration server, 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 integration node, integration server, or containing application
has been restarted. The flow or application is in stopped state after
deployment or redeployment, and after the integration node, integration server, 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 integration node, integration server, or containing application
is restarted.
To indicate how a flow or application is started after
deployment, or after the integration node, integration server, or containing application
is restarted, complete the following steps.
What to do next
Deploy the
BAR file by following the instructions
in
Deploying a BAR file.