App Connect

Hi,

I have an integration flow with a GroupScatter + GroupGather + GroupComplete flow, which uses an MqOutput node inbetween. The MqOutput node has a Timeout property inside the Gorup tab, which can set the timeout for the group message.

In our source code, that Group>Timeout property in the MqOutput node is set to 5.0 seconds, and we have a BAR file with the "Remove contents of the archive before building" option set, but the "Override configurable property values" not set, which configures a 180.0 second timeout for that same MqOutput node.

In IIB 10, this resulted in the deployed flow using a 180.0 second timeout. However, on ACE 12 this results in a 5.0 second configuration for the timeout.

Is this intended, or a bug?

If a bug, is it known already?

If not, what's the correct process to report it?

Nicolas,

this sounds like an 'undocumented feature'. If you want support for this you can open a case on the IBM support site:  https://www.ibm.com/mysupport/s/ .

Hi,

I have an integration flow with a GroupScatter + GroupGather + GroupComplete flow, which uses an MqOutput node inbetween. The MqOutput node has a Timeout property inside the Gorup tab, which can set the timeout for the group message.

In our source code, that Group>Timeout property in the MqOutput node is set to 5.0 seconds, and we have a BAR file with the "Remove contents of the archive before building" option set, but the "Override configurable property values" not set, which configures a 180.0 second timeout for that same MqOutput node.

In IIB 10, this resulted in the deployed flow using a 180.0 second timeout. However, on ACE 12 this results in a 5.0 second configuration for the timeout.

Is this intended, or a bug?

If a bug, is it known already?

If not, what's the correct process to report it?

Hi Jef, thanks for your response.

What exactly are you saying sounds like an 'undocumented feature'?

Overriding configuration using a BAR deployment file seems to be well documented, for example here https://www.ibm.com/docs/en/app-connect/12.0?topic=deployment-editing-configurable-properties-in-bar-file

An administrator can use configurable properties to update target-dependent properties that are associated with a solution, such as queue names, queue manager names, and database connections. 

(...)

By changing configurable properties, you can customize a BAR file for a new integration node (for example, a test system) without editing and rebuilding the message flows or the resources that they use, such as message mappings, ESQL code, and Java™ code. For example, if you select an application, you can set the start mode for that application. If you select a message flow, you can change properties for policy sets, monitoring, and the security profile. You can also expand a message flow and set the properties for the nodes in that flow. For information about the configurable properties that you can set, see Configurable properties in a BAR file.

The specific property I'm talking about is documented here https://www.ibm.com/docs/en/app-connect/12.0?topic=nodes-mqoutput-node

The Group properties of the node are described in the following table: 

(...)

Nicolas,

this sounds like an 'undocumented feature'. If you want support for this you can open a case on the IBM support site:  https://www.ibm.com/mysupport/s/ .

Hi,

I have an integration flow with a GroupScatter + GroupGather + GroupComplete flow, which uses an MqOutput node inbetween. The MqOutput node has a Timeout property inside the Gorup tab, which can set the timeout for the group message.

In our source code, that Group>Timeout property in the MqOutput node is set to 5.0 seconds, and we have a BAR file with the "Remove contents of the archive before building" option set, but the "Override configurable property values" not set, which configures a 180.0 second timeout for that same MqOutput node.

In IIB 10, this resulted in the deployed flow using a 180.0 second timeout. However, on ACE 12 this results in a 5.0 second configuration for the timeout.

Is this intended, or a bug?

If a bug, is it known already?

If not, what's the correct process to report it?

Hi Jef, thanks for your response.

What exactly are you saying sounds like an 'undocumented feature'?

Overriding configuration using a BAR deployment file seems to be well documented, for example here https://www.ibm.com/docs/en/app-connect/12.0?topic=deployment-editing-configurable-properties-in-bar-file

An administrator can use configurable properties to update target-dependent properties that are associated with a solution, such as queue names, queue manager names, and database connections. 

(...)

By changing configurable properties, you can customize a BAR file for a new integration node (for example, a test system) without editing and rebuilding the message flows or the resources that they use, such as message mappings, ESQL code, and Java™ code. For example, if you select an application, you can set the start mode for that application. If you select a message flow, you can change properties for policy sets, monitoring, and the security profile. You can also expand a message flow and set the properties for the nodes in that flow. For information about the configurable properties that you can set, see Configurable properties in a BAR file.

The specific property I'm talking about is documented here https://www.ibm.com/docs/en/app-connect/12.0?topic=nodes-mqoutput-node

The Group properties of the node are described in the following table: 

(...)

Nicolas,

this sounds like an 'undocumented feature'. If you want support for this you can open a case on the IBM support site:  https://www.ibm.com/mysupport/s/ .

Hi,

I have an integration flow with a GroupScatter + GroupGather + GroupComplete flow, which uses an MqOutput node inbetween. The MqOutput node has a Timeout property inside the Gorup tab, which can set the timeout for the group message.

In our source code, that Group>Timeout property in the MqOutput node is set to 5.0 seconds, and we have a BAR file with the "Remove contents of the archive before building" option set, but the "Override configurable property values" not set, which configures a 180.0 second timeout for that same MqOutput node.

In IIB 10, this resulted in the deployed flow using a 180.0 second timeout. However, on ACE 12 this results in a 5.0 second configuration for the timeout.

Is this intended, or a bug?

If a bug, is it known already?

If not, what's the correct process to report it?