IBM E02HRLL-G Administration Guide - Page 53

v First attempt fails v Destination retry 1 fails Transport retry 1 fails Transport retry 2 fails Transport retry 3 fails v Destination retry 2 fails Transport retry 1 fails Transport retry 2 fails Transport retry 3 fails v Destination retry 3 fails Transport retry 1 fails Transport retry 2 fails Transport retry 3 fails v Document fails delivery Every failed delivery attempt generates a warning event that is visible in the Community Console. Retry example The following example is an interaction for a retry using an HTTP destination. Configuration Transport: retries = 2, interval = 3000 ms (3 seconds) Console HTTP Destination: retries = 3, interval = 20 seconds, Connection timeout = 120 seconds. 1. The Delivery Manager calls the HTTP Destination Sender. The HTTP Destination Sender then sends the request but does not get the response within the connection time out value of 120 seconds (from the Connection time out value specified). 2. Console Gateway retry 1 of 3. The Delivery Manager checks the Console Gateway level retries. If it is greater than 0, then the delivery Manager waits for the specified Console interval (in this case, 20 seconds). a. The HTTP Destination Sender sends the request, but does not get the response within the connection timeout of 120 seconds (from the Connection timeout). b. The Delivery Manager waits for the specified Sleep per Transport properties interval of 3000 ms. c. The HTTP Destination Sender sends the request, but does not get a response within the connection timeout of 120 seconds (from the Connection timeout). This is Transport retry 1 of 2. d. The Delivery Manager waits for the specified Sleep per Transport properties interval of 3000 ms. e. HTTP Destination Sender sends the request, but does not get the response within the connection timeout of 120 seconds (from the Connection timeout). This is Transport retry 2 of 2. 3. Console Gateway retry 2 of 3. Chapter 5. Account administration tasks 47