Transmission Manager

This page is accessed via Business Process Automation > Integration > Transmission Manager.

If the transmission has the Inbound check box selected, it is considered an inbound transmission. Otherwise it is an outbound transmission.

The Transmission Manager lets you set the status of transmissions. You should frequently use the Transmission Manager to identify old transmissions which cannot succeed (for example a bad URL). These should be marked as PROCESSED or ERROR to stop automatic HTTP retries. Several statuses exist for transmissions:

• STAGED: The transmission is initially stored in the transmission tables.
• STAGING: The transmission has been staged and is waiting on a condition to be released for processing.
• FRESH: The transmission is waiting to complete processing.
• ERROR: The transmission has completed processing and there were errors during processing. When a error occurs, the system sends out a TransmissionReport to the external system. After examining the TransmissionReport, you can try to find the cause of the failure. Often missing data causes Oracle Transportation Management to fail to process a transmission. For example, a TransOrder may reference a location you have not yet entered into Oracle Transportation Management. After correcting the cause of the failure, you can reprocess the failed transmission.
• PROCESSED: The transmission successfully completed processing.
• REDO: When you perform the Mark as Redo action, this status is set. It indicates to the system that the transmission is ready to be reprocessed in process management. By setting this property to REDO, the Redo Transmission Processing process can automatically resend the transmission.

The Content Type field describes the format of the inbound/outbound transmission. The default is application/xml.

The External Status is the status value sent in by the system from which the transmission was received.

The Insertion Time indicates the time when the transmission entered the Oracle Transportation Management database. The Last Update Time shows the last time the transmission was updated.

The Acknowledgement Option is specified on the XML transmission. Depending on the setting, the transmission report may be generated or not.

• Error: The transmission report is only generated if there is an error.
• Yes: The transmission report is always generated.
• No: The transmission report is not generated.

If the Stop Process on Error check box is selected, the system does not process any further transactions after a faulty transaction occurs.

The Retries field shows the number of attempts that have been made to re-send the transmission. This count shows a value greater than 1 if a retry has been attempted or is in the process of being attempted. If the field is 0, then no retries were made.

The First Attempt and Last Attempt times are logged in GMT and not the local time zone.

Click the Details button to see the XML/JSON transmission or transaction.

Click the Persisted XML or Persisted JSON button to see the unformatted XML or JSON. You can then copy the XML/JSON and reuse it. If the XML is large enough for the transmission or transactions, it will be written out to a file on the server. The maximum size for viewing a transmission or transaction is controlled by this property: glog.integration.transmission.rawxml.maxchars. The Persisted XML/JSON button displays data stored in the database for the selected transmission number. For inbound XMLs, the Processed XML/JSON button displays data processed by the system for the selected transmission number.

The Transaction XML/JSON button displays process data of the associated transaction.