In previous
versions of message broker, If we deploy message flow it starts
running and we can’t deploy a messsage flow/application in stopped
state.
In some scenario, we may require some flows needs to be in stopped state after deployment and start the flow manually when required. Messsage Broker v8 provide an option to deploy the message flow in stopped state.
Messsage Broker v8 has the capability to configure and control the runstate of the message flow or application with help of new Start Mode property.
Maintained (default): If we deploy message flow/application, it starts running and when we restart broker/exectuion group/application or redeploy, the previous run state of the messageflows/applications are maintained. This behavior is followed in all previous versions of the message broker.
Automatic: If we deploy message flow/application, it will start running and when we restart broker/execution group/application or redeploy, it starts the message flow even if the flows was in stopped state before restart broker/execution group/application or redeploy
Manual: If we deploy message flow/application, it will go into stopped state and when we restart broker/exectuion group/application, it stops the message flow even if the flows was in running state before restart broker/exectuion group/application or redeploy.
Below table shows how the runstate of the message flows/applications getting affected against different value of the Start Mode when we go the following sequential actions.
Configuring Start Mode:
Can configure the Start Mode of the message flows or applications in two ways
1. Using Bar File editor:
We can configure Start Mode for both Applications and Message Flows at deployment time using bar File editor
For Applications:
For Message Flows:
Run state of the message flows also controlled by Start Mode of Applications
2. Using mqsiapplybaroverride
Use mqsireadbar to read current value of Start Mode property
Use mqsiapplybaroverride to change the value of Start Mode property at runtime
In some scenario, we may require some flows needs to be in stopped state after deployment and start the flow manually when required. Messsage Broker v8 provide an option to deploy the message flow in stopped state.
Messsage Broker v8 has the capability to configure and control the runstate of the message flow or application with help of new Start Mode property.
Maintained (default): If we deploy message flow/application, it starts running and when we restart broker/exectuion group/application or redeploy, the previous run state of the messageflows/applications are maintained. This behavior is followed in all previous versions of the message broker.
Automatic: If we deploy message flow/application, it will start running and when we restart broker/execution group/application or redeploy, it starts the message flow even if the flows was in stopped state before restart broker/execution group/application or redeploy
Manual: If we deploy message flow/application, it will go into stopped state and when we restart broker/exectuion group/application, it stops the message flow even if the flows was in running state before restart broker/exectuion group/application or redeploy.
Below table shows how the runstate of the message flows/applications getting affected against different value of the Start Mode when we go the following sequential actions.
Can configure the Start Mode of the message flows or applications in two ways
1. Using Bar File editor:
We can configure Start Mode for both Applications and Message Flows at deployment time using bar File editor
For Applications:
Run state of the message flows also controlled by Start Mode of Applications
Use mqsireadbar to read current value of Start Mode property
Fantastic. I really enjoyed this. And I am speaking as a person relatively new to this business. There is no getting around paying your dues and doing your homework.
ReplyDeleteFree Intraday Commodity Tips