You can configure the run state of applications, integration services, and message flows when you deploy or when you restart an integration server.
About this task
In previous versions of IBM® Integration Bus, when you deploy a new message flow to an integration server, the flow is started automatically. If you deploy an existing message flow to an integration server, 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 integration server.
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 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
BAR file. For instructions, see
Editing configurable properties in a BAR file. 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 integration node, integration
server, or containing application has been restarted. When an
application holds one or more flows, the state of the flows within the application is preserved if
the application is stopped and then started again. However, on redeployment of an application, the
status of the flows inside the application is not preserved.
- 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.
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.