Skip navigation.

Using WebLogic Integration - Business Connect

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Tracker

Tracker enables you to monitor your use of WebLogic Integration - Business Connect by providing runtime and archived views of database records of transactions and events. You also can use Tracker to search for and resend documents to your trading partners or resubmit them through the Server application to your translator or business application.

The following topics are provided.

Concepts

Procedures

Windows and Fields

 


Overview of Tracker

Tracker provides runtime and archived views of records or logs that show your organization's inbound and outbound document traffic as well as alert messages of high importance. Runtime views display database records before they have been archived. Archive view shows database records that have been archived. You control the frequency of archiving in the Administrator Schedules information viewer.

Tracker has information viewers that display database records of inbound, outbound and rejected documents. You can switch between views of the runtime and database records by selecting Runtime or Archive from the Database table drop-down list at the top left. Click Refresh to make sure the latest records are displayed (see Refreshing the Tracker Display.)

The following provides an overview of the information viewers in Tracker.

Alerts

You can view the date, time, partner ID or combined EDI qualifier and ID, contact name, and contact e-mail address for each alert or notification message. You can also view or print the text of the message.

Traffic

You can view runtime and archive database records for inbound, outbound and rejected documents. There are three Traffic information viewers:

The Inbound Traffic and Outbound Traffic information viewers provide an audit trail for documents you received from or sent to your trading partners. The Rejected Traffic information viewer provides a list of inbound or outbound documents that WebLogic Integration - Business Connect could not process and routed to the rejected directory.

Transactions

You can view a reverse chronological listing of each milestone event in the processing of in and outbound documents. For each transaction event, you can see the date, time, control ID, ID or combined EDI qualifier and ID, status, and any message associated with it.

 


Refreshing the Tracker Display

To view the latest database records, click Refresh or select View—>Refresh or press the F5 key. You must refresh the display when you want to view the latest records, especially the latest runtime records.

Tracker database information viewers refresh automatically the first time you display them. Automatic refreshing occurs when you start Tracker. It also occurs the first time you select another information viewer or change from a runtime to archive display or vice versa. Apart from that, you must manually refresh the displays.

When you click Refresh, the action refreshes records on the currently active information viewer, but not others. For example, say you click Refresh while viewing the Inbound Traffic information viewer. The viewer refreshes the record display. But if you switch to the Outbound Traffic information viewer, you must click Refresh again to also refresh the records displayed in that viewer.

If you want to see continuously updated records of document trading activity, open the server monitor page in a browser by selecting Tools—>Launch Server Monitor in Tracker or Administrator.

 


Filtering Tracker Records

Tracker has filters that enable you to view many or few runtime or archive database records at a time in information viewers. The filter settings persist from one Tracker session to another until you change them. You set filters by information viewer by database view. For example, the filter settings for the runtime view of the Alerts information viewer apply only to that window.

Click Filter or select View—>Filter to access the filter window for an information viewer. Use the optional fields to specify the date range and type of records you want to display and click OK.

You can specify to view only records dated between certain dates or records dated within the last number of hours, days or months that you specify.

On filter windows with a maximum records field, you can leave the field blank, which displays all records, or you can type the number of records you want displayed on the information viewer.

On filter windows with a control ID field, you can use the following values to filter records.

Type this

To display this

Control ID

All records associated with that number

XML

All XML records

Binary

All binary records

Profile

All profile records

Certificate

All X509 certificate records


 

 


Printing Tracker Records

You can print a list of the records in the currently active information viewer by selecting File—>Print or pressing Ctrl-P. Tracker prints to your system's default printer.

The application prints the data as displayed on the current information viewer, so maximizing the window size before you print yields longer horizontal printed records. Although the records print in landscape format, you might have to adjust the column widths or hide columns of data in the information viewers to print the columns you want. This is necessary to account for differences in fonts and printers.

You can adjust column widths by placing the cursor over the lines between the columns headings to make a double-arrow appear. Click and hold the left button to adjust the widths. You also can click and drag columns headings to change their locations. You can hide or show columns of data by selecting View—>Columns or right-clicking on a column heading and selecting the columns option.

 


Guidelines for Finding and Reprocessing

You can use Tracker to search for records of documents and, in the case of records of documents in the runtime database, you can submit such documents for reprocessing. Reprocessing involves resending documents to your trading partners or re-submitting documents through WebLogic Integration - Business Connect to your translator or business system. For procedure see Finding and Reprocessing Documents.

The following topics describe the various options for reprocessing documents:

Reprocessing Only the Most Recent Document

When you reprocess a document, WebLogic Integration - Business Connect creates a new version of it with a new, unique file name. You can reprocess each file name only once. To reprocess a document more than once, you must select only the most recently processed document.

For example, you attempt to send to your partner a document with the control ID 100000000 and a file name of 56in. The document is rejected. You use Tracker to resubmit this document through WebLogic Integration - Business Connect to your translator. WebLogic Integration - Business Connect names the resubmitted document (control ID 100000000) to file name 68in. To resubmit the document (control ID 100000000) a second time, choose file name 68in in the Find window.

Note: Tracker cannot reprocess completed documents that have been archived. This includes inbound documents that have been placed in the EDI-in directory and outbound documents for which you have received an MDN.

For procedure see Finding and Reprocessing Documents.

Reprocessing Unacknowledged Documents

When you send a document and you have selected the acknowledge documents option in the partner profile, your trading partner sends you an MDN, which acknowledges the receipt, successful decryption and verification of the document.

If your WebLogic Integration - Business Connect system does not receive an acknowledgment, it attempts to resend the transaction up to the limits in the Partner Profile window Preferences tab. If your system still does not receive an acknowledgment, WebLogic Integration - Business Connect generates and sends you an e-mail alert. You can then locate and resend the unacknowledged document.

From the document status drop-down list on the Find window, select Not Acknowledged to search for unacknowledged documents. When you find the documents you want, you can select them and click Reprocess. WebLogic Integration - Business Connect moves the selected documents to an outbound directory for reprocessing and retransmission to your trading partner.

For procedure see Finding and Reprocessing Documents.

Reprocessing Rejected Documents

You can resend rejected outbound documents to your trading partners and resubmit rejected inbound documents to your WebLogic Integration - Business Connect system for reprocessing.

From the document status drop-down list on the Find window, select Rejected to search for rejected documents. Based on the information about these documents, you should correct whatever condition caused the documents to be rejected before you attempt to reprocess them.

When you find the documents you want, you can select them and click Reprocess. Then the following occurs:

Outbound transactions

WebLogic Integration - Business Connect moves the selected documents to an outbound directory for reprocessing and retransmission to your trading partner. During this reprocessing, WebLogic Integration - Business Connect gives the documents new file names.

Inbound transactions

The documents are queued for reprocessing by WebLogic Integration - Business Connect and resubmission to your translator. The documents retain the same file names WebLogic Integration - Business Connect gave them when it processed or attempted to process them the first time.


 

For procedure see Finding and Reprocessing Documents.

Reprocessing by Control ID

A control ID is the unique identifier assigned to a document by a company's translator application. When you locate a document this way, you can resend it to your trading partners or resubmit it to your WebLogic Integration - Business Connect system for reprocessing.

In the control ID field on the Find window, type the control ID for the document you need to find. The control ID is an alphanumeric ID that has a maximum length of 12 characters. You must include any leading zeros.

When you find the document you want, you can select it and click Reprocess. Then the following occurs:

For outbound transactions

WebLogic Integration - Business Connect moves the selected document to an outbound directory for reprocessing and retransmission to your trading partner. During this reprocessing, WebLogic Integration - Business Connect gives the document a new file name.

For inbound transactions

WebLogic Integration - Business Connect sends a duplicate acknowledgment to the sender of the received document, but does no other processing.


 

For procedure see Finding and Reprocessing Documents.

Reprocessing by Partner

You can search for documents you sent to or received from a certain partner. When you locate the documents, you can resend outbound documents to your trading partners or resubmit inbound documents to your WebLogic Integration - Business Connect system for reprocessing.

From the trading partner drop-down list on the Find window, select the partner associated with the documents you want to find. When you find the documents you want, you can select them and click Reprocess. Then the following occurs:

For outbound transactions

WebLogic Integration - Business Connect moves the selected documents to an outbound directory for reprocessing and retransmission to your trading partner. During this reprocessing, WebLogic Integration - Business Connect gives the document a new file name.

For inbound transactions

WebLogic Integration - Business Connect sends duplicate acknowledgments to the senders of the received documents, but does no other processing


 

For procedure see Finding and Reprocessing Documents.

 


Logging on to Tracker

Use this procedure to start Tracker and log on.

Steps

  1. On Windows, select Programs—>BEA WebLogic Integration - Business Connect 8.1—>Tracker on the Start menu to open the login dialog box.
  2. On UNIX, ensure you have X Windows connectivity to the server where WebLogic Integration - Business Connect is installed. Log in to the account you created during installation. Run the following command to open the login dialog box:

    installation_directory/bin/tracker

  3. Type your user ID and password in the appropriate fields. Use the same user ID and password you use to access Administrator.
  4. Click OK.

 


Manually Archiving Database Records

Use this procedure to force the Server application to archive the runtime database records displayed in Tracker. Activating this feature forces archiving to occur now and overrides the archive schedule, which is accessed from Tools —>Configure Schedule—>Archive Schedule in Administrator. Using this feature also suspends all runtime processing until archiving is completed.

The Server application must be running for immediate archiving to occur.

After archiving is completed, you can switch to the archive view in Tracker to review archived database records.

Steps

  1. Select Tools—>Run Archiver Now in Tracker. A dialog box displays with a message prompting you to confirm whether you want to archive runtime database records.
  2. Click Yes to confirm you want to run the archiving process. A dialog box displays with a message that the archiving process has been scheduled.
  3. Click OK to close the dialog box.

 


Clearing Tracker Database Records

Use this procedure to clear the Tracker runtime or archive database records.

Note: If you clear the runtime database, you will permanently lose all records before they have been archived. Also, if you clear the archive database, you will permanently lose all archived records. Be careful when using these functions.

Steps

  1. Select File—>Clear All Archive Logs or File—>Clear All Runtime Logs.
  2. Click Yes on the confirm delete dialog box to clear all logs.

 


Finding and Reprocessing Documents

Use this procedure to find runtime and archive records of documents in Tracker. After you have found the documents you want, you can reprocess runtime documents, but not archived documents. Reprocessing involves resending documents to your trading partners or re-submitting documents through WebLogic Integration - Business Connect to your translator or business system. See Guidelines for Finding and Reprocessing.

The document search process enables you to search the Tracker database for one or more documents using a filter and then reprocess them. Searches you can perform include:

Tracker can find only those documents in the backup or rejected directories. Consequently, your ability to find and resend or resubmit documents depends on how often you elect to run the archive process.

You cannot reprocess a document that WebLogic Integration - Business Connect has successfully received from a partner. If you need to reprocess a document that already has been successfully received and processed, ask your partner to send the document to you again. Only MDNs that have been rejected can be reprocessed.

If you choose the do not back up option for inbound documents in your company profile preferences, you can use Tracker to access documents only in the rejected directory.

If you choose the back up and archive or the back up and delete option in your company profile preferences, the archive process deletes completed documents or moves them to the archive directory. A completed inbound document is one that has been placed in the inbound document directory. A completed outbound document is one for which you have received an MDN (if you requested one). After these completed documents have been moved or deleted, you can no longer search for them or reprocess them using Tracker.

If you want to reprocess an ebXML document for which you already have received an acknowledgment, be aware of the following. WebLogic Integration - Business Connect repackages documents that are selected for reprocessing. When you reprocess an ebXML document, your partner re-sends the original acknowledgment. This causes your system to generate a message integrity check (MIC) error upon receiving the acknowledgment, because the hash of the outbound reprocessed document does not match the hash of the inbound acknowledgment. This only occurs when an MCD is used and when a messageID element is present in the MCD.

Steps

The following are the steps for setting up a filtered search for documents. You do not have to use all the fields on the Find window to perform a search. The fields are available to help you perform a wide or narrow search.

  1. Click Find on the Tracker toolbar or select Edit—>Find or press Ctrl-F to open the Find window.
  2. Figure 18-1 Find Window

    Find Window


     
  3. Choose a date range for your search if you are not searching by a control ID (see the next step). Note the following about the date fields:
  4. Select a control ID. Because control IDs are unique, you can normally use it as the only search criterion. In other words, when you search for a document by control ID, leave the date fields blank.
  5. You must type all digits of the control ID, including leading zeros. You cannot use wild cards or Boolean symbols in this field.

  6. Select a partner from the trading partner drop-down list to search for documents sent to or received from that partner. Use the default selection All to search for documents for all partners.
  7. Select the direction of the traffic you want to display from the document direction drop-down list. The options are:
  8. Both

    Search for all documents you sent and received.

    Inbound

    Search only for documents you received.

    Outbound

    Search only for documents you sent.


     
  9. Select a document status from the document status drop-down list. The options are:
  10. All

    Search for documents in all status categories.

    Acknowledged

    Search for documents for which you received acknowledgments (MDNs).

    Ack Not Requested

    Search for documents for which you did not request acknowledgments (MDNs).

    Not Acknowledged

    Search for documents that timed-out before they could be sent or for which you did not receive acknowledgments (MDNs).

    Rejected

    Search for rejected documents.

    Rejected or Not Acknowledged

    Search for unacknowledged and rejected documents.


     
  11. Click Search to find documents that meet your search criteria. If documents are found, information about them is displayed (see Field Descriptions). If no documents are found, a message to that effect is displayed.
  12. When you find the documents you want, you can reprocess one or more documents by selecting them and clicking Reprocess.
  13. Click Close to exit the Find window.

Field Descriptions

The following describes the fields on the Find window for documents that Tracker has found that meet your search criteria. For procedure see Steps.

Date

The date and time WebLogic Integration - Business Connect processed the document. You can sort records in ascending or descending order by clicking the arrow in this column.

Control ID

The document's control ID. For EDI documents, this is the number assigned by the translator.

Documents without control IDs might be binary or XML documents. Or, it is an inbound document that WebLogic Integration - Business Connect could not read and placed in the rejected directory.

Sender ID

The ID or combined EDI qualifier and ID of the sender.

Receiver ID

The ID or combined EDI qualifier and ID of the recipient.

Direction

Indicates whether the document is inbound (you received it) or outbound (you sent it).

Acknowledgment

Values that can appear in this field for inbound documents include:

Yes

You sent an acknowledgment to the document's sender.

No

You did not send an acknowledgment, or your trading partner did not request that you send one.

N/A

Not applicable.


 

Values that can appear in this field for outbound documents include:

Yes

You received an acknowledgment from the document's recipient.

No

You did not receive an acknowledgment from the document's recipient, or you did not request that your partner send one.

N/A

Not applicable.

Unexpected processing error


 

Rejected

Values that can appear in this field include:

Yes

WebLogic Integration - Business Connect could not process this document and placed it in the rejected directory.

N/A

WebLogic Integration - Business Connect successfully processed this document.


 

Transport

The transport method.

File

The file name that your WebLogic Integration - Business Connect assigned to the document, either inbound or outbound.

Path

The complete path to the directory where this document is stored. This path is to one of the following directories.

Backup directory

WebLogic Integration - Business Connect stores all inbound and outbound documents in this directory. If the document is stored here, it has been processed successfully. The document is stored in this directory until the next time the WebLogic Integration - Business Connect archive process runs.

Rejected directory

Documents that WebLogic Integration - Business Connect cannot successfully process are stored in the rejected directory.


 

 


Alerts Information Viewer

Use the Alerts information viewer to examine records for alerts and notifications.

Access the viewer by selecting Alerts on the Tracker bar.

WebLogic Integration - Business Connect continuously performs self-checks to ensure proper operation. When it detects a problem, WebLogic Integration - Business Connect generates an alert or notification that appears in the Alerts information viewer. Simultaneously, WebLogic Integration - Business Connect sends your point of contact an e-mail message that describes the problem in plain text. Such e-mails are sent if a contact person's e-mail address is provided in the alert or notify mail address fields on the Preferences tab of the Company Profile window.

You can view the text of alerts and notifications by placing the cursor over the record line in the Alerts information viewer, right-clicking and selecting View on the pop-up menu. This displays a pop-up window with the text of the message. You also can copy a message by right-clicking. You can paste copied messages into a text editor.

Figure 18-2 Right-Click a Record and Select View to Display the Message

Right-Click a Record and Select View to Display the Message


 

Description of Alert E-Mail

Identified by the word alert in the e-mail subject line, alert messages are sent when WebLogic Integration - Business Connect detects a condition that halts document exchange and requires you to take action. An example is when WebLogic Integration - Business Connect cannot connect to the network or when there is a problem with the WebLogic Integration - Business Connect software.

Description of Notification E-Mail

Identified by the word notification in the e-mail subject line, notification messages are informational and do not require you to take action. Document exchange continues. WebLogic Integration - Business Connect sends a notification, for example, when it rejects a document or when it receives a binary (non-EDI) document from a partner for which it does not have a partner profile.

Figure 18-3 Alerts information Viewer

Alerts information Viewer


 

Field Descriptions

The following describes the fields on the Alerts information viewer.

Date

The date and time of the message. You can sort records in ascending or descending order by clicking the arrow in this column.

ID

The partner ID or combined EDI qualifier and ID for the document that caused or is related to this message.

Contact

The name of the person to whom the message was sent.

E-mail

The e-mail address, if any, to which the message was sent. This e-mail address is specified in the Company Profile window Preferences tab.

Message

The text of the message.

 


Traffic Information Viewers

Use the Traffic information viewers to view runtime and archive database records for inbound, outbound and rejected documents. There are three Traffic information viewers:

Access each viewer by selecting the corresponding icon on the Tracker bar.

The Inbound Traffic and Outbound Traffic information viewers provide an audit trail for documents you received from or sent to your trading partners.

The Rejected Traffic information viewer provides a list of inbound or outbound documents that WebLogic Integration - Business Connect could not process and routed to the rejected directory.

Reprocessing Documents

You can reprocess documents whose records appear in the runtime database of the Inbound Traffic, Outbound Traffic and Rejected Traffic information viewers. You do this by selecting one or more records, right-clicking, and selecting Reprocess on the pop-up menu. Or, you can select one or more records and select Tools—>Reprocess.

Reprocessing does the following:

Copying, Viewing, or Deleting Records

You can right-click records in the Traffic information viewers to view an inbound or rejected document or to copy or delete a record. The following describes what you can do in each viewer.

In the Inbound Traffic and Rejected Traffic information viewers you can:

In the Outbound Traffic information viewer you can:

In addition, in the Rejected Traffic information viewer you can double-click a record to view a dialog box with a plain text message about why the document was rejected.

Viewing Documents

In the Inbound Traffic and Rejected Traffic information viewers, you can display the document by right-clicking it and selecting View from the menu as follows:

Inbound and Outbound Traffic Field Descriptions

The following describes the fields on the Inbound Traffic and Outbound Traffic information viewers. The fields are on both viewers, except as noted.

Date

The date and time the record was created of the inbound, outbound or rejected document. You can sort records in ascending or descending order by clicking the arrow in this column.

Control ID

Possible values include:

Control ID

The control ID of an EDI document.

XML

An XML document without a control ID.

Binary

A binary document without a control ID.

Profile

The document is a profile created with WebLogic Integration - Business Connect.

Certificate

The document is an X509 certificate with a public key.


 

Sender ID

The ID or combined EDI qualifier and ID of the document's sender.

Receiver ID

The ID or combined EDI qualifier and ID of the document's recipient.

Acknowledgment (Inbound Traffic)

The acknowledgment status of the document. Possible values for inbound documents include:

Not Requested

Your partner did not request an acknowledgment.

Pending

You received the document, created an MDN and placed it in the queue to send.

Sent

You sent an MDN to your trading partner for this document.

Unknown

The acknowledgment status of the document cannot be determined because of an error condition in the database.


 

Acknowledgment (Outbound Traffic)

The acknowledgment status of the document. Possible values for outbound documents include:

Authentication Failed

Your remote trading partner could not verify the document you sent.

Decryption Failed

Your remote trading partner could not decrypt the document you sent.

Failed

Your remote trading partner could not process the document for unknown reasons.

Not Received

You have not yet received an acknowledgment for a document you sent.

Not Requested

You did not request an MDN.

Received

You received an acknowledgment for a document you sent.

Received, Generic

You received an S/MIME acknowledgment from a mail client.

Received, INVALID

You received a non-standard acknowledgment that did not specify a reason the remote trading partner could not process the document you sent.

Resend Limit Reached

WebLogic Integration - Business Connect re-sent the document as many times as you specified without receiving a requested acknowledgment. WebLogic Integration - Business Connect sends you an alert and does not attempt to send the document again.


 

Processed (Inbound Traffic)

Indicates whether WebLogic Integration - Business Connect processed the inbound document. Possible values are:

Yes

WebLogic Integration - Business Connect has completed processing the inbound document.

No

WebLogic Integration - Business Connect has not completed processing the inbound document.


 

Processed (Outbound Traffic)

Indicates whether WebLogic Integration - Business Connect processed the outbound document. Possible values are:

Yes

WebLogic Integration - Business Connect has completed processing the outbound document.

No

WebLogic Integration - Business Connect has not completed processing the outbound document.

Initial Send

WebLogic Integration - Business Connect sent the document and is waiting for an acknowledgment.

Retry-n

WebLogic Integration - Business Connect has sent the document again because it had not received an acknowledgment. The number of retries this attempt represents is indicated by the number (n) following the dash.

Retry Limit Exceeded

WebLogic Integration - Business Connect has attempted to re-send the document for the duration specified on the Partner Profile window Preferences tab.


 

Original File

The file name of the inbound or outbound document. This is the original name of the file as it originated on the sender's system.

Unique ID

The identification WebLogic Integration - Business Connect assigns to the document.

Backup File

The name of the file as it appears in the backup directory.

MDN File (Outbound Traffic)

The name of the MDN or ACK file in the backup directory, if you received an MDN or acknowledgment from a partner to acknowledge receiving a document from you. This serves to associate the MDN or ACK you received with the document you sent.

Type

The document type. Possible values include:

Binary

Binary (non-EDI) document

Certificate

X509 certificate containing the public key

MDN

MDN or acknowledgment

Profile

WebLogic Integration - Business Connect partner profile

X12

X12 EDI document

XML

XML document


 

Size

The file size in bytes of the inbound or outbound document.

Security Level

The security applied to this document. Possible values include:

Clear text

The document is neither encrypted nor signed.

Signed

The document is signed.

Encrypted

The document is encrypted.

Signed, Encrypted

The document is signed and encrypted.

Unknown

The security of the document cannot be determined because of an error condition in the database.


 

Transport

The transport method.

File (Inbound Traffic)

The fully qualified path to the document in the EDI-in, XML-in or binary-in directory.

Rejected Traffic Field Descriptions

The following describes the fields on the Rejected Traffic information viewer.

Date

The date and time the document was rejected. You can sort records in ascending or descending order by clicking the arrow in this column.

Control ID

Possible values include:

- The control ID of a rejected EDI document.

- NA-The document is an XML or binary document.

Sender ID

The ID or combined EDI qualifier and ID of the document's sender.

Receiver ID

The ID or combined EDI qualifier and ID of the document's recipient.

Type

The document type. The possible values are:

Binary

Binary (non-EDI) document

Certificate

X509 certificate containing the public key

MDN

MDN or acknowledgment

Profile

WebLogic Integration - Business Connect partner profile

X12

X12 EDI document

XML

XML document


 

Original File

The original file name of the rejected document as it was sent by the originator.

Unique ID

The identification WebLogic Integration - Business Connect assigns to the document.

File

The unique name WebLogic Integration - Business Connect gives to the file. This is the name of the file as it appears in the Rejected directory.

Transport

The transport method.

Reason

The reason WebLogic Integration - Business Connect rejected the document.

 


Transactions Information Viewer

Use the Transactions information viewer to view records about transaction activity. This viewer provides an audit trail for successfully processed and transmitted documents as they move through the system.

Access the viewer by selecting Transactions on the Tracker bar.

In the Transactions information viewer you can copy a record by right-clicking it and selecting Copy from the pop-up menu. You can then paste the record contents into a text editor.

Figure 18-5 Transactions Information Viewer

Transactions Information Viewer


 

Field Descriptions

The following describes the fields on the Transactions information viewer.

Date

The date and time of the event. You can sort records in ascending or descending order by clicking the arrow in this column.

Control ID

The possible values are:

Control ID

The control ID of an EDI document.

XML

An XML document without a control ID.

Binary

A binary document without a control ID.

Profile

The document is a profile created with WebLogic Integration - Business Connect.

Certificate

The document is an X509 certificate with a public key.


 

ID

The partner ID or combined EDI qualifier and ID associated with this transaction.

Status

The status of the transaction. Possible values include:

For outbound documents:

Document Packaged

WebLogic Integration - Business Connect encrypted, signed, and optionally compressed the document.

Document Sent

WebLogic Integration - Business Connect sent the document.

MDN Received

WebLogic Integration - Business Connect received an acknowledgment from the trading partner indicating the receipt of the document.


 

For inbound documents:

Document Received

WebLogic Integration - Business Connect received a document from a remote trading partner.

Document Transferred

WebLogic Integration - Business Connect decrypted, verified and optionally uncompressed the document and transferred it to the EDI In, XML In, or Binary In directory.

MDN Sent

WebLogic Integration - Business Connect sent an acknowledgment to the remote trading partner.


 

Source

The transport method.

Original File Name

The original name of the file. This enables you to distinguish between binary documents because all such documents are listed as binary in the ID field.

 

Skip navigation bar  Back to Top Previous Next