You are on page 1of 2

How to create Event and Subscription?

ANSWER:

What is the difference b/w asynchronous and synchronous Subscription? ANSWER: The method by which the event procedure code is executed for a Subscription-based object (ClassSubscription, ClassWorkflowSubscription, InstanceSubscription, InstanceWorkflowSubscription). To execute the event procedure synchronously, set the property to true. To execute the event procedure asynchronously (in the background), set the property to false. The default is false. Specify the property when you create the Subscription-based object. When an asynchronous event procedure is triggered, the action occurs on a separate execution thread, allowing the subscription processor to continue without waiting for the results of the action. The Content Engine inserts the event into the QueueItem table, after any other waiting asynchronous operations, and executes it when resources permit. While execution usually occurs instantaneously, there might be a delay if many other asynchronous events or operations (such as security propagation or XML classification) are waiting in the queue. If your application depends on a particular asynchronous event procedure being completed, your application should first test the status of that event to verify its completion.

If the asynchronous event action fails, the exception comes back to the server. The event action transaction rolls back, but the transaction of the originating activity executes.

Note that for domains in which there are multiple Content Engine server instances, any server in the domain can handle a queued asynchronous event, not just the server that generated the event.

When a synchronous event procedure is triggered, the call to execute the event action blocks further processing by the subscription processor until the action completes. The action runs in the same transaction as the originating activity on the target object. If the action fails, the exception comes back to the client. The single transaction rolls back; therefore, the originating activity fails along with the event action.

Note that, for a workflow subscription, this property is read-only with a value of false because a workflow subscription's event is always fired asynchronously on Content Engine.

Classification: Birlasoft Internal

icc2.1 and 2.2 any limitation regarding 2.1 and 2.2 what is p8connector. How to import and export task route stop task route how to tackle metadata in task route? email archiving in ICC filesystem 4.5 ce api -- pe api 5.X api version series id wsi -- iiop

Classification: Birlasoft Internal

You might also like