Purpose: Use the Event Logging screen to configure the logging to take place for Order Broker.
Logging options: You can configure Order Broker to write logs for:
• Order Broker modules:
• errors only
• deletions only (deletion logging is available only for the user interface)
• detailed: all events are logged
• nothing
• Integrated Message Logging:
• errors only
• all messages
• nothing
Note: Typically, you would set the XML logging to capture all messages only for diagnostic purposes, as the log files can become quite large if they capture every message.
Email notifications: You can also use the Event Logging screen to specify the events that should trigger an email notification to the admin (cloud) user; the individual user who performed the action, such as an upload; both the admin user and the individual user; or not to trigger an email.
Note: See the System screen for information on specifying the email address to receive the Order Broker Polling Status Email.
Where are the logs located? Log files are typically located at /usr/share/apache-tomcat/logs where /usr/share/apache-tomcat/ is where Order Broker is installed.
Log retention days: The Server Logs setting in the Retention Settings section of the Tenant screen controls how many days to retain log files until they are eligible for deletion through a scheduled process.
How to display this screen: Select Event Logging from the Home Screen or from the Systems Menu.
Note: Only users with Event Logging authority can display this screen. See the Role Wizard for more information.
Field |
Description |
|---|---|
|
Important: See Additional Logging Setup, above, for information on additional required setup that controls the level of detail in the logs and whether to log activity in files, in the database, or both. |
|
Probability Rules |
Controls the logging to take place when applying probability rules to locate items requests and other activities that require evaluation of availability in a product location. Possible settings: • Detailed: Not currently implemented. • Errors only: write to the error.log file if probability rule evaluation results in an error. Default setting. • Nothing: do not update logs based on probability rule activity. See Probability Rule Overview for background. |
Location Product Import |
Controls the logging to take place when importing product and inventory information from an external system, including the incremental import program. Possible settings are: • Detailed: write errors to the error.log file, and write other updates to the server.log and application.log files when importing information. • Errors only: write to the error.log and server.log file only when an error occurs during imports. Do not write to the application.log file. Default setting. • Nothing: do not update logs based on product or product location import activity or the incremental import. See System Import Schedule and the Incremental Inventory Import for background. |
User Interface |
Controls the logging to take place for activity in the Order Broker user interface. If this field is set to: • Detailed: Creation, update, and deletion of records are logged. • Deletions: Deletions only are logged. • Errors Only: Errors only are logged. Default setting. • Nothing: No screen activity is logged. |
Order Broker Request/Response |
Controls the logging that is related to the Routing Engine request and response messages. Set this option to: • Everything: • update the xml.log file with XML messages and the json.log file with interactive inventory request messages. The availability service request messages are generated only when the Connection Type at the System screen is set to URL. • update the error log with incorrectly formed XML messages. • Errors Only: update the error log file with incorrectly formed XML messages and the json.log file with interactive inventory request errors, but do not update the xml.log file. Default setting. • Nothing: do not update any logs based on Routing Engine requests and responses. |
Controls the logging that is related to the Supplier Direct Fulfillment request and response XML messages. Set this option to: • Everything: • update the xml_ds.log file with all messages. • update the error log with incorrectly formed XML messages. • Errors Only: update the error log with incorrectly formed XML messages, but do not update the xml_ds.log file. Default setting. • Nothing: do not update the error log or the xml_ds.log files for XML messages. Note: This setting, rather than the Vendor Portal Request/Response setting, controls the logging of the launchDSOrders messages between Order Broker and the integrated vendor. Because these are XML messages, they are logged in the xml_ds.log file. |
|
Controls the logging that is related to communication between Order Broker and an integrated vendor that use JSON messages. Set this option to: • Everything: • update the json_ds.log file with JSON messages (getDSOrders, getDSShipConfirm, and setDSAcknowledge request and response messages). • update the error log with incorrectly formed JSON messages. • Errors Only: update the error log with incorrectly formed JSON messages, but do not update the json_ds.log file. Default setting. • Nothing: do not update the error log for integrated vendor messages. Note: The Drop Ship Request/Response setting, rather than this setting, controls the logging of the launchDSOrders messages, which are logged in the xml_ds.log file. |
|
Controls the logging that is related to the integrated shipping option in the Vendor Portal and Store Connect. Set this option to: • Everything: update the shipping_ds.log file with messages between Order Broker and the integrated shipping provider. • Errors Only: update the error log file with incorrectly formed messages, but do not update the shipping_ds.log file. Default setting. • Nothing: do not update the error log or the shipping_ds.log file for messages between Order Broker and the integrated shipping provider. |
|
Inventory Request/Response |
Controls the logging that is related to the availability update request and response. Set this option to: • Everything: update the inventory.log file with availability update request and response messages, and the error.log file with any errors such as an invalid request message. • Errors Only: update the error.log file with incorrectly formed messages, but do not update the inventory.log file. Default setting. • Nothing: do not update the error.log or the inventory.log file for availability update request and response messages. |
Proximity Data Load |
Controls the generation of email notifications when you upload proximity data through the Proximity Uploads screen. Possible settings: • Administrator: generate an email notification to the Administrative email. • User only: generate an email notification to the email specified at the User Profiles screen for the user who submitted the upload. • Admin and User: generate email notifications to the email specified at the for the user who submitted the upload and to the Administrative email. • Nothing: do not generate an email. Default setting. See Proximity Upload Status Email for more information. |
Controls the generation of email notifications when importing product, system product, product barcode, location, and product location information for an external system. Possible settings: • Administrator: generate an email notification to the Administrative email. Default setting. • Nothing: do not generate an email. See the Product Import Status Email for more information. |
|
User Interface |
Controls the email generation of email notifications for activity that takes place using the Order Broker user interface. Additional information will be provided by Oracle at a later date. |
Incremental Inventory Import |
Controls the generation of email notifications when the Incremental Inventory Import does not run successfully. Possible settings: • Administrator: generate an email notification to the Administrative email if Order Broker cannot retrieve updated inventory information. • Nothing: do not generate an email if Order Broker cannot retrieve inventory updates. Default setting. For more information: See the Incremental Inventory Import. |
The email address to receive notifications. You can enter multiple email addresses, separating each with a semicolon (;). Note: • Order Broker uses this email address, rather than the email address specified for the admin (cloud) user at the User Profiles screen. • If you do not specify an internal email address, contact your email systems administrator to reset your mail server configuration to enable Order Broker to generate emails to addresses outside your company domain. |
|
The “from” email address to appear on generated emails; this does not need to be an existing email address. |
|
SMTP Server |
The IP address or name of the email server. |
Mail User |
A valid user ID for the email server. Needed if your mail server requires user authentication. |
Mail Password |
The current password for the Mail User. Needed if your mail server requires user authentication. |
________________________________
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Legal
Notices