Field
Description
Settings
UI Timeout
The number of minutes that Locate should wait before timing out a user’s inactive session. When the session times out, the screen displays an error when the user next clicks an option or attempts to navigate in Locate, and needs to close the browser before logging back in to Locate.
Your entry can be 1 to 999 minutes. Required.
The default setting is 30 minutes.
Lock Out
The number of unsuccessful, sequential login attempts that triggers Locate to disable a user account. When a user attempts to log in with a disabled account, Locate displays a general error indicating that the login failed.
Example: If you set this number to 4, a user account is disabled after the entry of 4 incorrect passwords in a row.
Reset: A user’s counter is reset:
• after a successful login (for example, if there are 3 unsuccessful login attempts, followed by a successful login, the counter is reset to 0
• when you re-enable the account at the User Profiles screen or the User Profile Configuration screen
LDAP user? If the user is flagged for LDAP authentication, the lockout counter does not apply, and the user’s Locate user account is not disabled, even if the login attempts exceeds the Lock Out number; however, the user’s general LDAP authority may be suspended based on the general LDAP settings, which effectively locks the user out of Locate.
Your entry can be 1 to 99 login attempts. The default setting is 5. Required.
Select this option to be able to use the Order Broker and see related screens.
Required settings:
• If you select the Use Store Connect option but not this option, this option is selected automatically.
• Locate requires that at least this option or the Use Vendor Portal option are selected. If you don’t select any of the module use options, the Use Order Broker option is selected automatically.
See the Home Screen for information on screen access controlled by this setting.
Tenant Logo
The URL for the logo to display at the Store Connect login page at a size of 254 x 33 pixels.
Preview the logo: After entering the URL, click the preview icon (
) to preview the image at 254 x 33.
Select this option to be able to use the Store Connect module. This option also requires the Order Broker. If you select this option and don’t select Use Order Broker, the Use Order Broker option is selected automatically.
See the Home Screen for information on screen access controlled by this setting.
Account
The name of the Locate database. The destination specified in inbound XML messages must match this setting. The default setting is locate. Required.
Once you set the account, it should not ordinarily be changed.
Select this option to use the Drop Ship (Supplier Direct Fulfillment) module.
See the Home Screen for information on screen access controlled by this setting.
Email Settings
Email Template Path
The folder on the Locate server where email templates are stored. Optional, but required to generate emails to vendors, Store Connect locations, or staff.
The template path should not ordinarily be changed. Enter double backslashes (\\) to separate folders, such as C:\\Locate\\data\\emailtemplates. In a multi-server environment, the path might be \\\\SERVERNAME\\Locate\\data\\emailtemplates.
This field is available only when you run Locate on premises.
Email Interval
The number of minutes that Locate should wait before generating:
• an updated Order Broker Polling Status Email, providing a list of orders that have not yet been acknowledged by the assigned fulfilling location. Locate sends this email to the system’s System Ops Email address if:
• the system is flagged to Require Status Update, and
• there are any orders whose Poll Count exceeds the system’s Polling Retries setting
See Require Status Update for Assigned Orders? for a discussion.
• Supplier Direct Fulfillment notifications to the assigned vendor or the retailer. See Supplier Direct Fulfillment Module Email Notifications Summary for a listing.
• Store Connect notification emails to the assigned fulfilling store or to the customer. See the Store Connect Email Notifications Summary for a listing.
Up to 6 positions. The default setting is 15 minutes.
Note: If you set this interval to 0, no emails are generated.
Retention Settings
The following settings control the number of days to retain certain types of files on a server or records in the database.
If set to 0 days: If you set one of the following to 0 days, then all files or records are purged the day after creation.
Report Files
The number of days to retain records of generated reports. After this number of days, a time-based scheduler automatically deletes the database records, so it is no longer possible to print the reports. Can be from 0 to 30 days. Required.
The number of days to retain entries in log files on the server before a time-based scheduler automatically deletes them. Can be from 0 to 30 days. Required.
See the Clean Up Schedule setting for information on how log files are renamed or deleted.
This field is available only when you run Locate on premises.
Product Import Files
The number of days to retain product import files before a time-based scheduler automatically deletes them. Can be from 0 to 30 days. Required.
For more information: See Product, System Product and Product Location for background, and see RESTful Inventory and Product Messages in the Operations Guide for details.
Pack Slip Files
The number of days to retain pack slip records for purchase orders that have been shipped through the Vendor Portal. After this number of days, a time-based scheduler automatically deletes the database records, so it is no longer possible for the vendor to print the pack slips. Can be from 0 to 30 days. Required.
Note: This setting does not control the retention of pack slip records generated through Store Connect. Locate automatically deletes these database records shortly after they are generated; the store associate cannot reprint pack slips using these records.
Note: Used only by the Supplier Direct Fulfillment module.
The time of day to rename the previous day’s log files or to delete outdated files based on the retention settings, above. Twenty-four hour time, HH:MM format. The default setting is 01:00. Required.
Example: The Server Logs setting is 7 days, and the Clean Up Schedule is 01:00. At 01:00 each day, the cleanup job:
• Renames the previous day’s log files using a date stamp (for example, if the current date is 04/02/15, the previous day’s server log is renamed server.log.2015-04-02.
• Deletes any retained log files older than 7 days.
Multiple servers? In a multi-server environment, the cleanup job runs at the scheduled time on each server.
Note: The cleanup job can’t rename or delete any log file that is currently in use. In this case, it writes an error to the server.log: Log File delete failed.
Data Folder Settings
On premises only: The Data Folder Settings area is displayed and enterable only when Locate is running on premises.
Product Import Files
Indicates where to place the pipe-delimited files containing the product import information used when importing inventory, attribute, and product information through a RESTful web service. This must be a shared folder that is accessible to the server running the LocateRSR service. Used only if you import product information without direct database access. Once set, this should not ordinarily be changed.
Enter double backslashes (\\) to separate folders, such as C:\\Locate\\data\\ProductUploadData. If you use a shared Windows folder, preface the folders with four backslashes, such as \\\\SERVERNAME\\Locate\\ProductUploadData. Subfolders are:
• archive: Includes a copy of each processed file
• error: Includes a copy of each file in error
Optional, but required to run the product import through the RESTful web service.
For more information: See Product, System Product and Product Location for background, and see RESTful Inventory and Product Messages in the Operations Guide for details.
Proximity Upload Files
The folder on the Locate server where Locate places files you upload through the Proximity Uploads screen. You use this screen to upload the .CSV (comma-separated value) files. Once set, this should not ordinarily be changed.
Enter double backslashes (\\) to separate folders, such as C:\\Locate\\data\\ProximityUploadData.
Optional, but required to upload proximity data.
You need to create this folder on your Locate server before you can perform the upload at the Proximity Uploads screen.
Export Files
The folder on the Locate server where:
• Store Connect export: The Store Connect Inventory Export program writes the pipe-delimited file listing order lines recently fulfilled in Store Connect locations
• Ecommerce export: The ecommerce export writes a pipe-delimited file of updated product locations, including the probable quantity, when it receives a getAvailabilityBySystem request from the ecommerce system. See Location Inventory Updates for Ecommerce in the Operations Guide for more information.
Enter double backslashes (\\) to separate folders, such as C:\\Locate\\Data\\STC Export.
Optional, but required to export Store Connect inventory data, or to support the ecommerce export process through a pipe-delimited file rather than a stored procedure, such as in the cloud.
You need to create this folder before using either of the export options. If you use multiple servers:
• For the Store Connect inventory export, the folder needs to be on the server where you are working when you run the export.
• For the ecommerce export, the folder needs to be on the server from the endpoint used for the getAvailabilityBySystem request.
Miscellaneous Settings
ESB WSDL Location
The location of the wsdl that defines the launchDSOrders message used by an integrated vendor, such as http://SERVERNAME:8080/launchDSOrders/services/launchDSOrders?wsdl. This setting might be required for an integrated vendor if the retailer does not use a vendor integration created and configured by MICROS, because the launchDSOrders message is defined in a separate wsdl (web service description language), while the remaining integrated vendor messages use JSON, and are defined in a wadl (web application description language) on the Locate server.
Optional, but required to support integrated vendors.
Used only by the Supplier Direct Fulfillment module.