C9530-001 Exam Dumps - IBM Integration Bus v10.0, Solution Development

If a shared library is updated, the changes are immediately visible to all referencing applications.

If you want to deploy and manage just one copy of those common resources, use a shared library. A shared library can be deployed directly to an integration server. Any application can reference the resources in that deployed shared library.

References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc23066_.htm

Applications provide runtime isolation whereby resources inside the application are not visible to other resources, such as message flows, libraries, or other applications that are running outside the application. Consider using applications if you need to ensure that updates to one group of deployed resources do not affect another group. For example, use an application when you want to control which flows pick up the latest version of an ESQL module.

References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc23060_.htm

The WebSphere Service Registry and Repository (WSRR) is a central repository of entities. The WebSphere Service Registry and Repository (WSRR) is a central repository of entities.

Use the WSRR nodes (the RegistryLookup and EndpointLookup nodes) to create message flows that retrieve data dynamically from WSRR. Use the WSRR nodes (the RegistryLookup and EndpointLookup nodes) to create message flows that retrieve data dynamically from WSRR. Use the EndpointLookup node to submit queries for Web service endpoints.

References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac56060_.htm

You can use the following tools to create, attach, and manage MQEndpoint policies:

To create a policy, use the mqsicreatepolicy command. For more information, see Creating and importing policies.

References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bi62102_.htm

When a node in a message flow throws an exception this is assigned a BIP number. As the exception is propagated up the flow, possibly being processed by various exception handling routines attached to the catch terminal of nodes it may be "wrapped" in several outer exceptions. This forms a "stack" of exceptions known as an ExceptionList.

If an exception reaches an input node without being handled by any branch of the flow then the input transaction is rolled back and each message in the ExceptionList is output to the syslog.

References: https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/diagnostic-tools/