Login/Register27 / 166
How to Publish a Documents to the Broker?
Step 1: A publishing service on the Integration Server sends a document to the dispatcher (or an adapter notification publishes a document when an event
occurs on the resource the adapter monitors).Before the Integration Server sends the document to the dispatcher, it validates
the document against its publishable document type. If the document is not valid, the service returns an exception specifying the validation error.
Step 2: The dispatcher obtains a connection from the connection pool. The connection pool is a reserved set of connections that the Integration Server uses to publish documents to the Broker. To publish a document to the Broker, the Integration Server uses a connection for the default client.
Step 3: The dispatcher sends the document to the Broker.
Step 4: The Broker examines the storage type for the document to determine how to store the document.
* If the document is volatile, the Broker stores the document in memory.
* If the document is guaranteed, the Broker stores the document in memory
and on disk.
Step 5: The Broker routes the document to subscribers by doing one of the following:
* If the document was published (broadcast), the Broker identifies subscribers and places a copy of the document in the client queue for each subscriber.
* If the document was delivered, the Broker places the document in the queue for the client specified in the delivery request.
* If there are no subscribers for the document, the Broker returns an acknowledgement to the publisher and then discards the document.
A document remains in the queue on the Broker until it is picked up by the subscribing client. If the time-to-live for the document elapses, the Broker
discards the document.
Step 6: If the document is guaranteed, the Broker returns an acknowledgement to the dispatcher to indicate successful receipt and storage of the document. The
dispatcher returns the connection to the connection pool.
Step 7: The Integration Server returns control to the publishing service, which executes the next step.
Asked In ::
Step 1: A publishing service on the Integration Server sends a document to the dispatcher (or an adapter notification publishes a document when an event
occurs on the resource the adapter monitors).Before the Integration Server sends the document to the dispatcher, it validates
the document against its publishable document type. If the document is not valid, the service returns an exception specifying the validation error.
Step 2: The dispatcher obtains a connection from the connection pool. The connection pool is a reserved set of connections that the Integration Server uses to publish documents to the Broker. To publish a document to the Broker, the Integration Server uses a connection for the default client.
Step 3: The dispatcher sends the document to the Broker.
Step 4: The Broker examines the storage type for the document to determine how to store the document.
* If the document is volatile, the Broker stores the document in memory.
* If the document is guaranteed, the Broker stores the document in memory
and on disk.
Step 5: The Broker routes the document to subscribers by doing one of the following:
* If the document was published (broadcast), the Broker identifies subscribers and places a copy of the document in the client queue for each subscriber.
* If the document was delivered, the Broker places the document in the queue for the client specified in the delivery request.
* If there are no subscribers for the document, the Broker returns an acknowledgement to the publisher and then discards the document.
A document remains in the queue on the Broker until it is picked up by the subscribing client. If the time-to-live for the document elapses, the Broker
discards the document.
Step 6: If the document is guaranteed, the Broker returns an acknowledgement to the dispatcher to indicate successful receipt and storage of the document. The
dispatcher returns the connection to the connection pool.
Step 7: The Integration Server returns control to the publishing service, which executes the next step.
Step 1: A publishing service on the Integration Server sends a document to the dispatcher (or an adapter notification publishes a document when an event occurs on the resource the adapter monitors).Before the Integration Server sends the document to the dispatcher, it validates the document against its publishable document type. If the document is not valid, the service returns an exception specifying the validation error.
Step 2: The dispatcher obtains a connection from the connection pool. The connection pool is a reserved set of connections that the Integration Server uses to publish documents to the Broker. To publish a document to the Broker, the Integration Server uses a connection for the default client.
Step 3: The dispatcher sends the document to the Broker.
Step 4: The Broker examines the storage type for the document to determine how to store the document.
* If the document is volatile, the Broker stores the document in memory.
* If the document is guaranteed, the Broker stores the document in memory and on disk.
Step 5: The Broker routes the document to subscribers by doing one of the following:
* If the document was published (broadcast), the Broker identifies subscribers and places a copy of the document in the client queue for each subscriber.
* If the document was delivered, the Broker places the document in the queue for the client specified in the delivery request.
* If there are no subscribers for the document, the Broker returns an acknowledgement to the publisher and then discards the document.
A document remains in the queue on the Broker until it is picked up by the subscribing client. If the time-to-live for the document elapses, the Broker discards the document.
Step 6: If the document is guaranteed, the Broker returns an acknowledgement to the dispatcher to indicate successful receipt and storage of the document. The dispatcher returns the connection to the connection pool.
Step 7: The Integration Server returns control to the publishing service, which executes the next step.
