C9530-001 IBM Integration Bus v10.0, Solution Development Questions and Answers

XML

BLOB

XMLNSC

JMSStream

In Terminal

Error Terminal

Throw Terminal

Failure Terminal

Start Date

Start Time

Timeout Interval

Transaction Mode

Application

Static library

Shared Library

Dynamic library

Event Monitoring

IIB log command

Toolkit workspace log

Toolkit Deployment log

The transaction was set to automatic on the MQOutput Node.

The developer should have used the MQInput Node instead of the MQGet Node.

The Integration Node is configured in a MQ cluster for load balancing and the object descriptor is set to the ReplyToQueueManager.

The backend request/reply message processing can only be accomplished by breaking up the flow into two flows.

By selecting the Pattern Target properties from any node any message flow.

Pattern properties must be configured in a Pattern Authoring project before selecting targets.

All properties in a message flow must be tagged for the Pattern Authoring Project to identify them.

By adding a reference all the Node properties are automatically exposed to the Pattern Authoring Project.

Define a timeout parameter in the Policy file.

Use the MbGlobalMapSeccionPolicy class to expire the Global Cache variable.

Set up an external process to check the variables that have not been modified in a speculated amount of time and remove them.

Use remove() on the MbGlobalMap class. In case of a catastrophic crash of the node, the cache will detect this and remove the variable implicitly.

A SOAP file.

A WADL document.

A Swagger 2.0 document.

A sample of the JSON that will be handled.

Deploy all the jar files as static libraries.

Deploy all the jar files as part of the applications.

common.jar deployed as a shared library along with the shlib1.jar and shlib2.jar as shared libraries.

shlib1.jar and shlib2.jar must now be deployed as static libraries and common.jar as a shared library.

MQCIient MQQMGR

MQPublish, MQSubscribe

MQEndpoint, MQTTEndpoint

MQEndpoint, MQTTPublish, MQTTSubscribe

MQTTSubscribe Policy 1

MQTTSubscribe Policy Test

MQTTSubscribe Policy apiv1

MQTTSubscribe Policy policy

Both databases and the MQ transactions are committed at the end of the flow.

MQ transactions are committed at the end of the flow but each database interaction is committed as the message is propagated from the Out terminal.

Since there is only one MQ Node the MQ transaction is committed while propagating from the Out terminal of the MQInput Node and all the database interactions are committed at the end of the flow.

Each of the nodes mentioned has a Transaction property to determine the transactional nature of the node and is always committed when propagating from the Out terminal independent of any other Nodes in the flow.

ErrorList

System log

ExceptionList

Exception log

A local map can be called from an ESQL procedure.

A local map can be defined by clicking File->New->Local Map.

A local map is an independent resource with a physical file associated.

The scope of a local map is the message map. A local map is processed with the messagemap.