Redo Transmission Processing

This page is accessed via Business Process Automation > Process Management > Redo Transmission Processing.

Use this page in the Process Manager to:

• Re-send outbound transmissions with a REDO status.
• Reprocess inbound transmissions with a REDO status.

You can redo the transmissions immediately or at regular intervals. When a redo transmission is done, the communication method will be the same as the original transmission.

Note: Regardless of any settings, if the system is restarted, any transmission with a FRESH status is automatically set to REDO.

How to Set the Status to REDO

You can manually set the status of a transmission to REDO in the Transmission Manager.

For outbound transmissions, you can also have Oracle Transportation Management automatically set the status to REDO.

Automatic REDO Status

When allowing Oracle Transportation Management to automatically set the status to REDO, a lot of transmissions may be scheduled for re-send. To control the rate of retries, you can schedule a recurring process:

• Set the Redo Number of Outbound Transmissions to some fixed number, like 50, to limit the number of transmissions Oracle Transportation Management tries to re-send each time.
• Schedule the process to run every 15 minutes or so to control the frequency of re-send attempts.

Note: If you leave the Redo Number of Outbound Transmissions field blank, Oracle Transportation Management re-sends all transmissions. This is probably disastrous behavior when glog.httppost.transmissionStatusOnFailure is REDO.

Use the Transmission Manager to identify old transmissions which cannot succeed (for example, if they contain a bad URL). These should be marked as PROCESSED to stop the HTTP retries.

1. Select the Transmission Type you want to send.
2. Enter the number of inbound transmissions you want to re-process in the Redo Number of Inbound Transmissions text box. If you leave it blank, Oracle Transportation Management re-processes all inbound transmissions. The oldest transaction is re-processed first.
3. Do the same in the Redo Number of Outbound Transmissions field.
4. If you are running cluster scalability, specify a cluster to which this request should be assigned.
5. Enter a User Role. When you run, publish, or schedule a recurring process, you can specify the user role used to perform the process, just like when you run agents. The user role can be used to specify a separate VPD role or another domain to run the agent. When a recurring process is modified, the user role of the recurring process can be modified as well.
6. Select a Log Profile to generate focused logging when reproducing an error for the specific action. You cannot select a log profile when you choose to schedule a process, as automatic generation of action logs is not supported.
7. Select Execute, Publish, or Schedule to determine when the process will be executed.
8. Click Submit.