Login/Register2 / 166
What is Subscribe path for documents delivered to the default client?
Step 1: The dispatcher on the Integration Server requests documents from the default client’s queue on the Broker.
Note: The default client is the Broker client created for the Integration Server.The Broker places documents in the default client’s Broker queue only if the publisher delivered the document to the Integration Server’s client ID.
Step 2: The thread retrieves documents delivered to the default client in batches.The number of documents the thread retrieves at one time is determined by the capacity and refill level of the default document store and the number of documents available for the default client on the Broker.
Step 3: The dispatcher places a copy of the documents in memory in the default document store.
Step 4: The dispatcher identifies subscribers to the document and routes a copy of the document to each subscriber’s trigger queue.In the case of delivered documents, the Integration Server saves the documents to a trigger queue. The trigger queue is located within a trigger document store that is saved on disk.
Step 5: The Integration Server removes the copy of the document from the default document store and, if the document is guaranteed, returns an acknowledgement to the Broker. The Broker removes the document from the trigger client queue.
Step 6: The dispatcher obtains a thread from the server thread pool, pulls the document from the trigger queue, and evaluates the document against the conditions in the trigger.
Note: If exactly-once processing is configured for the trigger, the Integration Server first determines whether the document is a duplicate of one already processed by the trigger. The Integration Server continues processing the document only if the document is new.
Step 7: If the document matches a trigger condition, the Integration Server executes the trigger service associated with that condition.If the document does not match a trigger condition, the Integration Server sends an acknowledgement to the trigger queue, discards the document (removes it from the trigger queue), and returns the server thread to the server thread pool. The Integration Server also generates a journal log message stating that the document did not match a condition.
Step 8: After the trigger service executes to completion (success or error), one of the followings occurs:
* If the trigger service executed successfully, the Integration Server returns an acknowledgement to the trigger queue (if this is a guaranteed document), removes the document from the trigger queue, and returns the server thread to the thread pool.
* If a service exception occurs, the trigger service ends in the error and the Integration Server rejects the document, removes the document from the trigger queue, returns the server thread to the thread pool, and sends an error document to indicate that an error has occurred. If the document is guaranteed, the Integration Server returns an acknowledgement to the trigger queue. The trigger queue removes its copy of the guaranteed document from storage.
* If a transient error occurs during trigger service execution and the service catches the error, wraps it and re-throws it as a run-time exception, then the Integration Server waits for the length of the retry interval and re-executes the service using the original document as input. If the Integration Server reaches the maximum number of retries and the trigger service still fails because of a transient error, the Integration Server treats the last failure as a service error.
Asked In ::
Step 1: The dispatcher on the Integration Server requests documents from the default client’s queue on the Broker.
Note: The default client is the Broker client created for the Integration Server.The Broker places documents in the default client’s Broker queue only if the publisher delivered the document to the Integration Server’s client ID.
Step 2: The thread retrieves documents delivered to the default client in batches.The number of documents the thread retrieves at one time is determined by the capacity and refill level of the default document store and the number of documents available for the default client on the Broker.
Step 3: The dispatcher places a copy of the documents in memory in the default document store.
Step 4: The dispatcher identifies subscribers to the document and routes a copy of the document to each subscriber’s trigger queue.In the case of delivered documents, the Integration Server saves the documents to a trigger queue. The trigger queue is located within a trigger document store that is saved on disk.
Step 5: The Integration Server removes the copy of the document from the default document store and, if the document is guaranteed, returns an acknowledgement to the Broker. The Broker removes the document from the trigger client queue.
Step 6: The dispatcher obtains a thread from the server thread pool, pulls the document from the trigger queue, and evaluates the document against the conditions in the trigger.
Note: If exactly-once processing is configured for the trigger, the Integration Server first determines whether the document is a duplicate of one already processed by the trigger. The Integration Server continues processing the document only if the document is new.
Step 7: If the document matches a trigger condition, the Integration Server executes the trigger service associated with that condition.If the document does not match a trigger condition, the Integration Server sends an acknowledgement to the trigger queue, discards the document (removes it from the trigger queue), and returns the server thread to the server thread pool. The Integration Server also generates a journal log message stating that the document did not match a condition.
Step 8: After the trigger service executes to completion (success or error), one of the followings occurs:
* If the trigger service executed successfully, the Integration Server returns an acknowledgement to the trigger queue (if this is a guaranteed document), removes the document from the trigger queue, and returns the server thread to the thread pool.
* If a service exception occurs, the trigger service ends in the error and the Integration Server rejects the document, removes the document from the trigger queue, returns the server thread to the thread pool, and sends an error document to indicate that an error has occurred. If the document is guaranteed, the Integration Server returns an acknowledgement to the trigger queue. The trigger queue removes its copy of the guaranteed document from storage.
* If a transient error occurs during trigger service execution and the service catches the error, wraps it and re-throws it as a run-time exception, then the Integration Server waits for the length of the retry interval and re-executes the service using the original document as input. If the Integration Server reaches the maximum number of retries and the trigger service still fails because of a transient error, the Integration Server treats the last failure as a service error.
