EventLogging

Event Logging

Purpose: Use the Event Logging screen to configure the logging to take place for Locate.

Logging options: You can configure Locate to write logs for:

• Locate 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 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 C:\Locate\server\logs where C:\ represents the default drive of your Locate server.

Additional Logging Setup

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.

Fields at this screen

Field	Description
Event Logging 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. Possible settings: • Detailed: • write to the application.log file whenever probability rules are evaluated for a locate items, submit order message, or change at the Order screen. • write to the error.log file if probability rule evaluation results in an error. • Errors only: write to the error.log file if probability rule evaluation results in an error. • 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 ecommerce update 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 product and product location information from an external system, including processing the ecommerce update. • Errors only: write to the error.log and server.log file only when an error occurs during product or product location import or the ecommerce update. Do not write to the application.log file. • Nothing: do not update logs based on product or product location import activity or the ecommerce update. See System Import Schedule and the Ecommerce tab of the System screen for background.
User Interface	Controls the logging to take place for activity in the Locate 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. • Nothing: No screen activity is logged.
Integrated Message Logging
Order Broker Request/Response	Controls the logging that is related to the Order Broker request and response messages. Set this option to: • Everything: • update the xml.log file with XML messages and the json.log file with availability service 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 availability request errors, but do not update the xml.log file. • Nothing: do not update any logs based on Order Broker requests and responses.
Drop Ship Request/Response	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. • 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 Locate and the integrated vendor. Because these are XML messages, they are logged in the xml_ds.log file.
Vendor Portal Request/Response	Controls the logging that is related to communication between Locate 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. • 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.
Integrated Shipping Request/Response	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 Locate 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. • Nothing: do not update the error log or the shipping_ds.log file for messages between Locate and the integrated shipping provider.
Email Notifications
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. See Proximity Upload Status Email for more information.
Location Product Import	Controls the generation of email notifications when importing product, inventory, and attribute information for an external system. Possible settings: • Administrator: generate an email notification to the Administrative email. • Nothing: do not generate an email. See the Product Import Status Email for more information.
User Interface	Not currently implemented.
Location Ecommerce Update	Controls the generation of email notifications when Locate cannot run a stored procedure over an external system’s database to retrieve updated inventory levels. Possible settings: • Administrator: generate an email notification to the Administrative email if Locate cannot retrieve updated inventory information. • Nothing: do not generate an email if Locate cannot retrieve inventory updates. For more information: See Location Inventory Updates for Ecommerce in the Operations Guide.
Email Settings
Administrative email	The email address to receive notifications. You can enter multiple email addresses, separating each with a semicolon (;). Note: • Locate uses this email address, rather than the email address specified for the admin 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 Locate to generate emails to addresses outside your company domain.
From Email	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.

________________________________