Table of Contents
Advertisement
3. Click OK in the warning window to confirm deletion.
Uploading transports
About this task
Use the following procedure to upload a transport.
1. Click Account Admin > Profiles > Destinations.
2. Select Manage Transport Type.
3. Click Browse and select the transport.
4. Select whether to commit the new transport to the database.
5. Select whether to overwrite the existing data.
6. Click Upload.
Deleting transports
About this task
If you no longer require a transport, use the following procedure to delete it.
1. Click Account Admin > Profiles > Destinations.
2. Select Manage Transport Type.
3. Click the Delete icon next to the listed transport.
Transport and destination retries
When delivery of a document to a partner destination fails, WebSphere Partner
Gateway attempts to deliver the document again. Each attempt is called a retry.
Retry functionality exists at two levels in WebSphere Partner Gateway: transport
and destination.
Transport retries
Transport retries are built-in, low-level retries that apply to all destinations. The
motivation for low-level retries is that transient failures are inherent in the
networks over which delivery is attempted, particularly the Internet. Thus, the
delivery system is designed to retry automatically without requiring the user to
define the retry parameters explicitly. The number of transport retries
(bcg.delivery.gwTransportMaxRetries) and the time interval between retries
(bcg.delivery.gwTransportRetryInterval) are defined in the Console under System
Administration > DocMgr Administration > Delivery Manager. The default
values are 3 retries at 3 second intervals. If the retry interval is set to 0 then no
Transport retry is attempted, but the destination retry will still occur.
Destination retries (also called document retries)
Destination retry parameters (the number of retries and the interval between
retries) are configured by the user in the destination properties. If the retry interval
is set to 0 then no retry occurs regardless of the settings for Transport retry.
Typically the destination retry interval is longer than the built-in transport retries.
The intent is to specify sufficient time for the user to correct the problem that is
preventing delivery. For example, the destination Web server might be down, or
the destination URL might be incorrect. Setting the parameter values requires that
the user assign values for each destination.
For each destination retry (user defined), WebSphere Partner Gateway will
automatically perform the transport retries. For example, if three destination retries
are specified, the system retry pattern is:
46
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
Advertisement
Table of Contents
