How can WebSphere Service Registry & Repository (WSRR) information be pre-loaded into the IBM Integration BUS (IIB) cache before sending any messages to the message flow?
By subscribing to WSRR notifications.
Adding predefinedCacheQueries to a custom policy within WSRR.
By using the predefinedCacheQueries parameter in the Configurable Services for the broker.
WSRR data cannot be loaded into the IIB cache without sending a message that accesses the WSRR node.
Correct answer: C
Explanation:
Enabling cache preloading After the query file is created and placed on the server, configure the broker to use the text file at execution group start up. The change properties command will be used to achieve this and is accomplished by running the following command:Command to enable preloading of the WSRR cache from file mqsichangeproperties <broker_name> -c ServiceRegistries -p "<wsrr_query_text_file>" -o DefaultWSRR -n predefinedCacheQueries Replace <broker_name> with the name of the broker that is being used. Replace <wsrr_query_text_file> with the absolute file path location and name of the query file. References: https://www.ibm.com/developerworks/websphere/library/techarticles/1404_smithson7/1404_smithson7.html
Enabling cache preloading
After the query file is created and placed on the server, configure the broker to use the text file at execution group start up. The change properties command will be used to achieve this and is accomplished by running the following command:
Command to enable preloading of the WSRR cache from file
Replace <broker_name> with the name of the broker that is being used. Replace <wsrr_query_text_file> with the absolute file path location and name of the query file.
When using the set of aggregation nodes, how does a developer tie the fan-out flow with the fan-in flow when it is included within the same message flow?
No properties need to be set, since the fan-out and fan-in flows are in the same messages flow.
Set the Aggregate Name property of the AggregateReply Node to the same value that you set for the Aggregate Name property in the corresponding Collector Node.
Set the Aggregate Name property of the AggregateReply Node to the same value that you set for the Aggregate Name property in the corresponding AggregateControl Node.
Set the Aggregate Name property of the AggregateReply Node to the same value that you set for the Aggregate Name property on each of the corresponding AggregateRequest Nodes in the fan-out flow.
Correct answer: C
Explanation:
Set the Aggregate Name property of the AggregateReply node to the same value that you set for the Aggregate Name property in the corresponding AggregateControl node in the fan-out flow. References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac12311_.htm
Set the Aggregate Name property of the AggregateReply node to the same value that you set for the Aggregate Name property in the corresponding AggregateControl node in the fan-out flow.
('MapToRequestor.CopyMessageHeaders', '6.14'). This resolved to ''1 + 1''. The result was ''2''.
What does 6.14 indicate here?
Line 6, Column 14 in the CopyMessageHeaders node.
Line 14, Column 6 in CopyMessageHeaders node.
Column 6, line 14 in the CopyMessageHeaders function of MapToRequestor.
Line 6, Column 14 in the CopyMessageHeaders function of MapToRequestor.
Correct answer: D
Explanation:
References such as '6.14' apply to the row and column number within a function that specify the location of the command that is being executed; in this case, row 6, column 14. Example:2005-07-12 16:17:18.242605 5344 UserTrace BIP2539I: Node 'Reply.MapToRequestor':Evaluating expression ''I'' at ('.MapToRequestor.CopyMessageHeaders', '6.12'). This resolved to ''I''. The result was ''1''. References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14320_.htm
References such as '6.14' apply to the row and column number within a function that specify the location of the command that is being executed; in this case, row 6, column 14.