Messages

Table 18-1 Message Types

Type	Description
Level 0 Messages	Level 0 messages identify normal events in WebLogic Integration - Business Connect. When you set Tracker to display level 0 and above messages, you show most events that occur in WebLogic Integration - Business Connect, including normal milestone events involving the packaging and movement of documents.
Level 1 Messages	Level 1 messages identify general notification events requiring no action. When you set Tracker to display level 1 and above messages, WebLogic Integration - Business Connect sends notifications of certain events that are not errors. Level 1 is the default message level in Tracker.
Level 2 Messages	Level 2 messages identify documents received from trading partners that WebLogic Integration - Business Connect has rejected. When you set Tracker to display level 2 and above messages, WebLogic Integration - Business Connect logs such errors and sends notifications via e-mail if you provided an e-mail address for notifications on the Company Profile Preferences tab.
Level 3 Messages	Level 3 messages identify general errors occurring in WebLogic Integration - Business Connect. When you set Tracker to display level 3 and above messages, WebLogic Integration - Business Connect sends notifications of errors.
Level 4 Messages	Level 4 messages identify connection exceptions. When you set Tracker to display level 4 and above messages, WebLogic Integration - Business Connect sends alerts for expected activity. Contact your network administrator for assistance.
Level 5 Messages	Level 5 messages identify transport errors. When you set Tracker to display level 5 and above messages, WebLogic Integration - Business Connect sends alerts of problems with the transport configuration. Contact your WebLogic Integration - Business Connect administrator for assistance.
Level 6 Messages	Level 6 messages identify that a transport has not been selected for sending documents to a trading partner. When you set Tracker to display level 6 and above messages, WebLogic Integration - Business Connect sends alerts in the event of transport configuration problems.
Level 7 Messages	Level 7 messages identify unexpected errors. When you set Tracker to display level 7 and above messages, WebLogic Integration - Business Connect sends alerts of errors not accounted for under other levels.
Level 8 Messages	Level 8 messages identify duplicate server errors. When you set Tracker to display level 8 messages only, WebLogic Integration - Business Connect sends alerts.

Table 18-2 Level 0 Messages

Level 0 message	Description
Agent started	An agent has started and is running.
Alert sent	An alert e-mail message has been created and sent.
Archive completed	The archiving process has completed successfully.
Backup file has been archived	A confirmation that a file was moved successfully from the backup directory to the archive directory.
Backup file has been deleted	A confirmation that a file was deleted successfully from the backup directory during the archiving process.
Companies started	Server has completed its startup routine.
Companies starting	Server starts all company-based threads (packager, inbound, https servers, and so on).
Duplicate MDN received	WebLogic Integration - Business Connect received a message disposition notice (MDN) for an outbound document that already has been acknowledged. This is because the original document was resent automatically, so multiple MDNs were returned. Or, the MDN was not deleted from the transport server after it was processed.
Duplicate received (automated resend)	WebLogic Integration - Business Connect received more than once a document that a partner resent automatically. WebLogic Integration - Business Connect discards all subsequent documents.
File backed up	A file has been copied to the backup directory.
MDN received with no matching outbound document	WebLogic Integration - Business Connect received an MDN for which there is no current record of a matching outbound document in the database. This might be because an outbound record was archived.
Partner certificate updated	A partner certificate has been changed, and the database has been updated successfully.
Partner profile updated	A partner profile has been changed, and the database has been updated successfully.
Server configuration completed	Server has successfully configured all agents and threads.
Server configuration started	Server starts all agents and threads and also starts building Administrator objects such as companies, partners, certificates and schedules.
Server shutdown completed	Server has successfully shut down all agents and threads.
Server shutdown started	Server begins the process of cleanly shutting down agents and threads.
Software registered	A software registration e-mail message has been created and sent.

Table 18-3 Level 1 Messages

Level 1 message	Description
MDN received	WebLogic Integration - Business Connect has received a message disposition notice (MDN), which confirms that the partner has received the document you sent.
MDN sent	WebLogic Integration - Business Connect has sent an MDN to a trading partner to acknowledge receiving a document from that partner.
Packaged	WebLogic Integration - Business Connect has successfully packaged a document for delivery. Packaged means the document has been encrypted and MIME wrapped.
Received	WebLogic Integration - Business Connect has received a document from a trading partner.
Sent	WebLogic Integration - Business Connect has successfully sent a document to a trading partner.
Transferred	WebLogic Integration - Business Connect has successfully copied a document received from a trading partner to the inbound and backup directories.

Table 18-4 Level 2 Messages

Level 2 message	Description, cause, remedy
Received miscellaneous document	WebLogic Integration - Business Connect received a binary or unidentifiable document that could not be associated with a partner. The file was placed in the company's other directory. Cause 1 WebLogic Integration - Business Connect received a binary document for a partner that has not been configured to receive such documents. In other words, there was no matching partner for the inbound document. Remedy 1 Examine the received file as necessary. Select a company for this partner in the binary company drop-down list in the partner's profile in WebLogic Integration - Business Connect. Cause 2 A MIME message does not have body parts. WebLogic Integration - Business Connect received an e-mail message without an attachment for this partner. Remedy 2 Resend or resubmit this document in Tracker. If necessary, examine the document in the other directory to see whether it is the one you need to receive. You then can manually route it to the appropriate application. If you want to receive binary documents from this partner, select a company in the binary company drop-down list in the partner's profile in WebLogic Integration - Business Connect.

Level 2 message

Description, cause, remedy

Received miscellaneous document

WebLogic Integration - Business Connect received a binary or unidentifiable document that could not be associated with a partner. The file was placed in the company's other directory.

Cause 1

WebLogic Integration - Business Connect received a binary document for a partner that has not been configured to receive such documents. In other words, there was no matching partner for the inbound document.

Remedy 1

Examine the received file as necessary. Select a company for this partner in the binary company drop-down list in the partner's profile in WebLogic Integration - Business Connect.

Cause 2

A MIME message does not have body parts. WebLogic Integration - Business Connect received an e-mail message without an attachment for this partner.

Remedy 2

Resend or resubmit this document in Tracker. If necessary, examine the document in the other directory to see whether it is the one you need to receive. You then can manually route it to the appropriate application.

If you want to receive binary documents from this partner, select a company in the binary company drop-down list in the partner's profile in WebLogic Integration - Business Connect.

Table 18-5 Level 3 Messages

Level 3 message	Description, cause, remedy
Duplicate document	WebLogic Integration - Business Connect received an EDI document with a control ID that was the same as a previously received document's control ID. WebLogic Integration - Business Connect detected this because the check box for preserving inbound binary and XML file names is selected for the partner's profile. Cause 1 Your partner sent you more than one EDI document with the same control ID. Remedy 1 If necessary, contact your partner for clarification. Cause 2 The check box for preserving inbound binary and XML file names is unintentionally selected on the Preferences tab for the partner's profile. Remedy 2 Turn off the selection for the partner's profile.
EDI parsing error	WebLogic Integration - Business Connect attempted to process a malformed X12 or EDIFACT document from your translator and rejected it. Cause 1 Your translator put a malformed EDI document in the WebLogic Integration - Business Connect EDI outbound directory. Remedy 1 Have your translator resubmit the document. Or, verify whether the rejected file is an EDI file; if not put the file in the correct outbound directory. Cause 2 WebLogic Integration - Business Connect received a malformed EDI document from a trading partner. The application determines this by checking the document for certain standard information that EDI documents should have. Remedy 2 Examine the file and contact the partner to resolve the EDI formatting problem.
Insufficient security: not encrypted	WebLogic Integration - Business Connect received an encrypted document from a partner, but was expecting to receive an unencrypted document. Or, WebLogic Integration - Business Connect received an unencrypted document from a partner, but was expecting to receive an encrypted document. WebLogic Integration - Business Connect requires you and your partner to have identical settings for signing documents, encrypting documents, acknowledging documents and signing acknowledgments. Cause 1 You and your partner do not have synchronized settings for document encryption. Remedy 1 Make sure you and your partner have the same setting for document encryption on the Partner Profile Security tab for your respective partners. The encrypt documents check box should be either checked or unchecked on both systems. Once the setting is synchronized, have your partner resend the document.
Insufficient security: not signed	WebLogic Integration - Business Connect received a signed document or MDN from a partner, but was expecting to receive an unsigned document or MDN. Or, WebLogic Integration - Business Connect received an unsigned document or MDN from a partner, but was expecting to receive a signed document or MDN. WebLogic Integration - Business Connect requires you and your partner to have identical settings for signing documents, encrypting documents, acknowledging documents and signing acknowledgments. Cause 1 You and your partner do not have synchronized settings for document signing. Remedy 1 Make sure you and your partner have the same setting for document signing on the Partner Profile Security tab for your respective partners. The sign documents check box should be either checked or unchecked on both systems. Once the setting is synchronized, have your partner resend the document. Cause 2 WebLogic Integration - Business Connect received an unsigned MDN. Remedy 2 Make sure you and your partner have the same setting for acknowledgments on the Partner Profile Security tab for your respective partners. The acknowledgment check box should be checked on both systems.
Invalid certificate used to verify	The certificate used to sign the document does not match a valid partner certificate. Cause 1 The certificate the partner is using to sign does not match one of your valid certificates for that partner. Remedy 1 Verify with the partner that certificates are correct.
Invalid MDN received	WebLogic Integration - Business Connect received an MDN that has a disposition of null or something other than processed, displayed or dispatched. Cause 1 Your partner failed to verify or decrypt a document that you sent. Remedy 1 Open the MDN with a text editor and determine its disposition. Compare the fingerprints in your and your partner's certificates. Cause 2 The partner had an unexpected parsing or processing error. Remedy 2 Examine the disposition of the rejected MDN. Verify with the partner that certificates are correct.
Malformed MIME message	WebLogic Integration - Business Connect received a malformed multipurpose Internet mail extensions (MIME) message. Cause 1 Data were corrupted during transport. Remedy 1 Examine the rejected file to determine the document type, sender, and so on. Ask the partner to resend the document to you. Cause 2 The trading partner is using FTP and has unchecked the check boxes for signing, encrypting and acknowledging documents on the Partner Profile Security tab. Because of this, the document was sent in FTP ASCII mode. Remedy 2 Ask the partner to check the check box for signing or encrypting documents on the Partner Profile Security tab or for compressing documents on the Partner Profile Preferences tab. This ensures documents are sent in FTP binary mode. WebLogic Integration - Business Connect requires you and your partner to have identical settings for signing documents, encrypting documents, acknowledging documents and signing acknowledgments. Cause 3 WebLogic Integration - Business Connect received via FTP a non-MIME wrapped document either from a partner who has turned off document signing, encrypting, acknowledging and compression in WebLogic Integration - Business Connect or from a partner who uses a trading engine other than WebLogic Integration - Business Connect. WebLogic Integration - Business Connect does not support receiving non-MIME wrapped data. Remedy 3 If your partner uses WebLogic Integration - Business Connect, ask your partner to turn on document signing, encrypting, acknowledging or compression for sending via FTP. Then ask your partner to resend the document.
No active encryption certificate	WebLogic Integration - Business Connect attempted to encrypt a document for a partner for whom you do not have an active certificate. Cause 1 You have one or more certificates for this partner, but none are active. Remedy 1 In the Certificates window in WebLogic Integration - Business Connect, select and activate the certificate. Cause 2 There are no certificates for this partner. Remedy 2 Ask the partner to send you a certificate. Cause 3 You do not want to exchange encrypted documents with this partner. Remedy 3 Clear the encrypt documents check box on the Security tab for this partner profile in WebLogic Integration - Business Connect.
No active partner	WebLogic Integration - Business Connect attempted to process a document for which there is no active partner. Cause 1 An EDI or XML document was dropped in the corresponding outbound directory. The document's recipient ID does not match any active partner. Remedy 1 Import and activate the profile of the partner to whom the document addressed. Resend the document in Tracker. If you do not want to send documents to this partner, make sure your EDI translator or XML application does not place documents in the outbound directories for WebLogic Integration - Business Connect. Cause 2 WebLogic Integration - Business Connect received a document from an inactive or nonexistent partner. Remedy 2 If you do not have a profile for this partner, ask the partner to send you one that you can import to WebLogic Integration - Business Connect. If you have a profile for this partner but it is inactive, activate it in the Partner window in WebLogic Integration - Business Connect.
No active signer certificate	WebLogic Integration - Business Connect attempted to sign a document or an MDN for a company for which there is no active certificate. Cause 1 A certificate exists for this company profile, but it is not active. Remedy 1 In the Certificates window in WebLogic Integration - Business Connect, select and activate the certificate. Cause 2 There is no certificate for this company profile. Remedy 2 Generate a self-signed certificate from the Certificates window in WebLogic Integration - Business Connect. Or, import a third-party certificate. Cause 3 You do not want to exchange signed documents with this partner. Remedy 3 Clear the sign documents check box on the Security tab for this partner profile in WebLogic Integration - Business Connect.
Returned message	WebLogic Integration - Business Connect received a message from a partner who has an ID identical to yours. Cause 1 You are trading documents with yourself (that is, testing with a single company exported or imported as the partner). Remedy 1 Create another company profile with a different ID. Export and import the second company and have the first company trade with the second company. Cause 2 The transport server (most likely SMTP-POP) has returned or bounced the message. Remedy 2 Verify the partner's e-mail address and the state of the SMTP-POP server and connection. Cause 3 There are two real-world companies with identical IDs. Remedy 3 Create another company profile with a unique ID or ask your partner to do so.
Security framework failed to verify signature	WebLogic Integration - Business Connect failed to verify the signature of a document. This indicates that the document you received has changed in some way from the original document that your partner sent you. Cause 1 The document was corrupted in transport. Remedy 1 Ask your partner to resend the document to you. Cause 2 An untrusted party attempted to send you a document. Remedy 2 Ask your partner to verify the document.
Security framework unable to verify - certificate expired	The certificate your partner used to sign a document you received has expired. Cause 1 The certificate has expired. Remedy 1 Ask your partner to generate or purchase a new certificate. Cause 2 Your and your partner's system time or time zone settings are not synchronized. Remedy 2 You and your partner should synchronize your system clocks. WebLogic Integration - Business Connect calculates Greenwich Mean Time (GMT) for document traffic based on the local time zones you select in WebLogic Integration - Business Connect and for your operating system. This serves to synchronize time between you and your trading partners. Make sure you and your partner have selected your local time zones in WebLogic Integration - Business Connect and in your operating systems.
Security framework unable to verify - certificate not yet valid	The partner's certificate that is used to verify an inbound document is not valid. This is because the date the certificate was created is later than your system's current date. Cause 1 The certificate is not valid yet. Remedy 1 Contact the partner. Wait until the certificate is active or request the partner to generate or purchase a new certificate. Cause 2 Your and your partner's system time or time zone settings are not synchronized. Remedy 2 You and your partner should synchronize your system clocks. WebLogic Integration - Business Connect calculates Greenwich Mean Time (GMT) for document traffic based on the local time zones you select in WebLogic Integration - Business Connect and for your operating system. This serves to synchronize time between you and your trading partners. Make sure you and your partner have selected your local time zones in WebLogic Integration - Business Connect and in your operating systems.
Security framework unable to verify - invalid signature	The certificate within an S/MIME document you received has changed. Cause 1 The document was corrupted during transport. Remedy 1 Contact the partner and request a resend or wait for an automatic resend. Cause 2 Your trading partner might have changed his or her certificate without updating you. Remedy 2 Ask your trading partner to send you a new certificate.
Security framework unable to verify - root not found	The root certificate of the certificate used to sign a received document does not exist in the root store. Cause 1 The document was corrupted during transport. Remedy 1 You can either ask your partner to resend the document to you or you can wait until WebLogic Integration - Business Connect automatically resends the document to you.
Security framework unable to verify - unknown root	The certificate your partner used to sign a document has an unknown or untrusted root certificate. Cause 1 The certificate chain that your partner uses to sign documents does not match one of the valid certificate chains you have for that partner. Remedy 1 Ask your partner to verify whether the partner's certificate and your certificate are correct. Cause 2 An untrusted party attempted to send you a document. Remedy 2 Ask the partner to verify the document that was sent.
The returned MDN MIC value was invalid	WebLogic Integration - Business Connect received an MDN with a MIC (message integrity check) that does not match that of the corresponding outbound document. Cause 1 A non-trusted party has sent the MDN. Remedy 1 Contact the partner to verify the state of the remote servers and network.
Unable to decrypt	The decryption of a public key-encrypted MIME message failed. Cause 1 The public key the partner is using to encrypt does not match one of your valid private keys. Remedy 1 Verify with the partner that the certificates are correct. Cause 2 The data was corrupted during transport. Remedy 2 Contact the partner and request a resend.
XML parsing error	WebLogic Integration - Business Connect attempted to process a malformed XML document and rejected it. Cause 1 Your XML application put a malformed XML document in the WebLogic Integration - Business Connect XML outbound directory. Remedy 1 Have your XML application resubmit the document. Or, verify whether the rejected file is an XML file; if not put the file in the correct outbound directory. Cause 2 WebLogic Integration - Business Connect received and rejected a malformed XML document. Remedy 2 Examine the file and contact the partner to resolve the formatting problem.

Table 18-6 Level 4 Messages

Level 4 message	Description, cause, remedy
Resend limit reached	WebLogic Integration - Business Connect has resent the document the configured number of times but has not received an acknowledgement from the trading partner. Cause 1 If you are sending documents by e-mail, the e-mail address might be incorrect. Remedy 1 Verify the e-mail address with your trading partner. Cause 2 The partner's transport server is failing or not in service. Remedy 2 Contact the partner. Cause 3 The partner is not online. Remedy 3 Contact the partner and verify that the partner's trading engine is online. Cause 4 If you are sending documents by FTP, the FTP information might be incorrect. Remedy 4 Verify with your partner the FTP inbox and pickup directories and the FTP server.

Level 4 message

Description, cause, remedy

Resend limit reached

WebLogic Integration - Business Connect has resent the document the configured number of times but has not received an acknowledgement from the trading partner.

Cause 1

If you are sending documents by e-mail, the e-mail address might be incorrect.

Remedy 1

Verify the e-mail address with your trading partner.

Cause 2

The partner's transport server is failing or not in service.

Remedy 2

Contact the partner.

Cause 3

The partner is not online.

Remedy 3

Contact the partner and verify that the partner's trading engine is online.

Cause 4

If you are sending documents by FTP, the FTP information might be incorrect.

Remedy 4

Verify with your partner the FTP inbox and pickup directories and the FTP server.

Table 18-7 Level 5 Messages

Level 5 message	Description, cause, remedy
Network error: inbound or Network error: outbound	WebLogic Integration - Business Connect is unable to send or receive documents due to transport protocol or network problems. Cause 1 The FTP or POP server is offline. Remedy 1 Verify the status of the POP server or FTP server or both. Cause 2 The local network is down. Remedy 2 Verify the network status. Cause 3 A firewall might be impeding document transport. Remedy 3 Verify correct connectivity through the firewall for inbound and outbound documents.
Unable to send	WebLogic Integration - Business Connect cannot send documents due to transport protocol or network problems. Cause 1 The SMTP or FTP server is offline. Remedy 1 Verify the status of the SMTP or FTP server. Cause 2 The local network or Internet connection is down. Remedy 2 Verify the network status. Cause 3 The partner's HTTPS server is offline. Remedy 3 Contact the partner and verify the status of the HTTPS server.

Level 5 message

Description, cause, remedy

Network error: inbound

or

Network error: outbound

WebLogic Integration - Business Connect is unable to send or receive documents due to transport protocol or network problems.

Cause 1

The FTP or POP server is offline.

Remedy 1

Verify the status of the POP server or FTP server or both.

Cause 2

The local network is down.

Remedy 2

Verify the network status.

Cause 3

A firewall might be impeding document transport.

Remedy 3

Verify correct connectivity through the firewall for inbound and outbound documents.

Unable to send

WebLogic Integration - Business Connect cannot send documents due to transport protocol or network problems.

Cause 1

The SMTP or FTP server is offline.

Remedy 1

Verify the status of the SMTP or FTP server.

Cause 2

The local network or Internet connection is down.

Remedy 2

Verify the network status.

Cause 3

The partner's HTTPS server is offline.

Remedy 3

Contact the partner and verify the status of the HTTPS server.

Table 18-8 Level 6 Messages

Level 6 message	Description, cause, remedy
Active transport for partner has been disabled	The partner is no longer listening on the active transport. Cause 1 A partner profile has been electronically updated. In other words, your partner has switched from one transport to another for receiving documents. Remedy 1 Activate a new transport for the partner.
No active transport	WebLogic Integration - Business Connect attempted to send a document or MDN to a partner who does not have an active transport. Cause 1 You created or imported a partner profile, but did not activate a transport. Remedy 1 Activate a transport for the partner on the Partner Profile Transports tab.

Level 7 message	Description, cause, remedy
Any level 7 message	All of level 7 (unexpected exception) events indicate application bugs. Cause 1 Level 7 events indicate application bugs. Remedy 1 Report the events to technical support.

Table 18-10 Level 8 Messages

Level 8 message	Description, cause, remedy
Unable to create directory. Shutting down	Server attempted to create the necessary directories and failed. Cause 1 The directories are not set correctly. Remedy 1 Verify the directories in the company, partner and tools panels. Cause 2 The current user does not have write permission. Remedy 2 Verify the current user has write permission in the application install directory.


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

WebLogic Integration Doc Home \| B2B Topics \| Using WLI-BC \| Previous Topic \| Next Topic \| Contents \| Index \| View as PDF